On Sat, Jun 21, 2008 at 07:43:37PM +0200, Valentin QUEQUET wrote: > Package: linux-image-2.6.25-2-amd64 > Version: 2.6.25-5 > Severity: grave > Justification: renders package unusable
learn to set severities, not working on *one* box is not grave > 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 read http://wiki.debian.org/InitramfsDebug and provide info based on that. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
