Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Apr 1999 20:32:51 -0300 (ADT)
From:      The Hermit Hacker <scrappy@hub.org>
To:        Paul Saab <paul@mu.org>
Cc:        Bill Paul <wpaul@skynet.ctr.columbia.edu>, David McNett <nugget@slacker.com>, freebsd-stable@FreeBSD.ORG, ghelmer@scl.ameslab.gov
Subject:   Re: xl0 timeouts in -STABLE
Message-ID:  <Pine.BSF.4.05.9904182031490.48256-100000@thelab.hub.org>
In-Reply-To: <19990418171958.A16138@elvis.mu.org>

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

Hi Paul...

	Got the same problem this afternoon, after upgradig my server last
night.  Since I didn't have ready access to the server when it happened, I
just got them to reboot the machine, but, does an 'ifconfig xl0
down;ifconfig xl0 up' correct the problem, or is a totaly reboot
required?


On Sun, 18 Apr 1999, Paul Saab wrote:

> Bill Paul (wpaul@skynet.ctr.columbia.edu) wrote:
> > Of all the gin joints in all the towns in all the world, David McNett 
> > had to walk into mine and say:
> > 
> > > I cvsupped a 3.1-STABLE box about 24 hours ago and rebuilt on the new
> > > source.  Since then I've begun experiencing xl0 timeouts which appear to
> > > mimic behavior reported under -CURRENT last September.  With no warning,
> > > and with no unusual syslog activity, my xl0 interface will simply stop
> > > working.  I did find a message in the archives with a patch made by Bill
> > > Paul to address the issue, but given the age of the patch and the fact
> > > that I also see reports of its failure to resolve the problem, I'm
> > > reluctant to attempt to fit it into my 3.1-STABLE codebase.
> > > 
> > > A few of the particulars:
> > > 
> > > Apr 18 09:29:39 dazed /kernel: xl0: <3Com 3c905-TX Fast Etherlink XL> rev 
> > >                 0x00 int a irq 12 on pci0.10.0
> > 
> > Okay, this is a boomerang card. Could you please try for me the
> > following:
> > 
> > http://www.freebsd.org/~wpaul/3Com/test/3.0
> > 
> > There's a test driver there with a patch to xl_txeof() which I
> > _THINK_ addresses this problem (the guy who was supposed to test this
> > for me hasn't replied yet).
> 
> I just got around to testing the new driver with the xl_txeof
> patches and I still get the watchdog timeout messages.  It actually
> locked up faster than before with this round of patches.
> 
> paul
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




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