On Fri, Feb 10, Olaf Hering wrote:

> I have seen this kind of error every once in a while on my G4/450 Mac.
> 
> 
> Linux version 2.6.13-20050921064541-default ([EMAIL PROTECTED]) (gcc version 
> 4.0.2 20050901 (prerelease) (SUSE Linux)) #1 Wed Sep 21 06:45:41 UTC 2005
> 
> sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
> PHY ID: 406212, addr: 0
> eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0a:27:e2:f3:3e 
> eth0: Found BCM5201 PHY
> eth0: Link is up at 100 Mbps, full-duplex.

> 86days uptime.
> 
> Feb 10 10:28:24 nectarine kernel: eth0: RX MAC fifo overflow smac[03810400].
> Feb 10 10:28:24 nectarine last message repeated 3 times
> Feb 10 10:28:24 nectarine kernel: eth0: RX MAC fifo overflow smac[00810400].

A G5 one the same switch had the same trouble, but no slab corruption.

Feb 10 10:24:42 mac -- MARK --
Feb 10 10:28:25 mac kernel: gem: RX MAC fifo overflow smac[00910440].
Feb 10 10:28:26 mac kernel: gem: RX MAC fifo overflow smac[00810440].
Feb 10 10:44:42 mac -- MARK --

sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
PHY ID: 2062e0, addr: 1
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0a:95:a6:5d:66 
eth0: Found BCM5421-K2 PHY
tg3.c:v3.49 (Feb 2, 2006)
PCI: Enabling device: (0001:06:03.0), cmd 6
gem: Link is up at 100 Mbps, full-duplex.
eth0: Tigon3 [partno(3C996B-T) rev 0105 PHY(5701)] (PCI:33MHz:64-bit) 
10/100/1000BaseT Ethernet 00:04:76:f3:c2:4f
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[0] 
eth0: dma_rwctrl[76ff2d0f]
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): bcm: link is not ready
gem: Link is up at 100 Mbps, full-duplex.
gem: Pause is enabled (rxfifo: 10240 off: 7168 on: 5632)

Linux version 2.6.16-rc2-git2-6-ppc64 ([EMAIL PROTECTED]) (gcc version 4.1.0 
20060201 (prerelease) (SUSE Linux)) #1 SMP Wed Feb 8 02:56:22 UTC 2006



-- 
short story of a lazy sysadmin:
 alias appserv=wotan
-
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

Reply via email to