Your message dated Tue, 16 Mar 2010 09:51:28 +0000
with message-id <20100316095127.ga25...@riva.ucam.org>
and subject line Re: Bug#568001: Any progress on this?
has caused the Debian Bug report #568001,
regarding grub-pc: grub locks up the machine
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 ow...@bugs.debian.org
immediately.)


-- 
568001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-pc
Version: 1.98~20100128-1
Severity: critical
Justification: breaks the whole system

After choosing the chain load grub2 option in the old grub menu the grub2 
screen 
loads correctly. When I choose a kernel to load, the system locks up completely 
and does not respond to Ctrl-Alt-Del. The messages loading kernel .... and 
loading initrd ... appear and then in the upper right corner of the grub2 
screen a horizontal line is drawn. Is there a way to make grub2 more verbose?


-- Package-specific info:

*********************** BEGIN /proc/mounts
/dev/mapper/Debian-root / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/Debian-home /home ext3 
rw,relatime,resuid=1000,errors=remount-ro,data=writeback 0 0
/dev/mapper/Debian-tmp /tmp ext3 rw,relatime,errors=remount-ro,data=writeback 0 0
/dev/mapper/Debian-usr /usr ext3 rw,relatime,errors=remount-ro,data=writeback 0 0
/dev/mapper/Debian-var /var ext3 rw,relatime,errors=remount-ro,data=writeback 0 0
/dev/mapper/a /home/mal/a ext3 rw,relatime,errors=remount-ro,data=writeback 0 0
/dev/sde1 /boot ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sdf2 /home/mal/b ext3 rw,relatime,errors=remount-ro,data=writeback 0 0
/dev/sdh1 /mnt/usb-disk ext2 rw,relatime,errors=remount-ro 0 0
*********************** END /proc/mounts

*********************** BEGIN /boot/grub/device.map
(hd0)   /dev/sda
(hd1)   /dev/sdb
(hd2)   /dev/sdc
(hd3)   /dev/sdd
(hd4)   /dev/sde
(hd5)   /dev/sdf
(hd6)   /dev/sdg
(hd7)   /dev/sdh
*********************** END /boot/grub/device.map

*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
  fi
}
insmod raid
insmod mdraid
insmod lvm
insmod ext2
set root=(Debian-usr)
search --no-floppy --fs-uuid --set f7d61e25-fbc5-4c29-b16d-a421c30b1c19
if loadfont /share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
insmod ext2
set root=(hd4,1)
search --no-floppy --fs-uuid --set c9bc9684-470c-4dec-831a-ddc34d79efe7
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod ext2
set root=(hd4,1)
search --no-floppy --fs-uuid --set c9bc9684-470c-4dec-831a-ddc34d79efe7
insmod png
if background_image /grub/moreblue-orbit-grub.png ; then
  set color_normal=black/black
  set color_highlight=magenta/black
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, with Linux 2.6.32-trunk-686" {
        set gfxpayload=keep
        insmod ext2
        set root=(hd4,1)
        search --no-floppy --fs-uuid --set c9bc9684-470c-4dec-831a-ddc34d79efe7
        echo    Loading Linux 2.6.32-trunk-686 ...
        linux   /vmlinuz-2.6.32-trunk-686 root=/dev/mapper/Debian-root ro  quiet
        echo    Loading initial ramdisk ...
        initrd  /initrd.img-2.6.32-trunk-686
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-trunk-686 (recovery mode)" {
        set gfxpayload=keep
        insmod ext2
        set root=(hd4,1)
        search --no-floppy --fs-uuid --set c9bc9684-470c-4dec-831a-ddc34d79efe7
        echo    Loading Linux 2.6.32-trunk-686 ...
        linux   /vmlinuz-2.6.32-trunk-686 root=/dev/mapper/Debian-root ro 
single 
        echo    Loading initial ramdisk ...
        initrd  /initrd.img-2.6.32-trunk-686
}
menuentry "Debian GNU/Linux, with Linux 2.6.31-1-686" {
        set gfxpayload=keep
        insmod ext2
        set root=(hd4,1)
        search --no-floppy --fs-uuid --set c9bc9684-470c-4dec-831a-ddc34d79efe7
        echo    Loading Linux 2.6.31-1-686 ...
        linux   /vmlinuz-2.6.31-1-686 root=/dev/mapper/Debian-root ro  quiet
        echo    Loading initial ramdisk ...
        initrd  /initrd.img-2.6.31-1-686
}
menuentry "Debian GNU/Linux, with Linux 2.6.31-1-686 (recovery mode)" {
        set gfxpayload=keep
        insmod ext2
        set root=(hd4,1)
        search --no-floppy --fs-uuid --set c9bc9684-470c-4dec-831a-ddc34d79efe7
        echo    Loading Linux 2.6.31-1-686 ...
        linux   /vmlinuz-2.6.31-1-686 root=/dev/mapper/Debian-root ro single 
        echo    Loading initial ramdisk ...
        initrd  /initrd.img-2.6.31-1-686
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
*********************** END /boot/grub/grub.cfg

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages grub-pc depends on:
ii  debconf [debconf-2.0]    1.5.28          Debian configuration management sy
ii  grub-common              1.98~20100128-1 GRand Unified Bootloader, version 
ii  libc6                    2.10.2-5        Embedded GNU C Library: Shared lib
ii  ucf                      3.0025          Update Configuration File: preserv

grub-pc recommends no packages.

Versions of packages grub-pc suggests:
ii  desktop-base                  5.0.5      common files for the Debian Deskto

-- debconf information:
  grub2/kfreebsd_cmdline:
* grub2/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
  grub-pc/kopt_extracted: true
  grub-pc/install_devices:
  grub-pc/postrm_purge_boot_grub: false
  grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default: quiet



--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 1.98-1

On Thu, Mar 11, 2010 at 01:08:49PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko 
wrote:
> Vincent Lefevre wrote:
> > On 2010-03-09 20:46:33 +0000, Chris Carr wrote:
> >> This bug is still showing as a critical blocker when I try to apt-get
> >> upgrade my Sid box. It doesn't seem like much is happening - if it's
> >> safe for most users, can it be downgraded in severity?
> >
> > Even if it isn't safe for a small number of users, the bug is
> > critical. A lock up at boot time is something any user wouldn't like
> > to see. The title of the bug should probably be more descriptive so
> > that users can decide whether it is safe to upgrade or not.
> 
> I believe this bug to be fixed. Please upgrade

Yes, we should no longer be forcing gfxpayload=keep inappropriately.
You may still have problems if you use the configuration file to set up
this configuration, of course, but it's not the default any more.

Thanks,

-- 
Colin Watson                                       [cjwat...@debian.org]


--- End Message ---

Reply via email to