From owner-freebsd-current Tue Oct 24 12: 3:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2B2D237B479 for ; Tue, 24 Oct 2000 12:03:38 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA00880; Tue, 24 Oct 2000 15:03:37 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e9OJ3bi12733; Tue, 24 Oct 2000 15:03:37 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 24 Oct 2000 15:03:36 -0400 (EDT) To: Motomichi Matsuzaki Cc: freebsd-current@freebsd.org Subject: Re: dc0: watchdog timeout In-Reply-To: <86hf62eovy.wl@tkc.att.ne.jp> References: <14836.62663.657129.698427@grasshopper.cs.duke.edu> <86hf62eovy.wl@tkc.att.ne.jp> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14837.56426.749643.769496@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Motomichi Matsuzaki writes: > > At Mon, 23 Oct 2000 22:46:26 -0400 (EDT), > Andrew Gallatin wrote: > > Anybody else seeing 'dc0: watchdog timeout' since SMPng integration? > > Yes I have. > > I have this several times before SMPng integration at a high load > situation. But, since the integration, it occurs frequently. I just switched out my tulip for an Intel EtherExpress Pro100B. I've had the machine sitting in a while 1 loop, rebuilding a debug kernel (which frequently triggered the dc0 watchdog reset). No problems after 3 hours, so I'm considering it "safe" It must be either a driver issue or something to do with tulips being sensative to not being serviced in a reasonable amount of time.. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message