Cannot boot after update to Maverick

Bug #648352 reported by Bremm
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After updating to Maverick from Lucid, the kernel (linux-image-2.6.35-22-generic) seems to be unable to boot. The old one (linux-image-2.6.32-24-generic) boots flawlessy. I have both at this moment on grub2.

Steps to reproduce this error:

Install Lucid with /dev/sda1 as reiserfs;
Upgrade to Maverick;
Boot with "2.6.35-22-generic".

After reboot you'll get the messge "Kernel Panic: VFS: Unable to mount root".

Also I've got a (poor) picture with my cellphone camera (if needed, please ask a copy).

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bremm 2111 F.... xfce4-mixer-plu
                      bremm 2139 F.... xfce4-volumed
CRDA: Error: [Errno 2] Arquivo ou diretório não encontrado
Card0.Amixer.info:
 Card hw:0 'CK804'/'NVidia CK804 with ALC850 at irq 23'
   Mixer name : 'Realtek ALC850 rev 0'
   Components : 'AC97a:414c4790'
   Controls : 42
   Simple ctrls : 27
Card1.Amixer.info:
 Card hw:1 'UART'/'MPU-401 UART at 0x330, irq 10'
   Mixer name : ''
   Components : ''
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

Date: Sun Sep 26 16:48:31 2010
HibernationDevice: RESUME=UUID=18e70129-30d5-4a1a-8892-caf6ad91e5ad
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 004: ID 1c4f:0002 SiGma Micro
 Bus 002 Device 003: ID 04d9:2083 Holtek Semiconductor, Inc.
 Bus 002 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=b951da7b-04b7-4406-a5de-7b9f92466a71 ro quiet splash
ProcEnviron:
 LANGUAGE=pt_BR:pt:pt_PT:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:

SourcePackage: linux
dmi.bios.date: 12/01/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1016
dmi.board.name: A8N-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1016:bd12/01/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Bremm (bremm) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Bremm, 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/ .

tags: added: bios-outdated-1805 regression-release
Changed in linux (Ubuntu):
status: Confirmed → New
status: New → Incomplete
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
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.