[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#581527: marked as done ([linux-2.6] linux-image-2.6.32-5-686 hangs on boot)

Your message dated Fri, 14 May 2010 16:34:15 +0200
with message-id <20100514143415.GD13054@baikonur.stro.at>
and subject line Re: Bug#581527: [linux-2.6] linux-image-2.6.32-5-686 hangs on boot
has caused the Debian Bug report #581527,
regarding [linux-2.6] linux-image-2.6.32-5-686 hangs on boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
581527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581527
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6
Version: linux-image-2.6.32-5-686
Severity: grave
Justification: renders package unusable

--- Please enter the report below this line. ---
I've just installed linux-image-2.6.32-5-686 and rebooted my system, but it hangs at startup. No way to make it boot rather than fallback to the old 2.6.32-3.
Please note that there are no logs for this hangs, it seems that it just hanged on startup before being able to mount the root file system, but also before the console initialization as no message was written to the screen.
I consider that this is a grave regression in the sense of the Debian policy but it may also be considered critical as it makes the whore system unusable as it even doesn't boot. Please ensure this version doesn't get into testing.

Cheers,
--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.32-5-686

Debian Release: squeeze/sid
  500 unstable        ftp.fr.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=


--- End Message ---
--- Begin Message --- 
On Fri, May 14, 2010 at 04:33:28PM +0200, Bastian Blank wrote:
> > Now, I've understood the issue : when the new kernel was installed, some
> > script asked me to convert my fstab automatically to use UUID. This was
> > done automatically. However, due to my configuration the kernel boots in
> > quiet mode, so nothing is displayed.
> > 
> > Removing the quiet flag, the system seems stuck on mounting root file
> > system. This is passed as root=/dev/hda1. Very strange as this kernel
> > version seems to assume all disks are serial (/dev/sd??).
> > 
> > I've used my laptop to investigate the issue, but it doesn't happen on
> > it, so this may look as a IDE/ATA issue.
> > 
> > Just replaced root=/dev/hda1 by root=/dev/sda1 and it worked :)
> > 
> > Great, this bug is resolved for me, know you should find a solution to
> > fix automatically update-grub for our users, they are not supposed all
> > to know how to fix that, and you can not ask them to get rid of their
> > old PC, did you?
> > 
> > Anyway, I thank you for the great effort you and all the kernel team
> > spend for giving us a better OS, but just try to be more user friendly
> > with non expert users.

thanks for your feedback.

closing as user error not to accept the UUID change. newer template have
a more explicit warning that this results in unbootable boxes.
thus closing bug report.

--- End Message ---
Reply to: