On *battery* power when ubuntu 17.10 boots, after the splashscreen a black screen appears

[Marco]

Also happens other people here https://askubuntu.com/questions/987821/asus-laptop-wont-boot-to-login-screen-when-on-battery-power-after-17-10-upgrade

I tried to manually upgrade the kernel to the latest one from the ubuntu mainline.
I tried to setup lightdm/gdm3 with no success.
However when setting up lightdm I can access to a tty and login. The file system for some weird reason becomes read-only.

If I plug the power chord and I reboot everything works fine. Lightdm comes up or gdm3 comes up depending on the setup that I made.

Hope this helps

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gdm3 3.26.1-3ubuntu3
Uname: Linux 4.15.0-041500rc9-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME-Flashback:GNOME
Date: Mon Jan 29 22:25:14 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-10 (690 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gdm3
UpgradeStatus: Upgraded to artful on 2018-01-27 (1 days ago)
---
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME-Flashback:GNOME
DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-10 (691 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Package: linux
PackageArchitecture: amd64
Tags: artful
Uname: Linux 4.15.0-041500rc9-generic x86_64
UpgradeStatus: Upgraded to artful on 2018-01-27 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1746099

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15

[Joseph Salisbury (jsalisbury)]

Also, can you boot back into a 17.04 kernel while on 17.10 to see if the bug still exists or not? If you don't have a 17.04 kernel still installed, you can get a 4.10 based Artful one from:

https://launchpad.net/ubuntu/+source/linux/4.10.0-26.30

Just select your arch under the "Builds" section and install the linux-image and linux-image-extra .deb packages.

[Marco (beatpanic)]

apport information

[Marco (beatpanic)]

apport information

[Marco (beatpanic)]

apport information

[Marco (beatpanic)]

apport information

[Marco (beatpanic)]

Hi,

It happened when upgrading from ubuntu 17.04 to 17.10
On 17.04 everything worked as expected on battery.

Steps that I tried as you suggested:

* I booted into 4.10 kernel and with battery power the problem still happens
* I booted into 4.15 kernel downloaded from the ubuntu mainline repo and with battery power the problem still happens.

I attached the logs again including JournalErrors.txt

Hope it helps! Thank you in advance

[Joseph Salisbury (jsalisbury)]

Do you recall the kernel version you were running on 17.04 when this bug did not happen?

[Marco (beatpanic)]

I do not remember for sure but I guess it was the last kernel provided with ubuntu 17.04. I upgraded 17.04 to keep in sync with security updates. My guess is that it's the 4.10 "series"

[Marco (beatpanic)]

I tried also to boot with 4.7.2-040702-generic with no success (it was an old kernel that worked on this machine)
The first kernel version that I have on this machine is 4.5.0-040500-generic, and even that one does not go after the splash screen. In previous ubuntu releases everything was working.

I noticed also when being on battery and booting that I can switch to a tty with ctrl+alt+F1 and I see some pcierror message. Not sure if it's relevant

[Joseph Salisbury (jsalisbury)]

If 17.04 did not exhibit the bug, it would be good to test one of the Xenial kernels. If you still expierence the bug with this kernel and a 17.10 userspace, the cause might be outside of the kernel.

Can you test the following kernel on 17.10:
https://launchpad.net/ubuntu/+source/linux/4.4.0-21.37

[Marco (beatpanic)]

Yes I can. Should I install debs or re-build it from source? If debs are available I can give it a try really quick. Thanks

[Marco (beatpanic)]

I found the debs. Sorry I am not that confident with launchpad.

Can these debs be installed from 17.10?

* https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9594168/+files/linux-headers-4.4.0-21-generic_4.4.0-21.37_amd64.deb
* https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9594168/+files/linux-headers-4.4.0-21_4.4.0-21.37_all.deb
* https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9594168/+files/linux-image-4.4.0-21-generic_4.4.0-21.37_amd64.deb

And,are they the ones that you would like me to try?

Thanks

[Joseph Salisbury (jsalisbury)]

You only need the linux-image and linux-image-extra .debs. They are available from here, under the "Built Files" section:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9594168

[Marco (beatpanic)]

I tried those debs (kernel 4.4.0-21-generic, however (with battery) I have same behaviour: black screen a PCIe Bus Error: printed which I cannot copy easily since, for some reason, the file system becomes read-only.

[Joseph Salisbury (jsalisbury)]

It sounds like the kernel is ruled out as the cause of this bug. The bug still happens with Xenial and 4.10 based kernels on Artful and the bug didn't happen on Zesty or Xenial prior to upgrading to Artful. This indicates something outside of the kernel.

[Mihai Serban (mihais)]

Possible duplicate of:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930

Please test the workaround given in comment #15: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/comments/15

[jperk2 (jperk2)]

Hi, I'm the asker of the question linked https://askubuntu.com/questions/987821/asus-laptop-wont-boot-to-login-screen-when-on-battery-power-after-17-10-upgrade

I can confirm that switching kernels did not work for me. I tried 4.4.0-21-generic. I can also confirm the read-only issue.

Following the workaround linked by Mihai worked for me:

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/comments/15

in /lib/udev/rules.d/99-laptop-mode.rules, I changed:
ACTION=="add", SUBSYSTEM=="usb", RUN+="lmt-udev force"
to
ACTION=="add", SUBSYSTEM=="usb", RUN+="lmt-udev auto"

And was able to reboot on battery power. Thanks!

[Will Cooke (willcooke)]

Confident this is a dupe of LP: 1726930 and the same work-around applies. Marking this as a dupe.

[Marco (beatpanic)]

I can confirm that the workaround worked also for me!
Yeah, this bug seems a duplicate of https://bugs.launchpad.net/bugs/1726930