[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: wm(4) issue/question
On Mar 2, 2010, at 11:09, Brian Buhrow wrote:
Hello. That message usually means the device isn't responding in a
timely manner, and the driver is resetting it. On the wm(4) cards, I
usually see it when the card has lost connectivity with the network
attached to, and when the machine is trying to transmit packets.
it's a fiber card, you might check to make sure autonegotiation is
fine, or just nail it up at 1000-baseSX. I submitted a number of
to make the nailing part work some years ago, and I believe those
are now a standard part of the driver.
I'll take a look for that the next time I try to attach it to the
If possible, look for errors on
the switch or router you're attached to and see if you're getting
connectivity drop outs. Perhaps you have a failing gbic or a bad
That's possible, but the parts are all new, so I don't expect that
would be the case. Sadly, it's a partially-managed switch, so I don't
have any real access to errors. Just status information through the
web U/I. The optical transmitter status showed okay, and I had link
lights. When I next try it, I'll verify that the link light is solid,
as well as trying what you suggested above.
Thanks for the pointers...
On Mar 2, 5:13pm, SAITOH Masanobu wrote:
} Subject: Re: wm(4) issue/question
} Hello, Chris.
} From: Chris Ross <cross+netbsd%distal.com@localhost>
} Subject: wm(4) issue/question
} Date: Sun, 28 Feb 2010 15:06:36 -0500
} > First of all, I want to point out that I don't presume this is
} > necessarily related to the wm(4) driver. But, it does involve
} > and I have an issue I don't understand. I'm hoping someone
} > the wm sources might be able to assist me.
} > I have an i386 router with a fiber Intel GigE card ("Intel
} > 1000BASE-X Ethernet, rev. 2"). This is connected to a SX GBIC
} > switch, and I'm running numerous 802.1q VLANs across it. This
} > working fine.
} I have a card which has the same chip.
} > I am trying to replace the 10/100 switches (with Gigabit GBIC
} > with full gigabit switches. I have a Dell 2724 with SX SFP's
} > and I tried connecting the i386 with wm(4) to one of them last
} > after trunking that new switch into the existing fabric.
} > I was getting 80% or more packet loss between my desktop and the
} > router (via one of it's many VLAN interfaces). I was,
} > attempt, seeing the following type message on the console of the
} > router:
} What NetBSD version are you running? Could you give me the full
} and ifconfig wm0 of your system?
} > wm0: device timeout (txfree 255 txsfree 63 txnext 6)
} > wm0: symbol error
} > wm0: device timeout (txfree 252 txsfree 62 txnext 64)
} > wm0: device timeout (txfree 252 txsfree 62 txnext 27)
} > wm0: device timeout (txfree 227 txsfree 41 txnext 121)
} > wm0: device timeout (txfree 249 txsfree 59 txnext 28)
} > wm0: device timeout (txfree 252 txsfree 62 txnext 10)
} > wm0: device timeout (txfree 255 txsfree 63 txnext 179)
} > So, my first question is, does anyone more familiar with the
} > driver have any sense what that message means, and what else I
} > look at/into to figure out what sort of problem this is?
} > Note, that I didn't try to pull everything into the new
} > cold, so things like ARP caches and such may still be involved
} > issue(s). But, this doesn't look like that sort of problem to
} > Thanks for any pointers or ideas anyone has...
} > - Chris
} I'll try to reproduce the bug.
} PR#40981 is a bug that device timeouts occur, but I suspect that
} different bug.
} SAITOH Masanobu (masanobu%iij.ad.jp@localhost
-- End of excerpt from SAITOH Masanobu
Main Index |
Thread Index |