[Crash-utility] Re: [PATCH v1 0/3] ppc64: A few bug fixes for 6.x kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Tao,

On 22/09/24 22:22, Aditya Gupta wrote:
Hi Tao,

crash-utility works well for me on pp64le, with the patches applied.
Seems to cause some issues, for every swapper task, it shows all stack frames as '_end':

crash> bt
PID: 0        TASK: c00000000a9cff00  CPU: 5    COMMAND: "swapper/5"
 R0:  0000000000000000    R1:  c00000000aaa7d10    R2: c000000001c19000
 R3:  0000000000000000    R4:  0000000000000000    R5: 000000000000003a
 R6:  0000000000000000    R7:  0000010000000000    R8: ffffffffffffffbf
 R9:  0000000000000000    R10: 0000000000000000    R11: 0000000000000000
 R12: 0000000000000000    R13: c00000297fffa300    R14: 0000000000000000
 R15: 000000001ef111a0    R16: 0000000000000000    R17: 0000000000000000
 R18: 0000000000000000    R19: 0000000000000000    R20: 0000000000000000
 R21: 0000000000000000    R22: 0000000000000000    R23: 0000000000000001
 R24: 0000000000000005    R25: 0000000000000000    R26: 000002a07e5f19e2
 R27: 0000000000000000    R28: 0000000000000000    R29: 0000000000000001
 R30: c0000000021820a0    R31: c0000000021820a8
 NIP: c0000000000fabec    MSR: 800000000298b033    OR3: 000000000000011c
 CTR: 0000000000000000    LR:  c00000000115b9c8    XER: 0000000020040000
 CCR: 0000000022000202    MQ:  0000000000000000    DAR: 0000000000000000
 DSISR: 0000000000000000     Syscall Result: 0000000000000000
 [NIP  : plpar_hcall_norets_notrace+24]
 [LR   : check_and_cede_processor+72]
 #0 [c00000000aaa7d10] _end at c00000000aaa7d60  (unreliable)
 #1 [c00000000aaa7d60] _end at c00000000aaa7dc0  (unreliable)
 #2 [c00000000aaa7db0] _end at c00000000aaa7e60  (unreliable)


Checking why.


Thanks,

Aditya Gupta


Haven't done extensive testing to give a tested-by, but will try.


Overall looks good to me.


Thanks,

Aditya Gupta


On 18/09/24 05:12, Tao Liu wrote:
There are 3 bugs, which are caused due to newer kernel change, they were
found when testing the gdb stack unwinding support[1] for ppc64 against the
6.x kernels. See the discussion in [2][3]. So they'd better to be fixed
in a batch.

Note: the NO.1 patch: "ppc64: Fix bt printing error stack trace" was
posted individually in [4], and it gets updated in this patchset.
So please review this patchset instead.

[1]: https://www.mail-archive.com/devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx/msg01079.html [2]: https://www.mail-archive.com/devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx/msg01116.html [3]: https://www.mail-archive.com/devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx/msg01126.html [4]: https://www.mail-archive.com/devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx/msg01124.html

Tao Liu (3):
   ppc64: Fix bt printing error stack trace
   ppc64: check sp at the start of stack back trace
   ppc64: fix the bug eframe won't print for newer kernel

  defs.h  |   6 +++-
  ppc64.c | 110 +++++++++++++++++++++++++++++++++++++++++++++++++-------
  2 files changed, 102 insertions(+), 14 deletions(-)

--
Crash-utility mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxxxxxx
https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/
Contribution Guidelines: https://github.com/crash-utility/crash/wiki




[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux