Re: System unbootable
Steffan Harris, 27.03.2011:
> Hi,
>
> I followed instructions at http://dendiz.com/blog/?p=138 on my MacBook Pro
> 7,1 running Debian Squeeze. Installing ndiswrapper seemed to do something to
> my kernal... after a reboot my system goes through GRUB but then comes up
> with:
>
> Setting parameters of disk: none
> Setting preliminary keycap: done
> Activating swap? done
> Checking root file system? fsck from util-linux-ng 2.16.2
> /dev/sda3: clean, 154353/11739136 files, 6058946/46948242 blocks
> done.
> Cleaning up ifupdown?
> Setting up networking?.
> Loading kernal modules? [16.584261] firewire_sbp2: fw1.0: orb reply timed
> out, rcode=0x11
> [16.593534] sd 2:0:0:0: [sdb] Asking for cache data failed
> [16.593587] sd 2:0:0:0: [sdb] Assuming drive cache: write through
> [16.598551] sd 2:0:0:0: [sdb] Asking for cache data failed
> [16.598601] sd 2:0:0:0: [sdb] Assuming drive cache: write through
> [21.381619] sd 2:0:0:0: [sdb] Asking for cache data failed
> [21.381649] sd 2:0:0:0: [sdb] Assuming drive cache: write through
>
> [77.311460] BUG: soft lockup - CPU#3 stuck for 61s! [modprobe:1117]
> udev[464]: worker [1156] unexpectedly returned with status 0x0100
>
> udevd[464]: worker[1156] failed while handling
> '/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/fw1/fw1.0/host2/target2:0:0:0/2:0:0:0/block/sdb'
>
> I don't know what has happened to my system and whether it can be recovered
> or not... and can I access any system logs for further information?
The error messages you have above don't look like they have anything to
do with ndiswrapper. Are you sure that's the only thing that changed
before the last reboot? Did you also change the kernel you used?
In grub, can you choose to boot into an older kernel or into recovery
mode?
Do you have an external hard drive? If so, can you try without that
plugged in?
(Googling for "BUG: soft lockup" or for
"firewire_sbp2: fw1.0: orb reply timed out, rcode=0x11"
returns many hits, some with suggestions, but I don't know which may be
relevant to your problem.)
Reply to: