[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#515733: marked as done (Stuck bootlogd causes kernel crash)

Your message dated Tue, 4 Jun 2013 00:29:54 +0200
with message-id <20130603222954.GD5604@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #515733,
regarding Stuck bootlogd causes kernel crash
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.)


-- 
515733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515733
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sysvinit
Version: 2.86.ds1-38
Severity: normal
File: /sbin/bootlogd

Hi,
there is problem with bootlogd under Xen domU, unless right console
device is specified on kernel command line.
Valid console device is tty1 for domU me and I'm not certein, this is
constant behavior (no knowledge). If I create domain with
    xm create -c etch
then logs in there and type tty, I get /dev/tty1.

When I add console=tty1 to kernel params of domain config file,
then bootlogd works as expected probably.

In the case of no console= in kernel command line bootlogd leaves in
deadlock eating up 100% VCPU and strace on it shows neverending:

open("/dev/ttyS0", O_WRONLY|O_NONBLOCK|O_NOCTTY) = 3
fcntl64(3, F_GETFL)                     = 0x801 (flags
O_WRONLY|O_NONBLOCK)
fcntl64(3, F_SETFL, O_WRONLY)           = 0
write(3, ".\r\n", 3)                    = -1 EIO (Input/output error)
close(3)                                = 0
open("/dev/ttyS0", O_WRONLY|O_NONBLOCK|O_NOCTTY) = 3
fcntl64(3, F_GETFL)                     = 0x801 (flags
O_WRONLY|O_NONBLOCK)
fcntl64(3, F_SETFL, O_WRONLY)           = 0
write(3, ".\r\n", 3)                    = -1 EIO (Input/output error)
close(3)                                = 0
...

There is comment in the source (before write_err() function)

/*
 *      We got a write error on the real console. If its an EIO,
 *      somebody hung up our filedescriptor, so try to re-open it.
 */

For some reason bootlogd suppose /dev/ttyS0 console device.
Regards.
-- 
zito

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-xen-686
Locale: LANG=C, LC_CTYPE=cs_CZ.ISO-8859-2 (charmap=ISO-8859-2)

Versions of packages sysvinit depends on:
ii  initscripts            2.86.ds1-38       Scripts for initializing and shutt
ii  libc6                  2.3.6.ds1-13etch2 GNU C Library: Shared libraries
ii  libselinux1            2.0.35-0.icz.2    SELinux shared libraries
ii  libsepol1              2.0.11-0.icz.1    Security Enhanced Linux policy lib
ii  sysv-rc                2.86.ds1-38       System-V-like runlevel change mech
ii  sysvinit-utils         2.86.ds1-38       System-V-like utilities

sysvinit recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: