Bug#611493: kernel panics or freezes helped but not eliminated by warm reboot or "rootdelay=20"

[Pascal BERNARD <pascal.bernard1@free.fr>]

I have installed linux-image-2.6.32-5-amd64   (2.6.32-41) and I have 
booted three times without a failure. I have my root partition no longer 
on a raid/lvm partition, but this should not make a difference I suppose.

The grub menu entry is:
menuentry 'Debian GNU/Linux, avec Linux 2.6.32-5-amd64' --class debian 
--class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(hd2,msdos7)'
        search --no-floppy --fs-uuid --set 
bf17e580-6ec1-4060-81a8-03b240e8a4b1
        echo    'Chargement de Linux 2.6.32-5-amd64 ...'
        linux   /boot/vmlinuz-2.6.32-5-amd64 
root=UUID=bf17e580-6ec1-4060-81a8-03b240e8a4b1 ro  quiet
        echo    'Chargement du disque mémoire initial ...'
        initrd  /boot/initrd.img-2.6.32-5-amd64

Hope this can help.

Pascal

On 12/02/2012 17:55, Jonathan Nieder wrote:
> Pascal BERNARD wrote:
>
>    
> > I must say that I have had no trouble since I switched to kernel 3.x.
> >      
> That's good to hear.
>
> I still would be interested to hear what the newest kernel you know of
> that does exhibit trouble is.  For example, if you can try 2.6.38 (?)
> which you mentioned being troublesome before or 2.6.32.y, that would
> be useful.
>
> Trying various versions to find out when the problem was fixed could
> help us find the fix and prevent others from having to experience the
> same on squeeze, but more importantly, trying just _one_ broken
> version of the kernel with everything else kept the same would be
> enough to confirm that this was a kernel bug that has been fixed.
>
> Thanks for the update.
> Jonathan
>