[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
This bug was fixed in the package linux - 4.4.0-127.153 --- linux (4.4.0-127.153) xenial; urgency=medium * CVE-2018-3639 (powerpc) - powerpc/pseries: Support firmware disable of RFI flush - powerpc/powernv: Support firmware disable of RFI flush - powerpc/rfi-flush: Move the logic to avoid a redo into the debugfs code - powerpc/rfi-flush: Make it possible to call setup_rfi_flush() again - powerpc/rfi-flush: Always enable fallback flush on pseries - powerpc/rfi-flush: Differentiate enabled and patched flush types - powerpc/rfi-flush: Call setup_rfi_flush() after LPM migration - powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags - powerpc: Add security feature flags for Spectre/Meltdown - powerpc/pseries: Set or clear security feature flags - powerpc/powernv: Set or clear security feature flags - powerpc/64s: Move cpu_show_meltdown() - powerpc/64s: Enhance the information in cpu_show_meltdown() - powerpc/powernv: Use the security flags in pnv_setup_rfi_flush() - powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() - powerpc/64s: Wire up cpu_show_spectre_v1() - powerpc/64s: Wire up cpu_show_spectre_v2() - powerpc/pseries: Fix clearing of security feature flags - powerpc: Move default security feature flags - powerpc/pseries: Restore default security feature flags on setup - SAUCE: powerpc/64s: Add support for a store forwarding barrier at kernel entry/exit * CVE-2018-3639 (x86) - SAUCE: Clean up IBPB and IBRS control functions and macros - SAUCE: Fix up IBPB and IBRS kernel parameters documentation - SAUCE: Remove #define X86_FEATURE_PTI - x86/cpufeature: Move some of the scattered feature bits to x86_capability - x86/cpufeature: Cleanup get_cpu_cap() - x86/cpu: Probe CPUID leaf 6 even when cpuid_level == 6 - x86/cpufeatures: Add CPUID_7_EDX CPUID leaf - x86/cpufeatures: Add Intel feature bits for Speculation Control - SAUCE: x86/kvm: Expose SPEC_CTRL from the leaf - x86/cpufeatures: Add AMD feature bits for Speculation Control - x86/msr: Add definitions for new speculation control MSRs - SAUCE: x86/msr: Rename MSR spec control feature bits - x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown - x86/cpufeature: Blacklist SPEC_CTRL/PRED_CMD on early Spectre v2 microcodes - x86/speculation: Add basic IBPB (Indirect Branch Prediction Barrier) support - x86/speculation: Add dependency - x86/cpufeatures: Clean up Spectre v2 related CPUID flags - x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature bits on Intel - SAUCE: x86/speculation: Move vendor specific IBRS/IBPB control code - SAUCE: x86: Add alternative_msr_write - SAUCE: x86/nospec: Simplify alternative_msr_write() - SAUCE: x86/bugs: Concentrate bug detection into a separate function - SAUCE: x86/bugs: Concentrate bug reporting into a separate function - arch: Introduce post-init read-only memory - SAUCE: x86/bugs: Read SPEC_CTRL MSR during boot and re-use reserved bits - SAUCE: x86/bugs, KVM: Support the combination of guest and host IBRS - SAUCE: x86/bugs: Expose /sys/../spec_store_bypass - SAUCE: x86/cpufeatures: Add X86_FEATURE_RDS - SAUCE: x86/bugs: Provide boot parameters for the spec_store_bypass_disable mitigation - SAUCE: x86/bugs/intel: Set proper CPU features and setup RDS - SAUCE: x86/bugs: Whitelist allowed SPEC_CTRL MSR values - SAUCE: x86/bugs/AMD: Add support to disable RDS on Fam[15,16,17]h if requested - SAUCE: x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest - SAUCE: x86/speculation: Create spec-ctrl.h to avoid include hell - SAUCE: prctl: Add speculation control prctls - x86/process: Optimize TIF checks in __switch_to_xtra() - SAUCE: x86/process: Allow runtime control of Speculative Store Bypass - SAUCE: x86/speculation: Add prctl for Speculative Store Bypass mitigation - SAUCE: nospec: Allow getting/setting on non-current task - SAUCE: proc: Provide details on speculation flaw mitigations - SAUCE: seccomp: Enable speculation flaw mitigations - SAUCE: x86/bugs: Honour SPEC_CTRL default - SAUCE: x86/bugs: Make boot modes __ro_after_init - SAUCE: prctl: Add force disable speculation - SAUCE: seccomp: Use PR_SPEC_FORCE_DISABLE - selftest/seccomp: Fix the flag name SECCOMP_FILTER_FLAG_TSYNC - SAUCE: seccomp: Add filter flag to opt-out of SSB mitigation - SAUCE: seccomp: Move speculation migitation control to arch code - SAUCE: x86/speculation: Make "seccomp" the default mode for Speculative Store Bypass - SAUCE: x86/bugs: Rename _RDS to _SSBD - SAUCE: proc: Use underscores for SSBD in 'status' - SAUCE: Documentation/spec_ctrl: Do some minor cleanups - SAUCE: x86/bugs: Fix __ssb_select_mitigation() return type - SAUCE: x86/bugs: Make cpu_show_common() static
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
This bug was fixed in the package linux - 4.4.0-127.153 --- linux (4.4.0-127.153) xenial; urgency=medium * CVE-2018-3639 (powerpc) - powerpc/pseries: Support firmware disable of RFI flush - powerpc/powernv: Support firmware disable of RFI flush - powerpc/rfi-flush: Move the logic to avoid a redo into the debugfs code - powerpc/rfi-flush: Make it possible to call setup_rfi_flush() again - powerpc/rfi-flush: Always enable fallback flush on pseries - powerpc/rfi-flush: Differentiate enabled and patched flush types - powerpc/rfi-flush: Call setup_rfi_flush() after LPM migration - powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags - powerpc: Add security feature flags for Spectre/Meltdown - powerpc/pseries: Set or clear security feature flags - powerpc/powernv: Set or clear security feature flags - powerpc/64s: Move cpu_show_meltdown() - powerpc/64s: Enhance the information in cpu_show_meltdown() - powerpc/powernv: Use the security flags in pnv_setup_rfi_flush() - powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() - powerpc/64s: Wire up cpu_show_spectre_v1() - powerpc/64s: Wire up cpu_show_spectre_v2() - powerpc/pseries: Fix clearing of security feature flags - powerpc: Move default security feature flags - powerpc/pseries: Restore default security feature flags on setup - SAUCE: powerpc/64s: Add support for a store forwarding barrier at kernel entry/exit * CVE-2018-3639 (x86) - SAUCE: Clean up IBPB and IBRS control functions and macros - SAUCE: Fix up IBPB and IBRS kernel parameters documentation - SAUCE: Remove #define X86_FEATURE_PTI - x86/cpufeature: Move some of the scattered feature bits to x86_capability - x86/cpufeature: Cleanup get_cpu_cap() - x86/cpu: Probe CPUID leaf 6 even when cpuid_level == 6 - x86/cpufeatures: Add CPUID_7_EDX CPUID leaf - x86/cpufeatures: Add Intel feature bits for Speculation Control - SAUCE: x86/kvm: Expose SPEC_CTRL from the leaf - x86/cpufeatures: Add AMD feature bits for Speculation Control - x86/msr: Add definitions for new speculation control MSRs - SAUCE: x86/msr: Rename MSR spec control feature bits - x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown - x86/cpufeature: Blacklist SPEC_CTRL/PRED_CMD on early Spectre v2 microcodes - x86/speculation: Add basic IBPB (Indirect Branch Prediction Barrier) support - x86/speculation: Add dependency - x86/cpufeatures: Clean up Spectre v2 related CPUID flags - x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature bits on Intel - SAUCE: x86/speculation: Move vendor specific IBRS/IBPB control code - SAUCE: x86: Add alternative_msr_write - SAUCE: x86/nospec: Simplify alternative_msr_write() - SAUCE: x86/bugs: Concentrate bug detection into a separate function - SAUCE: x86/bugs: Concentrate bug reporting into a separate function - arch: Introduce post-init read-only memory - SAUCE: x86/bugs: Read SPEC_CTRL MSR during boot and re-use reserved bits - SAUCE: x86/bugs, KVM: Support the combination of guest and host IBRS - SAUCE: x86/bugs: Expose /sys/../spec_store_bypass - SAUCE: x86/cpufeatures: Add X86_FEATURE_RDS - SAUCE: x86/bugs: Provide boot parameters for the spec_store_bypass_disable mitigation - SAUCE: x86/bugs/intel: Set proper CPU features and setup RDS - SAUCE: x86/bugs: Whitelist allowed SPEC_CTRL MSR values - SAUCE: x86/bugs/AMD: Add support to disable RDS on Fam[15,16,17]h if requested - SAUCE: x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest - SAUCE: x86/speculation: Create spec-ctrl.h to avoid include hell - SAUCE: prctl: Add speculation control prctls - x86/process: Optimize TIF checks in __switch_to_xtra() - SAUCE: x86/process: Allow runtime control of Speculative Store Bypass - SAUCE: x86/speculation: Add prctl for Speculative Store Bypass mitigation - SAUCE: nospec: Allow getting/setting on non-current task - SAUCE: proc: Provide details on speculation flaw mitigations - SAUCE: seccomp: Enable speculation flaw mitigations - SAUCE: x86/bugs: Honour SPEC_CTRL default - SAUCE: x86/bugs: Make boot modes __ro_after_init - SAUCE: prctl: Add force disable speculation - SAUCE: seccomp: Use PR_SPEC_FORCE_DISABLE - selftest/seccomp: Fix the flag name SECCOMP_FILTER_FLAG_TSYNC - SAUCE: seccomp: Add filter flag to opt-out of SSB mitigation - SAUCE: seccomp: Move speculation migitation control to arch code - SAUCE: x86/speculation: Make "seccomp" the default mode for Speculative Store Bypass - SAUCE: x86/bugs: Rename _RDS to _SSBD - SAUCE: proc: Use underscores for SSBD in 'status' - SAUCE: Documentation/spec_ctrl: Do some minor cleanups - SAUCE: x86/bugs: Fix __ssb_select_mitigation() return type - SAUCE: x86/bugs: Make cpu_show_common() static
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Ryan, thanks for the testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
The same patch should work for all kernel versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Correction, it works with the force argument. ACTION=="add", SUBSYSTEM=="usb", RUN+="lmt-udev force" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
I can confirm I no longer have issues. This with the /lib/udev/rules.d/99-laptop-mode.rules changed back to ACTION=="add", SUBSYSTEM=="usb", RUN+="lmt-udev auto" This is on 18.04 laptop-mode-tools 1.71-2 kernel 4.15.0-20 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Removing systemd, as I believe there is nothing to be changed in systemd for this fix to land. Are the affected users fixed with the proposed kernel? Please test proposed kernel asap! Otherwise the change will be dropped from the kernel again on xenial =( ** No longer affects: systemd (Ubuntu) ** No longer affects: systemd (Ubuntu Xenial) ** No longer affects: systemd (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: laptop-mode-tools (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
The kernel fix for this arrived in Xenial/16.04 via upstream stable v4.4.125. ** Also affects: laptop-mode-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
This bug was fixed in the package linux - 4.15.0-15.16 --- linux (4.15.0-15.16) bionic; urgency=medium * linux: 4.15.0-15.16 -proposed tracker (LP: #1761177) * FFe: Enable configuring resume offset via sysfs (LP: #1760106) - PM / hibernate: Make passing hibernate offsets more friendly * /dev/bcache/by-uuid links not created after reboot (LP: #1729145) - SAUCE: (no-up) bcache: decouple emitting a cached_dev CHANGE uevent * Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memory, try cap-htm=off" (kvm) (LP: #1752026) - powerpc: Use feature bit for RTC presence rather than timebase presence - powerpc: Book E: Remove unused CPU_FTR_L2CSR bit - powerpc: Free up CPU feature bits on 64-bit machines - powerpc: Add CPU feature bits for TM bug workarounds on POWER9 v2.2 - powerpc/powernv: Provide a way to force a core into SMT4 mode - KVM: PPC: Book3S HV: Work around transactional memory bugs in POWER9 - KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode - KVM: PPC: Book3S HV: Work around TEXASR bug in fake suspend state * Important Kernel fixes to be backported for Power9 (kvm) (LP: #1758910) - powerpc/mm: Fixup tlbie vs store ordering issue on POWER9 * Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16 namespaces (Bolt / NVMe) (LP: #1757497) - powerpc/64s: Fix lost pending interrupt due to race causing lost update to irq_happened * fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build (LP: #1760876) - [Packaging] include the retpoline extractor in the headers linux (4.15.0-14.15) bionic; urgency=medium * linux: 4.15.0-14.15 -proposed tracker (LP: #1760678) * [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor (LP: #1758662) - net/mlx4_en: Change default QoS settings * AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 (LP: #1759312) - powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features * Bionic update to 4.15.15 stable release (LP: #1760585) - net: dsa: Fix dsa_is_user_port() test inversion - openvswitch: meter: fix the incorrect calculation of max delta_t - qed: Fix MPA unalign flow in case header is split across two packets. - tcp: purge write queue upon aborting the connection - qed: Fix non TCP packets should be dropped on iWARP ll2 connection - sysfs: symlink: export sysfs_create_link_nowarn() - net: phy: relax error checking when creating sysfs link netdev->phydev - devlink: Remove redundant free on error path - macvlan: filter out unsupported feature flags - net: ipv6: keep sk status consistent after datagram connect failure - ipv6: old_dport should be a __be16 in __ip6_datagram_connect() - ipv6: sr: fix NULL pointer dereference when setting encap source address - ipv6: sr: fix scheduling in RCU when creating seg6 lwtunnel state - mlxsw: spectrum_buffers: Set a minimum quota for CPU port traffic - net: phy: Tell caller result of phy_change() - ipv6: Reflect MTU changes on PMTU of exceptions for MTU-less routes - net sched actions: return explicit error when tunnel_key mode is not specified - ppp: avoid loop in xmit recursion detection code - rhashtable: Fix rhlist duplicates insertion - test_rhashtable: add test case for rhltable with duplicate objects - kcm: lock lower socket in kcm_attach - sch_netem: fix skb leak in netem_enqueue() - ieee802154: 6lowpan: fix possible NULL deref in lowpan_device_event() - net: use skb_to_full_sk() in skb_update_prio() - net: Fix hlist corruptions in inet_evict_bucket() - s390/qeth: free netdevice when removing a card - s390/qeth: when thread completes, wake up all waiters - s390/qeth: lock read device while queueing next buffer - s390/qeth: on channel error, reject further cmd requests - soc/fsl/qbman: fix issue in qman_delete_cgr_safe() - dpaa_eth: fix error in dpaa_remove() - dpaa_eth: remove duplicate initialization - dpaa_eth: increment the RX dropped counter when needed - dpaa_eth: remove duplicate increment of the tx_errors counter - dccp: check sk for closed state in dccp_sendmsg() - ipv6: fix access to non-linear packet in ndisc_fill_redirect_hdr_option() - l2tp: do not accept arbitrary sockets - net: ethernet: arc: Fix a potential memory leak if an optional regulator is deferred - net: ethernet: ti: cpsw: add check for in-band mode setting with RGMII PHY interface - net: fec: Fix unbalanced PM runtime calls - net/iucv: Free memory obtained by kzalloc - netlink: avoid a double skb free in genlmsg_mcast() - net: Only honor ifindex in IP_PKTINFO if non-0 - net: systemport: Rewrite __bcm_sysport_tx_reclaim() - qed
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
@rrs > BTW, does Ubuntu have the systemd/udevd mount propagation fix included ? yes no maybe = Added in debian at ed16ca8690eb69c248a0a741def5324eedc9149d Removed from debian at d529d047752d8492d43e42e8b4223d6d37fa3dd3 Meaning it was for a while, if you mean the Debian bug linked to this bug report. But not since laptop-mode-tools 1.68 was fixed. I believe the debian bug attached to this bug report is a red herring. https://git.launchpad.net/~ubuntu-core-dev/+git/systemd/commit/?h =ubuntu-bionic&id=ed16ca8690eb69c248a0a741def5324eedc9149d https://git.launchpad.net/~ubuntu-core- dev/+git/systemd/commit/?h=d529d047752d8492d43e42e8b4223d6d37fa3dd3 ** No longer affects: systemd (Debian) ** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: laptop-mode-tools (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
The "auto" fix works for me too. Having just upgraded an old Dell Vostro v131 to 17.10, it no longer booted from battery but required the mains adaptor to be used. The change noted in #15 worked at it now boots correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
As requested, booted using battery power with setting "auto" in /lib/udev/rules.d/99-laptop-mode.rules. Then changed setting back to "force" and plugged in an external USB HDD (Transcend StoreJet). The USB device seemed to be mounted successfully and I could write to it. Dmesg output attached. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/+attachment/5063356/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Please attach full dmesg if possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
That's because what I instructed in #15 makes laptop-mode-tools ineffective to USB hotplug events. Not something that a user would want. As I see from the reports, this is what I think is happening. 1) Users have some combination of usb devices, getting hotplugged upon discovery. 2) Step 1 results in early invocation of LMT. 3) Which further results in file systems getting ro mounted. This step is still erratic and I have no clue what the calling parent is, to this ro mount. For users who've confirmed that #15 in the workaround works. Can you please apply the workaround, successfully boot, then change back the changes to its original, and then hotplug a USB device ? This will trigger the same chain of events, just that they'll be triggered upon full boot. Which should give us some insight into what may actually be behaving erratic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
(Sorry for accidentally hitting the wrong button earlier.) Same problem here on a fresh installation of Xubuntu 17.10 on a Tuxedo Book BU1406 (with Tuxedo-modifications tuxedo.sh ). Storage: 1 × M.2 SSD: 250 GB Samsung 960 EVO (/dev/nvme0n1). 1 × SATA III HDD: 1 TB Seagate Thin / 5400 rpm / 2.5" (/dev/sda). Disk encryption with LUKS, dm-crypt and LVM are active. The workaround from #15 seems to do the trick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Not really. The BX100 has broken LPM, it's not working under min/med power. The MX300 in askubuntu.com does have a working LPM, just unimaginably slow. I'll build a kernel with the workaround I used in comment #30, fallback to med_power_with_dipm when min_power gets selected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
It sounds like a workaround might be needed for all Crucial SSDs. More models that are problematic in low power mode are mentioned here: https://askubuntu.com/questions/844459/ubuntu-ssd-was-fast-is-now-extremely-slow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
https://lkml.org/lkml/2018/2/15/1184 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
ryan, So looks like we can only use max_power for your disk. What about yours, Stefan? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
I don't know how i missed this yesterday. I installed the kernel, then change the auto to force and reboot. I was assuming that reboot was the test. It appears that i have the same issue after another reboot, or shut down when AC is not attached I did run that link_power_management_policy when from tty2 from the failed boot. The results are the same that I posted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
/sys/devices/pci:00/:00:1f.2/ata1/host0/scsi_host/host0/link_power_management_policy:med_power_with_dipm /sys/devices/pci:00/:00:1f.2/ata2/host1/scsi_host/host1/link_power_management_policy:min_power /sys/devices/pci:00/:00:1f.2/ata3/host2/scsi_host/host2/link_power_management_policy:min_power -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
ryan, Can you attach the output of `find /sys/devices -name 'link_power_management_policy' | xargs grep .`? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
I can confirm this fix worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
This kernel has workaround for CT500BX100SSD1 in #23 and Micron_M600_MTFDDAV128MBF in #24. Use "force" in laptop-mode-tools to test it. people.canonical.com/~khfeng/lp1726930/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
I had the same problem since 4.9.0-4-amd64 Recently I updated the kernel to version 4.14.0-3-amd64 and now everything works as it should. ASUS UX305UA laptop Icon name: computer-laptop Chassis: laptop Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.14.0-3-amd64 Architecture: x86-64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Oh cool. Reminds me of this: https://askubuntu.com/questions/844459/ubuntu-ssd-was-fast-is-now-extremely-slow/879291#879291 I shall have to find the machine with that Crucial SSD... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
I can confirm that the workaround suggested in #15 works for my Asus UX305CA, too. I attached my hdparm output... ** Attachment added: "hdparm.sda" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/+attachment/5045486/+files/hdparm.sda -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
here is my hdpram for both drives ** Attachment added: "hdpram for sda sdb" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/+attachment/5042901/+files/b1726930-hdpram.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
To actually solve this, we need to disable min power LPM for faulty device in the Linux kernel. So please attach disk information if possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Hi, I'm using Debian Stretch on a Thinkpad X220 and had the same issue. The advice from Ritesh Raj Sarraf worked for me too and I just registered to confirm this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Okay. Thanks for the reports. It could very well be the flakiness in usb devices that are causing this problem. Anyways, the best fix for this is to contain usb execution to the runtime module only. Note to self: per module activation was reported to not activating general power savings. Check those before any conclusions s3nt fr0m a $martph0ne, excuse typ0s On 11-Jan-2018 15:56, "Douw Steyn" <1726...@bugs.launchpad.net> wrote: > Works for me too with Ubuntu 17.10 on an Acer Extensa laptop (i5-6200U > SkyLake). Same symptoms but changing 'force' to 'auto' as above results > in successful booting from battery. > > -- > You received this bug notification because you are subscribed to laptop- > mode-tools in Ubuntu. > https://bugs.launchpad.net/bugs/1726930 > > Title: > System fails to start (boot) on battery due to read-only root file- > system > > Status in laptop-mode-tools package in Ubuntu: > Confirmed > Status in systemd package in Ubuntu: > Confirmed > Status in systemd package in Debian: > Fix Released > > Bug 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 endpo
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Works for me too with Ubuntu 17.10 on an Acer Extensa laptop (i5-6200U SkyLake). Same symptoms but changing 'force' to 'auto' as above results in successful booting from battery. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Thanks for confirming @reckenrode. I'd appreciate if more users confirmed the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
I want to confirm that changing 'force' to 'auto' for the last entry in /lib/udev/rules.d/99-laptop-mode.rules did allow me to boot successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
This would still be a flaky device or a kernel bug. Because the mentioned laptop-mode-tools version (1.71) brought in forced execution mode, so that it could apply proper power saving values. That's pretty much it. That does not result in read only rootfs because if it logically did, it'd be seen on every machine. BTW, does Ubuntu have the systemd/udevd mount propagation fix included ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Folks... Does changing to following in /lib/udev/rules.d/99-laptop-mode.rules help ? ACTION=="add", SUBSYSTEM=="usb", RUN+="lmt-udev auto" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
This is more likely to be a kernel bug. Please attach output of `hdparm -I /dev/sdX` here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Like timor I can confirm the bug on the same laptop (ASUS Zenbook UX305CA), too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
This must be an Ubuntu specific problem. I haven't encountered the problem upstream. https://GitHub.com/rickysarraf/laptop-mode-tools s3nt fr0m a $martph0ne, excuse typ0s On 07-Dec-2017 02:36, "timor" <1726...@bugs.launchpad.net> wrote: > Uninstalling laptop-mode-tools helped me, but it's useful package and it > would be nice to get it back. > > -- > You received this bug notification because you are subscribed to laptop- > mode-tools in Ubuntu. > https://bugs.launchpad.net/bugs/1726930 > > Title: > System fails to start (boot) on battery due to read-only root file- > system > > Status in laptop-mode-tools package in Ubuntu: > Confirmed > Status in systemd package in Ubuntu: > Confirmed > Status in systemd package in Debian: > Fix Released > > Bug 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
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Uninstalling laptop-mode-tools helped me, but it's useful package and it would be nice to get it back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
I can confirm bug on ASUS Zenbook UX305CA. I have laptop-mode and pm- utils installed. Let me know how can I help you to fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Changed in: systemd (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Confirmed on a hp Spectre x360 13-4104ng. On battery power, the system DOESN'T boot up. With the charger connected, the system boots up just fine. See https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458 for my apport logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: laptop-mode-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Also affects: laptop-mode-tools Importance: Undecided Status: New ** No longer affects: laptop-mode-tools ** Bug watch added: Debian Bug tracker #762018 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762018 ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762018 Importance: Unknown Status: Unknown ** Description changed: 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 als
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
systemd-resolved.service and systemd.hostnamed.service show up pretty clearly on the startup console as having problems and their logs show repeated entries of the form: -- Logs begin at Mon 2017-10-23 13:01:36 EDT, end at Mon 2017-10-23 13:05:52 EDT. -- Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system Oct 23 13:01:38 T450s systemd[1]: Failed to start Network Name Resolution. Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Unit entered failed state. Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Failed with result 'resources'. Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart. Oct 23 13:01:38 T450s systemd[1]: Stopped Network Name Resolution. Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system -- Logs begin at Mon 2017-10-23 13:01:36 EDT, end at Mon 2017-10-23 13:06:20 EDT. -- Oct 23 13:01:38 T450s systemd[1]: systemd-hostnamed.service: Failed to run 'start' task: Read-only file system Oct 23 13:01:38 T450s systemd[1]: Failed to start Hostname Service. Oct 23 13:01:38 T450s systemd[1]: systemd-hostnamed.service: Unit entered failed state. Oct 23 13:01:38 T450s systemd[1]: systemd-hostnamed.service: Failed with result 'resources'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Attachment added: "Photo of startup console messages" https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+attachment/4991895/+files/IMAG2881.jpg ** Description changed: 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 + sys
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
The systemd/dbus issues are possibly related to the partial fix detailed in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1591411 However, there are 2 upstream DBus bugs/fixes and I believe one of them isn't in 17.10's DBus at present: "unix fd in-flight counting broken" https://bugs.freedesktop.org/show_bug.cgi?id=95263 " _dbus_timeout_set_enabled doesn't reset timeout ticking" https://bugs.freedesktop.org/show_bug.cgi?id=95619#c10 ** Bug watch added: freedesktop.org Bugzilla #95263 https://bugs.freedesktop.org/show_bug.cgi?id=95263 ** Bug watch added: freedesktop.org Bugzilla #95619 https://bugs.freedesktop.org/show_bug.cgi?id=95619 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Attachment added: "hwinfo.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/+attachment/4991778/+files/hwinfo.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Possibly related: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Description changed: 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 + $ 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 + $ 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 + $ 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 t