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)
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
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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
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
@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
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
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
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
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.
Please attach full dmesg if possible.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to start (boot) on battery due to read-only root file-
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
(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"
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to start (boot) on battery due to
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to start (boot) on battery due to
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
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
https://lkml.org/lkml/2018/2/15/1184
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to start (boot) on battery due to read-only root file-
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to
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
/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
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
I can confirm this fix worked for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to start (boot) on battery due to read-only root file-
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
Touch seeded packages, which is subscribed to
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
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
Touch seeded packages, which is
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
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
Touch seeded packages, which is
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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
Touch seeded packages, which is subscribed to systemd in
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
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
Touch seeded packages, which is subscribed
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to start
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to start
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
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to start (boot) on
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
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** 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
** 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,
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]:
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"
** 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Possibly related:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to start
** 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
53 matches
Mail list logo
