Date: Tue, 23 Dec 2003 14:49:49 -0800 From: "Kevin Oberman" <oberman@es.net> To: Soren Schmidt <sos@spider.deepcore.dk> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Tracking down ata0 reset hang Message-ID: <20031223224949.898365D04@ptavv.es.net> In-Reply-To: Message from Soren Schmidt <sos@spider.deepcore.dk> <200312232158.hBNLwBgZ074920@spider.deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: Soren Schmidt <sos@spider.deepcore.dk> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031223224949.898365D04>