Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Oct 2000 15:03:36 -0400 (EDT)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        Motomichi Matsuzaki <mzaki@e-mail.ne.jp>
Cc:        freebsd-current@freebsd.org
Subject:   Re: dc0: watchdog timeout
Message-ID:  <14837.56426.749643.769496@grasshopper.cs.duke.edu>
In-Reply-To: <86hf62eovy.wl@tkc.att.ne.jp>
References:  <14836.62663.657129.698427@grasshopper.cs.duke.edu> <86hf62eovy.wl@tkc.att.ne.jp>

next in thread | previous in thread | raw e-mail | index | archive | help

Motomichi Matsuzaki writes:
 > 
 > At Mon, 23 Oct 2000 22:46:26 -0400 (EDT),
 > Andrew Gallatin <gallatin@cs.duke.edu> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14837.56426.749643.769496>