Contrary to my earlier conclusion, the upgrade did not delete
older images. It appears a ramdisk generation change may have
included a bad module whose loading crashed the system later.
I could not boot other images because my Grub 2 configuration file
grub.cfg missed the corresponding initrd
Thanks for quashing my hasty conclusion about the timing of the kernel crash.
I now see that the crash occurred after the ramdisk stage succeeded. Probably,
this may have something to do with memory paging to disk. I could boot to the
shell, disable swapping, launch udev, resolvconf,
Package: linux-2.6
Version: 2.6.32-30
Severity: critical
Justification: breaks the whole system
Both normal and safe boot modes panicked when running the ram disk
image. Worse, the upgrade DELETED the earlier kernel image and ram disk
image. I managed to boot by editing the safe mode command
Package: linux-2.6
Version: 2.6.38-3
Severity: critical
Justification: breaks the whole system
Booting panics when bringing interfaces up, including a Wi-Fi adm8211
from drivers/net/wireless. The stack trace mentions
ieee80211_rx_handlers in mac80211, net_receive_skb, do_page_fault,
4 matches
Mail list logo
