From owner-freebsd-stable@FreeBSD.ORG Tue Sep 30 19:07:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C91D91065694 for ; Tue, 30 Sep 2008 19:07:09 +0000 (UTC) (envelope-from lists@rhavenn.net) Received: from smtp153.sat.emailsrvr.com (smtp153.sat.emailsrvr.com [66.216.121.153]) by mx1.freebsd.org (Postfix) with ESMTP id A8B6F8FC08 for ; Tue, 30 Sep 2008 19:07:09 +0000 (UTC) (envelope-from lists@rhavenn.net) Received: from relay5.relay.sat.mlsrvr.com (localhost [127.0.0.1]) by relay5.relay.sat.mlsrvr.com (SMTP Server) with ESMTP id 742A8258AFE; Tue, 30 Sep 2008 15:07:08 -0400 (EDT) Received: by relay5.relay.sat.mlsrvr.com (Authenticated sender: henrik-AT-ecwwebworks.com) with ESMTP id 730CA258057; Tue, 30 Sep 2008 15:06:33 -0400 (EDT) From: Henrik Hudson To: freebsd-stable@freebsd.org Date: Tue, 30 Sep 2008 11:06:27 -0800 User-Agent: KMail/1.9.7 References: <200809291955.21461.lists@rhavenn.net> <3a142e750809300223p529caafle7f02a58524abc18@mail.gmail.com> In-Reply-To: <3a142e750809300223p529caafle7f02a58524abc18@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809301106.27666.lists@rhavenn.net> Cc: "Paul B. Mahol" Subject: Re: wpi driver freeze on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lists@rhavenn.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2008 19:07:09 -0000 On Tuesday 30 September 2008, "Paul B. Mahol" sent a missive stating: > On 9/30/08, Henrik Hudson 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. > 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 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? Henrik -- Henrik Hudson lists@rhavenn.net ------------------------------ "God, root, what is difference?" Pitr; UF (http://www.userfriendly.org/)