From: Christian Mautner <linux@mautner.ca>
To: linux-kernel@vger.kernel.org
Subject: kernel BUG at kernel/timer.c:380!
Date: Fri, 18 Jul 2003 22:25:25 -0400 [thread overview]
Message-ID: <20030719022525.GA18446@mautner.ca> (raw)
I have a very reproducible problem with 2.6.0-test1.
The system is a fairly recent installation of Debian Sarge.
Linux version 2.6.0-test1 (chm@data) (gcc version 3.3.1 20030626 (Debian prerelease)) #1 Thu Jul 17 18:03:58 EDT 2003
The hardware is a VIA board. Can't tell what exactly it is, it's not
mine. I have no manual.
vendor_id : CentaurHauls
cpu family : 6
model : 7
model name : VIA Ezra
stepping : 8
cpu MHz : 665.148
eth0, eth1, eth2: RealTek RTL8139 Fast Ethernet (8139too.c)
I am experimenting with the ethernet bridging code. I do:
% brctl addbr br0
% brctl stp br0 off
% brctl addif br0 eth1
% brctl addif br0 eth2
%
% ifconfig eth1 up
% ifconfig eth2 up
% ifconfig br0 up
At which point the kernel tells me:
--------------------------------------------------------------------------------
kernel BUG at kernel/timer.c:380!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c0126c6a>] Not tainted
EFLAGS: 00010007
EIP is at cascade+0x3e/0x48
eax: cc171074 ebx: cc171074 ecx: 00048600 edx: cf757e98
esi: c02fb850 edi: c02fb000 ebp: c035ff28 esp: c035ff1c
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, threadinfo=c035e000 task=c02f8420)
Stack: 00000000 c0396608 c035e000 c035ff58 c012736e c02fb000 c02fb820 00000006
c02f9ec0 c035ff40 c035ff40 c035ff68 00000001 c0396608 fffffffd c035ff74
c012283b c0396608 00000046 c035e000 c035e000 00000002 c035ff94 c010d6b1
Call Trace:
[<c012736e>] run_timer_softirq+0x316/0x3c8
[<c012283b>] do_softirq+0x9f/0xa4
[<c010d6b1>] do_IRQ+0x221/0x328
[<c0108a2c>] default_idle+0x0/0x30
[<c0105000>] _stext+0x0/0xd0
[<c010bbd4>] common_interrupt+0x18/0x20
[<c0108a2c>] default_idle+0x0/0x30
[<c0105000>] _stext+0x0/0xd0
[<c0108a52>] default_idle+0x26/0x30
[<c0108abd>] cpu_idle+0x29/0x3c
[<c03606b1>] start_kernel+0x1c5/0x224
Code: 0f 0b 7c 01 07 dd 2c c0 eb d7 0f bf 05 36 c0 2f c0 55 03 05
<0>Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing
--------------------------------------------------------------------------------
If I do the steps mentioned above in different order, e.g. ifconfig
eth[12] up first, then it might not happen. But if I do it exactly as
said, the bug happens reliably.
The .config is available at http://66.11.173.144/tmp/config-2.6.0-test1
everything else on request.
chm.
--
christian mautner -- chm bei istop punkt com -- ottawa, canada
next reply other threads:[~2003-07-19 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 2:25 Christian Mautner [this message]
2003-07-19 10:41 ` kernel BUG at kernel/timer.c:380! Steffen Klassert
2003-07-29 8:32 ` Andrew Morton
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=20030719022525.GA18446@mautner.ca \
--to=linux@mautner.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.