Bug#474670: initramfs-tools: [alpha] boot failure with linux-image-2.6.22-3-alpha-generic
On Mon, 21 Apr 2008 15:57:58 +0200, maximilian attems wrote: it's very easy if you have the cable and just use screen and console=ttyS0 otherwise there are very cheap usb to serial adapters or you could use netconsole if that's more appealing to you. I understand you need output from serial console but I'm afraid it is not so easy as you think. I search enough infomation by googling etc. and if I can get bootlog, I'll report it here but I'm certain it will not happen in near future. In bug #473877, it seems I need to fiddle with swriteboot to boot with 2.6.24 (sigh). Regards,2008-4-24(Thu) -- Debian Developer - much more I18N of Debian Atsuhito Kohda kohda AT debian.org Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474670: initramfs-tools: [alpha] boot failure with linux-image-2.6.22-3-alpha-generic
On Wed, 9 Apr 2008 09:01:07 +0200, maximilian attems wrote: hmm could i see a bootlog of that box? with aboves initramfs or any other 2.6.22 generated with initramfs-tools any alpha box should have a serial console. I'm currently fishing in the dark without the bootlog. Sorry but I've never tried serial console and I'm afraid it is too much for me to do that at present. Regards,2008-4-21(Mon) -- Debian Developer - much more I18N of Debian Atsuhito Kohda kohda AT debian.org Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474670: initramfs-tools: [alpha] boot failure with linux-image-2.6.22-3-alpha-generic
On Mon, Apr 21, 2008 at 05:38:15PM +0900, Atsuhito Kohda wrote: On Wed, 9 Apr 2008 09:01:07 +0200, maximilian attems wrote: hmm could i see a bootlog of that box? with aboves initramfs or any other 2.6.22 generated with initramfs-tools any alpha box should have a serial console. I'm currently fishing in the dark without the bootlog. Sorry but I've never tried serial console and I'm afraid it is too much for me to do that at present. it's very easy if you have the cable and just use screen and console=ttyS0 otherwise there are very cheap usb to serial adapters or you could use netconsole if that's more appealing to you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474670: initramfs-tools: [alpha] boot failure with linux-image-2.6.22-3-alpha-generic
On Wed, Apr 09, 2008 at 02:02:11PM +0900, Atsuhito Kohda wrote: On Tue, 8 Apr 2008 16:36:36 +0200, maximilian attems wrote: could you please force it load with initramfs-tools: echo sym53c8xx /etc/initramfs-tools/modules update-initramfs -t -c -k 2.6.22-3-alpha-generic Unfortunately this doesn't help. hmm could i see a bootlog of that box? with aboves initramfs or any other 2.6.22 generated with initramfs-tools any alpha box should have a serial console. I'm currently fishing in the dark without the bootlog. thanks a lot for your efforts. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474670: initramfs-tools: [alpha] boot failure with linux-image-2.6.22-3-alpha-generic
On Tue, 8 Apr 2008 11:54:13 +0200, maximilian attems wrote: that is at the very top of the boot, what happens if you pass as boot arg break=top, do you land in initramfs shell? also try to add rootdelay=9 or such. Not yet. I'll try it later if possible. ok can you put them up somewhere, so that i can take a look if they look sane, before further debugging, also i'd need the output of sh -x mkinitramfs -o /tmp/foo I put all initrd.img-* and the output of mkinitramfs in http://www1.pm.tokushima-u.ac.jp/~kohda/alpha/ Thanks for your kind advices. Regards,2008-4-8(Tue) -- Debian Developer - much more I18N of Debian Atsuhito Kohda kohda AT debian.org Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474670: initramfs-tools: [alpha] boot failure with linux-image-2.6.22-3-alpha-generic
On Tue, Apr 08, 2008 at 10:48:15PM +0900, Atsuhito Kohda wrote: On Tue, 8 Apr 2008 11:54:13 +0200, maximilian attems wrote: that is at the very top of the boot, what happens if you pass as boot arg break=top, do you land in initramfs shell? also try to add rootdelay=9 or such. Not yet. I'll try it later if possible. okay not so important as belows try. I put all initrd.img-* and the output of mkinitramfs in http://www1.pm.tokushima-u.ac.jp/~kohda/alpha/ had a look at the initramfs and looked sane. as your root dev scsi driver seems to be sym53c8xx, could you please force it load with initramfs-tools: echo sym53c8xx /etc/initramfs-tools/modules update-initramfs -t -c -k 2.6.22-3-alpha-generic (-t is for takeover you have a backup of the yaird initramfs.) this smells like a kernel bug with sym53c8xx not properly loaded due to having some ressources stolen. the mkinitramfs ouput has not the eventual errors, so it looks sane. please use mkinitramfs -o /tmp/foo /tmp/mkinitramfs.log 21 thanks for the quick feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474670: initramfs-tools: [alpha] boot failure with linux-image-2.6.22-3-alpha-generic
On Tue, Apr 08, 2008 at 04:36:36PM +0200, maximilian attems wrote: On Tue, Apr 08, 2008 at 10:48:15PM +0900, Atsuhito Kohda wrote: On Tue, 8 Apr 2008 11:54:13 +0200, maximilian attems wrote: that is at the very top of the boot, what happens if you pass as boot arg break=top, do you land in initramfs shell? also try to add rootdelay=9 or such. Not yet. I'll try it later if possible. okay not so important as belows try. I put all initrd.img-* and the output of mkinitramfs in http://www1.pm.tokushima-u.ac.jp/~kohda/alpha/ had a look at the initramfs and looked sane. as your root dev scsi driver seems to be sym53c8xx, could you please force it load with initramfs-tools: echo sym53c8xx /etc/initramfs-tools/modules update-initramfs -t -c -k 2.6.22-3-alpha-generic (-t is for takeover you have a backup of the yaird initramfs.) this smells like a kernel bug with sym53c8xx not properly loaded due to having some ressources stolen. FWIW, I've been seeing issues on my alpha with udev not correctly autoloading modules in sid. If force-loading the module fixes it, we may be looking at the same issue; dunno if it's a kernel or udev bug, haven't had time to dig into it. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474670: initramfs-tools: [alpha] boot failure with linux-image-2.6.22-3-alpha-generic
On Tue, 8 Apr 2008 16:36:36 +0200, maximilian attems wrote: as your root dev scsi driver seems to be sym53c8xx, Right, lsmod in running system showed us; kohda:~$ /sbin/lsmod | grep scsi scsi_transport_spi 33673 1 sym53c8xx scsi_mod 189352 4 libata,sd_mod,sym53c8xx,scsi_transport_spi could you please force it load with initramfs-tools: echo sym53c8xx /etc/initramfs-tools/modules update-initramfs -t -c -k 2.6.22-3-alpha-generic Unfortunately this doesn't help. kohda:~$ cat /etc/initramfs-tools/modules # List of modules that you want to include in your initramfs. # # Syntax: module_name [args ...] # # You must run update-initramfs(8) to effect this change. # # Examples: # # raid1 # sd_mod sym53c8xx and after I did update-initramfs -t -c -k 2.6.22-3-alpha-generic kohda:~$ ls -l /boot/initrd.img-2.6.2* -rw--- 1 root root 1402449 2007-09-10 07:30 /boot/initrd.img-2.6.22-2-alpha-generic -rw-r--r-- 1 root root 7674776 2008-04-09 13:25 /boot/initrd.img-2.6.22-3-alpha-generic -rw-r--r-- 1 root root 7767549 2008-02-19 09:35 /boot/initrd.img-2.6.22-3-alpha-generic.bak -rw--- 1 root root 1358737 2008-02-19 13:05 /boot/initrd.img-2.6.22-3-alpha-generic.yaird -rw--- 1 root root 1333218 2008-04-01 10:48 /boot/initrd.img-2.6.24-1-alpha-generic Settings for aboot are as follows; kohda:~$ ls -l /initrd.img* lrwxrwxrwx 1 root root 38 2008-03-29 18:19 /initrd.img - boot/initrd.img-2.6.24-1-alpha-generic lrwxrwxrwx 1 root root 38 2007-10-31 07:20 /initrd.img.old - boot/initrd.img-2.6.22-3-alpha-generic lrwxrwxrwx 1 root root 38 2008-04-03 13:33 /initrd.img.osafe - boot/initrd.img-2.6.22-2-alpha-generic lrwxrwxrwx 1 root root 44 2008-04-03 13:30 /initrd.img.safe - boot/initrd.img-2.6.22-3-alpha-generic.yaird kohda:~$ cat /etc/aboot.conf 0:1/vmlinuz ro root=/dev/sda1 initrd=/initrd.img 1:1/vmlinuz.old ro root=/dev/sda1 initrd=/initrd.img.old 2:1/vmlinuz ro root=/dev/sda1 initrd=/initrd.img single 3:1/vmlinuz.2.2 ro root=/dev/sda1 4:1/vmlinuz ro root=/dev/sdb2 5:1/vmlinuz.safe ro root=/dev/sda1 initrd=/initrd.img.safe 6:1/vmlinuz.osafe ro root=/dev/sda1 initrd=/initrd.img.osafe 7:1/vmlinuz.old ro root=/dev/sda1 initrd=/initrd.img.old rootdelay=9 I booted with pressing a key l and then a key 1 for aboot prompt(?) but it stopped in the same stage; Input: AT Translated Set 2 keyboard as /class/input/input0 The system is running with kernel 2.6.22-2 at present. Really thanks for your help. Regards,2008-4-9(Wed) -- Debian Developer - much more I18N of Debian Atsuhito Kohda kohda AT debian.org Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474670: initramfs-tools: [alpha] boot failure with linux-image-2.6.22-3-alpha-generic
Package: initramfs-tools Version: 0.91e Severity: important Hi, I encountered the following boot failure on my alpha machine. When linux-image-2.6.22-3-alpha-generic came into testing, my system failed to boot with the initrd.img generated by initramfs-tools but it still booted with the initrd.img generated by yaird so I suspect this is a bug of initramfs-tools. However, linux-image-2.6.24-alpha-generic failed to boot with initrd.img generated both initramfs-tools and yaird. The messages when it failed to boot were as follows: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice EISA: Probing bus 0 at eisa.0 TCP sic registered NET: Registered protocol family 1 NET: Registered protocol family 17 Freeing unused kernel memory: 288k freed Loading, please wait... Input: AT Translated Set 2 keyboard as /class/input/input0 and it stopped there. The outputs of ls -l /boot/initrd.img-2.6.2* -rw--- 1 root root 1402449 2007-09-10 07:30 /boot/initrd.img-2.6.22-2-alpha-generic -rw-r--r-- 1 root root 7670981 2008-04-07 13:49 /boot/initrd.img-2.6.22-3-alpha-generic -rw-r--r-- 1 root root 7767549 2008-02-19 09:35 /boot/initrd.img-2.6.22-3-alpha-generic.bak -rw--- 1 root root 1358737 2008-02-19 13:05 /boot/initrd.img-2.6.22-3-alpha-generic.yaird -rw--- 1 root root 1333218 2008-04-01 10:48 /boot/initrd.img-2.6.24-1-alpha-generic initrd.img-2.6.22-3-alpha-generic.yaird is what I backed up for later use if necessary. initrd.img-2.6.22-3-alpha-generic is what initramfs-tools geneted this morning. I booted with 2.6.22-2 and generated initrd.img with a command dpkg-reconfigure linux-image-2.6.22-3-alpha-generic after setting up /etc/kernel-img.conf for initramfs-tools. Regards. -- Package-specific info: -- /proc/cmdline ro root=/dev/sda1 -- /proc/filesystems ext2 cramfs -- lsmod Module Size Used by tcp_diag2264 0 inet_diag 15064 1 tcp_diag nf_conntrack_ipv4 24872 7 xt_state3248 7 nf_conntrack 84600 2 nf_conntrack_ipv4,xt_state nfnetlink 8376 2 nf_conntrack_ipv4,nf_conntrack xt_tcpudp 4312 9 iptable_filter 3780 1 ip_tables 15720 1 iptable_filter x_tables 19920 3 xt_state,xt_tcpudp,ip_tables ipv6 339256 30 pcspkr 4104 0 ide_cd 51032 0 cdrom 45984 1 ide_cd ata_generic 9164 0 libata153080 1 ata_generic generic 6580 0 [permanent] tsdev 10876 0 tulip 70184 0 psmouse54560 0 bitrev 2368 1 tulip cmd64x 13448 0 [permanent] serio_raw 8764 0 ide_core 151240 3 ide_cd,generic,cmd64x sd_mod 35688 5 sym53c8xx 95328 3 scsi_transport_spi 33673 1 sym53c8xx scsi_mod 189352 4 libata,sd_mod,sym53c8xx,scsi_transport_spi evdev 12816 0 fbcon 50456 0 tileblit3616 1 fbcon crc32 4800 2 tulip,fbcon font8904 1 fbcon bitblit 7584 1 fbcon fbcon_rotate3952 1 bitblit fbcon_cw7896 1 fbcon_rotate fbcon_ud7960 1 fbcon_rotate fbcon_ccw 7960 1 fbcon_rotate softcursor 2920 4 bitblit,fbcon_cw,fbcon_ud,fbcon_ccw -- /etc/kernel-img.conf # Do not create symbolic links in / do_symlinks = Yes #ramdisk = mkinitrd.yaird -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: alpha Kernel: Linux 2.6.22-2-alpha-generic Locale: LANG=ja_JP.EUC-JP, LC_CTYPE=ja_JP.EUC-JP (charmap=EUC-JP) Shell: /bin/sh linked to /bin/bash Versions of packages initramfs-tools depends on: ii cpio 2.9-12 GNU cpio -- a program to manage ar ii findutils4.2.33-1utilities for finding files--find, ii klibc-utils 1.5.7-4 small statically-linked utilities ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo ii udev 0.114-2 /dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.1.3-5 Tiny utilities for small and embed -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
