Date: Tue, 30 Sep 2008 22:02:59 +0200 From: "Paul B. Mahol" <onemda@gmail.com> To: lists@rhavenn.net Cc: freebsd-stable@freebsd.org Subject: Re: wpi driver freeze on boot Message-ID: <3a142e750809301302l330f517dwe9e5a6bbd272c68e@mail.gmail.com> In-Reply-To: <200809301106.27666.lists@rhavenn.net> References: <200809291955.21461.lists@rhavenn.net> <3a142e750809300223p529caafle7f02a58524abc18@mail.gmail.com> <200809301106.27666.lists@rhavenn.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/30/08, Henrik Hudson <lists@rhavenn.net> wrote: > On Tuesday 30 September 2008, "Paul B. Mahol" <onemda@gmail.com> sent a > missive stating: >> On 9/30/08, Henrik Hudson <lists@rhavenn.net> wrote: >> > I've got a HP dv8000 laptop. Setting up the wpi driver for wireless >> > freezes the system on boot with the following error: >> > >> > wpi0 requested unsupported memory range >> > wpi0: could not allocate memory resource >> > >> > It lists a pcbi device (pcbi4 i think) and an actual memory range, but >> > since I >> > have to reboot using kernel.old the /var/run/dmesg.boot is wiped with >> > the >> > info. Is there anyway to grab the info when it freezes when it reboots? >> >> Perhaps, entering single-user mode. > > Nope. Disable ACPI, safe-mode and single user don't help at all. Ah, I see it, there is no way to look dmesg output in that way because it was never actually saved. >> Add this lines to your kernel to help debug problem. >> >> makeoptions DEBUG=-g >> options KDB >> options DDB >> options GDB >> options INVARIANTS >> options INVARIANT_SUPPORT >> options WITNESS >> options WITNESS_SKIPSPIN > > This doesn't really add anything to the output near the wpi freeze and I > still This one should put you into kdb when system panics, from where you could post output of bt. > can't get to the actual message, since when I reboot it wipes it out. Any > other isolation steps or ways to get detailed info to at least a cut and > pastable state? In that case you need to enter to kdb as soon as possible during boot, and sidestep each boot instruction until something bad happens, .... well it is not trivial task at all. For more info you may read developers-hanbook. (Located in /usr/share/doc/en/books/)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750809301302l330f517dwe9e5a6bbd272c68e>