package linux-image-2.6.32-22-generic 2.6.32-22.36 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Bug #593352 reported by emarkay
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Darn launchpad "Timed Out" again.
Will someone PLEASE address this!

Anyway, "Yea, what I said before... GRRRR!"

Second time I tried to make a boot USB with "Create Startup Disk" in an updated Lucid.
This is a 16GB USB with 4GB persistence.
Will get more data as available.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.36
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 4271 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SI7012'/'SiS SI7012 with ALC655 at irq 18'
   Mixer name : 'Realtek ALC655 rev 0'
   Components : 'AC97a:414c4760'
   Controls : 41
   Simple ctrls : 26
Date: Sun Jun 13 15:38:59 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 2
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
RelatedPackageVersions: linux-firmware 1.34.1
RfKill:

SourcePackage: linux
Title: package linux-image-2.6.32-22-generic 2.6.32-22.36 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
dmi.bios.date: 03/07/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7060
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd03/07/2005:svn:pn:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7060:rvr:cvn:ct3:cvr:

Revision history for this message
emarkay (mrk) wrote :
Revision history for this message
emarkay (mrk) wrote :

Upon rebooting I get" "Kernel Panic. Not synching VFS. Unable to mount root on unknown block (8,1)"
and the a hang.

This happens when I update the USB install with "Update manager".
I did the same thing last night, and the same result this morning on a completely "erased" USB stick.

I get a message at the end of the update in the "Details" section about 3 "Linux" installs - x.22 Kernel, -Generic) that even "Depmod" can't fix. I can't seem to "Cut-n-paste" the messages to a text file to save the exact data. (If it's in a log, it's gone now because erased everything and am trying again - I at least want a bootable Lucid USB for now.)

Let me know if this is just a temporary issue or there is a problem with the x.22 Kernel in this instance. I will try the update on this USB stick with additional info or debugging tools later if advised to.

tags: added: kj-triage
Revision history for this message
emarkay (mrk) wrote :

Triaged? Any further info?

Opened a forum thread here: http://ubuntuforums.org/showthread.php?p=9459904#post9459904

Revision history for this message
emarkay (mrk) wrote :

Reiterate: it's crashing at the Kernel Update.

(This also happens when I use the method from "PenDriveLinux".)

I even updated the Lucid data using Update Manager, EXCEPT the x.22 Kernel files, then it booted OK - But then I updated the Kernel files with Update Manager, I got the "Kernel Panic" on reboot.

Screen images attached.

Revision history for this message
emarkay (mrk) wrote :
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.