Aiee, Killing Interrupt Handler

Forum: Linux IP NAT Forum
Keywords: NAT Problem
Date: Thu, 29 Jan 1998 03:02:21 GMT
From: Bill Harris <bill@tradeweb.net>

I have several systems in production running NAT. Every now and then two of them lock up and this message gets dumped to the /var/log/messages file. Jan 29 05:25:29 trojan kernel: general protection: 0000 Jan 29 05:25:29 trojan kernel: CPU: 0 Jan 29 05:25:29 trojan kernel: EIP: 0010:[<0014e066>] Jan 29 05:25:29 trojan kernel: EFLAGS: 00010202 Jan 29 05:25:29 trojan kernel: eax: 6e657365 ebx: 0097a048 ecx: 00000002 e dx: 00000006 Jan 29 05:25:29 trojan kernel: esi: 6e657365 edi: 03f1c810 ebp: 0097a048 e sp: 001cf02c Jan 29 05:25:29 trojan kernel: ds: 0018 es: 0018 fs: 002b gs: 0018 ss: 0 018 Jan 29 05:25:29 trojan kernel: Process swapper (pid: 0, process nr: 0, stackpage =001cd1c8) Jan 29 05:25:29 trojan kernel: Stack: 0097a048 00000000 03f1c810 0097a048 000000 2a 0097a026 03f100ff 0013ffff Jan 29 05:25:29 trojan kernel: 0097ffff 001d0806 0097a01e 00000246 001370 02 00137e12 00000002 0097a048 Jan 29 05:25:29 trojan kernel: 0097a038 0d02a8c0 03f1c810 00149665 0097a0 48 03f1c810 00000000 03f1c810 Jan 29 05:25:29 trojan kernel: Call Trace: [<0013ffff>] [<00137002>] [<00137e12> ] [<00149665>] [<00138d00>] [<001486d7>] [<001485f8>] Jan 29 05:25:29 trojan kernel: [<001114d4>] [<00116b47>] [<0010a5bb>] [<0 01095ff>] [<00109653>] [<0010a635>] [<00109374>] [<00109200>] Jan 29 05:25:29 trojan kernel: [<001162e0>] [<00110a74>] Jan 29 05:25:29 trojan kernel: Code: 8a 06 89 c2 83 e2 0f 8d 3c 96 89 7c 24 2c 2 4 f0 3c 40 0f 85 Jan 29 05:25:29 trojan kernel: Aiee, killing interrupt handler Jan 29 05:25:29 trojan kernel: kfree of non-kmalloced memory: 001cf210, next= 03 f1c810, order=1852142437 Jan 29 05:25:29 trojan kernel: kfree of non-kmalloced memory: 001cf200, next= 03 f1c810, order=1852142437 Jan 29 05:25:29 trojan kernel: kfree of non-kmalloced memory: 001cf714, next= 03 f1c810, order=1852142437 Jan 29 05:25:29 trojan kernel: idle task may not sleep Jan 29 05:25:29 trojan last message repeated 4 times Jan 29 05:41:51 trojan kernel: general protection: 0000 Jan 29 05:41:51 trojan kernel: CPU: 0 Jan 29 05:41:51 trojan kernel: EIP: 0010:[<0014e066>] Jan 29 05:41:51 trojan kernel: EFLAGS: 00010202 Jan 29 05:41:51 trojan kernel: eax: 63634120 ebx: 0097a924 ecx: 00000002 e dx: 00000006 Jan 29 05:41:51 trojan kernel: esi: 63634120 edi: 001dc6dc ebp: 0097a924 e sp: 001cee44 Jan 29 05:41:51 trojan kernel: ds: 0018 es: 0018 fs: 002b gs: 0000 ss: 0 018 Jan 29 05:41:51 trojan kernel: Process swapper (pid: 0, process nr: 0, stackpage =001cd1c8) Jan 29 05:41:51 trojan kernel: Stack: 0097a924 00000000 01dc6dc 0097a924 000000 Jan 29 05:41:51 trojan kernel: 0097ffff 001d0806 0097a8fa 00000246 001370 02 00137e12 00000002 0097a924 Jan 29 05:41:51 trojan kernel: 0097a914 01a300d0 001dc6dc 00149665 0097a9 24 001dc6dc 00000000 0061b2b0 Jan 29 05:41:51 trojan kernel: Call Trace: [<0013ffff>] [<00137002>] [<00137e12> ] [<00149665>] [<0019b1c6>] [<00138d00>] [<00149848>] Jan 29 05:41:51 trojan kernel: [<00137ff0>] [<00116b47>] [<0010a5bb>] [<0 011572b>] [<00115a88>] [<0010abe3>] [<05000000>] [<04800000>] Jan 29 05:41:51 trojan kernel: [<00140018>] [<0010aff8>] [<0010afd0>] [<0 010a7c0>] Jan 29 05:41:51 trojan kernel: Code: 8a 06 89 c2 83 e2 0f 8d 3c 96 89 7c 24 2c 2 4 f0 3c 40 0f 85 Jan 29 05:41:51 trojan kernel: Aiee, killing interrupt handler Jan 29 05:41:53 trojan kernel: general protection: 0000 Jan 29 05:41:53 trojan kernel: CPU: 0 Jan 29 05:41:53 trojan kernel: EIP: 0010:[<0014e066>] Jan 29 05:41:53 trojan kernel: EFLAGS: 00010202 Jan 29 05:41:53 trojan kernel: eax: 69727020 ebx: 0097ae10 ecx: 00000002 e dx: 00000006 Jan 29 05:41:53 trojan kernel: esi: 69727020 edi: 001dc6dc ebp: 0097ae10 e sp: 001cec5c Any Thoughts are greatly appreciated. Bill@Tradeweb.Net

Messages Inline: Outline:

1. Similar Aiee problem by Dan Lasley, 1/29/98

2. version? by Michael J. Maravillo, 1/29/98

1. version info by Dan Lasley, 1/29/98

2. Which Version - 2,0.29 by Bill Harris, 1/29/98

3. How about that 2.0.33-patch? by Michael Hasenstein, 2/03/98

4. It may be another problem by Artur Pinheiro, 3/16/98