From owner-freebsd-stable Sun Apr 18 15:23: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from elvis.mu.org (elvis.mu.org [206.156.231.253]) by hub.freebsd.org (Postfix) with ESMTP id A0F8714DA1 for ; Sun, 18 Apr 1999 15:22:56 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: (from paul@localhost) by elvis.mu.org (8.9.1/8.9.1) id RAA16234; Sun, 18 Apr 1999 17:19:58 -0500 (CDT) (envelope-from paul) Date: Sun, 18 Apr 1999 17:19:58 -0500 From: Paul Saab To: Bill Paul Cc: David McNett , freebsd-stable@FreeBSD.ORG, ghelmer@scl.ameslab.gov Subject: Re: xl0 timeouts in -STABLE Message-ID: <19990418171958.A16138@elvis.mu.org> References: <19990418103232.A796@dazed.slacker.com> <199904181800.OAA11302@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199904181800.OAA11302@skynet.ctr.columbia.edu>; from Bill Paul on Sun, Apr 18, 1999 at 02:00:15PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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