| 2017-10-24 16:15:55 |
TJ |
bug |
|
|
added bug |
| 2017-10-24 16:15:55 |
TJ |
attachment added |
|
systemd.log_level=debug https://bugs.launchpad.net/bugs/1726930/+attachment/4991702/+files/systemd-debug.log |
|
| 2017-10-24 16:16:30 |
TJ |
bug task added |
|
laptop-mode-tools (Ubuntu) |
|
| 2017-10-24 16:33:14 |
TJ |
description |
This report is to capture the extended diagnostic efforts done on IRC #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was upgraded from 17.04 to 17.10 and since fails to complete start-up of services when powered on battery.
We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'" workaround in case this was an ACPI DSDT issue.
This appears to be due to a read-only root file-system. What is not clear is how the rootfs goes read-only.
The file-system (sda6, ext4) is fsck-ed successfully in the initrd according to the /run/initramfs/fsck.log.
From the start-up logs (with "systemd.log_level=debug") we see the ext4 driver report a remount operation not once but five times.
$ grep 'EXT4-fs.*sda6' systemd-debug.log
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Those last five appear to be carrying options generated by laptop-mode-tools.
User has disabled laptop-mode.service and laptop-mode.timer, and lmt-poll.service, but the issue remains.
We see several reports of "read-only file-system":
$ grep 'Read-only' systemd-debug.log
Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open `/boot/grub/grubenv': Read-only file system.
Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to /var/log/gpu-manager.log failed (Read-only file system)
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: Read-only file system
...
Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of "/var/log/cups" - Read-only file system
Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file "/var/log/cups/access_log" - Read-only file system
Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open /var/log/lastlog: Read-only file system
We also see several problems with systemd's connection to Dbus:
$ grep 'Transport endpoint' systemd-debug.log
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit change signal for lmt-poll.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change signal for polkit.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit change signal for cups-browsed.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change signal for gdomap.service: Transport endpoint is not connected |
This report is to capture the extended diagnostic efforts done on IRC #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was upgraded from 17.04 to 17.10 and since fails to complete start-up of services when powered on battery.
We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'" workaround in case this was an ACPI DSDT issue.
This appears to be due to a read-only root file-system. What is not clear is how the rootfs goes read-only.
The file-system (sda6, ext4) is fsck-ed successfully in the initrd according to the /run/initramfs/fsck.log.
From the start-up logs (with "systemd.log_level=debug") we see the ext4 driver report a remount operation not once but five times.
$ grep 'EXT4-fs.*sda6' systemd-debug.log
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Those last five appear to be carrying options generated by laptop-mode-tools.
User has disabled laptop-mode.service and laptop-mode.timer, and lmt-poll.service, but the issue remains.
We see several reports of "read-only file-system":
$ grep 'Read-only' systemd-debug.log
Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open `/boot/grub/grubenv': Read-only file system.
Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to /var/log/gpu-manager.log failed (Read-only file system)
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: Read-only file system
...
Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of "/var/log/cups" - Read-only file system
Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file "/var/log/cups/access_log" - Read-only file system
Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open /var/log/lastlog: Read-only file system
We also see several problems with systemd's connection to Dbus:
$ grep 'Transport endpoint' systemd-debug.log
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit change signal for lmt-poll.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change signal for polkit.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit change signal for cups-browsed.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change signal for gdomap.service: Transport endpoint is not connected
When the user purged laptop-mode-tools the system starts successfully on battery.
The user installed a fresh instance of 17.10 on a 2nd M2 SSD. When laptop-mode-tools was added to that instance it also exhibited the failure. |
|
| 2017-10-24 16:46:04 |
ryan eckenrode |
attachment added |
|
hwinfo.log https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/+attachment/4991778/+files/hwinfo.log |
|
| 2017-10-24 16:47:14 |
ryan eckenrode |
bug |
|
|
added subscriber ryan eckenrode |
| 2017-10-24 17:19:55 |
TJ |
bug watch added |
|
https://bugs.freedesktop.org/show_bug.cgi?id=95263 |
|
| 2017-10-24 17:19:55 |
TJ |
bug watch added |
|
https://bugs.freedesktop.org/show_bug.cgi?id=95619 |
|
| 2017-10-24 17:25:41 |
TJ |
attachment added |
|
Photo of startup console messages https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+attachment/4991895/+files/IMAG2881.jpg |
|
| 2017-10-24 17:28:13 |
TJ |
description |
This report is to capture the extended diagnostic efforts done on IRC #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was upgraded from 17.04 to 17.10 and since fails to complete start-up of services when powered on battery.
We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'" workaround in case this was an ACPI DSDT issue.
This appears to be due to a read-only root file-system. What is not clear is how the rootfs goes read-only.
The file-system (sda6, ext4) is fsck-ed successfully in the initrd according to the /run/initramfs/fsck.log.
From the start-up logs (with "systemd.log_level=debug") we see the ext4 driver report a remount operation not once but five times.
$ grep 'EXT4-fs.*sda6' systemd-debug.log
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Those last five appear to be carrying options generated by laptop-mode-tools.
User has disabled laptop-mode.service and laptop-mode.timer, and lmt-poll.service, but the issue remains.
We see several reports of "read-only file-system":
$ grep 'Read-only' systemd-debug.log
Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open `/boot/grub/grubenv': Read-only file system.
Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to /var/log/gpu-manager.log failed (Read-only file system)
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: Read-only file system
...
Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of "/var/log/cups" - Read-only file system
Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file "/var/log/cups/access_log" - Read-only file system
Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open /var/log/lastlog: Read-only file system
We also see several problems with systemd's connection to Dbus:
$ grep 'Transport endpoint' systemd-debug.log
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit change signal for lmt-poll.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change signal for polkit.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit change signal for cups-browsed.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change signal for gdomap.service: Transport endpoint is not connected
When the user purged laptop-mode-tools the system starts successfully on battery.
The user installed a fresh instance of 17.10 on a 2nd M2 SSD. When laptop-mode-tools was added to that instance it also exhibited the failure. |
This report is to capture the extended diagnostic efforts done on IRC #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was upgraded from 17.04 to 17.10 and since fails to complete start-up of services when powered on battery.
We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'" workaround in case this was an ACPI DSDT issue.
This appears to be due to a read-only root file-system. What is not clear is how the rootfs goes read-only.
The file-system (sda6, ext4) is fsck-ed successfully in the initrd according to the /run/initramfs/fsck.log.
From the start-up logs (with "systemd.log_level=debug") we see the ext4 driver report a remount operation not once but five times.
$ grep 'EXT4-fs.*sda6' systemd-debug.log
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Those last five appear to be carrying options generated by laptop-mode-tools.
User has disabled laptop-mode.service and laptop-mode.timer, and lmt-poll.service, but the issue remains.
We see several reports of "read-only file-system":
$ grep 'Read-only' systemd-debug.log
Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open `/boot/grub/grubenv': Read-only file system.
Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to /var/log/gpu-manager.log failed (Read-only file system)
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: Read-only file system
...
Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of "/var/log/cups" - Read-only file system
Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file "/var/log/cups/access_log" - Read-only file system
Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open /var/log/lastlog: Read-only file system
We also see several problems with systemd's connection to Dbus:
$ grep 'Transport endpoint' systemd-debug.log
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit change signal for lmt-poll.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change signal for polkit.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit change signal for cups-browsed.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change signal for gdomap.service: Transport endpoint is not connected
When the user purged laptop-mode-tools the system starts successfully on battery.
The user installed a fresh instance of 17.10 on a 2nd M2 SSD. When laptop-mode-tools was added to that instance it also exhibited the failure.
# apt-cache rdepends laptop-mode-tools
laptop-mode-tools
Reverse Depends:
systemd
tlp
powertop-1.13
powertop
# apt-cache depends systemd
systemd
PreDepends: libc6
Depends: libacl1
...
Breaks: apparmor
Breaks: ifupdown
Breaks: laptop-mode-tools
Breaks: <systemd-shim>
Breaks: udev
...
So it seems that systemd 'knows' it'll break laptop-mode-tools but during a release-upgrade it doesn't cause that package to be removed. |
|
| 2017-10-24 17:40:48 |
TJ |
bug task added |
|
laptop-mode-tools |
|
| 2017-10-24 17:40:57 |
TJ |
bug task deleted |
laptop-mode-tools |
|
|
| 2017-10-24 17:41:28 |
TJ |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762018 |
|
| 2017-10-24 17:41:28 |
TJ |
bug task added |
|
systemd (Debian) |
|
| 2017-10-24 17:45:28 |
TJ |
description |
This report is to capture the extended diagnostic efforts done on IRC #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was upgraded from 17.04 to 17.10 and since fails to complete start-up of services when powered on battery.
We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'" workaround in case this was an ACPI DSDT issue.
This appears to be due to a read-only root file-system. What is not clear is how the rootfs goes read-only.
The file-system (sda6, ext4) is fsck-ed successfully in the initrd according to the /run/initramfs/fsck.log.
From the start-up logs (with "systemd.log_level=debug") we see the ext4 driver report a remount operation not once but five times.
$ grep 'EXT4-fs.*sda6' systemd-debug.log
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Those last five appear to be carrying options generated by laptop-mode-tools.
User has disabled laptop-mode.service and laptop-mode.timer, and lmt-poll.service, but the issue remains.
We see several reports of "read-only file-system":
$ grep 'Read-only' systemd-debug.log
Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open `/boot/grub/grubenv': Read-only file system.
Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to /var/log/gpu-manager.log failed (Read-only file system)
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: Read-only file system
...
Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of "/var/log/cups" - Read-only file system
Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file "/var/log/cups/access_log" - Read-only file system
Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open /var/log/lastlog: Read-only file system
We also see several problems with systemd's connection to Dbus:
$ grep 'Transport endpoint' systemd-debug.log
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit change signal for lmt-poll.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change signal for polkit.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit change signal for cups-browsed.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change signal for gdomap.service: Transport endpoint is not connected
When the user purged laptop-mode-tools the system starts successfully on battery.
The user installed a fresh instance of 17.10 on a 2nd M2 SSD. When laptop-mode-tools was added to that instance it also exhibited the failure.
# apt-cache rdepends laptop-mode-tools
laptop-mode-tools
Reverse Depends:
systemd
tlp
powertop-1.13
powertop
# apt-cache depends systemd
systemd
PreDepends: libc6
Depends: libacl1
...
Breaks: apparmor
Breaks: ifupdown
Breaks: laptop-mode-tools
Breaks: <systemd-shim>
Breaks: udev
...
So it seems that systemd 'knows' it'll break laptop-mode-tools but during a release-upgrade it doesn't cause that package to be removed. |
This report is to capture the extended diagnostic efforts done on IRC #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was upgraded from 17.04 to 17.10 and since fails to complete start-up of services when powered on battery.
We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'" workaround in case this was an ACPI DSDT issue.
This appears to be due to a read-only root file-system. What is not clear is how the rootfs goes read-only.
The file-system (sda6, ext4) is fsck-ed successfully in the initrd according to the /run/initramfs/fsck.log.
From the start-up logs (with "systemd.log_level=debug") we see the ext4 driver report a remount operation not once but five times.
$ grep 'EXT4-fs.*sda6' systemd-debug.log
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600
Those last five appear to be carrying options generated by laptop-mode-tools.
User has disabled laptop-mode.service and laptop-mode.timer, and lmt-poll.service, but the issue remains.
We see several reports of "read-only file-system":
$ grep 'Read-only' systemd-debug.log
Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open `/boot/grub/grubenv': Read-only file system.
Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to /var/log/gpu-manager.log failed (Read-only file system)
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: Read-only file system
...
Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of "/var/log/cups" - Read-only file system
Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file "/var/log/cups/access_log" - Read-only file system
Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open /var/log/lastlog: Read-only file system
We also see several problems with systemd's connection to Dbus:
$ grep 'Transport endpoint' systemd-debug.log
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit change signal for lmt-poll.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change signal for polkit.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit change signal for cups-browsed.service: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: Transport endpoint is not connected
Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change signal for gdomap.service: Transport endpoint is not connected
When the user purged laptop-mode-tools the system starts successfully on battery.
The user installed a fresh instance of 17.10 on a 2nd M2 SSD. When laptop-mode-tools was added to that instance it also exhibited the failure.
# apt-cache rdepends laptop-mode-tools
laptop-mode-tools
Reverse Depends:
systemd
tlp
powertop-1.13
powertop
# apt show systemd | grep Breaks
Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 1.68~), systemd-shim (<< 10-3~), udev (<< 228-5)
# apt-cache policy laptop-mode-tools
laptop-mode-tools:
Installed: (none)
Candidate: 1.71-2ubuntu1 |
|
| 2017-10-24 18:19:18 |
Launchpad Janitor |
laptop-mode-tools (Ubuntu): status |
New |
Confirmed |
|
| 2017-10-24 18:19:18 |
Launchpad Janitor |
systemd (Ubuntu): status |
New |
Confirmed |
|
| 2017-10-24 19:54:10 |
Markus Birth |
bug |
|
|
added subscriber Markus Birth |
| 2017-10-25 08:12:56 |
Bug Watch Updater |
systemd (Debian): status |
Unknown |
Fix Released |
|
| 2018-01-25 14:11:38 |
ryan eckenrode |
attachment added |
|
hdpram for sda sdb https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/+attachment/5042901/+files/b1726930-hdpram.log |
|
| 2018-01-30 10:58:49 |
Stefan Lobas |
attachment added |
|
hdparm.sda https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/+attachment/5045486/+files/hdparm.sda |
|
| 2018-01-31 09:28:02 |
Will Cooke |
bug |
|
|
added subscriber Will Cooke |
| 2018-01-31 10:42:45 |
Daniel van Vugt |
bug |
|
|
added subscriber Daniel van Vugt |
| 2018-02-19 08:35:57 |
Ansgar Bohmann |
bug |
|
|
added subscriber Ansgar Bohmann |
| 2018-02-19 14:32:43 |
Ansgar Bohmann |
information type |
Public |
Public Security |
|
| 2018-02-19 15:01:33 |
Ansgar Bohmann |
information type |
Public Security |
Public |
|
| 2018-02-26 09:14:11 |
Douw Steyn |
attachment added |
|
dmesg.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/+attachment/5063356/+files/dmesg.txt |
|
| 2018-03-07 19:54:47 |
Tony Baines |
bug |
|
|
added subscriber Tony Baines |
| 2018-04-02 19:16:08 |
Thadeu Lima de Souza Cascardo |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-04-02 19:17:04 |
Thadeu Lima de Souza Cascardo |
bug task added |
|
linux (Ubuntu) |
|
| 2018-04-02 19:17:15 |
Thadeu Lima de Souza Cascardo |
bug task added |
|
laptop-mode-tools (Ubuntu Bionic) |
|
| 2018-04-02 19:17:15 |
Thadeu Lima de Souza Cascardo |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2018-04-02 19:17:15 |
Thadeu Lima de Souza Cascardo |
bug task added |
|
systemd (Ubuntu Bionic) |
|
| 2018-04-02 19:17:29 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2018-04-03 08:34:30 |
Will Cooke |
tags |
|
rls-bb-incoming |
|
| 2018-04-04 16:05:51 |
Dimitri John Ledkov |
bug task deleted |
systemd (Debian) |
|
|
| 2018-04-04 16:05:57 |
Dimitri John Ledkov |
systemd (Ubuntu Bionic): status |
Confirmed |
Incomplete |
|
| 2018-04-13 23:43:34 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-04-24 15:59:37 |
Stefan Bader |
nominated for series |
|
Ubuntu Xenial |
|
| 2018-04-24 15:59:37 |
Stefan Bader |
bug task added |
|
laptop-mode-tools (Ubuntu Xenial) |
|
| 2018-04-24 15:59:37 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2018-04-24 15:59:37 |
Stefan Bader |
bug task added |
|
systemd (Ubuntu Xenial) |
|
| 2018-04-24 16:00:42 |
Stefan Bader |
linux (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2018-04-24 16:00:42 |
Stefan Bader |
linux (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2018-04-26 07:01:46 |
Launchpad Janitor |
laptop-mode-tools (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2018-04-26 07:01:46 |
Launchpad Janitor |
systemd (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2018-04-26 07:03:58 |
Ralph Navarro |
bug |
|
|
added subscriber Ralph Navarro |
| 2018-04-27 19:11:56 |
Brad Figg |
tags |
rls-bb-incoming |
rls-bb-incoming verification-needed-xenial |
|
| 2018-05-18 19:01:28 |
Dimitri John Ledkov |
bug task deleted |
systemd (Ubuntu) |
|
|
| 2018-05-18 19:01:32 |
Dimitri John Ledkov |
bug task deleted |
systemd (Ubuntu Xenial) |
|
|
| 2018-05-18 19:01:37 |
Dimitri John Ledkov |
bug task deleted |
systemd (Ubuntu Bionic) |
|
|
| 2018-05-22 00:00:38 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2018-05-22 00:00:38 |
Launchpad Janitor |
cve linked |
|
2017-16995 |
|
| 2018-05-22 00:00:38 |
Launchpad Janitor |
cve linked |
|
2017-17862 |
|
| 2018-05-22 00:00:38 |
Launchpad Janitor |
cve linked |
|
2018-1000004 |
|
| 2018-05-22 00:00:38 |
Launchpad Janitor |
cve linked |
|
2018-3639 |
|
| 2018-05-22 00:00:39 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
