Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
Taking the easy question first ;-) output of dpkg -l busybox gives: ii busybox1:1.10.2-2 Tiny utilities for small and embedded system Seems like splashy is out of the system anyway - output of dpkg -l splashy gives: un splashy (no description available) As for trying to load "unix" I can't answer that because it does not appear in the /etc/initramfs-tools/modules file at present. I may have loaded "unix" when loading modules manually - thinking it might be needed. It is certainly a result of the local initramfs build environment that has caused the problem. I have created a fresh install of Debian 5.04 using the same boot partition; the initrd.img-2.6.26-2-686 that it produces boots my system with no problems. I would be quite happy for you to close this bug now. We know it was something to do with my environment and no others, and I intend to reinstall with 5.04 soon. I really appreciate the effort that has been made to solve this problem but I am sure there are more pressing matters. Many thanks, Bruce maximilian attems wrote: On Tue, 09 Mar 2010, Bruce Ward wrote: Hello Max. Did you get the initramfs? I sent it 17 February. Bruce didn't see any trouble relevant modules are inside. only thing that I remakred was splashy, could you please purge that to have it out of the game? and then update-initramfs of course.. ;) why do you attempt to load "unix" in /etc/initramfs-tools/modules it is built in since very long. although this shouldn't change the trouble.. don't get the " /bin/sleep: not found" it is clearly in the initramfs. might be due a busybox bug, which version of busybox are you running dpkg -l busybox thanks -- === Bruce Ward, Nelson, New Zealand -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bbd9da3.4020...@orcon.net.nz
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
On Tue, 09 Mar 2010, Bruce Ward wrote: > Hello Max. > > Did you get the initramfs? I sent it 17 February. > > Bruce didn't see any trouble relevant modules are inside. only thing that I remakred was splashy, could you please purge that to have it out of the game? and then update-initramfs of course.. ;) why do you attempt to load "unix" in /etc/initramfs-tools/modules it is built in since very long. although this shouldn't change the trouble.. don't get the " /bin/sleep: not found" it is clearly in the initramfs. might be due a busybox bug, which version of busybox are you running dpkg -l busybox thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100406043739.ga3...@stro.at
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
On Wed, 10 Feb 2010, Bruce Ward wrote: > What to try next? > could you send me privately that faulty initramfs? thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100216164839.gc9...@stro.at
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
maximilian attems wrote: On Thu, 11 Feb 2010, Bruce Ward wrote: Greetings. More data. I have managed to get an initramfs debug out of the system and have also provided a debug from a 2.6.26-1-686 kernel which boots OK. I'm damned if I can see any reason from the debug for the recent kernel (2.6.26-2-686) to fail to boot! Interesting (but possibly not relevant) observations from my playing around (exploration). Remember there are only a few modules (thermal ones) loaded when the system drops out. 1. Load USB drivers - they find the pendrive, but no entry created in /dev. 2. Use mknod to create /dev/sda3 for the ext3 partition on pendrive. sda3 is the only SCSI entry in /dev. 3. Load ext3 module, and mount the sda3 partition and, behold, there are entries in /dev/ for sda, sda1, and sda2, as well as sda3. 4. Load the SATA drivers and suddenly there are sdb entries in /dev for all partitions on the drive I have failed to boot from. that points a bit to udev is it running at this stage? And more data. Attached is the list of entries in /dev at fail-time. Not extensive and no subdirectories. It seems that udev is doing something, but not enough. Bruce === Bruce Ward, Nelson, New Zealand crw-rw1 00 5, 1 Feb 12 19:12 console crw-rw1 00 10, 63 Feb 12 19:11 cpu_dma_latency crw-rw1 00 1, 7 Feb 12 19:11 full crw-rw1 00 10, 228 Feb 12 19:11 hpet crw-rw1 00 1, 2 Feb 12 19:11 kmem crw-rw1 00 1, 11 Feb 12 19:11 kmsg crw-rw1 00 1, 1 Feb 12 19:11 mem crw-rw1 00 13, 63 Feb 12 19:11 mice crw-rw1 00 10, 62 Feb 12 19:11 network_latency crw-rw1 00 10, 61 Feb 12 19:11 network_throughput crw-rw1 00 1, 3 Feb 12 19:11 null crw-rw1 00 1, 4 Feb 12 19:11 port crw-rw1 00 10, 1 Feb 12 19:11 psaux crw-rw1 00 5, 2 Feb 12 19:11 ptmx brw-rw1 00 1, 0 Feb 12 19:11 ram0 brw-rw1 00 1, 1 Feb 12 19:11 ram1 brw-rw1 00 1, 10 Feb 12 19:11 ram10 brw-rw1 00 1, 11 Feb 12 19:11 ram11 brw-rw1 00 1, 12 Feb 12 19:11 ram12 brw-rw1 00 1, 13 Feb 12 19:11 ram13 brw-rw1 00 1, 14 Feb 12 19:11 ram14 brw-rw1 00 1, 15 Feb 12 19:11 ram15 brw-rw1 00 1, 2 Feb 12 19:11 ram2 brw-rw1 00 1, 3 Feb 12 19:11 ram3 brw-rw1 00 1, 4 Feb 12 19:11 ram4 brw-rw1 00 1, 5 Feb 12 19:11 ram5 brw-rw1 00 1, 6 Feb 12 19:11 ram6 brw-rw1 00 1, 7 Feb 12 19:11 ram7 brw-rw1 00 1, 8 Feb 12 19:11 ram8 brw-rw1 00 1, 9 Feb 12 19:11 ram9 crw-rw1 00 1, 8 Feb 12 19:11 random crw-rw1 00254, 0 Feb 12 19:11 rtc0 crw-rw1 00 10, 231 Feb 12 19:11 snapshot crw-rw1 00 5, 0 Feb 12 19:11 tty crw-rw1 00 4, 0 Feb 12 19:11 tty0 crw-rw1 00 4, 1 Feb 12 19:11 tty1 crw-rw1 00 4, 10 Feb 12 19:11 tty10 crw-rw1 00 4, 11 Feb 12 19:11 tty11 crw-rw1 00 4, 12 Feb 12 19:11 tty12 crw-rw1 00 4, 13 Feb 12 19:11 tty13 crw-rw1 00 4, 14 Feb 12 19:11 tty14 crw-rw1 00 4, 15 Feb 12 19:11 tty15 crw-rw1 00 4, 16 Feb 12 19:11 tty16 crw-rw1 00 4, 17 Feb 12 19:11 tty17 crw-rw1 00 4, 18 Feb 12 19:11 tty18 crw-rw1 00 4, 19 Feb 12 19:11 tty19 crw-rw1 00 4, 2 Feb 12 19:11 tty2 crw-rw1 00 4, 20 Feb 12 19:11 tty20 crw-rw1 00 4, 21 Feb 12 19:11 tty21 crw-rw1 00 4, 22 Feb 12 19:11 tty22 crw-rw1 00 4, 23 Feb 12 19:11 tty23 crw-rw1 00 4, 24 Feb 12 19:11 tty24 crw-rw1 00 4, 25 Feb 12 19:11 tty25 crw-rw1 00 4, 26 Feb 12 19:11 tty26 crw-rw1 00 4, 27 Feb 12 19:11 tty27 crw-rw1 00 4, 28 Feb 12 19:11 tty28 crw-rw1 00 4, 29 Feb 12 19:11 tty29 crw-rw1 00 4, 3 Feb 12 19:11 tty3 crw-rw1 00 4, 30 Feb 12 19:11 tty30 crw-rw1 00 4, 31 Feb 12 19:11 tty31 crw-rw1 0
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
maximilian attems wrote: On Thu, 11 Feb 2010, Bruce Ward wrote: Greetings. More data. I have managed to get an initramfs debug out of the system and have also provided a debug from a 2.6.26-1-686 kernel which boots OK. I'm damned if I can see any reason from the debug for the recent kernel (2.6.26-2-686) to fail to boot! Interesting (but possibly not relevant) observations from my playing around (exploration). Remember there are only a few modules (thermal ones) loaded when the system drops out. 1. Load USB drivers - they find the pendrive, but no entry created in /dev. 2. Use mknod to create /dev/sda3 for the ext3 partition on pendrive. sda3 is the only SCSI entry in /dev. 3. Load ext3 module, and mount the sda3 partition and, behold, there are entries in /dev/ for sda, sda1, and sda2, as well as sda3. 4. Load the SATA drivers and suddenly there are sdb entries in /dev for all partitions on the drive I have failed to boot from. that points a bit to udev is it running at this stage? Yes, udev is running. Attached is a ps capture as soon as I had the pendrive mounted. When the boot stopped, the listing of processes stopped at PID 732. udev is there before running the rescue shell. Bruce === Bruce Ward, Nelson, New Zealand PID USER COMMAND 1 0/bin/sh /init 2 0[kthreadd] 3 0[migration/0] 4 0[ksoftirqd/0] 5 0[watchdog/0] 6 0[events/0] 7 0[khelper] 39 0[kblockd/0] 41 0[kacpid] 42 0[kacpi_notify] 149 0[kseriod] 186 0[pdflush] 187 0[pdflush] 188 0[kswapd0] 189 0[aio/0] 396 0udevd --daemon 732 0/bin/sh -i 736 0[ksuspend_usbd] 739 0[khubd] 788 0[scsi_eh_0] 789 0[usb-storage] 842 0[kjournald] 843 0ps
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
On Thu, 11 Feb 2010, Bruce Ward wrote: > Greetings. > > More data. I have managed to get an initramfs debug out of the > system and have also provided a debug from a 2.6.26-1-686 kernel > which boots OK. I'm damned if I can see any reason from the debug > for the recent kernel (2.6.26-2-686) to fail to boot! > > Interesting (but possibly not relevant) observations from my playing > around (exploration). Remember there are only a few modules (thermal > ones) loaded when the system drops out. > > 1. Load USB drivers - they find the pendrive, but no entry created in /dev. > 2. Use mknod to create /dev/sda3 for the ext3 partition on pendrive. > sda3 is the only SCSI entry in /dev. > 3. Load ext3 module, and mount the sda3 partition and, behold, there > are entries in /dev/ for sda, sda1, and sda2, as well as sda3. > 4. Load the SATA drivers and suddenly there are sdb entries in /dev > for all partitions on the drive I have failed to boot from. that points a bit to udev is it running at this stage? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
Greetings.
More data. I have managed to get an initramfs debug out of the system
and have also provided a debug from a 2.6.26-1-686 kernel which boots
OK. I'm damned if I can see any reason from the debug for the recent
kernel (2.6.26-2-686) to fail to boot!
Interesting (but possibly not relevant) observations from my playing
around (exploration). Remember there are only a few modules (thermal
ones) loaded when the system drops out.
1. Load USB drivers - they find the pendrive, but no entry created in /dev.
2. Use mknod to create /dev/sda3 for the ext3 partition on pendrive.
sda3 is the only SCSI entry in /dev.
3. Load ext3 module, and mount the sda3 partition and, behold, there are
entries in /dev/ for sda, sda1, and sda2, as well as sda3.
4. Load the SATA drivers and suddenly there are sdb entries in /dev for
all partitions on the drive I have failed to boot from.
A minor bug (?). ls /bin shows mknod, but trying to use it (/bin/mknod)
gives the error:
/bin/sh: /bin/mknod: not found
I have not tried using mknod to put the partitions in /dev/disk/by-label
where init is expecting to find them, and then continuing the boot
process. Would this be useful?
Does it look as though the process which is supposed to load modules is
failing?
Bruce
===
Bruce Ward, Nelson, New Zealand
+ [ -z ]
+ export resume=/dev/sdb6
+ depmod -a
+ maybe_break top
+ [ = top ]
+ run_scripts /scripts/init-top
+ initdir=/scripts/init-top
+ [ ! -d /scripts/init-top ]
+ get_prereqs
+ set_initlist
+ unset initlist
+ [ /scripts/init-top/all_generic_ide = /scripts/init-top/* ]
+ [ ! -x /scripts/init-top/all_generic_ide ]
+ [ -d /scripts/init-top/all_generic_ide ]
+ initlist= all_generic_ide
+ [ /scripts/init-top/framebuffer = /scripts/init-top/* ]
+ [ ! -x /scripts/init-top/framebuffer ]
+ [ -d /scripts/init-top/framebuffer ]
+ initlist= all_generic_ide framebuffer
+ [ /scripts/init-top/keymap = /scripts/init-top/* ]
+ [ ! -x /scripts/init-top/keymap ]
+ [ -d /scripts/init-top/keymap ]
+ initlist= all_generic_ide framebuffer keymap
+ /scripts/init-top/all_generic_ide prereqs
+ tmp=
+ eval array_all_generic_ide=""
+ array_all_generic_ide=
+ /scripts/init-top/framebuffer prereqs
+ tmp=
+ eval array_framebuffer=""
+ array_framebuffer=
+ /scripts/init-top/keymap prereqs
+ tmp=
+ eval array_keymap=""
+ array_keymap=
+ reduce_prereqs
+ unset runlist
+ set -- all_generic_ide framebuffer keymap
+ i=3
+ [ 3 -ne 0 ]
+ oldi=3
+ reduce_satisfied all_generic_ide
+ render array_all_generic_ide
+ eval echo -n ${array_all_generic_ide}
+ echo -n
+ deplist=
+ unset tmpdeplist
+ deplist=
+ eval array_all_generic_ide=""
+ array_all_generic_ide=
+ render array_all_generic_ide
+ eval echo -n ${array_all_generic_ide}
+ echo -n
+ count_unsatisfied
+ set --
+ return 0
+ cnt=0
+ [ 0 -eq 0 ]
+ runlist= all_generic_ide
+ pop_list_item all_generic_ide all_generic_ide framebuffer keymap
+ item=all_generic_ide
+ shift
+ set -- all_generic_ide framebuffer keymap
+ unset tmppop
+ [ all_generic_ide = all_generic_ide ]
+ continue
+ [ framebuffer = all_generic_ide ]
+ tmppop= framebuffer
+ [ keymap = all_generic_ide ]
+ tmppop= framebuffer keymap
+ initlist= framebuffer keymap
+ i=2
+ reduce_satisfied framebuffer
+ render array_framebuffer
+ eval echo -n ${array_framebuffer}
+ echo -n
+ deplist=
+ unset tmpdeplist
+ deplist=
+ pop_list_item all_generic_ide
+ item=all_generic_ide
+ shift
+ set --
+ unset tmppop
+ deplist=
+ eval array_framebuffer=""
+ array_framebuffer=
+ render array_framebuffer
+ eval echo -n ${array_framebuffer}
+ echo -n
+ count_unsatisfied
+ set --
+ return 0
+ cnt=0
+ [ 0 -eq 0 ]
+ runlist= all_generic_ide framebuffer
+ pop_list_item framebuffer framebuffer keymap
+ item=framebuffer
+ shift
+ set -- framebuffer keymap
+ unset tmppop
+ [ framebuffer = framebuffer ]
+ continue
+ [ keymap = framebuffer ]
+ tmppop= keymap
+ initlist= keymap
+ i=1
+ reduce_satisfied keymap
+ render array_keymap
+ eval echo -n ${array_keymap}
+ echo -n
+ deplist=
+ unset tmpdeplist
+ deplist=
+ pop_list_item all_generic_ide
+ item=all_generic_ide
+ shift
+ set --
+ unset tmppop
+ deplist=
+ pop_list_item framebuffer
+ item=framebuffer
+ shift
+ set --
+ unset tmppop
+ deplist=
+ eval array_keymap=""
+ array_keymap=
+ render array_keymap
+ eval echo -n ${array_keymap}
+ echo -n
+ count_unsatisfied
+ set --
+ return 0
+ cnt=0
+ [ 0 -eq 0 ]
+ runlist= all_generic_ide framebuffer keymap
+ pop_list_item keymap keymap
+ item=keymap
+ shift
+ set -- keymap
+ unset tmppop
+ [ keymap = keymap ]
+ continue
+ initlist=
+ i=0
+ [ 0 -eq 3 ]
+ [ 0 -ne 0 ]
+ call_scripts
+ [ = y ]
+ /scripts/init-top/all_generic_ide
+ [ -e /conf/param.conf ]
+ [ = y ]
+ /scripts/init-top/framebuffer
+ [ -e /conf/param.conf ]
+ [ = y ]
+ /scripts/init-top/keymap
+ [ -e /conf/param.conf ]
+ maybe_break modules
+ [ = modules ]
+ log_begin_msg Loading essential drivers
+ [ -x /sbin/usplash_write ]
+ _log_msg Begin: Loading essential drivers ...
+ [ n
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
maximilian attems wrote: On Thu, 04 Feb 2010, Bruce Ward wrote: Here is the log from a run today. Looking into a real initram image also created today I see that the modules (/lib/modules/2.6.28-2-686/kernel/drivers/ ...) all have a 27 Dec. 2010 date! This is a little surprising as the modules in the directory on the drive all have 2009 (27 Dec.) date. Further, I was not correct in my first posting - the system DOES get to: Loading, please wait ... which might put suspicion on the actual driver modules rather than the initramfs creation. Bruce seen nothing suspicious at first sight, please use rootdelay bootparam and follow http://wiki.debian.org/InitramfsDebug thanks Thanks for the link. I have used the 'break=' parameter but not found anything that looked like solving the problem. Root device does not exist at any stage, nor do the SATA modules get loaded. (I've tried manual loading of all modules I thought might be needed but no luck.) Root boot argument is OK - indicates that I am booting from the disc I expect (there are a number of discs in this machine). I have attached the filelists from the two initrd.img files, there are a number of differences but I can't tell if any of them are significant. What to try next? With further exploration I might be able to do a debug and get the file onto a USB stick. (Manual loading of modules will get the system to recognise a pen-drive even if it will not admit the presence of any hard disc!) Bruce === Bruce Ward, Nelson, New Zealand .. ./init ./usr ./usr/lib ./usr/lib/libglib-2.0.so.0 ./usr/lib/libdirect-1.0.so.0 ./usr/lib/liblzo2.so.2 ./usr/lib/libfusion-1.0.so.0 ./usr/lib/libdirectfb-1.0.so.0 ./usr/lib/libpcre.so.3 ./usr/lib/libgcrypt.so.11 ./usr/lib/libgpg-error.so.0 ./lib ./lib/libgcc_s.so.1 ./lib/libc.so.6 ./lib/libcfont.so.0 ./lib/libsplashycnf.so.1 ./lib/libsplashy.so.1 ./lib/libpthread.so.0 ./lib/libm.so.6 ./lib/modules ./lib/modules/2.6.26-2-686 ./lib/modules/2.6.26-2-686/kernel ./lib/modules/2.6.26-2-686/kernel/drivers ./lib/modules/2.6.26-2-686/kernel/drivers/ssb ./lib/modules/2.6.26-2-686/kernel/drivers/ssb/ssb.ko ./lib/modules/2.6.26-2-686/kernel/drivers/hid ./lib/modules/2.6.26-2-686/kernel/drivers/hid/hid.ko ./lib/modules/2.6.26-2-686/kernel/drivers/hid/usbhid ./lib/modules/2.6.26-2-686/kernel/drivers/hid/usbhid/usbhid.ko ./lib/modules/2.6.26-2-686/kernel/drivers/pcmcia ./lib/modules/2.6.26-2-686/kernel/drivers/pcmcia/pcmcia.ko ./lib/modules/2.6.26-2-686/kernel/drivers/pcmcia/pcmcia_core.ko ./lib/modules/2.6.26-2-686/kernel/drivers/usb ./lib/modules/2.6.26-2-686/kernel/drivers/usb/core ./lib/modules/2.6.26-2-686/kernel/drivers/usb/core/usbcore.ko ./lib/modules/2.6.26-2-686/kernel/drivers/usb/storage ./lib/modules/2.6.26-2-686/kernel/drivers/usb/storage/usb-storage.ko ./lib/modules/2.6.26-2-686/kernel/drivers/usb/host ./lib/modules/2.6.26-2-686/kernel/drivers/usb/host/ehci-hcd.ko ./lib/modules/2.6.26-2-686/kernel/drivers/usb/host/uhci-hcd.ko ./lib/modules/2.6.26-2-686/kernel/drivers/usb/host/ohci-hcd.ko ./lib/modules/2.6.26-2-686/kernel/drivers/message ./lib/modules/2.6.26-2-686/kernel/drivers/message/i2o ./lib/modules/2.6.26-2-686/kernel/drivers/message/i2o/i2o_core.ko ./lib/modules/2.6.26-2-686/kernel/drivers/message/i2o/i2o_block.ko ./lib/modules/2.6.26-2-686/kernel/drivers/message/fusion ./lib/modules/2.6.26-2-686/kernel/drivers/message/fusion/mptscsih.ko ./lib/modules/2.6.26-2-686/kernel/drivers/message/fusion/mptspi.ko ./lib/modules/2.6.26-2-686/kernel/drivers/message/fusion/mptbase.ko ./lib/modules/2.6.26-2-686/kernel/drivers/message/fusion/mptfc.ko ./lib/modules/2.6.26-2-686/kernel/drivers/message/fusion/mptsas.ko ./lib/modules/2.6.26-2-686/kernel/drivers/video ./lib/modules/2.6.26-2-686/kernel/drivers/video/vgastate.ko ./lib/modules/2.6.26-2-686/kernel/drivers/video/vga16fb.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide ./lib/modules/2.6.26-2-686/kernel/drivers/ide/ide-floppy.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/ide-core.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/ide-cd_mod.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/legacy ./lib/modules/2.6.26-2-686/kernel/drivers/ide/legacy/ide-cs.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/ide-tape.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/pdc202xx_new.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/siimage.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/hpt34x.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/aec62xx.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/amd74xx.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/slc90e66.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/opti621.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/trm290.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/it821x.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/alim15x3.ko ./lib/modules/2.6.26-2-686/kernel/drivers/ide/pci/ns87415.k
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
On Thu, 04 Feb 2010, Bruce Ward wrote: > Here is the log from a run today. > > Looking into a real initram image also created today I see that the > modules (/lib/modules/2.6.28-2-686/kernel/drivers/ ...) all have a > 27 Dec. 2010 date! This is a little surprising as the modules in the > directory on the drive all have 2009 (27 Dec.) date. > > Further, I was not correct in my first posting - the system DOES get to: >Loading, please wait ... > > which might put suspicion on the actual driver modules rather than > the initramfs creation. > > Bruce > seen nothing suspicious at first sight, please use rootdelay bootparam and follow http://wiki.debian.org/InitramfsDebug thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
[ please keep bug report on cc, otherwise your mail may get lost, thanks ] On Wed, 21 Oct 2009, Bruce Ward wrote: > > > > > >please post output of: > >sh -x mkinitramfs -o /dev/null > > > > How do I do that? > Simple redirection (sh -x mkinitramfs -o /dev/null > mkramfs) gives > a zero length file. include stderr in redirect: sh -x mkinitramfs -o /dev/null/ > initramfs.log 2>&1 can you still reproduce the original bug? sorry for late reply but your mail got really lost.. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
On Tue, Oct 20, 2009 at 09:37:23PM +1300, Bruce Ward wrote: > Package: linux-image-2.6.26-2-686 > Version: 2.6.26-19 > Severity: important > > Kernel image 2.6.26-1-686 is no problem. 2.6.26-2-686 drops me to a shell > titled (initramfs) shortly after issuing the message: > "Booting the kernel." > It never gets to "Loading, please wait ..." > > Before I get control there are a (large) number of screen messages of the > form: > /init: line1: /bin/sleep: not found > and then > "Gave up waiting for root device" > and > "ALERT! /dev/disk/by-label/D5root does not exist. Dropping to a shell! > > At this stage, looking at the filesystem available in initramfs: > there is no /dev/disk/ directory although /dev exists, > /proc/modules contains only thermal_sys, fan, processor, and thermal, > /lib/modules/2.6.26-2-686/ appears well-populated, > /sbin contains only 7 files (depmod, modprobe, resume, rmmod, udevadm, > udevd, udevsettle), > /bin/sleep exists so the multiple /init errors are not looking for > /bin/sleep. > > I am using GRUB (legacy) and root=LABEL statements identical to the ones > which boot 2.6.26-1-686 without any problem. I have regenerated the > initrd-img a number of times to no effect. > > please post output of: sh -x mkinitramfs -o /dev/null -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
Package: linux-image-2.6.26-2-686 Version: 2.6.26-19 Severity: important Kernel image 2.6.26-1-686 is no problem. 2.6.26-2-686 drops me to a shell titled (initramfs) shortly after issuing the message: "Booting the kernel." It never gets to "Loading, please wait ..." Before I get control there are a (large) number of screen messages of the form: /init: line1: /bin/sleep: not found and then "Gave up waiting for root device" and "ALERT! /dev/disk/by-label/D5root does not exist. Dropping to a shell! At this stage, looking at the filesystem available in initramfs: there is no /dev/disk/ directory although /dev exists, /proc/modules contains only thermal_sys, fan, processor, and thermal, /lib/modules/2.6.26-2-686/ appears well-populated, /sbin contains only 7 files (depmod, modprobe, resume, rmmod, udevadm, udevd, udevsettle), /bin/sleep exists so the multiple /init errors are not looking for /bin/sleep. I am using GRUB (legacy) and root=LABEL statements identical to the ones which boot 2.6.26-1-686 without any problem. I have regenerated the initrd-img a number of times to no effect. -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-686 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-2-686 recommends: ii libc6-i6862.7-18 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-2-686 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 (no description available) -- debconf information: linux-image-2.6.26-2-686/postinst/bootloader-error-2.6.26-2-686: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-2-686/postinst/old-dir-initrd-link-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/overwriting-modules-2.6.26-2-686: true linux-image-2.6.26-2-686/postinst/bootloader-test-error-2.6.26-2-686: linux-image-2.6.26-2-686/postinst/depmod-error-2.6.26-2-686: false linux-image-2.6.26-2-686/preinst/bootloader-initrd-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/abort-overwrite-2.6.26-2-686: linux-image-2.6.26-2-686/preinst/abort-install-2.6.26-2-686: linux-image-2.6.26-2-686/postinst/depmod-error-initrd-2.6.26-2-686: false linux-image-2.6.26-2-686/postinst/create-kimage-link-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/failed-to-move-modules-2.6.26-2-686: linux-image-2.6.26-2-686/preinst/initrd-2.6.26-2-686: linux-image-2.6.26-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-2-686/prerm/would-invalidate-boot-loader-2.6.26-2-686: true linux-image-2.6.26-2-686/postinst/kimage-is-a-directory: linux-image-2.6.26-2-686/postinst/old-initrd-link-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/elilo-initrd-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/lilo-initrd-2.6.26-2-686: true linux-image-2.6.26-2-686/prerm/removing-running-kernel-2.6.26-2-686: true linux-image-2.6.26-2-686/postinst/old-system-map-link-2.6.26-2-686: true -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
