From owner-freebsd-bugs Wed Jan 22 13:28: 7 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 E99C137B401 for ; Wed, 22 Jan 2003 13:28:05 -0800 (PST) Received: from www.gotbrains.org (www2.gotbrains.org [206.180.149.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23CB443ED8 for ; Wed, 22 Jan 2003 13:28:05 -0800 (PST) (envelope-from cravey@gotbrains.org) Received: from www.gotbrains.org (localhost [127.0.0.1]) by www.gotbrains.org (8.12.6/8.12.6) with ESMTP id h0MLRx3A021815; Wed, 22 Jan 2003 15:27:59 -0600 (CST) (envelope-from cravey@gotbrains.org) Received: from localhost (cravey@localhost) by www.gotbrains.org (8.12.6/8.12.6/Submit) with ESMTP id h0MLRxiX021812; Wed, 22 Jan 2003 15:27:59 -0600 (CST) X-Authentication-Warning: www.gotbrains.org: cravey owned process doing -bs Date: Wed, 22 Jan 2003 15:27:59 -0600 (CST) From: Stephen Cravey To: Mike Silbersack Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/47251: 5.0 RELEASE, panic in mii_physubr.c (xl0 Driver) In-Reply-To: <20030121220726.C4494-100000@patrocles.silby.com> Message-ID: <20030122150625.L20398@www.gotbrains.org> References: <20030121171746.F37185@www.gotbrains.org> <20030121220726.C4494-100000@patrocles.silby.com> 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 > As for adding this to 5.0-release; it's too late Actually, I meant as something like -Release-p1 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message