[systemd-devel] Question about "Job dev-tty1.device/start timed out" ?

[Lennart Poettering]

On Thu, 20.10.11 20:30, Chen Jie (chenj at lemote.com) wrote:

> Hi all,
> 
> I occasionally got no getty on tty[1-6]. When I went through the dmesg and
> found the following:
> """
> [   40.679687] <28>systemd[1]: Job dev-tty1.device/start timed out.
> [   40.683593] <31>systemd[1]: Job dev-tty1.device/start finished,
> result=timeout
> [   40.683593] <31>systemd[1]: Job getty at tty1.service/start finished,
> result=dependency
> [   40.859375] <29>systemd[1]: Job getty at tty1.service/start failed with
> result 'dependency'.
> [   40.925781] <29>systemd[1]: Job dev-tty1.device/start failed with result
> 'timeout'.
> [   40.988281] <31>systemd[1]: getty.target changed dead -> active
> [   41.046875] <31>systemd[1]: Job getty.target/start finished, result=done
> """
> 
> What may cause dev-ttyN.device timed out?

All devices marked with the "systemd" tag in the udev database show up
as .device units in systemd as soon as they are cold or hotplugged. If
this times out for you then there's something wrong with the message
delivery, or your /dev/tty1 device is gone for some reason or the udev
rules to mark all tty devices with the "systemd" tag didn't get
executed.

To debug this is might be worth using "udevadm info -p
/sys/class/tty/tty1 -q all" when this happens. This should normally show
you an output like the following:

<snip>
$ udevadm info -p /sys/class/tty/tty1 -q all
P: /devices/virtual/tty/tty1
N: tty1
E: UDEV_LOG=3
E: DEVPATH=/devices/virtual/tty/tty1
E: MAJOR=4
E: MINOR=1
E: DEVNAME=/dev/tty1
E: SUBSYSTEM=tty
E: ID_MM_CANDIDATE=1
E: TAGS=:systemd:
</snip>

The last line of that is what matters here.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.