I'm running the Debian 2.6.15 kernel from backports.org on a machine
with two Opteron 275s. I am getting a BUG in tg3.c quite reliably if I
ping flood the machine from a few others and cause a bit of other
network activity. Sometimes it takes a few minutes, sometimes half an
hour. The BUG also fires in more realistic situations - it just takes
longer to reproduce.
The machine has a Tyan S2882-D motherboard with dual BCM5704C network
interfaces. Only one is in use.
The Debian 2.6.15 version of tg.c seems to be identical to the one in
stock 2.6.15. It doesn't look like either of the two changes to tg3.c
in 2.6.16-rc1 are likely to be related to this.
I'm not subscribed to this list - please let me know if there is any
more information I can provide or if there are any patches you'd like
me to try.
TIA
Kernel BUG at drivers/net/tg3.c:2914
invalid operand: 0000 [1] SMP
CPU 3
Modules linked in: ipt_REJECT ip_tables nfsd nfs lockd nfs_acl sunrpc
autofs4 ipv6 megaraid dm_mod ide_disk joydev psmouse evdev i2c_amd756
hw_random i2c_amd811 1 serio_raw i2c_core pcspkr shpchp pci_hotplug
xfs exportfs ide_cd cdrom ide_generic sd_mod generic e100
megaraid_mbox scsi_mod amd74xx ohci_hcd mii tg3 megarai d_mm ide_core
thermal processor fan
Pid: 0, comm: swapper Not tainted 2.6.15-1-amd64-k8-smp #1
RIP: 0010:[<ffffffff88044459>] <ffffffff88044459>{:tg3:tg3_tx+59}
RSP: 0018:ffff8101044ffeb8 EFLAGS: 00010246
RAX: 0000000000000148 RBX: ffff8101fd93cec0 RCX: 0000000000000001
RDX: ffff8100f8bf8580 RSI: ffff810000011000 RDI: ffff8101044dc6d0
RBP: 0000000000000000 R08: ffff8100f7db21b8 R09: 0000000000000009
R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000148
R13: ffff8100f9fa0440 R14: 0000000000000000 R15: 0000000000000000
FS: 00002aaaaaf15090(0000) GS:ffffffff8040a980(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00002aaaaaac0000 CR3: 0000000000101000 CR4: 00000000000006e0
Process swapper (pid: 0, threadinfo ffff81000c058000, task ffff81000c052100)
Stack: ffff81000c058000 ffff8100f9f26000 ffff8100f9fa0440 ffff8100f9fa0000
ffff8101044fff2c 0000000000000000 ffff8101044fff88 ffffffff88044e08
ffff8100f9fa0000 ffff8100f9fa0000
Call Trace: <IRQ> <ffffffff88044e08>{:tg3:tg3_poll+98}
<ffffffff8026b009>{net_rx_action+172}
<ffffffff80135550>{__do_softirq+80} <ffffffff8010eaff>{call_softirq+31}
<ffffffff801103a0>{do_softirq+47} <ffffffff8011036a>{do_IRQ+50}
<ffffffff8010dd20>{ret_from_intr+0} <EOI>
<ffffffff802cd943>{thread_return+0}
<ffffffff8010b9ad>{default_idle+57} <ffffffff8010bbbc>{cpu_idle+93}
Code: 0f 0b 68 98 f2 04 88 c2 62 0b 49 8b 4d 40 8b 95 80 00 00 00
RIP <ffffffff88044459>{:tg3:tg3_tx+59} RSP <ffff8101044ffeb8>
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!
--
Mike Crowe
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
