Hang on boot after updated to 12.04 Precise Pangolin

Bug #990510 reported by Rigoberto Calleja on 2012-04-28
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned

Bug Description

After updating to Ubuntu version 12.04 Precise Pangolin.
Everytime I try to boot with default kernel version: 3.2.0-24-generic the system hangs on boot.
The system boots fine with previous kernel version: 3.0.0-17-generic.

If recovery mode is selected the last message displayed is Firewire_ohci failed to set link power status

summary: + Hang on boot kernel 3.2.0-24-generic 12.04 Precise Pangolin
Firewire_ohci failed to set link power status
tags: added: kernel-bug precise
description: updated
Rigoberto Calleja (rigobertoc) wrote :
Rigoberto Calleja (rigobertoc) wrote :
Rigoberto Calleja (rigobertoc) wrote :
summary: - Hang on boot kernel 3.2.0-24-generic 12.04 Precise Pangolin
- Firewire_ohci failed to set link power status
+ Hang on boot after updated to 12.04 Precise Pangolin

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/990510/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
Brad Figg (brad-figg) on 2012-04-28
Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Can you follow the "Boot options" instructions on the following wiki to enable additional output on boot:

https://wiki.ubuntu.com/DebuggingKernelBoot

As mentioned on the wiki, it would be great if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand.

Changed in linux (Ubuntu):
importance: Undecided → Medium
importance: Medium → High
Rigoberto Calleja (rigobertoc) wrote :

I've attached a digital photo showing last messages displayed before boot hangs.

nickleus (nick-humphrey) wrote :

the workaround i got to work and allowed me to boot was to add the following to the boot options:
blacklist=firewire_ohci

nickleus (nick-humphrey) wrote :

when you boot the machine, press F8 to get to the kernel selection list.
mark the top line (the latest kernel) and press "e" to edit the boot options.
scroll down to the line with "quiet" and "splash" (i think it's the second to last line) and add:
blacklist=firewire_ohci

press F10 to boot

Rigoberto Calleja (rigobertoc) wrote :

I tried the workarround Nick suggested but got the same result with different messages. Please see attached picture.

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc4-precise/

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Rob Allen (theburge) wrote :

I tested using 3.4.0-030400rc4-generic and I can confirm that it fails in the same way as 3.2.0-24-generic.

If I add blacklist=firewire_ohci to the kernel command line, as well as blacklisting it in /etc/modprobe.d/blacklist.conf, I can boot successfully.

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Workaround as described in bug #981936 worked fine for me.
I run an Acer TravelMate 8210

Rigoberto Calleja, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

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

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-kernel-logs
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  Edit
Everyone can see this information.

Other bug subscribers