Subject: kern/29787: recurrent kernel panics on a i386 router with 2 wm nics
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Markus W Kilbinger <kilbi@rad.rwth-aachen.de>
List: netbsd-bugs
Date: 03/24/2005 20:21:00
>Number: 29787
>Category: kern
>Synopsis: recurrent kernel panics on a i386 router with 2 wm nics
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Mar 24 20:21:00 +0000 2005
>Originator: kilbi@rad.rwth-aachen.de
>Release: NetBSD 3.99.1
>Organization:
>Environment:
System: NetBSD radix 3.99.1 NetBSD 3.99.1 (RADIX) #3: Thu Mar 24 09:02:07 MET 2005 root@lw:/usr/src/sys/arch/i386/compile/RADIX i386
Architecture: i386
Machine: i386
>Description:
Since at least a week a i386 machine with 2 wm nics
wm0 at pci2 dev 10 function 0: Intel i82545EM 1000BASE-T Ethernet, rev. 1
wm0: interrupting at ioapic0 pin 22 (irq 5)
wm0: 32-bit 33MHz PCI bus
wm0: 256 word (8 address bits) MicroWire EEPROM
wm0: Ethernet address 00:07:e9:xx:xx:xx
makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
wm1 at pci2 dev 11 function 0: Intel i82545EM 1000BASE-T Ethernet, rev. 1
wm1: interrupting at ioapic0 pin 23 (irq 9)
wm1: 32-bit 33MHz PCI bus
wm1: 256 word (8 address bits) MicroWire EEPROM
wm1: Ethernet address 00:07:e9:yy:yy:yy
makphy1 at wm1 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
makphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
running nearly daily compiled -current kernels and acting as a
router (incl. ipf) panics recurrently (about 1 - 3 times a
day) with (different panic messages, sometimes no message):
hy0 at wm0 phy 1: Mm == 0, len 1
or
hy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev
or
panic: m_copym: m == 0, len 1 [!COPYALL]
or
panic: m_copydata: m == 0, len 1
Sometimes more parts of the nic's boot message are displayed
before rebooting!?
Sometimes even 'syncing disks... 2 done' succeeds!
For me this problem seems to be wm related, because in some
panic messages 'wm0' appears explicitly. We also have 2 other
i386 machine acting in a similar environment (routing) with
other nic's (ex , ti) which do not suffer from this problem.
Turning on/off hardware checksums does not influence this
problem.
>How-To-Repeat:
Setup a i386 machine with 2 wm nics as a router and use it. I
cannot specify specific network traffic to provoke this
problem.
>Fix:
n/a
>Unformatted: