Strange panic on ppc64
Justin Hibbits
jhibbits at freebsd.org
Sat Jun 8 14:21:36 UTC 2013
On Wed, Jun 5, 2013 at 9:47 AM, Justin Hibbits <jhibbits at freebsd.org> wrote:
> Will do, when I get it panicking again.
>
> - Justin
> On Jun 5, 2013 9:46 AM, "Nathan Whitehorn" <nwhitehorn at freebsd.org> wrote:
>
>> On 06/04/13 22:35, Justin Hibbits wrote:
>>
>>> After a string of seemingly random hangs, I added invariants (but not
>>> witness) to my custom kernel config, and I get the following panic,
>>> recreated from a fuzzy cell phone picture:
>>>
>>>
>>> [thread pid -1 tid 1006665719 ]
>>> Stopped at 0: illegal instruction 0
>>> db> panic: mutex ohci1 owned at
>>> /usr/home/chmeee/freebsd/head/**sys/dev/usb/usb_transfer.c:**2280
>>> cpuid = 0
>>> Uptime: 9h8m1s
>>> <my dump code>
>>> ...
>>> panic: msleep1
>>> cpu = 0
>>> KDB: enter: panic
>>> [ thread pid -1 tid 100665719 ]
>>> ....
>>>
>>> The first question I have is how the hell it got such a strange PID/TID,
>>> memory corruption my guess, something is stomping on the pcpu or
>>> something,
>>> and I think these hangs have only happened since I added a lot more
>>> memory
>>> (up to 12G from 4G, Andreas Tobler was seeing hangs as well), so it might
>>> be something in the moea64 pmap code, but that's pure speculation on my
>>> part. Then the other panic messages, owned mutex and panic in msleep1.
>>> I
>>> enabled more trace code, so hopefully the next time it panics I can
>>> collect
>>> better data.
>>>
>>> - Justin
>>> ______________________________**_________________
>>> freebsd-ppc at freebsd.org mailing list
>>> http://lists.freebsd.org/**mailman/listinfo/freebsd-ppc<http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>
>>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@**freebsd.org<freebsd-ppc-unsubscribe at freebsd.org>
>>> "
>>>
>>
>> Could you post the output from show reg? It looks like it tried to jump
>> to a null pointer there.
>> -Nathan
>>
>
Well, it's hard to do get that output, because I just hit that 'mutex
owned' panic, and here's the backtrace:
Stopped at 0x102ca4: stdu r31, r1, 0xfd60,
db> panic: mutex ohci1 owned at
/usr/home/chmeee/freebsd/head/sys/dev/usb/usb_transfer.c:2280
cpuid = 0
KDB: stack backtrace:
0x0000000000a79c70: at .kdb_backtrace+0x5c
0x0000000000a79da0: at .vpanic+0x13c
0x0000000000a79e40: at .panic+0x38
0x0000000000a79ed0: at .__mtx_assert+0xdc
0x0000000000a79f50: at .usbd_callback_wrapper+0xd4
0x0000000000a79ff0: at .usb_command_wrapper+0x110
0x0000000000a7a070: at .usb_callback_proc+0x80
0x0000000000a7a100: at .usbd_transfer_poll+0x260
0x0000000000a7a1c0: at .ukbd_do_poll+0xd0
0x0000000000a7a250: at .ukbd_check+0x84
0x0000000000a7a2e0: at .ukbd_check_char+0xb4
0x0000000000a7a380: at .kbdmux_read_char+0x130
0x0000000000a7a420: at .scgetc+0xac
0x0000000000a7a4e0: at .sc_cngetc+0x7c
0x0000000000a7a580: at .cncheckc+0x74
0x0000000000a7a600: at .cngetc+0x28
0x0000000000a7a680: at .db_readline+0x88
0x0000000000a7a710: at .db_read_line+0x2c
0x0000000000a7a7a0: at .db_command_loop+0x58
0x0000000000a7a830: at .db_trap+0x148
0x0000000000a7ac00: at .kdb_trap+0x108
0x0000000000a7acb0: at .db_trap_glue+0x6c
0x0000000000a7ad30: at dbtrap+0x128
Uptime: 3d8h9m13s
- Justin
More information about the freebsd-ppc
mailing list