Ubuntu
linux-source-2.6.20 package

System will not boot with kernel 2.6.20-13 unless acpi=off

Bug #98821 reported by Ralph
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Undecided
Brian Murray

Bug Description

Fresh install of either Feisty Fawn Kubuntu beta or Ubuntu beta (former from desktop CD and latter from alternate CD). Updates after install include new kernel (2.6.20-13). Booting with the new kernel exits to a non-gui screen on which last two lines are :
* Saving VESA state [OK]
* loading ACPI modules ...

System hangs at this point. If GRUB kernel parameters interactively modified to add acpi=off, the boot is successful. I am now reverting to kernel 2.6.20-12, which works quite well).

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Additionally what happens if you boot the 2.6.20-13 kernel in rescue mode? Thanks in advance!

Revision history for this message
Ralph (ralph-puncher-deactivatedaccount) wrote :

Output of uname -a:
Linux puncher-nb 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

See attachments dmesg and lspci -vvnn outputs.

Revision history for this message
Ralph (ralph-puncher-deactivatedaccount) wrote :

If I boot 2.6.20-13 in rescue mode I do get the command prompt from which I can issue commands and bring up gdm, although I get an internal error for failure to initialize HAL.

Revision history for this message
Brian Murray (brian-murray) wrote :

Is that the exact HAL error message you are getting? Thanks again.

Revision history for this message
Ralph (ralph-puncher-deactivatedaccount) wrote : Hal message

The actual message is:
internal error
failed to initialize HAL

I did not take this message too seriously since I had booted up in the
rescue mode and then from the prompt issued the gdm command without even
logging in.

Brian Murray (brian-murray)
Changed in linux-source-2.6.20:
assignee: brian-murray → ubuntu-kernel-team
status: Needs Info → Confirmed
Revision history for this message
Ralph (ralph-puncher-deactivatedaccount) wrote :

Upgraded to 2.6.20-14 kernel. Results with this kernel identical to those with the 2.6.20-13 kernel.

Revision history for this message
Ralph (ralph-puncher-deactivatedaccount) wrote :

The problem has been fixed in kernel 2.6.20-15. See problem 96480.

Revision history for this message
Brian Murray (brian-murray) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. Thanks again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in linux-source-2.6.20:
assignee: ubuntu-kernel-team → brian-murray
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.