Date: Wed, 14 Feb 1996 10:56:22 +0500 From: Richard J Kuhns <rjk@sparcmill.grauel.com> To: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: One problem && one question Message-ID: <9602141556.AA00009@sparcmill.grauel.com> In-Reply-To: <199602140522.VAA08632@freefall.freebsd.org> References: <9602131927.AA23929@sparcmill.grauel.com> <199602140522.VAA08632@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Justin T. Gibbs writes: > >That works fine for any ``working'' kernel; apparently none of the boot > >messages from a non-working kernel end up in the circular buffer dmesg > >uses. IE, if I boot-working then boot-nonworking then boot-working and run > >dmesg, I get the messages from the 2 boot-working kernels only. > > How would you expect the dmesg buffer to be written to disk if the > probe for your disk controller isn't successful? 8-) > I didn't think the dmesg buffer was ever written to disk -- I thought it was just a circular in-core deal. I don't recall ever seeing messages from an earlier boot after a power cycle, anyhow. > > > When you get a chance, try this one. Now that I'm not editing over a link > > > with 50% packet loss, its much easier to check my work. :) > > > > > > >I tried it; I'm afraid it made no difference. By the way, here's one more > >line from the (failing) pci-probe: > > > >bt0: uses 4 bytes of I/O space from 6000 upto 6003 > > Ahh. It did make a difference. Unfortunately, when I was cleaning > up the bt driver, I assumed that the PCI probe would always return > one of the ISA compatibility addresses. As Rod pointed out, this is > not always the case. This patch should do the trick > Thanks... I'll try it over lunch and let you know how it goes down... -- Rich Kuhns rjk@grauel.com PO Box 6249 100 Sawmill Road Lafayette, IN 47903 (317)477-6000 x319
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9602141556.AA00009>