Bug 15975

Summary:	HP Pavillion dv6 2044el paralized just after the grub launch the kernel
Product:	ACPI	Reporter:	Angelo (angelo70)
Component:	BIOS	Assignee:	acpi_bios
Status:	CLOSED DUPLICATE
Severity:	normal	CC:	ben, rui.zhang
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	2.6.34-rc2	Subsystem:
Regression:	No	Bisected commit-id:

Description Angelo 2010-05-14 09:45:18 UTC

Dear all,

i report this issue, as requested in the discussion in bugs.debian.org.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571251

Honestly, i am still not sure this issue is really ACPI-BIOS related.
PC hangs at boot between 30 and 50% of the times.
Sorry, but i can describe the issue only visually, since i can find no dmesg traces or logs on the hd.

I switch on the PC, GRUB load the boot menu correctly, always.
Then, i select the kernel entry for loading. Between 2.6.30 and 2.6.34 there are some little differences, but pc hangs in any case:

2.6.30

-Let's say after 2 seconds i see the WIFI led to become blue, and see some HD activity.
-just after i see just two lines of the boot message:
Fail in evaluating the _REG object of EC devices. Broken BIOS is suspected
Loading, Plese wait

Then the cusrsor stop to blink and PC hang completely.

2.6.34
-Let's say after 2 seconds i see the WIFI led to become blue, and see some HD activity.
-just after, i see just two lines of the boot message:
[1.111781] pci 000:01:00.0: no compatible bridge window for [mem:0xfff80000 -0xffffffff pref]
[1.111789] pci 000:03:00.0: no compatible bridge window for [mem:0xfff80000 -0xffffffff pref]

Then the cusrsor stop to blink and PC hang completely.


Many thanks,
Regard,
Angelo

Comment 1 Zhang Rui 2010-05-19 07:01:31 UTC

please verify if this is a duplicate of bug https://bugzilla.kernel.org/show_bug.cgi?id=14716

Comment 2 Angelo 2010-05-19 12:02:31 UTC

Dear Zhang Rui,

i have tried the acpi=off, it works,
i have tried removing b43 and ssb modules, it works 

So i would say, yes, it is the same bug.

Workarounds above works for me.
Many thanks,
Angelo

*** This bug has been marked as a duplicate of bug 14716 ***