[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153

--- Comment #17 from Leandro Lupori <luporl at FreeBSD.org> ---
I've tested dumping and inspecting the crashdump using r358813, on a POWER8 VM.
It worked fine.

These were the test commands and output:

# sysctl debug.kdb.panic=1
...
db> dump
Dumping 216 out of 8148 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
Dump complete
db> panic
panic: from debugger
...
(reboot)
...
Mar 11 15:53:08 fbsd2 savecore[534]: reboot after panic: kdb_sysctl_panic
Writing crash summary to /var/crash/core.txt.1.
...

# kgdb /boot/kernel/kernel /var/crash/vmcore.last
...
Unread portion of the kernel message buffer:                             
panic: kdb_sysctl_panic                                     
cpuid = 6                                                                       
time = 1583952756                                                               
KDB: stack backtrace:                                                           
0xe00000005758b030: at kdb_backtrace+0x60                                       
0xe00000005758b140: at vpanic+0x1e4                                             
0xe00000005758b1f0: at panic+0x40                         
0xe00000005758b220: at kdb_sysctl_panic+0xa4                                    
0xe00000005758b2a0: at sysctl_root_handler_locked+0x114                  
0xe00000005758b310: at sysctl_root+0x290                   
0xe00000005758b400: at userland_sysctl+0x174                          
0xe00000005758b520: at sys___sysctl+0x8c                                        
0xe00000005758b610: at trap+0x940                                               
0xe00000005758b750: at powerpc_interrupt+0x1b8                         
0xe00000005758b7e0: user SC trap by 0x8102b6110: srr1=0x800000000280f032        
            r1=0x3fffffffffffc300 cr=0x22800282 xer=0 ctr=0x8102b6100
r2=0x8102d2378 frame=0xe00000005758b8
10                                                                              
KDB: enter: panic                                                         

0xc000000000735e78 in doadump (textdump=16884644) at
/usr/src/sys/kern/kern_shutdown.c:393
393             savectx(&dumppcb);                              

(kgdb) bt                                                                   
#0  0xc000000000735e78 in doadump (textdump=16884644) at
/usr/src/sys/kern/kern_shutdown.c:393
#1  0xc000000000230394 in db_dump (dummy=<optimized out>, dummy2=<optimized
out>, dummy3=<optimized out>,
    dummy4=<optimized out>) at /usr/src/sys/ddb/db_command.c:575                
#2  0xc000000000230028 in db_command (last_cmdp=<optimized out>,
cmd_table=<optimized out>, dopager=0)
    at /usr/src/sys/ddb/db_command.c:482                                     
#3  0xc00000000022fcd8 in db_command_loop () at
/usr/src/sys/ddb/db_command.c:535
#4  0xc0000000002343fc in db_trap (type=<optimized out>, code=<optimized out>)
    at /usr/src/sys/ddb/db_main.c:253                
#5  0xc00000000079a548 in kdb_trap (type=<optimized out>, code=<optimized out>,
tf=0xc0000000010a5370)
    at /usr/src/sys/kern/subr_kdb.c:699                                 
#6  0xc000000000b8c6d8 in db_trap_glue (frame=<optimized out>) at
/usr/src/sys/powerpc/powerpc/trap.c:940
#7  <signal handler called>
#8  0xc000000000799758 in kdb_enter (why=0xc000000000eabdc0 "panic",
msg=<optimized out>)
    at /usr/src/sys/kern/subr_kdb.c:485                         
#9  0xc00000000073614c in vpanic (fmt=0xc000000000ea221f "kdb_sysctl_panic",
ap=<optimized out>)
    at /usr/src/sys/kern/kern_shutdown.c:902
...


Note that a recent gdb/kgdb is needed.

The 'ps -M' command worked too:

# ps aux -M /var/crash/vmcore.last                    
USER PID %CPU %MEM   VSZ  RSS TT  STAT STARTED    TIME COMMAND            
root   0  0.0  0.0     0    0  -  DLs  31Dec69 0:00.10 [kernel]           
root   1  0.0  0.0 11308 1108  -  DLs  31Dec69 0:00.02 [init]             
root   2  0.0  0.0     0    0  -  DL   31Dec69 0:00.00 [crypto]           
root   3  0.0  0.0     0    0  -  DL   31Dec69 0:00.00 [crypto returns 0] 
root   4  0.0  0.0     0    0  -  DL   31Dec69 0:00.00 [crypto returns 1]
root   5  0.0  0.0     0    0  -  DL   31Dec69 0:00.00 [crypto returns 2]
...
root 711  0.0  0.0 13456 3608  -  Ds   31Dec69 0:00.01 [login]
root 712  0.0  0.1 14828 4604  -  D    31Dec69 0:00.04 [csh]
root 715  0.0  0.0 12108 2456  -  R+   31Dec69 0:00.00 [sysctl]


The STARTED field is invalid, but the otherwise the command output seems
correct.

-- 
You are receiving this mail because:
You are the assignee for the bug.