[Pkg-sysvinit-devel] Bug#454147: /sbin/bootlogd: bootlogd: deadlock under Xen domU, wrong console device

Petter Reinholdtsen pere at hungry.com
Tue Jul 14 22:00:30 UTC 2009

The crashing kernel is obviously a kernel bug, and should be reported
in a separate BTS report to the kernel or Xen people.  The looping
bootlogd issue might be a bug in bootlogd, but I do not know the
bootlogd code well enough to tell.

The bootlogd code contain a list of known devices to test when not
finding any on the kernel argument list.  Perhaps this list need to be
extended for Xen?

This is the current list of recognized devices:

 *      Console devices as listed on the kernel command line and
 *      the mapping to actual devices in /dev
struct consdev {
        char    *cmdline;
        char    *dev1;
        char    *dev2;
} consdev[] = {
        { "ttyB",       "/dev/ttyB%s",          NULL            },
        { "ttySC",      "/dev/ttySC%s",         "/dev/ttsc/%s"  },
        { "ttyS",       "/dev/ttyS%s",          "/dev/tts/%s"   },
        { "tty",        "/dev/tty%s",           "/dev/vc/%s"    },
        { "hvc",        "/dev/hvc%s",           "/dev/hvc/%s"   },
        { NULL,         NULL,                   NULL            },

 *      Devices to try as console if not found on kernel command line.
 *      Tried from left to right (as opposed to kernel cmdline).
char *defcons[] = { "tty0", "hvc0", "ttyS0", "ttySC0", "ttyB0", NULL };

Someone with Xen knowledge need to provide a working patch.

Happy hacking,
Petter Reinholdtsen

More information about the Pkg-sysvinit-devel mailing list