Ubuntu
module-init-tools package

  1. Bug #37430
  2. Comment #25

Comment 25 for bug 37430

Revision history for this message
Michael R. Head (burner) wrote :

One more spam to this bug (sorry for not combining all these comments into one post).

On the machine under upgrade, it is not possible to kill modprobe, so "sudo kill -9 13666" leaves the above process alive. After killing the update manager, I did a sudo dpkg --configure -a to complete the upgrade, and the machine has now hung. It doesn't even respond to pings anymore.

After attempting to boot with the 2.6.15-386 kernel, I get a kernel panic -- not syncing: VFS: Unable to mount root fs on unknown block(0,0). I'm guessing it's initramfs wasn't made properly due to the failed pcmcia upgrade.

When I boot with the old 2.6.12-10-k7-smp kernel, the boot process stops at the "Starting PCMCIA services..." script. Ctrl-alt-delete and Ctrl-C fail to do anything, but I can see my keystrokes echoed on the text terminal.

When I boot with the 2.6.12-10-386 kernel, I get a nice big kernel backtrace on the console during "starting pcmcia services...", but the boot continues. With the non-SMP kernel, I was able to run the sudo dpkg --configure -a and finish the upgrade. After competeing the upgrade, the 2.6.15-23-k7 kernel boots the machine fine.

So it seems that there's some serious problem with the dapper versions of modprobe or pcmcia when running on the 2.6.12 SMP kernels.