[intrepid] Live CD not booting on Intel Centrino Laptop with GME chipset - possibly ACPI

[Ricardo Solano]

Live CD won't boot unless acpi is disabled.

Machine is an Intel Centrino laptop (Intel GME chipset), single core.

All previous Ubuntu releases Live CDs since Breezy have worked properly on the same hardware.

Editing the kernel parameters so that acpi=off allows booting the system and installing successfully, however since acpi isn't present power management is non-existent, i.e. pressing the power button will result in instant power-off.

[xteejx (xteejx-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please boot into the liveCD and include the information requested at https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

Thankyou

[Ricardo Solano (rickman)]

Thank you for your prompt reponse.

I have followed the trouble booting instructions as suggested and only the parameters acpi=off and acpi=ht would allow the kernel to boot. Using any other parameter would throw a kernel panic.

[xteejx (xteejx-deactivatedaccount)]

Thank you for providing the requested information. This should be enough to set this as Confirmed. If any more information is needed at a later date please provide it.

[Dana Goyette (danagoyette)]

I'm not sure if my issue is the same bug, but my new HP Elitebook 8530w also won't boot with ACPI enabled. Using the Linux serial console through AMT Serial-Over-LAN, I was able to capture the boot messages from when I boot wityh ACPI enabled; note that the system hangs after the last boot message. If I hit ctrl-alt-delete at that point, it will sometimes send the system into a confused shutting-down-while-still-booting state.

Note that I am on the 2.6.28 kernel in Jaunty now, but the Intrepid kernel displays the same symptoms.
Linux EliteBook 2.6.28-1-ub-generic #1 SMP Wed Nov 26 19:15:48 UTC 2008 i686 GNU/Linux

These patches may be relevant to the kernel oops:
http://lkml.org/lkml/2008/10/23/41
http://lkml.org/lkml/2008/10/25/29

[TJ (tj)]

Dana, thanks for capturing the boot log - that helps immensely.

Having had a look it *seems* as if the cause might be related to decoding one of the ACPI DSDT thermal zone packages. Could you extract and attach the DSDT of that system please?

acpidump -b -t DSDT -o /tmp/HP-Elite-8530w.dsdt
tar -czf /tmp/HP-Elite-8530w.dsdt.tar.gz -C /tmp/ HP-Elite-8530w.dsdt

[Dana Goyette (danagoyette)]

Interestingly enough, if I disable thermal zone control by adding "options thermal off=1" to some modprobe.d file, it instead errors out on the battery module.

[Dana Goyette (danagoyette)]

I've now upgraded to the 2.6.28-2-ub-generic kernel, and the bug still exists in that kernel.

[Dana Goyette (danagoyette)]

Here's something interesting on the 2.6.28-2-generic kernel (now that they've gotten rid of the "-ub"): I booted with thermal control disabled as above, and I managed to boot the thing with ACPI enabled -- but this time it OOPS'd out on the battery module. Additionally, the system hung at the following line, for about 5 whole minutes, and then surprised me by resuming booting.
Here's the line it hung at:
[ 22.827451] input: PS/2 Generic Mouse as /devices/platform/i8042/serio4/serio5/input/input7

I am attaching the dmesg output from this time of booting.

[Ricardo Solano (rickman)]

Ok I have no idea what the kernel folks did, but I just upgraded to 2.6.27-11-generic and everything works like a charm, like in the "old" days.

This comes in handy as I was about to downgrade. I wonder though if the bug will come up again when I upgrade Jaunty, as Dana seems to have the same problem under a more recent kernel.

Anyway, thanks for looking into it.

[Dana Goyette (danagoyette)]

Actually, I'd say my issue is a different one, after all: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/288385

[xteejx (xteejx-deactivatedaccount)]

This bug report is being closed due to your comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.