Your message dated Sun, 29 Jun 2008 16:44:43 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Early boot-time kernel panic with
linux-image-2.6.25-2-amd64 (2.6.25-5).
has caused the Debian Bug report #487421,
regarding Early boot-time kernel panic with linux-image-2.6.25-2-amd64
(2.6.25-5).
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 [EMAIL PROTECTED]
immediately.)
--
487421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487421
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-5
Severity: grave
Justification: renders package unusable
Hello all,
I experience early boot-time kernel panic with linux-image-2.6.25-2-amd64
(2.6.25-5)
on my amd64 box.
After having read tons of posts on forums, and particularly:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482773
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479101
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607#96
I know that the bug I discovered is closely related to already reported bug
#479607
which apparently concerns lilo because:
The bug - kernel panic - happens just before any piece of userspace code being
loaded from initial RAM disk :
=======================================
RAMDISK: Couldn't find valid RAM disk image starting at 0.
List of all partitions :
0100 65536 ram0 (driver?)
..
..
..
010f 65536 ram15 (driver?)
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(22,65)
=======================================
But I have to add food for thought:
Here follow key files on my Debian_amd64 system:
ls -l /boot gave: ( cropped the list to meaningful parts )
-rw-r--r-- 1 root root 6621847 jun 21 11:19 initrd.img-2.6.18-6-amd64
-rw------- 1 root root 7090895 jun 21 09:40 initrd.img-2.6.24-1-amd64
-rw-r--r-- 1 root root 7276007 jun 21 11:41 initrd.img-2.6.25-2-amd64
-rw-r--r-- 1 root root 21132800 jun 21 18:03 initrd.img-2.6.25-2-amd64.cpio
-rw-r--r-- 1 root root 5598429 jun 21 18:06 initrd.img-2.6.25-2-amd64_light
-rw-r--r-- 1 root root 16109056 jun 21 18:12
initrd.img-2.6.25-2-amd64_light.cpio
-rw-r--r-- 1 root root 1512362 jun 6 09:20 vmlinuz-2.6.18-6-amd64
-rw-r--r-- 1 root root 1668248 mai 10 11:32 vmlinuz-2.6.24-1-amd64
-rw-r--r-- 1 root root 1727488 jun 12 18:35 vmlinuz-2.6.25-2-amd64
ls -l /boot/initrd.img-2.6.*amd64{,_light}{,.cpio} gave: ( cropped the list to
meaningful parts )
/boot/initrd.img-2.6.18-6-amd64: gzip compressed data, from Unix,
last modified: Sat Jun 21 11:19:01 2008
/boot/initrd.img-2.6.24-1-amd64: gzip compressed data, from Unix,
last modified: Sat Jun 21 09:40:50 2008
/boot/initrd.img-2.6.25-2-amd64: gzip compressed data, from Unix,
last modified: Sat Jun 21 11:41:17 2008
/boot/initrd.img-2.6.25-2-amd64.cpio: ASCII cpio archive (SVR4 with no
CRC)
/boot/initrd.img-2.6.25-2-amd64_light: gzip compressed data, from Unix,
last modified: Sat Jun 21 18:06:31 2008, max compression
/boot/initrd.img-2.6.25-2-amd64_light.cpio: ASCII cpio archive (SVR4 with no
CRC)
WHERE initrd.img-2.6.25-2-amd64_light is a manually lightened customization of
the
original initrd.
Finally, since I only experience trouble - very early kernel panic - with
2.6.25-2-amd64
regardless wether my initrd is heavy or not, how do you explain this strange
behavior ?
In hope my report will prove useful.
Sincerely,
Valentin QUEQUET
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.25-2-amd64 depends on:
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92b tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
linux-image-2.6.25-2-amd64 recommends no packages.
-- debconf information:
linux-image-2.6.25-2-amd64/preinst/abort-overwrite-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/postinst/create-kimage-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/failed-to-move-modules-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/postinst/depmod-error-2.6.25-2-amd64: false
linux-image-2.6.25-2-amd64/postinst/bootloader-test-error-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/prerm/would-invalidate-boot-loader-2.6.25-2-amd64:
true
linux-image-2.6.25-2-amd64/postinst/old-dir-initrd-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/lilo-has-ramdisk:
linux-image-2.6.25-2-amd64/preinst/bootloader-initrd-2.6.25-2-amd64: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.25-2-amd64/prerm/removing-running-kernel-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/old-initrd-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/abort-install-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/postinst/kimage-is-a-directory:
linux-image-2.6.25-2-amd64/postinst/old-system-map-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/overwriting-modules-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/depmod-error-initrd-2.6.25-2-amd64: false
linux-image-2.6.25-2-amd64/preinst/elilo-initrd-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/bootloader-error-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/preinst/lilo-initrd-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/initrd-2.6.25-2-amd64:
--- End Message ---
--- Begin Message ---
closing as dupllicate report of that lilo trouble.
afaik the trouble has not been debugged yet on the lilo side.
not much intiative from upstream as no other distro still shipps it.
--
maks
--- End Message ---
