ubuntu 12.04 fails to boot on Dell Mini 10

Bug #905769 reported by Florin Iucha
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Unassigned

Bug Description

I am reporting this bug from a different box.

I have tried to boot Ubuntu Precise Pangolin 12.04 alpha 1 and daily build (2011-12-17) on a Dell Mini 10. In both cases I got past the 'Ubuntu 12.04 with four dots' screen and then the machine froze with a traceback.

I am attaching a screenshot of the traceback.

Bug exists in kernel 3.2.0-2.5, as well as kernel 3.2.0-5.11

Revision history for this message
Florin Iucha (florin-iucha) wrote :
Revision history for this message
Florin Iucha (florin-iucha) wrote :

Disregard all text files attached to this bug report. It was submitted from a different box!

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: maverick
Revision history for this message
Phil. V (philip.v) wrote :

I'll clean up the irrelevant apport information.

description: updated
tags: added: precise
removed: maverick
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-5.11)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-5.11
Revision history for this message
Phil. V (philip.v) wrote :

As 3.2.0-5.11 was the kernel in the 2011-12-17 daily build, and still the current kernel in the 2011-12-19 build, I'll mark this as confirmed and amend the description to be more specific as to the tested kernels.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-6.12)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-6.12
Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
Revision history for this message
Travis Larson (tlarson) wrote :

This is still an issue on the current daily image (2011-12-30). My traceback is a little different. Attaching image.

Thanks!

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
Revision history for this message
Jim Raredon (decoy-umd) wrote :

This bug still exists in Beta 1; it won't boot at all. Same issue.

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-20.32)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-20.32
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Was there an earlier kernel version or Ubuntu release that booted on this system?

Revision history for this message
Jim Raredon (decoy-umd) wrote :

The bug no longer exists in the daily CD build from March 22nd. My only problem is a video problem which is obviously reserved for a separate bug.

Sometime between Beta 1 and the Daily build from March 22nd, this must have been fixed. Thanks for all the great work!!!

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
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.