kernel panic on boot

Bug #132490 reported by Marc Andrysco
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.22 (Ubuntu)
Fix Released
Medium
Brian Murray

Bug Description

On occasion, the operating system will boot up fine. Most of the time, it will give the following error about 1 second after I select to boot the OS in grub (dual boot with Vista).

[ 0.231524] [<c0210d54>] acpi_ds_init_aml_walk+0xb4/0xfe
[ 0.231738] [<c021e47c>] acpi_ps_execute_pass+0x81/0x94
[ 0.231953] [<c021e57d>] acpi_ps_execute_method+0xbe/0x14d
[ 0.232168] [<c021b951>] acpi_ns_evaluate+0x9d/0xfc
[ 0.232382] [<c021b4a9>] acpi_evaluate_object+0x139/0x1e0
[ 0.232597] [<c020d321>] acpi_evaluate_integer+0x80/0xb3
[ 0.232811] [<c0225246>] acpi_bus_get_status+0x32/0x8a
[ 0.233025] [<c0229315>] acpi_add_single_object+0x1b0/0x7d8
[ 0.233240] [<c022400c>] acpi_ut_acquire_mutex+0x32/0x7a
[ 0.233454] [<c0223f2f>] acpi_ut_release_mutex+0x5b/0x63
[ 0.233669] [<c0229a52>] acpi_bus_scan+0x115/0x184
[ 0.233882] [<c03f24a0>] acpi_scan_init+0x16b/0x18d
[ 0.234097] [<c0100511>] init+0x111/0x330
[ 0.234310] [<c0103126>] ret_from_fork+0x6/0x20
[ 0.234524] [<c0100400>] init+0x0/0x330
[ 0.234736] [<c0100400>] init+0x0/0x330
[ 0.234946] [<c01044c7>] kernel_thread_helper+0x7/0x10
[ 0.235160] =======================
[ 0.235271] Code: 55 57 56 53 89 c3 8d 70 04 83 ec 0c 89 f0 65 8b 3d 08 00 00
 00 e8 c6 0c 00 00 8d 6b 08 b8 ff ff ff ff 8b 55 04 89 2c 24 89 65 04 <89> 22 89
 54 24 04 89 7c 24 08 87 03 83 e8 01 74 2a 8d 74 26 00
[ 0.241913] EIP: [<c02eda4b>] __mutex_lock_slowpath+0x2b/0x90 SS:ESP 0068:df9
05b74
[ 0.242237] <0>Kernel panic - not syncing: Attempted to kill init!
[ 0.242459]

I'm using an Acer Aspire 5720-6497 that is brand new, and the few times I can boot into Linux, things seem to run just fine. I've run Ubuntu on a few desktops as well as a laptop, all running without a hitch. Also, this effects both kernel 2.6.20-15 and 2.6.20-16.

Revision history for this message
Brian Murray (brian-murray) wrote : Re: [Bug 132490] kernel panic on boot

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducable with the live environment of the Desktop CD of the
development release - Gutsy Gibbon. It would help us greatly if you
could test with it so we can work on getting it fixed in the actively
developed kernel. You can find out more about the development release
at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your
help.

 status incomplete
 importance medium
 assignee <email address hidden>

Revision history for this message
Marc Andrysco (marc-andrysco) wrote :

I just tried out the Gutsy Gibbon Live CD, and when I run it, the menu pops up. I press to Run/Install, the installer just barely begins before it dumps to some type of terminal, saying something about BusyBox. This was the same error that the standard installer for Feisty gave, and, if I ran the command without the quiet argument, it crashed giving me the same error as above. Sorry that I don't have more info. I just got my wisdom teeth out and don't feel like getting myself too involved while I'm feeling like this.

I've never done any work to try to solve any of these problems, but if you could point me in the right direction, I may be able to look into trying to write a patch myself.

~ Marc Andrysco

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

There should be a log file on the live system called 'casper.log' if you could copy that to a USB stick and then add it to your bug report that would be helpful. Thanks again.

Revision history for this message
Marc Andrysco (marc-andrysco) wrote :

Okay, the problem persisted in Tribe-4, although with the update to Tribe-5, the problem has completely vanished. I've been running for quite some time now expecting it to crop up, but it's gone. Thanks.

~ Marc Andrysco

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. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status . Thank you 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.

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.