On Tue, Jun 06, 2006 at 11:12:45AM +0200, Marco Berizzi wrote: > > I have moved this damn pc from the remote to my site and I have > placed it in production environment with 2.6.17-rc5 > No problem after 24 hours (on the remote side the problem was > arising after a couple of hours). I have modprobed 3c59x with > debug=4. I see only these kind of messages (are they fine?): > > Jun 5 14:31:25 Pleiadi kernel: eth2: vortex_error(), status=0x8081 > Jun 5 14:31:40 Pleiadi last message repeated 3 times > Jun 5 14:31:47 Pleiadi kernel: eth2: vortex_error(), status=0x8281 > Jun 5 14:31:47 Pleiadi kernel: eth2: Media selection timer tick happened, > Autonegotiate. > Jun 5 14:31:47 Pleiadi kernel: dev->watchdog_timeo=1250 > Jun 5 14:31:47 Pleiadi kernel: eth2: MII transceiver has status 782d. > Jun 5 14:31:47 Pleiadi kernel: eth2: Media selection timer finished, > Autonegotiate. > Jun 5 14:31:51 Pleiadi kernel: eth2: vortex_error(), status=0x8081 > Jun 5 14:32:03 Pleiadi last message repeated 2 times > Jun 5 14:32:10 Pleiadi kernel: eth2: vortex_error(), status=0x8481 > Jun 5 14:32:15 Pleiadi kernel: eth2: vortex_error(), status=0x8081 > Jun 5 14:32:46 Pleiadi last message repeated 7 times
This is ok, just normal operation of the NIC. > > The only relevant change, between the remote and my site, is a > different ethernet switch where the 3c905C is connected to. > Could it be an issue? Well, I think it can. Problems with a switch are mostly related to the autonegotiation of the media type and full/half-duplex. But in your case the autonegotiation seems to be ok (mii-tool/ethtool output). More specific information you can get with the mii-diag and vortex-diag tools. You can find these tools at http://www.scyld.com/ethercard_diag.html There are problems with a cisco switch documented in Documentation/networking/vortex.txt for example. Steffen - 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
