|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd timeout waiting for serial console tty .device | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Andreas Färber <afaerber> |
| Component: | Basesystem | Assignee: | E-mail List <bnc-team-screening> |
| Status: | VERIFIED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | thomas.blume |
| Version: | 13.2 Milestone 0 | ||
| Target Milestone: | --- | ||
| Hardware: | armv7 | ||
| OS: | openSUSE 13.2 | ||
| URL: | http://lists.opensuse.org/opensuse-arm/2014-04/msg00050.html | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Solution found: CONFIG_FHANDLE=y |
On several ARM boards I am seeing issues like this over the serial console: [ 10.900000] systemd[1]: Expecting device dev-ttySAC3.device... Expecting device dev-ttySAC3.device... ... [ TIME ] Timed out waiting for device dev-ttySAC3.device. [DEPEND] Dependency failed for Serial Getty on ttySAC3. Here on Arndale Octa, using "console=ttySAC3,115200n8", with latest self-compiled 3.15.rc2+ as well as 3.14.0. Dito for ODROID-XU using "console=ttySAC2,115200n8", with downstream 3.14. There I can ssh in and do see the device, long before the timeout: $ ll /dev/ttySAC2 crw-rw---- 1 root dialout 204, 66 Jan 1 2000 /dev/ttySAC2 Yet `systemctl start serial-getty@ttySAC2.service` times out again. However, `yast services` > "serial-getty@ttySAC2" (shown "Disabled|Inactive") > "Start/Stop" > "OK" revives it (until the next boot). $ udevadm info -qall -p /sys/class/tty/ttySAC2 P: /devices/12c20000.serial/tty/ttySAC2 N: ttySAC2 E: DEVNAME=/dev/ttySAC2 E: DEVPATH=/devices/12c20000.serial/tty/ttySAC2 E: MAJOR=204 E: MINOR=66 E: SUBSYSTEM=tty E: TAGS=:systemd: E: USEC_INITIALIZED=11940 A similar timeout happened waiting for dev-mmcblk0p1.device after assigning the mount point /boot to that partition and booting with root=/dev/mmcblk0p2. I.e., systemd does not see dev-foo.device despite /dev/foo getting created.