Feisty always freeze on first Boot, run ok on other boot but can't shutdown

Bug #113050 reported by Joseph Maillardet
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

-> The computer always freeze on first boot with Feisty (fresh install up-to-date).
-> linux-image 2.6.20-15.27, uname -a : Linux casa 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
-> Founding this in syslog :

(...)
May 7 13:04:52 casa kernel: [ 56.583923] BUG: soft lockup detected on CPU#1!
May 7 13:04:52 casa kernel: [ 56.583955] [softlockup_tick+156/240] softlockup_tick+0x9c/0xf0
May 7 13:04:52 casa kernel: [ 56.583992] [update_process_times+51/128] update_process_times+0x33/0x80
(...)

-> Other boot run ok.
-> No problem with older release (Dapper, Edgy, ...).

***

-> Unable to shutdown the computer (with all release).
-> Try anythings in Bios do nothing :-(
-> Feisty without splash display this :

(...)
* Will now halt
[ 137,040348] System halted

but computer not halt !

***

So I put here some of my files / commands results in additional comments to let's you finding solution. Ask me what you need if you need more.

Revision history for this message
Joseph Maillardet (jokx) wrote :
Revision history for this message
Joseph Maillardet (jokx) wrote :
Revision history for this message
Joseph Maillardet (jokx) wrote :
Revision history for this message
Joseph Maillardet (jokx) wrote :

HellloOOOoOOOoo ? Somebody heeeerre ?

Revision history for this message
Joseph Maillardet (jokx) wrote :

So, if somebody read this I have to inform you that anything work well on Debian Etch.
- No freeze on first boot.
- No problem to shutdown the machine.

What happen with Feisty ? 0_o

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
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.