Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready. - Debian

This is a discussion on Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready. - Debian ; Package: Installation-reports Boot method: Booted from CD The following is copied from Etch dmesg sym0: rev 0x12 at pci 0000:00:0c.0 irq 11 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: SCSI BUS has been reset. scsi0 : sym-2.2.3 ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.

  1. Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.

    Package: Installation-reports

    Boot method: Booted from CD
    The following is copied from Etch dmesg

    sym0: <810a> rev 0x12 at pci 0000:00:0c.0 irq 11
    sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
    sym0: SCSI BUS has been reset.
    scsi0 : sym-2.2.3
    Vendor: PLEXTOR Model: CD-ROM PX-40TS Rev: 1.01
    Type: CD-ROM ANSI SCSI revision: 02
    target0:0:1: Beginning Domain Validation
    target0:0:1: asynchronous
    target0:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 8)

    BIOS is SDMS 4.12.0.0, and reports "No Emulation" mode on
    BIOS screen while booting.


    Image version: 157034496 2008-10-28 22:11 debian-LennyBeta2-i386-netinst.iso

    Second try with daily build
    debian-testing-i386-netinst.iso
    from
    http://cdimage.debian.org/cdimage/da...t/i386/iso-cd/

    But it is also reproducible with a Knoppix CD, and
    therefore probably a general Isolinux problem not
    limited to the Debian Installer.

    Date: Oct 29

    Machine: Homebuilt 24/7 machine, motherboard ASUS A7V 1.04 with
    latest BIOS 1011 from 2002, running under Debian Etch
    normally.

    SCSI controller is an ASUS SC-200,
    SDMS BIOS 4.12.0.0 is delivered by the motherboard, as usual
    for these controllers.


    Processor: Duron 600

    CPU: After generic identify, caps: 0183f9ff c1c7f9ff 00000000 00000000 00000000 00000000 00000000
    CPU: After vendor identify, caps: 0183f9ff c1c7f9ff 0000000000000000 00000000 00000000 00000000
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 64K (64 bytes/line)
    CPU: After all inits, caps: 0183f9ff c1c7f9ff 00000000 00000420 00000000 00000000 00000000
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    CPU: AMD Duron(tm) Processor stepping 00
    Checking 'hlt' instruction... OK.

    Memory: SDRAM 100

    383MB LOWMEM available.

    Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on
    /dev/hda1 ext3 21342047 4444456 15813206 22% /
    tmpfs tmpfs 193452 0 193452 0% /lib/init/rw
    udev tmpfs 10240 84 10156 1% /dev
    tmpfs tmpfs 193452 8 193444 1% /dev/shm
    /dev/hdc2 ext3 91658564 44736272 42266256 52% /home
    /dev/hde1 ext3 476750548 341159516 111373448 76% /home/hajo/Archiv
    /dev/hdf1 ext3 240362656 143533616 84619240 63% /home/hajo/Archiv/Bahn


    Output of lspci -knn (or lspci -nn):

    00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] [1106:0305] (rev 02)
    00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] [1106:8305]
    00:04.0 ISA bridge [0601]: VIA Technologies, Inc. VT82C686 [Apollo Super South] [1106:0686] (rev 22)
    00:04.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 10)
    00:04.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 10)
    00:04.3 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 10)
    00:04.4 Bridge [0680]: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] [1106:3057] (rev 30)
    00:09.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 02)
    00:09.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 02)
    00:0a.0 Multimedia controller [0480]: Philips Semiconductors TriMedia TM-1300 [1131:5402] (rev 83)
    00:0b.0 PCI bridge [0604]: IBM IBM27-82351 [1014:0022] (rev 01)
    00:0c.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c810 [1000:0001] (rev 12)
    00:0d.0 Multimedia audio controller [0401]: C-Media Electronics Inc CM8738 [13f6:0111] (rev 10)
    00:11.0 Mass storage controller [0180]: Promise Technology, Inc. PDC20265 (FastTrak100 Lite/Ultra100) [105a:0d30] (rev 02)
    01:00.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA G400/G450 [102b:0525] (rev 04)
    02:00.0 Network controller [0280]: Compaq Computer Corporation Netelligent Dual 10/100 TX PCI UTP [0e11:ae40] (rev 10)
    02:01.0 Network controller [0280]: Compaq Computer Corporation Netelligent Dual 10/100 TX PCI UTP [0e11:ae40] (rev 10)




    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: [ ]

    Comments/Problems:

    BIOS boot uneventful, Hostadapter BIOS reports "No Emulation" mode,
    Installation CD screen comes up fine with all the help options. After
    , I get
    Loading /something-386/vmlinuz .....................
    Loading /something-386/initrd.gz .......................................
    ..........................ready.

    After that, the machine stops activity, nothing even after 10 minutes,
    and does not react to Ctrl-Alt-Del. Hardware reset necessary.

    I also tried with Kernel boot parameters "noapic nolapic acpi=off" with
    the same results. After the Lenny II Beta, I tried with another CD from
    daily build, and I also tried with Knoppix. Knoppix gives the same
    result to ...........ready, just with different naming for kernel and
    initrd.










    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.

    On Thursday 30 October 2008, Hans-Joachim Zierke wrote:
    > Comments/Problems:
    > BIOS boot uneventful, Hostadapter BIOS reports "No Emulation" mode,
    > Installation CD screen comes up fine with all the help options. After
    > , I get
    > Loading /something-386/vmlinuz .....................
    > Loading /something-386/initrd.gz
    > ....................................... .........................ready.
    >
    > After that, the machine stops activity, nothing even after 10 minutes,
    > and does not react to Ctrl-Alt-Del. Hardware reset necessary.


    Please try booting in expert mode (see advanced menu) and give us the boot
    log information visible on the screen when it hangs.

    If it is clear where the problem is, you may only have to give the last
    few lines. If it is not clear, please provide as much context as possible
    (a screenshot with a camera is OK as long as it is clear [1]).

    Cheers,
    FJP

    [1] Note that large attachments may not reach the mailinglist, so please
    check that your message is visible in the mailing list archive:
    http://lists.debian.org/debian-boot/



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  3. Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.

    On 30.10.2008 17:27:54, Frans Pop wrote:


    > > Loading /something-386/vmlinuz .....................
    > > Loading /something-386/initrd.gz
    > > ....................................... .........................ready.



    > Please try booting in expert mode (see advanced menu) and give us the boot
    > log information visible on the screen when it hangs.



    In expert mode, the result is exactly the same:

    Loading /install.386/vmlinuz .....................
    Loading /install.386/initrd.gz ..................................
    ...............................ready.


    And that's it.



    Ciao
    Hans-Joachim



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  4. Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.

    On Thursday 30 October 2008, Hans-Joachim Zierke wrote:
    > In expert mode, the result is exactly the same:
    >
    > Loading /install.386/vmlinuz .....................
    > Loading /install.386/initrd.gz ..................................
    > ..............................ready.


    OK. This is very clearly a kernel problem, not an installer problem. We
    can try one more thing, but I think you'll have to report this to the
    upstream kernel developers.

    Please try booting in expert mode using a current daily built image with
    the following added parameters:
    debug earlyprintk=vga,keep edd=off

    It could also possibly an isolinux problem. have you tried installing the
    Lenny kernel on your Etch system and booting that?



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  5. Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.

    On 01.11.2008 16:08:13, Frans Pop wrote:


    > OK. This is very clearly a kernel problem, not an installer problem. We
    > can try one more thing, but I think you'll have to report this to the
    > upstream kernel developers.
    >
    > Please try booting in expert mode using a current daily built image with
    > the following added parameters:
    > debug earlyprintk=vga,keep edd=off



    This did not give any other result.




    But I found it by completely disabling almost everything in the BIOS,
    getting a success, then systematically reenabling stuff.

    It's the Promise ATA-100 BIOS. If I reset that BIOS from "Auto" to
    "Disabled", then I get the

    Ok, booting the kernel

    message. The A7V Board has an ATA-66 controller in the chipset, plus an
    additional ATA-100 Promise controller on the motherboard. The relevant
    lspci lines:

    00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/ C PIPC Bus Master IDE (rev 10)

    00:0c.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 12)

    00:11.0 Mass storage controller: Promise Technology, Inc. PDC20265 (FastTrak100 Lite/Ultra100) (rev 02)

    It does /not/ help, to set boot priority to "SCSI/ATA100" (as I had
    done), and it does /not/ help, if I don't allow booting from it. The
    Promise BIOS /must/ be /disabled/ for booting the kernel from SCSI CD.

    I guess, but don't know, that the Linux boot system ignores the boot
    priorities of the BIOS, gets confused, and tries to find a CD at the
    Promise controller.




    > It could also possibly an isolinux problem. have you tried installing the
    > Lenny kernel on your Etch system and booting that?


    I won't even know how to do that. ;-) I know how to compile a kernel
    for the running system with make-kpkg, but that's it.

    I'm not a Linux freak, but a user. When I looked for Lenny news on the
    website, I read that we should try the installer, so I did.


    Hans-Joachim




    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  6. Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.

    reassign 504016 linux-2.6
    thanks

    On Saturday 01 November 2008, Hans-Joachim Zierke wrote:
    > But I found it by completely disabling almost everything in the BIOS,
    > getting a success, then systematically reenabling stuff.
    >
    > It's the Promise ATA-100 BIOS. If I reset that BIOS from "Auto" to
    > "Disabled", then I get the
    >
    > Ok, booting the kernel
    >
    > message. The A7V Board has an ATA-66 controller in the chipset, plus an
    > additional ATA-100 Promise controller on the motherboard.


    The strange thing is that your initial report shows that the initrd and
    kernel do get loaded from the CD; it just fails to take the next step.

    As this really looks like a kernel issue, I'm reassigning your report to
    the kernel team. Maybe they can offer additional help.

    > > It could also possibly an isolinux problem. have you tried installing
    > > the Lenny kernel on your Etch system and booting that?

    >
    > I won't even know how to do that. ;-) I know how to compile a kernel
    > for the running system with make-kpkg, but that's it.


    Just download the package from packages.debian.org and install it
    using 'dpkg -i '.

    > I'm not a Linux freak, but a user. When I looked for Lenny news on the
    > website, I read that we should try the installer, so I did.


    Thanks a lot for testing it. We do appreciate that and the fact that you
    filed your installation report.

    Unfortunately when you do run into such a problem with Linux it's
    basically up to the user to find the correct person to look into the
    problem and to provide any needed info to track it down. Depending on the
    issue, that can require a significant amount of effort on the user's
    part.

    Cheers,
    FJP



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

+ Reply to Thread