Results 1 to 1 of 1
I'm having some difficulty tracking down a bug I have when a TCP connection is initialized. Specifically, I'm getting this error message when I try to start sshd: Code: Kernel ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 05-10-2011 #1
- Join Date
- May 2011
How to debbug crashes in interrupts?
I'm having some difficulty tracking down a bug I have when a TCP connection is initialized. Specifically, I'm getting this error message when I try to start sshd:
Kernel panic – not syncing: Fatal exception in interrupt Pid: 4261, comm: sshd Tainted: G D 2.6.36-r5-lttcp #33 Call Trace: panic+0x58/0x155 oops_end+0x8b/0x9a no_context+0x114/0x11e __bad_area_nosemaphore+0xe5/0xed bad_area_nosemaphore+0xd/0x10 do_page_fault+0x12b/0x270 ? do_page_fault+0x0/0x270 error_code+0x5a/0x60 ? do_page_fault+0x0/0x270 ? __sk_nulls_add_node_rcu+0x11/0x16 inet_hash+0x6e/0x8a inet_csk_listen_start+0x94/0xaf inet_listen+0x3c/0x60 sys_listen++0x47/0x5e sys_socketcall+0x91/0x1a3 sysenter_do_call+0x12/0x22
I'm a little confused as to what "?" means in this call trace.
I can't see my printk statements I've added to inet_hash() because the call trace is pushing them off the screen. Is there any way to get them written to disk? Are they being written to disk already, and if so, where? I also remember reading somewhere that printks wait until after an interrupt exits before they are written, which would mean I wouldn't see these printk statements anyways as it appears to be crashing in an interrupt. Is that correct?
I'm really just looking for any sort of debugging tips to help me get some more info about why its crashing here.
Thanks in advance,