Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Quagga>
  3. Dev
kernel BUG
bp at dynastytech
Sep 8, 2003, 5:32 PM
Post #1 of 7 (1947 views)
Permalink
received this kernel BUG while shutting down a Soekris net4521 (ospfd was
running and the BUG mentioned ospfd...):

-bash-2.05b# shutdown -r now
INIT: Sending processes started by init the TERM signal
INIT: Sending all processes the TERM signal...
cardmgr[53]: exeScheduling in interrupt
cuting: './netwokernel BUG at sched.c:564!
invalid operand: 0000
CPU: 0
EIP: 0010:[<c0115a7b>] Not tainted
EFLAGS: 00010282
eax: 00000018 ebx: c11be280 ecx: 00000001 edx: 00000001
esi: c38a6000 edi: c38a6000 ebp: c38a7fa0 esp: c38a7f80
ds: 0018 es: 0018 ss: 0018
Process ospfd (pid: 85, stackpage=c38a7000)
Stack: c02d798a c38a6000 c38a6000 00000000 c38a6000 c11be280 c10b5200
c38a6000
00000000 c011b51d c38a6000 4018db4c 00000000 bffff85c c011b65f
00000000
c01071d3 00000000 00000001 00000000 4018db4c 00000000 bffff85c
00000001
Call Trace: [<c011b51d>] [<c011b65f>] [<c01071d3>]

Code: 0f 0b 34 02 82 79 2d c0 5a e9 1c fd ff ff 0f 0b 2d 02 82 79
<0>Kernel panic: Aiee, killing interrupt handler!

In interrupt handler - not syncing
<6>wlan0: SW TICK stuck? bits=0x0 EvStat=8000 IntEn=e09f
wlan1: SW TICK stuck? bits=0x0 EvStat=8000 IntEn=e09f
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan0: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
wlan1: SW TICK stuck? bits=0x0 EvStat=8080 IntEn=e018
Re: kernel BUG [ In reply to ]
syscow at EnterZone
Sep 8, 2003, 5:40 PM
Post #2 of 7 (1883 views)
Permalink
On Mon, 8 Sep 2003, Bubba Parker wrote:

> received this kernel BUG while shutting down a Soekris net4521 (ospfd was
> running and the BUG mentioned ospfd...):
>

OK. We know what hardware you're running... What OS? BSD? Linux? What?

Note: I suggest that you shut down routing processes prior to shutting
down network interfaces and the like. It would appear that you don't have
a shutdown script for your routing processes and instead, you're simply
letting your shutdown script send a kill -TERM to them whenever it
likes. Orderly shutdown will always make things easier to diagnose when
you have things like this happen.


---
John Fraizer | High-Security Datacenter Services |
President | Dedicated circuits 64k - 155M OC3 |
EnterZone, Inc | Virtual, Dedicated, Colocation |
http://www.enterzone.net/ | Network Consulting Services |
Re: kernel BUG [ In reply to ]
bp at dynastytech
Sep 8, 2003, 5:47 PM
Post #3 of 7 (1884 views)
Permalink
----- Original Message -----
From: "John Fraizer" <syscow@EnterZone.Net>
To: "Bubba Parker" <bp@dynastytech.com>
Cc: <quagga-users@lists.quagga.net>; <quagga-dev@lists.quagga.net>
Sent: Monday, September 08, 2003 19:40
Subject: Re: [quagga-dev 228] kernel BUG


>
> On Mon, 8 Sep 2003, Bubba Parker wrote:
>
> > received this kernel BUG while shutting down a Soekris net4521 (ospfd
was
> > running and the BUG mentioned ospfd...):
> >
>
> OK. We know what hardware you're running... What OS? BSD? Linux? What?
>
> Note: I suggest that you shut down routing processes prior to shutting
> down network interfaces and the like. It would appear that you don't have
> a shutdown script for your routing processes and instead, you're simply
> letting your shutdown script send a kill -TERM to them whenever it
> likes. Orderly shutdown will always make things easier to diagnose when
> you have things like this happen.
>
>
> ---
> John Fraizer | High-Security Datacenter Services |
> President | Dedicated circuits 64k - 155M OC3 |
> EnterZone, Inc | Virtual, Dedicated, Colocation |
> http://www.enterzone.net/ | Network Consulting Services |
>
>
>
>
>
Re: kernel BUG [ In reply to ]
bp at dynastytech
Sep 8, 2003, 5:48 PM
Post #4 of 7 (1894 views)
Permalink
sorry, last message had no message.

the OS I'm using (that encountered the BUG) is Linux (2.4.22).
Re: kernel BUG [ In reply to ]
in-quagga-dev at ib
Sep 8, 2003, 11:19 PM
Post #5 of 7 (1890 views)
Permalink
> Call Trace: [<c011b51d>] [<c011b65f>] [<c01071d3>]
> Code: 0f 0b 34 02 82 79 2d c0 5a e9 1c fd ff ff 0f 0b 2d 02 82 79

Please run this through ksymoops with correct System.map, as now this
report is useless - offsets indicated are specific to your kernel.


> <0>Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing

The fault happened in driver, but the cause for it might be somewhere else
- possibly messed up input queues.


Ignas
Re: kernel BUG [ In reply to ]
quagga at pccc
Sep 9, 2003, 2:42 AM
Post #6 of 7 (1889 views)
Permalink
Are you using HTB? I had a similar problem using HTB together with CIPE
tunnels. It was actually HTB causing the problem. disabling HTB solved
that problem (although it wasnt the perfect solution obviously). I was
using 2.4.20 and 2.4.21 kernels.

Paul




On Tue, 2003-09-09 at 08:19, Ignas Bagdonas wrote:
> > Call Trace: [<c011b51d>] [<c011b65f>] [<c01071d3>]
> > Code: 0f 0b 34 02 82 79 2d c0 5a e9 1c fd ff ff 0f 0b 2d 02 82 79
>
> Please run this through ksymoops with correct System.map, as now this
> report is useless - offsets indicated are specific to your kernel.
>
>
> > <0>Kernel panic: Aiee, killing interrupt handler!
> > In interrupt handler - not syncing
>
> The fault happened in driver, but the cause for it might be somewhere else
> - possibly messed up input queues.
>
>
> Ignas
>
> _______________________________________________
> Quagga-dev mailing list
> Quagga-dev@lists.quagga.net
> http://lists.quagga.net/mailman/listinfo/quagga-dev
Re: kernel BUG [ In reply to ]
bp at dynastytech
Sep 9, 2003, 9:10 AM
Post #7 of 7 (1884 views)
Permalink
Reading Oops report from the terminal
kernel BUG at sched.c:564!
kernel BUG at sched.c:564!
invalid operand: 0000
invalid operand: 0000
CPU: 0
EIP: 0010:[<c0115a7b>] Not tainted
EFLAGS: 00010282
CPU: 0
EIP: 0010:[<c0115a7b>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: 00000018 ebx: c11be280 ecx: 00000001 edx: 00000001
eax: 00000018 ebx: c11be280 ecx: 00000001 edx: 00000001
esi: c38a6000 edi: c38a6000 ebp: c38a7fa0 esp: c38a7f80
esi: c38a6000 edi: c38a6000 ebp: c38a7fa0 esp: c38a7f80
esi: c38a6000 edi: c38a6000 ebp: c38a7fa0 esp: c38a7f80
ds: 0018 es: 0018 ss: 0018
ds: 0018 es: 0018 ss: 0018
Process ospfd (pid: 85, stackpage=c38a7000)
Process ospfd (pid: 85, stackpage=c38a7000)
Stack: c02d798a c38a6000 c38a6000 00000000 c38a6000 c11be280 c10b5200
Stack: c02d798a c38a6000 c38a6000 00000000 c38a6000 c11be280 c10b5200
c38a6000
c38a6000
00000000 c011b51d c38a6000 4018db4c 00000000 bffff85c c011b65f
00000000
00000000 c011b51d c38a6000 4018db4c 00000000 bffff85c c011b65f
00000000
c01071d3 00000000 00000001 00000000 4018db4c 00000000 bffff85c
c01071d3 00000000 00000001 00000000 4018db4c 00000000 bffff85c
00000001
00000001
Call Trace: [<c011b51d>] [<c011b65f>] [<c01071d3>]
Call Trace: [<c011b51d>] [<c011b65f>] [<c01071d3>]

Code: 0f 0b 34 02 82 79 2d c0 5a e9 1c fd ff ff 0f 0b 2d 02 82 79
Code: 0f 0b 34 02 82 79 2d c0 5a e9 1c fd ff ff 0f 0b 2d 02 82 79


>>EIP; c0115a7b <schedule+31b/340> <=====

>>ebx; c11be280 <_end+e1d248/3848e028>
>>esi; c38a6000 <_end+3504fc8/3848e028>
>>edi; c38a6000 <_end+3504fc8/3848e028>
>>ebp; c38a7fa0 <_end+3506f68/3848e028>
>>esp; c38a7f80 <_end+3506f48/3848e028>

Trace; c011b51d <do_exit+14d/260>
Trace; c011b65f <sys_exit+f/10>
Trace; c01071d3 <system_call+33/40>

Code; c0115a7b <schedule+31b/340>
00000000 <_EIP>:
Code; c0115a7b <schedule+31b/340> <=====
0: 0f 0b ud2a <=====
Code; c0115a7d <schedule+31d/340>
2: 34 02 xor $0x2,%al
Code; c0115a7f <schedule+31f/340>
4: 82 (bad)
Code; c0115a80 <schedule+320/340>
5: 79 2d jns 34 <_EIP+0x34> c0115aaf
<__wake_up+f/60>
Code; c0115a82 <schedule+322/340>
7: c0 5a e9 1c rcrb $0x1c,0xffffffe9(%edx)
Code; c0115a86 <schedule+326/340>
b: fd std
Code; c0115a87 <schedule+327/340>
c: ff (bad)
Code; c0115a88 <schedule+328/340>
d: ff 0f decl (%edi)
Code; c0115a8a <schedule+32a/340>
f: 0b 2d 02 82 79 00 or 0x798202,%ebp

<0>Kernel panic: Aiee, killing interrupt handler!
<0>Kernel panic: Aiee, killing interrupt handler!

In interrupt handler - not syncing


----- Original Message -----
From: "Ignas Bagdonas" <in-quagga-dev@ib.sc.vu.lt>
To: "Bubba Parker" <bp@dynastytech.com>
Cc: <quagga-users@lists.quagga.net>; <quagga-dev@lists.quagga.net>
Sent: Tuesday, September 09, 2003 01:19
Subject: Re: [quagga-dev 228] kernel BUG


>
> > Call Trace: [<c011b51d>] [<c011b65f>] [<c01071d3>]
> > Code: 0f 0b 34 02 82 79 2d c0 5a e9 1c fd ff ff 0f 0b 2d 02 82 79
>
> Please run this through ksymoops with correct System.map, as now this
> report is useless - offsets indicated are specific to your kernel.
>
>
> > <0>Kernel panic: Aiee, killing interrupt handler!
> > In interrupt handler - not syncing
>
> The fault happened in driver, but the cause for it might be somewhere else
> - possibly messed up input queues.
>
>
> Ignas
>

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal