linux-kernel - PROBLEM: HP dv6000z Laptop ACPI/nVidia/bcm43xx issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat, 2 Sep 2006 14:04:51 -0400
From:	"M W" <wumarkus@...mail.com>
To:	<linux-kernel@...r.kernel.org>
Subject: PROBLEM: HP dv6000z Laptop ACPI/nVidia/bcm43xx issues

Upon boot-up, I am seeing the following error message on both 2.16 and 2.17
kernels (32 or 64 bit):

PCI: Failed to allocate mem resource #6:20000@...00000 for 0000:05:00.0

I am also unable to boot the system properly unless I boot with "acpi=off"
This may be related to my bcm43xx wireless card that I have been unable to
get working properly both with the native driver or ndiswrapper. 

Here is the information on my system:
HP dv6000z Laptop (just released in the past month)
AMD Turion x64 ML-52
nVidia nForce chipset (410/430?)
nVidia GeForce Go 7200 Video Chipset (256 "TurboCache)
Broadcom a/b/g wireless w/Bluetooth (bcm4306)
nVidia onboard NIC
Conexant HD audio? (works sometimes with generic nVidia driver in ubuntu)

I believe the mem resource issue may have something to do with the
"TurboCache" feature of the chipset, which I believe borrows some of the
system RAM. I can verify that the 000:05:00 address refers to the graphics
card. Also, there is a LED for the wireless functions, which stays blue
during boot-up with ACPI turned-on. When turned-off, the light stays red and
audio functions do not work.

I have tried several distributions (ubuntu, gentoo, suse) and have witnessed
this issue on all distributions (both the system lock-ups and the mem
resource message). Recompiling the kernel with the latest test build
resulted in the same issue, as well. At this point, I assume since this
hardware is so new that this is just a configuration that hasn't been
considered yet.

-- 
VGER BF report: U 0.500599
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/