FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 08-30-2011, 06:22 PM
Marcus Osdoba
 
Default Bug#636123: kernel panic after installing 2.6.39 from backports on squeeze

Am 22.08.2011 20:32, schrieb Ben Hutchings:

On Mon, Aug 22, 2011 at 06:55:12PM +0200, Valentijn Scholten wrote:

I am running into a similar isue with 2.6.39.2. amd64.

I decided to install 2.6.39.2 from backports (apt-get install ...)

I rebooted, and got a kernel panic about not being able to find the
root file system.

"No filesystem could mount root, tried:"
"Kernel panic = not syncing: VFA: Unable to mount root fs on
unkown-block(0,0)."

[...]


Hi,
Im running Squeeze on an Intel S1200BTS (quite new hardware with
i3-2100T and two NICs). Because only one NIC was supported by the recent
stable kernel, I decided to install the newest kernel from
squeeze-backports. I've made positive experiences with 2.6.38bpo on
other systems.


The root systems resides on a bios backed softraid (dm-raid) level 1.
After installing the 2.6.39bpo I run into the same trap as described
above. I rebooted with the default stable kernel kernel.


Because installing the system on the dm-raid device wasn't that straight
forward, I thought it had to do something with the generated device name
in /dev/mapper/<generatedid> for the dm-raid (thesis: different
behaviour with UUID for dmraids in newer kernels?). So I changed the
kernel commandline in grub.cfg and reconfigured grub (replace UUID with
/dev/mapper/<id> which regenerated a ramdisk, too). The newer kernel
booted fine now.


But after reading, that other people experienced the same problem with
installing 2.6.39bpo (in devmapperlib context), I now know, that a
missing update-initramfs after installing might be the problem (which I
triggered unconciously by reconfiguring grub).


I do not use dracut, just stable with kernel from backports.
So I like to state, that there is a known workaround: Make sure to
regenerate the initramfs before rebooting and do not uninstall the
stable kernel ;-)


I'm not in front of the mentioned hardware right now, so I cannot
reproduce it reliably. Therefore I don't want to spam the bug history.


Regards,
Marcus


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E5D2A4B.5080801@googlemail.com">http://lists.debian.org/4E5D2A4B.5080801@googlemail.com
 
Old 09-06-2011, 04:38 AM
Ben Hutchings
 
Default Bug#636123: kernel panic after installing 2.6.39 from backports on squeeze

On Tue, 2011-08-30 at 20:22 +0200, Marcus Osdoba wrote:
[...]
> I do not use dracut, just stable with kernel from backports.
> So I like to state, that there is a known workaround: Make sure to
> regenerate the initramfs before rebooting and do not uninstall the
> stable kernel ;-)
[...]

Well, of course that works, but it's always supposed to happen
automatically.

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?

Ben.
 
Old 09-06-2011, 07:55 PM
Marcus Osdoba
 
Default 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


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E667AA6.9040500@googlemail.com">http://lists.debian.org/4E667AA6.9040500@googlemail.com
 
Old 09-07-2011, 01:45 AM
Ben Hutchings
 
Default Bug#636123: kernel panic after installing 2.6.39 from backports on squeeze

On Tue, 2011-09-06 at 21:55 +0200, Marcus Osdoba wrote:
> 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...

OK.

> 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.

I don't believe that the reported failures to generate an initramfs have
anything at all to do with the disk configuration. It must be something
to do with the order of upgrades.

Ben.

> Finally, I need to recheck it on the real hardware.
>
> Regards,
> Marcus
>
 

Thread Tools




All times are GMT. The time now is 12:12 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org