Ubuntu freezes on startup with 2.6.27-7 generic until power button is pressed

Bug #292155 reported by Adrian Moya
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

On startup, ubuntu freezes in the progress bar screen with the ubuntu logo. If I press the power button, startup continues. This did not happen on 2.6.24-21.

My hardware: HP dv6955la turion x2 TL-60, atheros wireless, nvidia 7000m.

Revision history for this message
Anthony Noto (angusthefuzz) wrote :

Thanks for your bug report and for your contribution to ubuntu. In order to determine if this issue is usplash related, would you boot your computer with usplash disabled and then shutdown to see if you can reproduce the issue? To disable usplash for a single boot, you can follow these steps :

1.Press Esc during Grub boot delay to access the boot menu.
2.Select your actual Ubuntu boot line and press "e" to edit it.
3.Select the "kernel" line and press "e" to edit it.
4.At the end of the line, remove "splash" and "quiet" and press "enter".
5.Type "b" to boot the custom boot line.

Revision history for this message
Adrian Moya (adrianmoya) wrote :

Hi, booting as you told reproduce the error, exactly in this line:

[ 2.415744] forcedeth 0000:00:0a.0: PCI INT A -> Link[LMAC] -> GSI 20 (level, low) -> IRQ 20

It stops there, until I press the power button and then continues. I'm attaching dmesg.

Thanks for the quick response

Revision history for this message
Anthony Noto (angusthefuzz) wrote :

This looks like a kernel bug to me for your particular hardware.

Please include the following additional information, if you have not already done so (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" after a fresh boot 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.

Thanks in advance!

Revision history for this message
Adrian Moya (adrianmoya) wrote :

uname -a = Linux amoya-laptop 2.6.27-7-generic #1 SMP Thu Oct 30 04:18:38 UTC 2008 i686 GNU/Linux

Revision history for this message
Adrian Moya (adrianmoya) wrote :
Revision history for this message
Anthony Noto (angusthefuzz) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in linux:
assignee: angusthefuzz → ubuntu-kernel-team
status: Incomplete → Confirmed
Revision history for this message
Miguel (mmf1902) wrote :

I have the same issue as Adrian. In order to bypass the problem I disabled acpi at boot.

After this ubuntu starts smoothly. The problem is that - now - I have no acpi in my laptop.

Revision history for this message
Shawn vega (svega85-gmail) wrote :

I have this same issue. can you please tell me how to disable acpi?

Revision history for this message
Anthony Noto (angusthefuzz) wrote :

Shawn, please follow my instructions in the first post and after removing quiet and splash add "acpi=off" and follow the rest of the instructions.

Revision history for this message
Shawn vega (svega85-gmail) wrote :

it appears that your instructions to turn off acpi worked. the computer boots without a problem.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Mehall (mehall) wrote :

This also affects me.

My hardware: HP G6062ea turion x2 TL-59, atheros wireless, nvidia 7000m.

HP's, TK-xx, atheros wifi and 7000m? something in common here ;)

I'm just about to try acpi=off, though of course that's a drawback

Revision history for this message
Mehall (mehall) wrote :

Booted fine with acpi=off

Obviously not ideal.

Revision history for this message
Mehall (mehall) wrote :

Okay, just did some ACPI debugging, as per the Ubuntu Wiki page about just that.

here is what I did:

Copied the debug instructions from wiki, added own comments: (it's all fairly clear)

Try booting with the "acpi=off" kernel parameter
This will disable ACPI support. If the error is the same with acpi enabled and disabled, this may not be an ACPI issue.
If "acpi=off" allows the system to boot, try to isolate the ACPI issue with the following boot parameters

Did that, boots fine then

Try booting with "acpi=ht"
This disables all of ACPI except just enough to enable Hyper Threading. If acpi=off works and acpi=ht fails, then the issue is in the ACPI table parsing code itself, or perhaps the SMP code.
Try booting with "pci=noacpi"
This disables ACPI for IRQ routing and PCI scanning.
Try booting with "acpi=noirq"
This disables ACPI for IRQ routing.

All the above make it boot fine.

Try booting with "pnpacpi=off"
This disables the ACPI component of the Linux Plug and Play code.
Try booting with "noapic"
Disables the IO-APIC for IRQ routing or PCI scanning.

Those two options make it boot, but same as original bug, need to press keys to force it to boot.

Try booting with "nolapic"
Disables the local APIC

Boot fails at:

"ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00:qc timeout (cmd 0xec)
ata3.00: failed to IDENTIFY (I/O erroor, err_mask=0x4)"

that's the main thing, then it says "Gave up waiting for root device" and then lists common issues, etc.

Drops to Busybox.

Revision history for this message
penalvch (penalvch) wrote :

Adrian Moya, thank you for reporting this and helping make Ubuntu better. Intrepid reached EOL on April 30, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: intrepid needs-upstream-testing
removed: 8.10
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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