Well, debug information didn't seem to have any positive effect. Here are the
additional configure parameters I turned on:
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_INFO=y
CONFIG_FRAME_POINTER=y
Let me know if I'm missing something or need to turn on additional parameters.
Also, please note that this crash never seemed to end! It kept hitting
breakpoints! Here are the start of the messages:
myserver:~#
Program received signal SIGSEGV, Segmentation fault.
0x0806b21f in chan_interrupt ()
(gdb) bt
#0 0x0806b21f in chan_interrupt ()
#1 0x00000000 in ?? ()
(gdb) c
Continuing.
Breakpoint 1, 0x0807d0c0 in panic ()
(gdb) bt
#0 0x0807d0c0 in panic ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0807d0c4 in panic ()
(gdb) bt
#0 0x0807d0c4 in panic ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0807d0cb in panic ()
(gdb) bt
#0 0x0807d0cb in panic ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0818fdd0 in bust_spinlocks ()
(gdb) bt
#0 0x0818fdd0 in bust_spinlocks ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0818fdd3 in bust_spinlocks ()
(gdb) bt
#0 0x0818fdd3 in bust_spinlocks ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0818fdd7 in bust_spinlocks ()
(gdb) bt
#0 0x0818fdd7 in bust_spinlocks ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0818fddb in bust_spinlocks ()
(gdb) bt
#0 0x0818fddb in bust_spinlocks ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0818fddd in bust_spinlocks ()
(gdb) bt
#0 0x0818fddd in bust_spinlocks ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0818fddf in bust_spinlocks ()
(gdb) bt
#0 0x0818fddf in bust_spinlocks ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0818fde4 in bust_spinlocks ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0818fdea in bust_spinlocks ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0818fdee in bust_spinlocks ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0818fdf1 in bust_spinlocks ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0807d0d0 in panic ()
(gdb)
I eventually killed the process. It never actually reached the previous error
message. Also, this crash occurred a few seconds after I had finished typing my
last command (ls -l /etc/network/).
Tony
>>> "Anthony Brock" <[EMAIL PROTECTED]> 05/03/05 08:16AM >>>
Hmmm, I think I need to recompile the kernel with debug information. In any
case, here are the results:
myserver:~#
Program received signal SIGSEGV, Segmentation fault.
0x0806b21f in chan_interrupt ()
(gdb) bt
#0 0x0806b21f in chan_interrupt ()
#1 0x00000000 in ?? ()
(gdb) c
Continuing.
Kernel panic - not syncing: Kernel mode fault at addr 0xd, ip 0x0
EIP: 0000:[<00000000>] CPU: 0 Not tainted EFLAGS: 00000000
Not tainted
EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000
ESI: 00000000 EDI: 00000000 EBP: 00000000 DS: 0000 ES: 0000
Call Trace:
08297338: [<0808c30d>] notifier_call_chain+0x2d/0x50
08297348: [<0818fe16>] bust_spinlocks+0x46/0x50
08297358: [<0807d131>] panic+0x71/0x120
08297378: [<08066997>] segv+0x217/0x250
082973d8: [<08064eb5>] change_signals+0x65/0x90
08297468: [<08066cb7>] segv_handler+0xd7/0xe0
08297488: [<080697f0>] sig_handler_common_skas+0x90/0xe0
082974b8: [<08075e87>] sig_handler+0x17/0x20
08297508: [<0806b21f>] chan_interrupt+0xf/0x130
08297530: [<08064f70>] enable_mask+0x50/0x70
08297550: [<08064fc3>] get_signals+0x33/0x50
082975b0: [<0806505d>] set_signals+0x7d/0x130
08297620: [<0806505d>] set_signals+0x7d/0x130
082976b0: [<0806505d>] set_signals+0x7d/0x130
08297710: [<0806505d>] set_signals+0x7d/0x130
08297740: [<08064eb5>] change_signals+0x65/0x90
082977d0: [<0806b85f>] line_interrupt+0x2f/0x40
082977f0: [<08099900>] handle_IRQ_event+0x30/0x80
08297820: [<080999f8>] __do_IRQ+0xa8/0xf0
08297840: [<0805fea3>] do_IRQ+0x33/0x50
08297850: [<0806004a>] sigio_handler+0xda/0x140
08297870: [<080697f0>] sig_handler_common_skas+0x90/0xe0
08297894: [<080690e0>] start_kernel_proc+0x0/0x40
0829789c: [<08068cc0>] new_thread_handler+0x0/0x120
082978a0: [<08075e87>] sig_handler+0x17/0x20
082978cc: [<080690e0>] start_kernel_proc+0x0/0x40
082978d0: [<08068cc0>] new_thread_handler+0x0/0x120
08297a40: [<08068937>] switch_threads+0x87/0x90
08297a70: [<08064eb5>] change_signals+0x65/0x90
08297b10: [<08064f0f>] unblock_signals+0xf/0x20
08297b20: [<080799e7>] finish_task_switch+0x27/0x70
08297b40: [<08244353>] schedule+0x2e3/0x4e0
08297b90: [<08065e93>] idle_sleep+0x23/0x30
08297bac: [<08068cc0>] new_thread_handler+0x0/0x120
08297bb0: [<08062f37>] default_idle+0x67/0x70
08297bd0: [<080690d8>] init_idle_skas+0x28/0x30
08297bd4: [<0805f210>] init+0x0/0x110
08297be0: [<080495b3>] start_kernel+0x163/0x1a0
08297bf4: [<08049130>] unknown_bootoption+0x0/0x200
08297c00: [<0806910b>] start_kernel_proc+0x2b/0x40
08297c04: [<080690e0>] start_kernel_proc+0x0/0x40
08297c10: [<08062978>] run_kernel_thread+0x78/0x80
08297c28: [<080690e0>] start_kernel_proc+0x0/0x40
08297c30: [<08068cc0>] new_thread_handler+0x0/0x120
08297c38: [<08062940>] run_kernel_thread+0x40/0x80
08297cd4: [<080690e0>] start_kernel_proc+0x0/0x40
08297cdc: [<08068cc0>] new_thread_handler+0x0/0x120
08297ce0: [<08068d8e>] new_thread_handler+0xce/0x120
08297ce4: [<080690e0>] start_kernel_proc+0x0/0x40
08297d40: [<08068cc0>] new_thread_handler+0x0/0x120
Program exited with code 01.
(gdb)
>>> Jeff Dike <[EMAIL PROTECTED]> 05/02/05 08:13PM >>>
[EMAIL PROTECTED] said:
> Is this your "stack trace"?
Close. What I'd really like is to get it to crash when it's running under
gdb, with a breakpoint on panic. Then, 'bt' to gdb at that point.
That gives the true call trace, plus line number information.
> 08297488: [<080697f0>] sig_handler_common_skas+0x90/0xe0
> 082974b8: [<08075e87>] sig_handler+0x17/0x20
> 08297508: [<0806b21f>] chan_interrupt+0xf/0x130
> 08297530: [<08064f70>] enable_mask+0x50/0x70
This tells me that chan_interrupt segfaulted, but not necessarily exactly
where, and a lot of the other stuff on the stack isn't in the true call
chain.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
