From owner-freebsd-stable Mon Mar 5 22:17:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from poontang.schulte.org (poontang.schulte.org [209.134.156.197]) by hub.freebsd.org (Postfix) with ESMTP id DBC4137B719 for ; Mon, 5 Mar 2001 22:17:24 -0800 (PST) (envelope-from christopher@schulte.org) Received: from TARMAP.schulte.org (tarmap.schulte.org [209.134.156.198]) by poontang.schulte.org (8.9.3/8.9.3) with ESMTP id AAA20491; Tue, 6 Mar 2001 00:17:22 -0600 (CST) (envelope-from christopher@schulte.org) Message-Id: <5.0.2.1.0.20010306001037.00aecaf0@pop.schulte.org> X-Sender: schulte@pop.schulte.org X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 06 Mar 2001 00:16:16 -0600 To: "Todd Punderson" , From: Christopher Schulte Subject: Re: Problem with 4.2-STABLE and dc0 In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Same problem here, installworld and install installkernel just after freeze. Card is a Linksys LNE 100-TX. dc0: failed to force tx and rx to idle state Last CVSUP was December-ish, so that's not going to help any. ;p The card still works; I can login just fine and no apparent (as of yet) problems with throughput or such. At 01:09 AM 3/6/2001 -0500, Todd Punderson wrote: >I just cvsup'ed 11pm EST 3/5/01. After I heard that stable was locked >thinking all would be well....Well, I now get this message repeated many >times: > >dc0: failed to force tx and rx to idle state > >The card is a Netgear FA310TX. It was fine before I did this update. The >last cvsup I ran was appx. 2 weeks ago (around 2/24.) Hopefully that will >let you pin down where the program crept in. >Thanks! >Todd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message