From owner-freebsd-bugs Wed Jan 22 20:50:19 2003 Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36D5A37B401 for ; Wed, 22 Jan 2003 20:50:18 -0800 (PST) Received: from out1.mx.nwbl.wi.voyager.net (out1.mx.nwbl.wi.voyager.net [169.207.3.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD04843E4A for ; Wed, 22 Jan 2003 20:50:17 -0800 (PST) (envelope-from silby@silby.com) Received: from [10.1.1.6] (d169.as28.nwbl0.wi.voyager.net [169.207.71.235]) by out1.mx.nwbl.wi.voyager.net (Postfix) with ESMTP id 98587E6B12; Wed, 22 Jan 2003 22:50:15 -0600 (CST) Date: Wed, 22 Jan 2003 22:58:02 -0600 (CST) From: Mike Silbersack To: Stephen Cravey Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/47251: 5.0 RELEASE, panic in mii_physubr.c (xl0 Driver) In-Reply-To: <20030122150625.L20398@www.gotbrains.org> Message-ID: <20030122225549.G9454-100000@patrocles.silby.com> References: <20030121171746.F37185@www.gotbrains.org> <20030121220726.C4494-100000@patrocles.silby.com> <20030122150625.L20398@www.gotbrains.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 22 Jan 2003, Stephen Cravey wrote: > Actually, I meant as something like -Release-p1 5.1? :) > In any case, the DELAY(1) patch seemed to ALMOST completely solve the > problem for me. It manifested once after about 100 megs had been pushed > through the interface. > > The patch you forgot to MFC makes my problem infinitely worse. After > applying it and rebuilding ther kernel (after cleaning the old object > files) the system is now almost totally inaccessible. Rather than being > getting errors now, the stack seems to totally halt on that session. I can > open new sessions, but the old sessions are totally locked. After about 20 > minutes, I've had one become useable again. Seems strange to me, but you > know more about the driver than I do. > > The problem is now manifesting almost as soon as I log in. I can get the > MOTD to show up usually, but most of the time I can't get the output from > 'ls' to show up before it dies. Putty sometimes responds with an "invalid > CRC on packet" error. (2-10 minutes later it seems) > > I'm moving back to the DELAY(1) patch until someone comes up with > something else to try. > > -Stephen Well, damn. Only one person had encountered the problem you're experiencing, and the extra MII_SETs fixed it for him. Looks like I'm going to have to add the DELAY calls back; I'll do that (or come up with something better!) this weekend. For future reference, could you include the output of pciconf -l and your system's dmesg? Perhaps the systems which require DELAYs have something in common. Thanks, Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message