Kernel Panic not syncing ... unable to mount vfs on block 0:0.

Bug #196046 reported by dl.zerocool
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hello,

Yesterday there was un update probably the kernel that made my Asus F8SV unbootable.
I can of course always start with other kernels.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

I didn't see another report so I assume there's no other one about this bug.
If you need mor information like logs etc, just ask.

Here is my lspci.
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GT (rev a1)
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
05:00.0 Memory controller: Intel Corporation Turbo Memory Controller (rev 01)
08:03.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
08:03.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
08:03.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
08:03.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
08:03.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)

Tags: cft-2.6.27
Revision history for this message
dl.zerocool (dl.zerocool) wrote : Re: Kernel Panic not syncing ... unable to mount fs on unkownblock 0:0.

Just correcting the title.

Revision history for this message
yngens (foranycase) wrote :

Exactly this happened to me after tonights update.

Revision history for this message
audunpoi (audun-didgeridoo) wrote :

Happened to me just now. Have no idea what to do. Not able to boot recovery mode either.

Revision history for this message
Caroline Ford (secretlondon) wrote :

Could you follow the instructions at https://wiki.ubuntu.com/KernelTeamBugPolicies and attach the following files:

All bug reports should contain at least the output of these commands on a terminal window or console:

    * uname -a > uname-a.log
    * cat /proc/version_signature > version.log
    * dmesg > dmesg.log
    * sudo lspci -vvnn > lspci-vvnn.log

These four files should be attached to the bug report (not pasted into comments, as it makes things harder to read, and formatting is completely broken). Please note the comment about dmesg output below.

Changed in linux:
status: New → Incomplete
Revision history for this message
Justin Chudgar (justinzane) wrote :

Same issue with 2.6.24.15. Reports are attached. Thanks.

Revision history for this message
Justin Chudgar (justinzane) wrote :
Revision history for this message
Justin Chudgar (justinzane) wrote :
Revision history for this message
Justin Chudgar (justinzane) wrote :
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
dl.zerocool (dl.zerocool) wrote :

Hello,

I already have the 2.6.27, actually the bug is solved but it was already solved with the last 2.6.26 in development branch of Ubuntu.
Not encountering any regression introduced by the 2.6.27.

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

Thanks for the update. Bonsai, since you are the original bug reporter, I'm going to mark this "Fix Released". Thanks.

Changed in linux:
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.