Interrupt problems causing crash of network driver and Kernel panic?

Adam Lackorzynski adam at os.inf.tu-dresden.de
Sun Feb 7 23:50:38 CET 2010


On Thu Jan 28, 2010 at 14:33:43 +0100, Andreas Speier wrote:
> The main hardware components are an embedded board with 1GHz VIA C7
> processor, 1GB of RAM and 2 network interface cards (VIA-Rhine, 3Com).
> The drivers are compiled into the L4Linux kernel.
> 
> Running this application works fine until some more interrupt intensive
> process will be started. Then the VoIP communication (SIP) breaks down
> and I got the following output in /var/log/syslog:
> 
> #################
> Jan 28 08:24:58 TESTPC kernel: ------------[ cut here ]------------
> Jan 28 08:24:58 TESTPC kernel: kernel BUG at
> /home/[...]/l4linux-2.6.29/net/core/dev.c:2625!
> Jan 28 08:24:58 TESTPC kernel: Trap: 6: 0000 [#1]
> Jan 28 08:24:58 TESTPC kernel: last sysfs file:
> Jan 28 08:24:58 TESTPC kernel: Modules linked in:
> Jan 28 08:24:58 TESTPC kernel:
> Jan 28 08:24:58 TESTPC kernel: Pid: 872, comm: find Not tainted
> (2.6.29-l4 #3)
> Jan 28 08:24:58 TESTPC kernel: EIP: ff04:[<0063c5bf>] EFLAGS: 00010246
> CPU: 0
> Jan 28 08:24:58 TESTPC kernel: EIP is at __napi_complete+0x2f/0x40
> Jan 28 08:24:58 TESTPC kernel: EAX: 0092d45c EBX: 0092d45c ECX: 0092d45c
> EDX: 008aa40c
> Jan 28 08:24:58 TESTPC kernel: ESI: 00000001 EDI: 0092d45c EBP: b0afff14
> ESP: b0afff0c
> Jan 28 08:24:58 TESTPC kernel: DS: 4000 ES: 7032 FS: 0023 GS: 0043 SS: 0023
> Jan 28 08:24:58 TESTPC kernel: Process find (pid: 872, ti=b0afe000
> task=0a5391b0 task.ti=0a564000)
> Jan 28 08:24:58 TESTPC kernel: Stack:
> Jan 28 08:24:58 TESTPC kernel: b0afff14 eacff011 b0afff24 0063dd25
> 0092d444 00000001 b0afff40 00640473
> Jan 28 08:24:58 TESTPC kernel: 00000040 000107b2 00000040 00000000
> 0092d45c b0afff5c 006404ca 000107b4
> Jan 28 08:24:58 TESTPC kernel: 0000012c 00000001 0000000c 00000100
> b0afff74 0041afe7 0000000a 00000000
> Jan 28 08:24:58 TESTPC kernel: Call Trace:
> Jan 28 08:24:58 TESTPC kernel: [<0063dd25>] ? napi_complete+0x25/0x40
> Jan 28 08:24:58 TESTPC kernel: [<00640473>] ? process_backlog+0x93/0xa0
> Jan 28 08:24:58 TESTPC kernel: [<006404ca>] ? net_rx_action+0x4a/0x100
> Jan 28 08:24:58 TESTPC kernel: [<0041afe7>] ? __do_softirq+0x67/0x100
> Jan 28 08:24:58 TESTPC kernel: [<0040bb05>] ? do_softirq+0x55/0x60
> Jan 28 08:24:59 TESTPC kernel: [<0041af15>] ? irq_exit+0x35/0x40
> Jan 28 08:24:59 TESTPC kernel: [<0040ba75>] ? do_IRQ+0x35/0x70
> Jan 28 08:24:59 TESTPC kernel: [<00523ad5>] ? irq_dev_thread+0xf5/0x190
> Jan 28 08:24:59 TESTPC kernel: Code: e5 f6 40 08 01 74 24 8b 40 20 85 c0
> 75 21 8b 11 8b 41 04 89 42 04 89 10 c7 41 04 00 02 20 00 c7 01 00 01 10
> 00 80 61 08 fe 5d c3 <0f> 0b eb fe 0f 0b eb fe 89 f6 8d bc 27 00 00 00
> 00 55 ba d0 00

Hmm, I'm afraid that could be a bug. Is that (well) reproducible?



Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/




More information about the l4-hackers mailing list