From: "Brad Parker" <parker@citynetwireless.net>
To: <linux-kernel@vger.kernel.org>
Subject: kernel BUG in sched.c
Date: Mon, 8 Sep 2003 19:38:50 -0500 [thread overview]
Message-ID: <007e01c3766a$bd0f8df0$6ff6d618@bp> (raw)
I got a kernel BUG mentioning the process ospfd (zebra/quagga routing
protocol daemon) while trying to "shutdown -r now", I already contaced the
quagga people, but I thought maybe this would be a kernel issue, so here
goes:
the machine is a Soekris net4521 (Elan SC520 cpu)
the output:
-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
next reply other threads:[~2003-09-09 0:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 0:38 Brad Parker [this message]
2003-09-09 17:39 ` kernel BUG in sched.c Mike Fedyk
2003-09-09 17:46 ` Brad Parker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='007e01c3766a$bd0f8df0$6ff6d618@bp' \
--to=parker@citynetwireless.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox