Debian Bug report logs - #606976
Kernel panic with Squeeze (AMD64) d-i beta 2

Package: debian-installer; Maintainer for debian-installer is Debian Install System Team <debian-boot@lists.debian.org>; Source for debian-installer is src:debian-installer.

Reported by: Taro Sato <ubutsu@gmail.com>

Date: Mon, 13 Dec 2010 15:51:02 UTC

Severity: normal

Tags: moreinfo

Done: Holger Levsen <holger@layer-acht.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Install Team <debian-boot@lists.debian.org>:
Bug#606976; Package installation-reports. (Mon, 13 Dec 2010 15:51:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Taro Sato <ubutsu@gmail.com>:
New Bug report received and forwarded. Copy sent to Debian Install Team <debian-boot@lists.debian.org>. (Mon, 13 Dec 2010 15:51:05 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Taro Sato <ubutsu@gmail.com>
To: submit@bugs.debian.org
Subject: Kernel panic with Squeeze (AMD64) d-i beta 2
Date: Mon, 13 Dec 2010 11:49:40 -0400
Package: installation-reports

Boot method: CD and USB stick
Image version: http://cdimage.debian.org/cdimage/squeeze_di_beta2/amd64/iso-cd/debian-squeeze-di-beta2-amd64-netinst.iso
Date: Dec 13, 2010

Machine: Dell XPS 630i
Processor: Core 2 Quad 2.4 GHz
Memory: 4 GB
Partitions: N/A

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [E ]
Detect network card:    [ ]
Configure network:      [ ]
Detect CD:              [ ]
Load installer modules: [ ]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Install base system:    [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [E ]

Comments/Problems:

I've tried d-i beta 2 on Dell XPS 630i.  I first tried creating a USB
memory stick with the installer .iso on it (following a standard
procedure); the install USB stick works on my other computer (Lenovo
T410s).  However, on 630i it always fails at the beginning of the
install process.  The message, when kernel panics, typically goes like
this:

... (no apparent error messages thru this point) ...
[0.597991] List of all partitions:
[0.600310] No filesystem could mount root, tried:
[0.602749] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(8,3)
... (call trace output after this) ...

(This output is from an attempt to use CD install medium.)

I have tried adding rootdelay=10 option for the kernel, without any effect.

I have observed the same symptom with the netinst .iso burned on a
blank CD.  In fact, I have never been able to use d-i successfully on
630i (I've tried the same thing several months ago).  Last time I
installed Debian, I had to install off a Lenny install medium and then
do dist-upgrade.

Is there any way to get Squeeze d-i to work on this machine?  Any help
is appreciated.




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install Team <debian-boot@lists.debian.org>:
Bug#606976; Package installation-reports. (Thu, 16 Dec 2010 16:30:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ferenc Wagner <wferi@niif.hu>:
Extra info received and forwarded to list. Copy sent to Debian Install Team <debian-boot@lists.debian.org>. (Thu, 16 Dec 2010 16:30:03 GMT) Full text and rfc822 format available.

Message #10 received at 606976@bugs.debian.org (full text, mbox):

From: Ferenc Wagner <wferi@niif.hu>
To: Taro Sato <ubutsu@gmail.com>
Cc: 606976@bugs.debian.org,control@bugs.debian.org
Subject: Re: Bug#606976: Kernel panic with Squeeze (AMD64) d-i beta 2
Date: Thu, 16 Dec 2010 17:27:10 +0100
tag 606976 +moreinfo
thanks

Taro Sato <ubutsu@gmail.com> writes:

> I've tried d-i beta 2 on Dell XPS 630i.  I first tried creating a USB
> memory stick with the installer .iso on it (following a standard
> procedure); the install USB stick works on my other computer (Lenovo
> T410s).  However, on 630i it always fails at the beginning of the
> install process.  The message, when kernel panics, typically goes like
> this:
>
> ... (no apparent error messages thru this point) ...
> [0.597991] List of all partitions:
> [0.600310] No filesystem could mount root, tried:
> [0.602749] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(8,3)
> ... (call trace output after this) ...
>
> (This output is from an attempt to use CD install medium.)

Hi,

I have to say that all of this looks very much out of place.  First of
all, the boot menu should start the kernel with the "quiet" parameter,
so you should see no messages before the kernel panic.

 1. Did you edit the command line in the boot loader or by any other
    means?

 2. What was your exact sequence of actions after powering on your
    computer with the CD in the drive?

The above message indicates that no initramfs was loaded with the
kernel, or maybe it was corrupt.  If you didn't remove the "quiet"
parameter from the kernel command line, you'd see the message

    Initramfs unpacking failed: junk in compressed archive

in the latter case.

 3. What messages do you get with the "quiet" parameter?

You could also try writing the mini.iso downloaded from
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/netboot/mini.iso
to a pendrive and test that.  If you pendrive (the full device) is
/dev/sdb, then just do

    cat mini.iso >/dev/sdb

and try to boot from the pendrive.  This is very similar to the method
used for HD media, except that boot.img.gz is compressed.

> Is there any way to get Squeeze d-i to work on this machine?

There should be.  Please do the above tests and report back to help us
find out how.
-- 
Thanks,
Feri.




Added tag(s) moreinfo. Request was from Ferenc Wagner <wferi@niif.hu> to control@bugs.debian.org. (Thu, 16 Dec 2010 16:30:05 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install Team <debian-boot@lists.debian.org>:
Bug#606976; Package installation-reports. (Wed, 22 Dec 2010 02:09:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Taro Sato <taro@ap.smu.ca>:
Extra info received and forwarded to list. Copy sent to Debian Install Team <debian-boot@lists.debian.org>. (Wed, 22 Dec 2010 02:09:03 GMT) Full text and rfc822 format available.

Message #17 received at 606976@bugs.debian.org (full text, mbox):

From: Taro Sato <taro@ap.smu.ca>
To: Ferenc Wagner <wferi@niif.hu>
Cc: 606976@bugs.debian.org, control@bugs.debian.org
Subject: Re: Bug#606976: Kernel panic with Squeeze (AMD64) d-i beta 2
Date: Tue, 21 Dec 2010 22:08:14 -0400
On Thu, Dec 16, 2010 at 12:27 PM, Ferenc Wagner <wferi@niif.hu> wrote:
> tag 606976 +moreinfo
> thanks
>
> Taro Sato <ubutsu@gmail.com> writes:
>
>> I've tried d-i beta 2 on Dell XPS 630i.  I first tried creating a USB
>> memory stick with the installer .iso on it (following a standard
>> procedure); the install USB stick works on my other computer (Lenovo
>> T410s).  However, on 630i it always fails at the beginning of the
>> install process.  The message, when kernel panics, typically goes like
>> this:
>>
>> ... (no apparent error messages thru this point) ...
>> [0.597991] List of all partitions:
>> [0.600310] No filesystem could mount root, tried:
>> [0.602749] Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(8,3)
>> ... (call trace output after this) ...
>>
>> (This output is from an attempt to use CD install medium.)
>
> Hi,
>
> I have to say that all of this looks very much out of place.  First of
> all, the boot menu should start the kernel with the "quiet" parameter,
> so you should see no messages before the kernel panic.
>
>  1. Did you edit the command line in the boot loader or by any other
>    means?
>
>  2. What was your exact sequence of actions after powering on your
>    computer with the CD in the drive?
>
> The above message indicates that no initramfs was loaded with the
> kernel, or maybe it was corrupt.  If you didn't remove the "quiet"
> parameter from the kernel command line, you'd see the message
>
>    Initramfs unpacking failed: junk in compressed archive
>
> in the latter case.
>
>  3. What messages do you get with the "quiet" parameter?
>
> You could also try writing the mini.iso downloaded from
> http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/netboot/mini.iso
> to a pendrive and test that.  If you pendrive (the full device) is
> /dev/sdb, then just do
>
>    cat mini.iso >/dev/sdb
>
> and try to boot from the pendrive.  This is very similar to the method
> used for HD media, except that boot.img.gz is compressed.


1.  Yes, in troubleshooting I did remove the "quiet" parameter.  But
that only gave me more verbose diagnostics, and the symptom doesn't
change.  If I left the quiet parameter, it only shows this line:

[0.602749] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(8,3)


2. I popped in the install CD right after powering on the box, hit F12
to change the boot device temporarily (to CD or USB).  The Debian
installaer starts with the logo and the menu.  I choose "Install" and
the next thing is the kernel panic.

As for:

Initramfs unpacking failed: junk in compressed archive

I've never seen this message, though it might be possible that's
something scrolls out of the screen when the boot process spews out
the log message till the kernel panic.  I don't know how to capture
it.


3. That's my response to 1 above.


I just tried the mini.iso on a USB stick and I see exactly the same
kernel panic.

(In order to get the system back up, I installed Lenny first, and then
installed Squeeze from a hard disk partition which ended up very
successful.  Wonder what the difference is.)

Taro




Bug reassigned from package 'installation-reports' to 'linux-2.6'. Request was from Miguel Figueiredo <elmig@debianpt.org> to control@bugs.debian.org. (Sun, 09 Jan 2011 15:39:02 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#606976; Package linux-2.6. (Sun, 09 Jan 2011 16:09:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Miguel Figueiredo <elmig@debianpt.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sun, 09 Jan 2011 16:09:03 GMT) Full text and rfc822 format available.

Message #24 received at 606976@bugs.debian.org (full text, mbox):

From: Miguel Figueiredo <elmig@debianpt.org>
To: 606976@bugs.debian.org
Date: Sun, 09 Jan 2011 16:07:03 +0000
i got this info on #debian-boot which may help:

- the message points to a missing initramfs
- you get this message if no initramfs is around, so unless mistaken
this smells isolinux to me.
- I'd ask him to try the dailies, irc isolinux got fixes for broken
bios'es.

So, can you try with the dailies?


-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org





Bug reassigned from package 'linux-2.6' to 'debian-installer'. Request was from Miguel Figueiredo <elmig@debianpt.org> to control@bugs.debian.org. (Sun, 09 Jan 2011 16:15:03 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>:
Bug#606976; Package debian-installer. (Sun, 09 Jan 2011 21:54:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ferenc Wagner <wferi@niif.hu>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>. (Sun, 09 Jan 2011 21:54:06 GMT) Full text and rfc822 format available.

Message #31 received at 606976@bugs.debian.org (full text, mbox):

From: Ferenc Wagner <wferi@niif.hu>
To: Taro Sato <taro@ap.smu.ca>
Cc: 606976@bugs.debian.org
Subject: Re: Bug#606976: Kernel panic with Squeeze (AMD64) d-i beta 2
Date: Sun, 09 Jan 2011 22:50:58 +0100
Taro Sato <taro@ap.smu.ca> writes:

> On Thu, Dec 16, 2010 at 12:27 PM, Ferenc Wagner <wferi@niif.hu> wrote:
>
>> Taro Sato <ubutsu@gmail.com> writes:
>>
>>> I've tried d-i beta 2 on Dell XPS 630i.  I first tried creating a USB
>>> memory stick with the installer .iso on it (following a standard
>>> procedure); the install USB stick works on my other computer (Lenovo
>>> T410s).  However, on 630i it always fails at the beginning of the
>>> install process.  The message, when kernel panics, typically goes like
>>> this:
>>>
>>> ... (no apparent error messages thru this point) ...
>>> [0.597991] List of all partitions:
>>> [0.600310] No filesystem could mount root, tried:
>>> [0.602749] Kernel panic - not syncing: VFS: Unable to mount root fs on
>>> unknown-block(8,3)
>>> ... (call trace output after this) ...

Could you please also type in the call trace output what you get if you
remove the "quiet" parameter?  If this machine has a serial port, you
can also use that to capture the whole boot log, which would be
interesting as well (with a console=ttyS0,115200n8r or similar boot
parameter).  Unfortunately, serial ports are getting rare...

>> The above message indicates that no initramfs was loaded with the
>> kernel, or maybe it was corrupt.  If you didn't remove the "quiet"
>> parameter from the kernel command line, you'd see the message
>>
>>    Initramfs unpacking failed: junk in compressed archive
>>
>> in the latter case.
>
> I've never seen this message, though it might be possible that's
> something scrolls out of the screen when the boot process spews out
> the log message till the kernel panic.  I don't know how to capture
> it.

No, that message is printed even with "quiet", so you would have seen
it right above the panic line if it was present.

>> You could also try writing the mini.iso [...] to a pendrive
>
> I just tried the mini.iso on a USB stick and I see exactly the same
> kernel panic.
>
> (In order to get the system back up, I installed Lenny first, and then
> installed Squeeze from a hard disk partition which ended up very
> successful.  Wonder what the difference is.)

Do you mean that when you loaded the installer kernel and initrd by Grub
from your hard disk, everything went OK?  Most strange, again.  Long shot:
what if you add "edd=off" to your kernel command line (after "quiet")?

I don't think it would change anything, but you may want to test some
RC1-pre medium from http://cdimage.debian.org/cdimage/.squeeze_di_rc1/.
-- 
Thanks,
Feri.




Reply sent to Holger Levsen <holger@layer-acht.org>:
You have taken responsibility. (Sun, 21 Jul 2013 12:36:22 GMT) Full text and rfc822 format available.

Notification sent to Taro Sato <ubutsu@gmail.com>:
Bug acknowledged by developer. (Sun, 21 Jul 2013 12:36:22 GMT) Full text and rfc822 format available.

Message #36 received at 606976-done@bugs.debian.org (full text, mbox):

From: Holger Levsen <holger@layer-acht.org>
To: control@bugs.debian.org, 704499-done@bugs.debian.org, 593258-done@bugs.debian.org, 606976-done@bugs.debian.org, 625290-done@bugs.debian.org, 605815-done@bugs.debian.org, 692001-done@bugs.debian.org, 657345-done@bugs.debian.org, 656327-done@bugs.debian.org
Subject: dealing with old debian-installer bugs
Date: Sun, 21 Jul 2013 14:32:43 +0200
[Message part 1 (text/plain, inline)]
reassign 716710 preseed,release-notes
forcemerge 704881 552563
tags 633128 + confirmed
reassign 633128 src:linux,kernel-wedge
affects 633128 debian-installer
reassign 653391 archdetect
forcemerge 653390 653391 
reassign 655579 rootskel-gtk
reassign 690246 partman-lvm
affects 690246 debian-installer
severity 699430 wishlist
reassign 655124 kernel-wedge
affects 655124 debian-installer
thanks

Hi,

thank you for submitting bug reports concering debian-installer, much 
appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old and/or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - and that's often better, as the bug 
log will be clearer and shorter and not contain cruft.


cheers,
        Holger
[signature.asc (application/pgp-signature, inline)]

Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Mon, 19 Aug 2013 07:39:00 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Thu Apr 17 10:41:02 2014; Machine Name: beach.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.