| View previous topic :: View next topic |
| Author |
Message |
deanpence
Apprentice
Joined: 08 Nov 2004
Posts: 158
Location: Earth
|
 Posted: Thu Aug 25, 2005 3:52 pm Post subject: kernel panic - killing interrupt handler |
 |
|
I'm not sure where else to post this, but I thought some gentoo folks might be able to help.
I'm getting the following in syslog (via UDP) from one of our many machines running a 2.6.10 kernel (gentoo-sources):
| Code: | 2005-08-25 13:05:47 nypa088 [kern.warning]: ----------- [cut here ] --------- [please bite here ] ---------
2005-08-25 13:05:47 nypa088 [kern.alert]: Kernel BUG at tcp_output:922
2005-08-25 13:05:47 nypa088 [kern.emerg]: invalid operand: 0000 [1] SMP
2005-08-25 13:05:47 nypa088 [kern.warning]: CPU 0
2005-08-25 13:05:47 nypa088 [kern.warning]: Modules linked in:
2005-08-25 13:05:47 nypa088 [kern.warning]: Pid: 8692, comm: rmserver Not tainted 2.6.10-gentoo-r6
2005-08-25 13:05:47 nypa088 [kern.warning]: RIP: 0010:[<ffffffff8034a417>] <ffffffff8034a417>{tcp_retransmit_skb+615}
2005-08-25 13:05:47 nypa088 [kern.warning]: RSP: 0000:ffffffff8046ae68 EFLAGS: 00010202
2005-08-25 13:05:47 nypa088 [kern.warning]: RAX: 00000000000005a0 RBX: 00000100691030c0 RCX: 00000100f5ede640
2005-08-25 13:05:47 nypa088 [kern.warning]: RDX: 0000000000000000 RSI: 0000000000000388 RDI: 00000100e90f1440
2005-08-25 13:05:47 nypa088 [kern.warning]: RBP: 00000100faea8348 R08: 0000000000000000 R09: 0000000000000000
2005-08-25 13:05:47 nypa088 [kern.warning]: R10: 0000000000000000 R11: 0000000000000000 R12: 00000100337b5d80
2005-08-25 13:05:47 nypa088 [kern.warning]: R13: 00000100faea8040 R14: 00000000000005a0 R15: 0000000000000218
2005-08-25 13:05:47 nypa088 [kern.warning]: FS: 0000002a95c36b00(0000) GS:ffffffff804b4ac0(0000) knlGS:0000000000000000
2005-08-25 13:05:47 nypa088 [kern.warning]: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2005-08-25 13:05:47 nypa088 [kern.warning]: CR2: 0000000001cb03d8 CR3: 0000000000101000 CR4: 00000000000006e0
2005-08-25 13:05:48 nypa088 [kern.warning]: Stack: 000000000000000e ffffffff8013c75e 00100100cef02900 0000000000000001
2005-08-25 13:05:48 nypa088 [kern.warning]: 00000100faea8040 00000100faea8348 0000000000000008 00000100faea8078
2005-08-25 13:05:48 nypa088 [kern.warning]: 00000100faea80f8 ffffffff8034cbe8
2005-08-25 13:05:48 nypa088 [kern.warning]: Call Trace:<IRQ> <ffffffff8013c75e>{signal_wake_up+30} <ffffffff8034cbe8>{tcp_write_timer+1144}
2005-08-25 13:05:48 nypa088 [kern.warning]: <ffffffff8013ac8d>{__mod_timer+317} <ffffffff8034c770>{tcp_write_timer+0}
2005-08-25 13:05:48 nypa088 [kern.warning]: <ffffffff8013b10e>{run_timer_softirq+350} <ffffffff801373b1>{__do_softirq+113}
2005-08-25 13:05:48 nypa088 [kern.warning]: <ffffffff80137465>{do_softirq+53} <ffffffff8010dc4f>{apic_timer_interrupt+99}
2005-08-25 13:05:48 nypa088 [kern.warning]: <EOI> <ffffffff8010d406>{system_call+126}
2005-08-25 13:05:48 nypa088 [kern.warning]:
2005-08-25 13:05:48 nypa088 [kern.warning]: Code: 0f 0b a0 e7 3c 80 ff ff ff ff 9a 03 49 8b 44 24 10 4c 63 f6
2005-08-25 13:05:48 nypa088 [kern.alert]: RIP <ffffffff8034a417>{tcp_retransmit_skb+615} RSP <ffffffff8046ae68>
2005-08-25 13:05:48 nypa088 [kern.warning]: <0>Kernel panic - not syncing: Aiee, killing interrupt handler! |
|
|
| Back to top |
|
 |
dementer
Tux's lil' helper
Joined: 25 Jan 2004
Posts: 139
Location: New Zealand
|
| Posted: Thu Aug 25, 2005 9:19 pm Post subject: |
|
|
Well the top of that log says its caused by a bad operand in the SMP component. Was this kernel compiled specifically for/on this machine? You could try recompiling the kernel without SMP support and see if you still get the same problem. Id sugest a bug report if that turned out to be the case, but 2.6.10 is quite old now.
If you decide to recompile your kernel, why not upgrade to a newer version. 
If you still get this (which I doubt but anything is pos.) then try changing the preempt setting and/or disabling preempt kernel-biglock |
|
| Back to top |
|
|
deanpence
Apprentice
Joined: 08 Nov 2004
Posts: 158
Location: Earth
|
| Posted: Sat Aug 27, 2005 4:12 am Post subject: |
|
|
| dementer wrote: | | Well the top of that log says its caused by a bad operand in the SMP component. Was this kernel compiled specifically for/on this machine? |
Well, it was compiled specifically for this motherboard. We have about 200 very homogenous machines; some are multiproc; some are not; but all run the same architecture and motherboard.
| dementer wrote: | | You could try recompiling the kernel without SMP support and see if you still get the same problem. Id sugest a bug report if that turned out to be the case, but 2.6.10 is quite old now. |
I would love to upgrade, and I have in new machines, but our machines run high-availability (i.e., 100% uptime), high-demand, proprietary server applications, and though I'm the sysadmin, I'm not allowed to make any significant changes (like the kernel version)--especially ones that bring machines down entirely--without a very detailed and foolproof plan, which I am working on.
| dementer wrote: | If you decide to recompile your kernel, why not upgrade to a newer version.
If you still get this (which I doubt but anything is pos.) then try changing the preempt setting and/or disabling preempt kernel-biglock |
Thanks for the tip. I may try it. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
