Date: Tue, 09 Jul 2002 00:12:45 +1000 From: Stephen McKay <mckay@thehub.com.au> To: Martin Blapp <mb@imp.ch> Cc: hackers@freebsd.org, mckay@thehub.com.au Subject: Re: dc0: failed to force tx and rx to idle state Message-ID: <200207081412.g68ECjh16273@dungeon.home> In-Reply-To: <20020705100135.U41780-100000@levais.imp.ch> from Martin Blapp at "Fri, 05 Jul 2002 10:13:58 %2B0200" References: <20020705100135.U41780-100000@levais.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 5th July 2002, Martin Blapp wrote: >This problem still persists. On my Laptop a ACCTON MiniPCI >100Mbit card does make this output. Then I loose my network >connection. Only a ifconfig down/up of the interface helps. Are you running -current? I did a quick (but safe) hack in -stable hoping that people would test -current and report back. Nobody did. If you are running -current, I will be able to make the error message go away, but that will not solve any hang problem. The code really has no effect at all except to print a warning on some cards. The Linux driver for these cards has no wait for tx and rx idle at all, and just assumes the effect is instant. In practice this is so. Perhaps I should just remove this loop. If anyone is using -current with PNIC, Davicom, or Accton cards and the dc driver, please speak up. I'd like to squash this tiny bug. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207081412.g68ECjh16273>