console-setup.service fails on ppc64el

Bug #1516591 reported by Martin Pitt
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

In ScalingStack ppc64el instances, console-setup.service fails:

$ sudo systemctl status -l console-setup.service
● console-setup.service - Set console keymap
   Loaded: loaded (/lib/systemd/system/console-setup.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2015-11-16 11:38:44 UTC; 47s ago
     Docs: man:loadkeys(1)
  Process: 245 ExecStart=/usr/bin/loadkeys /etc/console-setup/cached.kmap.gz (code=exited, status=1/FAILURE)
 Main PID: 245 (code=exited, status=1/FAILURE)

Nov 16 11:38:44 ubuntuubuntu-xenial-adt-ppc64el-server-20151114 systemd[1]: Starting Set console keymap...
Nov 16 11:38:44 ubuntuubuntu-xenial-adt-ppc64el-server-20151114 loadkeys[245]: Couldn't get a file descriptor referring to the console
Nov 16 11:38:44 ubuntuubuntu-xenial-adt-ppc64el-server-20151114 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE
Nov 16 11:38:44 ubuntuubuntu-xenial-adt-ppc64el-server-20151114 systemd[1]: Failed to start Set console keymap.
Nov 16 11:38:44 ubuntuubuntu-xenial-adt-ppc64el-server-20151114 systemd[1]: console-setup.service: Unit entered failed state.
Nov 16 11:38:44 ubuntuubuntu-xenial-adt-ppc64el-server-20151114 systemd[1]: console-setup.service: Failed with result 'exit-code'.

strace shows

open("/dev/console", O_RDWR) = 3
ioctl(3, TCGETS, {c_iflags=0, c_oflags=0x3, c_cflags=0x4b0f, c_lflags=0, c_line=0, c_cc[VMIN]=1, c_cc[VTIME]=0, c_cc="\x03\x1c\x7f\x15\x04\x01\x00\x00\x00\x00\x17\x12\x1a\x11\x13\x16\x15\x00\x00"}) = 0
ioctl(3, KDGKBTYPE, 0x3ffff3111300) = -1 ENOTTY (Inappropriate ioctl for device)
close(3) = 0

while on amd64 this succeeds:

open("/dev/console", O_RDWR) = 3
ioctl(3, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {c_iflags=0x5, c_oflags=0, c_cflags=0xbf, c_lflags=0, c_line=0, c_cc[VMIN]=1, c_cc[VTIME]=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0
ioctl(3, KDGKBTYPE, 0x7ffe41f71877) = 0
ioctl(3, KDGKBMODE, 0x7ffe41f71898) = 0
close(3) = 0

Revision history for this message
Simon Eisenmann (longsleep) wrote :

I have the same issue on aarch64:

openat(AT_FDCWD, "/dev/console", O_RDWR) = 3
ioctl(3, TCGETS, {c_iflags=0x5500, c_oflags=0x5, c_cflags=0x1cb2, c_lflags=0xa3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0
ioctl(3, KDGKBTYPE, 0x7fc80de317) = -1 ENOTTY (Inappropriate ioctl for device)

and the console-setup service fails

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in console-setup (Ubuntu):
status: New → Confirmed
Revision history for this message
Oliver Grawert (ogra) wrote :

does the kernel cmdline by chance point to a non existing console device in both cases ?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.