Toby DiPasquale on 30 Mar 2007 00:03:11 -0000 |
On Wed, Mar 28, 2007 at 10:45:41AM -0400, Chad Waters wrote: > On 3/28/07, Marc Zucchelli <X> wrote: > >I was not able to ping my server this morning. I sent a reboot request to > >the datacenter. Unsure of where to begin investigating, I looked in > >/var/log/messages and I see these lines over and over again: > > > >Mar 28 00:32:53 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out > >Mar 28 00:32:53 localhost kernel: tg3: eth0: Link is down. > >Mar 28 00:32:55 localhost kernel: tg3: eth0: Link is up at 10 Mbps, full > >duplex. > >Mar 28 00:32:55 localhost kernel: tg3: eth0: Flow control is off for TX and > >off for RX. > >Mar 28 00:42:02 localhost kernel: APIC error on CPU0: 40(40) > > > >Has anybody seen this before? Would this be the reason I wasn't able to > >ping the server? What is Netdev Watchdog? What could be causing this > >problem? What do I need to do to get to the bottom of it and fix the > >underlying problem? > > > >Separatly, I am seeing the APIC error on CPU0: 40(40) message every few > >hours up until the beginning of the /var/log/messages file, which is March > >25th. The server has been up since then, I'm sure that message isn't a big > >deal, or is it? > > Are you expecting a 10Mbs connection speed? There maybe some link > negotiation mismatch. I agree. I've seen this when the autonegotiation is going haywire. Try locking the NIC to the correct speed and duplex with ethtool or mii-tool and periodically checking for the return of these messages. -- Toby DiPasquale ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|