Bug#499030: debian-installer: [s390] installer fails to boot 'attempt to kill init' - Debian

This is a discussion on Bug#499030: debian-installer: [s390] installer fails to boot 'attempt to kill init' - Debian ; Package: debian-installer Severity: serious I just tried a daily image for s390 in the Hercules emulator, but the installer fails to boot with kernel panic - not syncing: Attempted to kill init I can see that udevd starts OK, but ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Bug#499030: debian-installer: [s390] installer fails to boot 'attempt to kill init'

  1. Bug#499030: debian-installer: [s390] installer fails to boot 'attempt to kill init'

    Package: debian-installer
    Severity: serious

    I just tried a daily image for s390 in the Hercules emulator, but the
    installer fails to boot with
    kernel panic - not syncing: Attempted to kill init

    I can see that udevd starts OK, but the following command fails:
    exec /sbin/reopen-console /bin/busybox init

    I know that Jérémy uploaded a changed version of rootskel yesterday, so
    this needs re-testing with that, but I wanted to register the issue
    anyway.

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.9 (GNU/Linux)

    iEYEABECAAYFAkjOloAACgkQgm/Kwh6ICoSEmgCePam8QApKcMnnMLvIIvOMGRTh
    NMYAoIudeBcUA0S7hFSUw959GmOyhBxX
    =NYKZ
    -----END PGP SIGNATURE-----


  2. Bug#499030: debian-installer: [s390] installer fails to boot 'attempt to kill init'

    tags 499030 pending
    thanks

    On Friday 19 September 2008, Frans Pop wrote:
    > As the installer should just be using /dev/console in my case, the
    > solution seems to be to add a check that the console device actually
    > exists in reopen-console (and probably log a warning if it does not).


    I've committed a patch for this. Without logging of devices that get
    ignored as syslogd is not yet running at that point.

    Jérémy: could you have a look at the patch and upload if OK?



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

  3. Bug#499030: debian-installer: [s390] installer fails to boot 'attempt to kill init'

    On Fri, Sep 19, 2008 at 04:11:12PM +0200, Frans Pop wrote:
    > On Friday 19 September 2008, Frans Pop wrote:
    > > With the new rootskel I get an endless repetition of:
    > > steal-ctty: No such file or directory

    >
    > Running with set-x gives a bit more info:
    > + -f /var/run/console-device !
    > + cat /var/run/console-device
    > + exec /sbin/steal-ctty /dev/ttyS0 /sbin/debian-installer
    > steal-ctty: No such file or directory
    >
    > This repeats endlessly. Note that the first line is mangled a bit because
    > of the "!" in the if statement.


    reopen-console is writing in /var/run/console-device the console that
    was found in the first run, so the result would be more meaningful if
    the "set -x" was add by using BOOT_DEBUG=3 and then running something
    like "/sbin/reopen-console echo" manually.

    > There seem to be various issues:
    > - trying /dev/ttyS0 is just plain wrong for s/390: /dev/ttyS0 does not
    > exist, which explains the error from steal-ccty


    Indeed. Could you look at kernel messages for anything related to the
    console? Using "dmesg -s 65535 | grep console" should probably do the
    trick.

    I might have misunderstood the meaning of the "console handover" line
    and that's probably where the /dev/ttyS0 line came from, as
    reopen-console defaults to /dev/console if no console can be found.

    > - steal-ctty's error message should include the name of the file that does
    > not exist


    True.

    > - the program should not end in a loop


    The loop is caused by init trying, as told in inittab, to respawn the
    process. It don't really feel like an issue for me, because this should
    not happen. What could be done is a final check in reopen-console for
    the existence of the device file, though…

    Cheers,
    --
    Jérémy Bobbio .''`.
    lunar@debian.org : :Ⓐ : # apt-get install anarchism
    `. `'`
    `-

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFI1DYe2PUjs9fQ72URAqmYAJ0dIQnfNjpPPT+Ye+OcM1 lSSfzsygCfRa+R
    2ffO3pOawqCmVgZq/pCCfmY=
    =Ou5U
    -----END PGP SIGNATURE-----


  4. Bug#499030: marked as done (debian-installer: [s390] installer fails to boot 'attempt to kill init')


    Your message dated Sun, 21 Sep 2008 09:02:24 +0000
    with message-id
    and subject line Bug#499030: fixed in rootskel 1.69
    has caused the Debian Bug report #499030,
    regarding debian-installer: [s390] installer fails to boot 'attempt to killinit'
    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 owner@bugs.debian.org
    immediately.)


    --
    499030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499030
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems


+ Reply to Thread