Date: Thu, 15 Apr 2004 18:05:40 +1000 From: Stephen McKay <smckay@internode.on.net> To: "Crist J. Clark" <cristjc@comcast.net> Cc: Stephen McKay <smckay@internode.on.net> Subject: Re: dc(4) Troubles 5.2.1 to CURRENT Message-ID: <200404150805.i3F85e0A029221@dungeon.home> In-Reply-To: <20040415061122.GA10883@blossom.cjclark.org> from "Crist J. Clark" at "Thu, 15 Apr 2004 06:11:22 %2B0000" References: <20040415061122.GA10883@blossom.cjclark.org>
index | next in thread | previous in thread | raw e-mail
On Thursday, 15th April 2004, "Crist J. Clark" wrote: >It has been working alright in 5.2.1-R, but with CURRENT, I end up with, > > dc0: failed to force tx and rx to idle state This bit is my fault, at least to some extent. I changed some code to match the letter of the law, as far as real DEC/Intel 21143 chips see it. Unfortunately, various clones don't like it. It works fine for all the cards I have, of course. I'll probably get around to fixing this (maybe even deleting the whole section as in all tests I did a working card ran the loop exactly zero times), but until then it is a harmless message. > dc0: watchdog timeout This isn't my fault. Yay! :-) I'd guess interrupts aren't arriving, but have no idea why that would be. >Anyone else have this card and see this? Ideas about what may have changed? When I get time, I'll put a dc card in my -current box again. I put them all in the junk box when I got a few Intel pro 100 cards. They really are much better cards, and work well even in crappy old VIA boards. Stephen.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404150805.i3F85e0A029221>