Re: Bug#636123: kernel panic after installing 2.6.39 from backports on squeeze
Am 06.09.2011 06:38, schrieb Ben Hutchings:
I've now tested upgrading from squeeze to squeeze-backports kernel
package in a VM, with the results:
# apt-get install linux-image-2.6.39-bpo.2-pae
Fails, complaining that initramfs-tools will be broken.
# apt-get install linux-image-2.6.39-bpo.2-pae initramfs-tools/squeeze-backport
Succeeds and builds an initramfs automatically as expected.
# aptitude install linux-image-2.6.39-bpo.2-pae
Offers to install dracut and remove initramfs-tools!
# aptitude install linux-image-2.6.39-bpo.2-pae initramfs-tools/squeeze-backport
Succeeds and builds an initramfs automatically as expected.
So my best theory is that aptitude is leading some people astray.
Do you use aptitude? Did you get dracut installed, even though you
don't intentionally use it?
I always used apt-* and never aptitude. But my upgrade path was a bit
different from yours.
- Install vanilla Squeeze (from 6.0.2.1 netinstcd)
- Add backports to sources.list as described on the Wiki page
- install with
# apt-get install -t squeeze-backports linux-image-2.6.39-bpo.2-amd64
(I don't remember exactly, but initramfs-tools were updated, too in this
step; so I guess this was initramfs-tools from backports)
I've never noticed a dracut installation...
I did the same steps in a virtual machine now and I was NOT able to
reproduce the problem (dracut not installed, kernel 2.6.39bpo boots fine
with the generated ramdisk). The original bug report mentions an lvm.
I've discovered the problem with an installation on a dm-raid device.
Finally, I need to recheck it on the real hardware.
Regards,
Marcus
Reply to: