From owner-freebsd-current@FreeBSD.ORG Tue Dec 23 14:49:52 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE37D16A4CE for ; Tue, 23 Dec 2003 14:49:52 -0800 (PST) Received: from postal1.es.net (proxy.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A23643D66 for ; Tue, 23 Dec 2003 14:49:51 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Tue, 23 Dec 2003 14:49:50 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 898365D04; Tue, 23 Dec 2003 14:49:49 -0800 (PST) To: Soren Schmidt In-Reply-To: Message from Soren Schmidt <200312232158.hBNLwBgZ074920@spider.deepcore.dk> Date: Tue, 23 Dec 2003 14:49:49 -0800 From: "Kevin Oberman" Message-Id: <20031223224949.898365D04@ptavv.es.net> cc: jesse@wingnet.net cc: freebsd-current@FreeBSD.ORG Subject: Re: Tracking down ata0 reset hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2003 22:49:52 -0000 > From: Soren Schmidt > Date: Tue, 23 Dec 2003 22:58:11 +0100 (CET) > > It seems Kevin Oberman wrote: > > > > > > Pretty darn wierd. Anyone have any ideas as to why it works when the serial > > > console AND verbose boot is enabled? > > > > I can confirm this on my system, as well. And I do have an explanation > > (but a fix will probably have to come from Søren. > > > > The reason is almost certainly a timing issue. When you boot -v, the > > resume sends a LOT more data to the screen and when you use -D, it sends > > it to both the screen and the serial port which is MUCH slower to > > complete than the screen. This allows SOMETHING to clear or complete or > > something on resume and all is well. > > I think its more likely that we hit the infamous console lockup bug > thats been around for months (probably a lock messup somewhere). Well, I spoke too soon. While the use of "boot -D -v" seems to improve the chance of a recovery, my last attempt failed again. :-( Not that this really has much impact om me as S3 does not turn off the backlight making it pretty useless. But I suspect the backlight resolution is coming and it would be nice to get past this by then. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634