All 2.6.33-based kernels in Experimental failed to boot here since they
were available. The last boot message I see is the infamous "Waiting for
root filesystem". No specific errors or the like are printed before that.
I have to Ctrl+Alt+Del my way out and boot with 2.6.32 again.
- -- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
sys_vendor: To Be Filled By O.E.M.
product_name: To Be Filled By O.E.M.
product_version: To Be Filled By O.E.M.
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: P2.10
board_vendor:
board_name: AM2NF3-VSTA
board_version:
** USB devices:
Bus 002 Device 003: ID 0b05:1715 ASUSTek Computer, Inc. 2045 Bluetooth 2.0 Device with trace filter
Bus 002 Device 002: ID 04b8:010f Seiko Epson Corp. Perfection 1250
Bus 002 Device 004: ID 046d:c01e Logitech, Inc. MX518 Optical Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Kernel: Linux 2.6.32-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.33-2-amd64 depends on:
ii debconf [debconf 1.5.30 Debian configuration management sy
ii initramfs-tools 0.93.4 tools for generating an initramfs
ii linux-base 2.6.33-1~experimental.4 Linux image base package
ii module-init-tool 3.12~pre2-2 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.33-2-amd64 recommends:
ii firmware-linux-f 2.6.33-1~experimental.4 Binary firmware for various driver
ii libc6-i686 2.10.2-6 GNU C Library: Shared libraries [i
Versions of packages linux-image-2.6.33-2-amd64 suggests:
pn grub | lilo <none> (no description available)
pn linux-doc-2.6.33 <none> (no description available)
Versions of packages linux-image-2.6.33-2-amd64 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
ii firmware-linux 0.23 Binary firmware for various driver
ii firmware-linux-nonfree 0.23 Binary firmware for various driver
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100330142114.2870.18122.reportbug@core2">http://lists.debian.org/20100330142114.2870.18122.reportbug@core2
03-30-2010, 03:11 PM
maximilian attems
Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot "Waiting for root filesystem"
On Tue, Mar 30, 2010 at 04:21:14PM +0200, Mathias Brodala wrote:
> Package: linux-2.6
> Version: 2.6.33-1~experimental.4
> Severity: grave
> Tags: experimental
> Justification: renders package unusable
not at most important, as only local breakage, works fine for thousand
others and we need more info.
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> All 2.6.33-based kernels in Experimental failed to boot here since they
> were available. The last boot message I see is the infamous "Waiting for
> root filesystem". No specific errors or the like are printed before that.
>
> I have to Ctrl+Alt+Del my way out and boot with 2.6.32 again.
how are you booting?
post your grub2 /boot/grub/grub.cfg
> pn grub | lilo <none> (no description available)
that seems fishy for i686.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100330151111.GD32211@baikonur.stro.at">http://lists.debian.org/20100330151111.GD32211@baikonur.stro.at
03-30-2010, 03:23 PM
Mathias Brodala
Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot "Waiting for root filesystem"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
maximilian attems, 30.03.2010 17:11:
> On Tue, Mar 30, 2010 at 04:21:14PM +0200, Mathias Brodala wrote:
>> Package: linux-2.6
>> Version: 2.6.33-1~experimental.4
>> Severity: grave
>> Tags: experimental
>> Justification: renders package unusable
>
> not at most important, as only local breakage, works fine for thousand
> others and we need more info.
I never really liked the description of severities since there?s no way
for me to know if others are also affected by my specific issue. But
yeah, downgrade the severity as seems fit.
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> All 2.6.33-based kernels in Experimental failed to boot here since they
>> were available. The last boot message I see is the infamous "Waiting for
>> root filesystem". No specific errors or the like are printed before that.
>>
>> I have to Ctrl+Alt+Del my way out and boot with 2.6.32 again.
>
> how are you booting?
Not sure what kind of answer you expect from me here.
> post your grub2 /boot/grub/grub.cfg
Attached to this mail.
>> pn grub | lilo <none> (no description available)
>
> that seems fishy for i686.
Why? The "grub" package is only a dummy transitional package, thus I
don?t need it. If you mean something else, please let me know.
Regards, Mathias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuyF3oACgkQYfUFJ3ewsJhT1QCeLrVVTNdY/YAw1UET4HsgIOUY
S2cAoJj7iSo49z5wlvhtlxlRnv/rrvIR
=8/zW
-----END PGP SIGNATURE-----
#
# 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 ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=1920x1080
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='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
set locale_dir=($root)/boot/grub/locale
set lang=de
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, with Linux 2.6.33-2-amd64" --class debian --class gnu-linux --class gnu --class os {
set gfxpayload=keep
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
echo Loading Linux 2.6.33-2-amd64 ...
linux /boot/vmlinuz-2.6.33-2-amd64 root=/dev/hda6 ro vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,8 5,255,255,255,255 vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,2 55,85,85,255,255 vt.default_red=250,170,0,170,0,170,0,51,85,255,85, 255,85,255,85,255
echo Loading initial ramdisk ...
initrd /boot/initrd.img-2.6.33-2-amd64
}
menuentry "Debian GNU/Linux, with Linux 2.6.33-2-amd64 (recovery mode)" --class debian --class gnu-linux --class gnu --class os {
set gfxpayload=keep
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
echo Loading Linux 2.6.33-2-amd64 ...
linux /boot/vmlinuz-2.6.33-2-amd64 root=/dev/hda6 ro single vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,8 5,255,255,255,255 vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,2 55,85,85,255,255 vt.default_red=250,170,0,170,0,170,0,51,85,255,85, 255,85,255,85,255
echo Loading initial ramdisk ...
initrd /boot/initrd.img-2.6.33-2-amd64
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-2-amd64" --class debian --class gnu-linux --class gnu --class os {
set gfxpayload=keep
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
echo Loading Linux 2.6.32-2-amd64 ...
linux /boot/vmlinuz-2.6.32-2-amd64 root=/dev/hda6 ro vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,8 5,255,255,255,255 vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,2 55,85,85,255,255 vt.default_red=250,170,0,170,0,170,0,51,85,255,85, 255,85,255,85,255
echo Loading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-2-amd64
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-2-amd64 (recovery mode)" --class debian --class gnu-linux --class gnu --class os {
set gfxpayload=keep
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
echo Loading Linux 2.6.32-2-amd64 ...
linux /boot/vmlinuz-2.6.32-2-amd64 root=/dev/hda6 ro single vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,8 5,255,255,255,255 vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,2 55,85,85,255,255 vt.default_red=250,170,0,170,0,170,0,51,85,255,85, 255,85,255,85,255
echo Loading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-2-amd64
}
### 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 ###
03-30-2010, 04:11 PM
Ben Hutchings
Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot "Waiting for root filesystem"
On Tue, Mar 30, 2010 at 05:23:38PM +0200, Mathias Brodala wrote:
[...]
> linux /boot/vmlinuz-2.6.33-2-amd64 root=/dev/hda6 ro vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,8 5,255,255,255,255 vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,2 55,85,85,255,255 vt.default_red=250,170,0,170,0,170,0,51,85,255,85, 255,85,255,85,255
[...]
This says '/dev/hda6' but root has probably changed to /dev/sda6. How did
you answer the upgrade questions?
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100330161134.GO16821@decadent.org.uk">http://lists.debian.org/20100330161134.GO16821@decadent.org.uk
03-30-2010, 04:23 PM
Mathias Brodala
Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot "Waiting for root filesystem"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
Ben Hutchings, 30.03.2010 18:11:
> On Tue, Mar 30, 2010 at 05:23:38PM +0200, Mathias Brodala wrote:
> [...]
>> linux /boot/vmlinuz-2.6.33-2-amd64 root=/dev/hda6 ro
>> vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,8 5,255,255,255,255
>> vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,2 55,85,85,255,255
>> vt.default_red=250,170,0,170,0,170,0,51,85,255,85, 255,85,255,85,255
>>
> [...]
>
> This says '/dev/hda6' but root has probably changed to /dev/sda6.
> How did you answer the upgrade questions?
I told it to leave it as it is. I guess it won’t be a big issue to
rename this to sda and move my existing sd? devices down. Or how can I
make that question re-appear? I tried with dpkg-reconfigure once but it
didn’t appear again.
(Maybe it should be noted that answering with "No" to that question will
result in an unbootable state if one tries to boot with such a kernel.)
Regards, Mathias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4BB2257F.6000507@noctus.net">http://lists.debian.org/4BB2257F.6000507@noctus.net
03-30-2010, 04:36 PM
maximilian attems
Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot "Waiting for root filesystem"
On Tue, Mar 30, 2010 at 05:23:38PM +0200, Mathias Brodala wrote:
> Not sure what kind of answer you expect from me here.
>
> > post your grub2 /boot/grub/grub.cfg
>
> Attached to this mail.
that one
anyway grub2 looks fine, so we need more info can you please check
http://wiki.debian.org/InitramfsDebug
thanks
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100330163618.GE32211@baikonur.stro.at">http://lists.debian.org/20100330163618.GE32211@baikonur.stro.at