From owner-freebsd-current@FreeBSD.ORG Thu Apr 15 01:05:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B88116A4CE; Thu, 15 Apr 2004 01:05:48 -0700 (PDT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A2F843D41; Thu, 15 Apr 2004 01:05:46 -0700 (PDT) (envelope-from smckay@internode.on.net) Received: from dungeon.home (ppp167-147.lns1.bne3.internode.on.net [150.101.167.147])i3F85fZq038139; Thu, 15 Apr 2004 17:35:41 +0930 (CST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.12.8p2/8.11.6) with ESMTP id i3F85e0A029221; Thu, 15 Apr 2004 18:05:40 +1000 (EST) (envelope-from mckay) Message-Id: <200404150805.i3F85e0A029221@dungeon.home> To: "Crist J. Clark" References: <20040415061122.GA10883@blossom.cjclark.org> In-Reply-To: <20040415061122.GA10883@blossom.cjclark.org> from "Crist J. Clark" at "Thu, 15 Apr 2004 06:11:22 +0000" Date: Thu, 15 Apr 2004 18:05:40 +1000 From: Stephen McKay X-Mailman-Approved-At: Thu, 15 Apr 2004 05:13:22 -0700 cc: truckman@freebsd.org cc: current@freebsd.org cc: Stephen McKay Subject: Re: dc(4) Troubles 5.2.1 to CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Apr 2004 08:05:48 -0000 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.