Bug#611493: dmesg obtained from initrd shell

2011-09-11 Thread Jonathan Nieder
Hi again, pascal.berna...@free.fr wrote: If it is a hardware problem, I do not see why it doesn't show with the Mint system. From a certain point of view, even many kernel bugs that have been fixed are hardware problems. That is, it can be possible to work around quirky hardware once

Bug#611493: dmesg obtained from initrd shell

2011-09-07 Thread pascal . bernard1
If it is a hardware problem, I do not see why it doesn't show with the Mint system. Moreover, if all is fine for a few minutes, the computer will go for hours, using all the memory, without any panic. I will try to install a Mint Debian on a native partition to see what happens. Thank you for

Bug#611493: dmesg obtained from initrd shell

2011-09-06 Thread Jonathan Nieder
unmerge 611493 reassign 611493 src:linux-2.6 2.6.32-35 affects 611493 = retitle 611493 kernel panics or freezes helped but not eliminated by warm reboot or rootdelay=20 # haven't ruled out a hardware problem tags 611493 = moreinfo quit Ben Hutchings wrote: On Mon, 2011-09-05 at 21:08 +0200,

Bug#611493: dmesg obtained from initrd shell

2011-09-05 Thread Pascal BERNARD
Here is the result of dmesg from the initrd shell. ls /dev/mapper shows that some logical volumes are not present. The final message of dmesg is about a failure of vgchange. All this confirm that the lvm track is worth investigations. [0.00] Initializing cgroup subsys cpuset [

Bug#611493: dmesg obtained from initrd shell

2011-09-05 Thread Ben Hutchings
On Mon, 2011-09-05 at 21:08 +0200, Pascal BERNARD wrote: Here is the result of dmesg from the initrd shell. ls /dev/mapper shows that some logical volumes are not present. The final message of dmesg is about a failure of vgchange. All this confirm that the lvm track is worth investigations.