Bug#494422: Processed: Re: Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot
Sorry for the late reply :( $cat /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = yes do_bootfloppy = no do_initrd = yes link_in_boot = no On Thu, Aug 14, 2008 at 1:11 PM, maximilian attems <[EMAIL PROTECTED]> wrote: > On Thu, Aug 14, 2008 at 09:27:08AM +, Debian Bug Tracking System wrote: >> Processing commands for [EMAIL PROTECTED]: >> >> > reassign 494422 initramfs-tools >> Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel >> panic on next reboot >> Bug reassigned from package `lilo' to `initramfs-tools'. > > post the ouput of > cat /etc/kernel-img.conf > > > -- > maks > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494422: Processed: Re: Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot
On Thu, Aug 14, 2008 at 09:27:08AM +, Debian Bug Tracking System wrote: > Processing commands for [EMAIL PROTECTED]: > > > reassign 494422 initramfs-tools > Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel > panic on next reboot > Bug reassigned from package `lilo' to `initramfs-tools'. post the ouput of cat /etc/kernel-img.conf -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot
Processing commands for [EMAIL PROTECTED]: > reassign 494422 initramfs-tools Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot Bug reassigned from package `lilo' to `initramfs-tools'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot
Hello, thank you very much for your insights Martin. I was able to solve the problem. I updated lilo to 1:22.8-6 and rebooted... another kernel panic. Then added the line "large-memory" in /etc/lilo.conf and this time I was able to reboot the system using the new kernel :D Then I installed grub on the first partition of my drive (some people will want it on the MBR isntead) grub-install /dev/sda1 And after another reboot I removed lilo. The bug is with lilo, which should add the "large-memory" line in lilo.conf. At the very least issue a warning. I would suggest initramfs-tools to ask the user which bootloader he is using when both lilo and grub are detected. Or at least issue a warning like "lilo was executed, but you may want grub instead, in that case run it yourself by ..." This bug should be changed to minor or wishlist. Thanks and regards. PS: after all of this I'm unsure if I should update my grub package :-/ heh On Sat, Aug 9, 2008 at 12:57 PM, Martin Michlmayr <[EMAIL PROTECTED]> wrote: > * Monkey D. Luffy <[EMAIL PROTECTED]> [2008-08-09 12:05]: >> I reboot the system and surprise: grub was *overwritten* by lilo!!! >> I try to boot anyway... and another surprise: >> >> ramdisk: couldn't find valid ram disk image starting at 0 >> list of all partitions: >> no filesystem could mount root, tried: >> kernel panic - not syncing: VFS: unable to mount root fs in unknown-block >> (8,1) > > This is a known bug in lilo, see #479607 Although I see it was > fixed in version 1:22.8-6. Which version of lilo do you have > installed? > I had 1:22.8-3, in which #479607 was open (by looking at debian changelog), since it was only fixed in 1:22.8-5. I have now upgraded to 1:22.8-6 but it didn't fix me the problem. I get the same kernel panic error. >> I reboot the system and surprise: grub was *overwritten* by lilo!!! > > Maybe this is what happens when you have both grub and lilo installed. > But I don't know. > It could be it. It was stupid of me to have both boot loaders... maybe some dependency or suggestions made me install it... I don't know. But ideally it should detect which bootloader is being used and use it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot
Processing commands for controlbugs.debian.org: > reassign 494422 lilo Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot Bug reassigned from package `initramfs-tools' to `lilo'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot
* Monkey D. Luffy <[EMAIL PROTECTED]> [2008-08-09 12:05]: > I reboot the system and surprise: grub was *overwritten* by lilo!!! > I try to boot anyway... and another surprise: > > ramdisk: couldn't find valid ram disk image starting at 0 > list of all partitions: > no filesystem could mount root, tried: > kernel panic - not syncing: VFS: unable to mount root fs in unknown-block > (8,1) This is a known bug in lilo, see #479607 Although I see it was fixed in version 1:22.8-6. Which version of lilo do you have installed? > I reboot the system and surprise: grub was *overwritten* by lilo!!! Maybe this is what happens when you have both grub and lilo installed. But I don't know. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot
Package: initramfs-tools Version: 0.92e Severity: critical --- Please enter the report below this line. --- NOTE: I am reporting this bug from my old kernel. The bug happened when I was running 2.6.26-1-amd64 and updated initramfs-tools and then rebooted. So I'm not sure how usefull is the system and modules information. After upgrading initramfs-tools from 0.89 to 0.92e. The output was: == Setting up initramfs-tools (0.92e) ... Installing new version of config file /etc/initramfs-tools/update-initramfs.conf ... update-initramfs: Generating /boot/initrd.img-2.6.26-1-amd64 Warning: LBA32 addressing assumed Warning: /dev/sda1 is not on the first disk Added Linux * Added LinuxOLD 2 warnings were issued. == I reboot the system and surprise: grub was *overwritten* by lilo!!! I try to boot anyway... and another surprise: ramdisk: couldn't find valid ram disk image starting at 0 list of all partitions: no filesystem could mount root, tried: kernel panic - not syncing: VFS: unable to mount root fs in unknown-block (8,1) According to cat /proc/partitions (8,1) is sda1, which is my boot partition. (my MBR has another boot loader) Fortunately I had my old 2.6.21, otherwise I wouldn't be able to boot from my computer. I checked initramfs contents according to http://wiki.debian.org/InitramfsDebug I'm attaching the diff file. (hurray for initramfs making a backup of the initrd.img) How do I generate a valid initrd.img? Why was grub overwritten by lilo? Will running "grub-install (hd0,0)" fix the problem? Thank you for any help. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.21-2-amd64 Debian Release: lenny/sid 990 testing www.debian-multimedia.org 990 testing security.debian.org 990 testing ftp.debian.org 990 testing ftp.de.debian.org 500 unstablewww.debian-multimedia.org 500 unstableftp.debian.org 500 unstableftp.de.debian.org 500 unstabledeb.opera.com 500 stable security.debian.org --- Package information. --- Depends (Version) | Installed ==-+-= klibc-utils (>= 1.5.9-1) | 1.5.12-1 cpio | 2.7-3 module-init-tools | 3.3-pre11-4 udev (>= 0.086-1) | 0.105-4 findutils (>= 4.2.24) | 4.2.32-1 --- Output from package bug script --- -- /proc/cmdline BOOT_IMAGE=LinuxOLD ro root=801 bootkbd=pt -- /proc/filesystems cramfs ext3 fuseblk -- lsmod Module Size Used by ipt_MASQUERADE 8192 1 iptable_nat12292 1 nf_nat 25132 2 ipt_MASQUERADE,iptable_nat binfmt_misc17164 1 cpufreq_ondemand 13200 2 cpufreq_userspace 9472 0 cpufreq_powersave 6272 0 acpi_cpufreq 13704 0 freq_table 9600 2 cpufreq_ondemand,acpi_cpufreq rfcomm 48424 4 l2cap 32640 9 rfcomm bluetooth 64004 4 rfcomm,l2cap ppdev 13704 0 parport_pc 41512 0 lp 17352 0 parport44428 3 ppdev,parport_pc,lp button 13472 0 ac 10376 0 battery15624 0 ipv6 295936 18 xt_limit7552 1 xt_tcpudp 7936 9 nf_conntrack_ipv4 24592 6 iptable_nat xt_state7040 4 nf_conntrack 73308 5 ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state nfnetlink 11720 3 nf_nat,nf_conntrack_ipv4,nf_conntrack iptable_filter 7552 1 ip_tables 24296 2 iptable_nat,iptable_filter x_tables 24968 6 ipt_MASQUERADE,iptable_nat,xt_limit,xt_tcpudp,xt_state,ip_tables fuse 50480 1 dm_snapshot21192 0 dm_mirror 25664 0 dm_mod 64656 2 dm_snapshot,dm_mirror sbp2 28292 0 loop 22032 2 snd_emu10k1_synth 11904 0 snd_emux_synth 39424 1 snd_emu10k1_synth snd_seq_virmidi11904 1 snd_emux_synth snd_seq_midi_emul 10880 1 snd_emux_synth snd_emu10k1 141792 2 snd_emu10k1_synth snd_ac97_codec116824 1 snd_emu10k1 ac97_bus7040 1 snd_ac97_codec snd_util_mem9600 2 snd_emux_synth,snd_emu10k1 snd_hwdep 14728 2 snd_emux_synth,snd_emu10k1 tsdev 12928 0 bt878 16232 0 snd_hda_intel 26784 2 snd_hda_codec 260608 1 snd_hda_intel snd_pcm_oss48416 0 snd_mixer_oss 21376 1 snd_pcm_oss snd_pcm89608 5 snd_emu10k1,snd_ac97_codec,snd_hda_intel,snd_hda_codec,snd_pcm_oss tuner 65960 0 snd_seq_dummy 8452 0 snd_seq_midi 13504 0 msp340034976 0 snd_s
