Date: Thu, 18 Sep 2003 12:17:56 -0500 From: Steve Ames <steve@energistic.com> To: w@dream.vg Cc: freebsd-current@freebsd.org Subject: Re: ATAng still problematic Message-ID: <20030918171756.GB39734@energistic.com> In-Reply-To: <20030918165507.GE22643@student.agh.edu.pl> References: <20030918155125.GC22643@student.agh.edu.pl> <200309181638.h8IGcPox025307@spider.deepcore.dk> <20030918164635.GA99217@energistic.com> <20030918165507.GE22643@student.agh.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 18, 2003 at 06:55:07PM +0200, Jan Srzednicki wrote: > On Thu, Sep 18, 2003 at 11:46:35AM -0500, Steve Ames wrote: > > On Thu, Sep 18, 2003 at 06:38:25PM +0200, Soren Schmidt wrote: > > > Anyhow, what I need to be able to tell what may be going on, is that > > > you boot verbose and get me the output from dmesg from a boot that > > > found all device, and from a boot that missed. > > > > Anyone know how to make the message buffer larger? I don't have > > a serial console hooked up currently and a boot verbose is way > > over the 32K default buffer size so only get the last 32K once > > the system is booted up. > > How about /var/run/dmesg.boot? ;) That file only contains what can be held in the buffer until the file system is up (I think). It also only contains the last 32K or so of boot up messages.. I still lose all of the first messages: steve@energistic:/home/steve> head /var/run/dmesg.boot 0x30 ata1-master: stat=0x20 err=0x20 lsb=0x20 msb=0x20 ata1-slave: stat=0x30 err=0x30 lsb=0x30 msb=0x30 ata1-master: stat=0x20 err=0x20 lsb=0x20 msb=0x20 ata1-slave: stat=0x30 err=0x30 lsb=0x30 msb=0x30 See what I mean? -Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030918171756.GB39734>