Re: [tulip-bug] FreeBSD Problems with dc(4) ADMtek AN985 chip
Hi, This technique cannot be efficiently used with mbufs in *BSD, so there must be two different ring handling code paths: both chained and wrapped-ring configurations. Ok That's very likely a media selection problem, rather than a Rx descriptor problem. Of course resetting the chip will clear a descriptor hang, but that wouldn't be my first guess. It looks like you are right. I've seen two problems and they produced mixed results. 1.) TX underrun (FreeBSD specific) 2.) Media selection problem after small timeouts (cable problems) (Linux and FreeBSD) But why I don't see this in wind*** ? I run now this patch for two days (Enable automatically TX underrun recovery) http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34236 This patch fixed the problems that all connections got dropped. After have fixed this, I still had the connection problems, but the connections were still active. It looks now that the media selection does not work all the times. If the connection goes away for just a few moments 1/10sec or faster (maybe two times fery fast) the link stays broken even if the connection is there again 100%. If the connection is interrupted more than 5/10sec the link works again. My switch does still show a active link, and ifconfig does show it as active. It looks that some recovery function does not work as expected. How does this have to behave normally. Hardware bug (chip) or software bug ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
FreeBSD Problems with dc(4) ADMtek AN985 chip
Hi everybody, (I also wrote to the linux tulip list, maybe someone has encountered the bug in linux too as I do ?) My notebook has a Accton EN2242 network chip, which is integrated into a VIA PN133 chipset. I encounter serious connection problems as desribed in the manpage. I have to replug the cable over and over again till it works. And then the connection stays about some seconds and then it get wedged again. Unusable ... From a cold boot into Linux, is see the same symptoms as FreeBSD. Linux kernel 2.4.9-13 ... The windows driver seems to work :-( . From the FreeBSD dc manpage. The ADMtek AL981 chip (and possibly the AN985 as well) has been observed to sometimes wedge on transmit: this appears to happen when the driver queues a sequence of frames which cause it to wrap from the end of the transmit descriptor ring back to the beginning. The dc driver attempts to avoid this condition by not queuing any frames past the end of the transmit ring during a single invocation of the dc_start() routine. This workaround has a negligible impact on transmit performance. But this workaround seems not to work for me. For some reason, replugging the cable works for me, ifconfig (down/up) does not. Whe link always stays up, it is just the reciever queue with is wedged. Have other people the same problem with the dc driver ? If you own such a card here: Linksys EtherFast LNE100TX Accton EN2242 Please tell me your experiences. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD Problems with dc(4) ADMtek AN985 chip
Hi, The NIC is the external interface on my gateway. It was originally connected to an old HP 8-port 10bT hub and is now connected directly to a Westel DSL bridge. It has worked seemingly without problems handling the 768/128 DSL traffic. I say seemingly because I've never bothered to really push the NIC and I've never seen any link-level problems. 10 or 100 mbit with your Westel DSL bridge ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD Problems with dc(4) ADMtek AN985 chip
Martin Blapp wrote: Hi, The NIC is the external interface on my gateway. It was originally connected to an old HP 8-port 10bT hub and is now connected directly to a Westel DSL bridge. It has worked seemingly without problems handling the 768/128 DSL traffic. I say seemingly because I've never bothered to really push the NIC and I've never seen any link-level problems. 10 or 100 mbit with your Westel DSL bridge ? 10mbit half-duplex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD Problems with dc(4) ADMtek AN985 chip
Hi, I have a 100mbit full-duplex connection, maybe this is the difference ? 10mbit half-duplex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD Problems with dc(4) ADMtek AN985 chip
Martin Blapp wrote: Hi, I have a 100mbit full-duplex connection, maybe this is the difference ? 10mbit half-duplex Since the issue seems to be the sort where high amounts of traffic would be a triggering factor, it's quite possible. Give me 20 minutes or so and I'll go swap the interfaces around so the dc is on the inside connected to 100mbit/full and flood the link. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD Problems with dc(4) ADMtek AN985 chip
Darren Pilgrim wrote: Martin Blapp wrote: I have a 100mbit full-duplex connection, maybe this is the difference ? 10mbit half-duplex Since the issue seems to be the sort where high amounts of traffic would be a triggering factor, it's quite possible. Give me 20 minutes or so and I'll go swap the interfaces around so the dc is on the inside connected to 100mbit/full and flood the link. I swapped the NICs around and hammered the LNE100TX for at least 30 minutes straight. I didn't get any problems. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
