[SOLVED] Suspend to RAM stopped working in liquorix 5.1.0-9
Posted: Jun 12, 19, 5:04 phd
 Status: Interested
Joined: 20 Dec 2018
Posts: 15
Reply Quote
I noticed that suspend to RAM stopped working in liquorix 5.1.0-9.
It worked fine in 5.1.0-8 and all previous liquorix builds and kernel versions.

When trying to suspend to RAM the screen turns black and after a second it is on again.
Computer doesn't even stop for a moment during this.
Looks like the DE knows it should handle suspend, but the suspend doesn't actually happen.

Calling
:: Code ::
sudo /usr/sbin/pm-suspend
directly doesn't work either.

Anyone has similar issues? Or is it just my (quite old) laptop?

inxi -b:
:: Code ::
System:    Host: lap Kernel: 5.1.0-9.1-liquorix-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.16.0
           Distro: Ubuntu 19.04 (Disco Dingo)
Machine:   Type: Laptop System: Acer product: Aspire 5750G v: V1.11 serial: LXRMU020251290D1311601
           Mobo: Acer model: JE50_HR serial: N/A BIOS: Acer v: 1.11 date: 05/24/2011
Battery:   ID-1: BAT0 charge: 21.7 Wh condition: 21.7/48.8 Wh (44%)
CPU:       Dual Core: Intel Core i3-2310M type: MT MCP speed: 1248 MHz min/max: 800/2100 MHz
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel
           Device-2: NVIDIA GF119M [GeForce GT 520M] driver: nouveau v: kernel
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.0.2
Network:   Device-1: Broadcom and subsidiaries NetLink BCM57785 Gigabit Ethernet PCIe driver: tg3
           Device-2: Broadcom and subsidiaries BCM43227 802.11b/g/n driver: wl
Drives:    Local Storage: total: 465.76 GiB used: 136.31 GiB (29.3%)
Info:      Processes: 284 Uptime: 3m Memory: 3.71 GiB used: 1.16 GiB (31.2%) Shell: bash inxi: 3.0.33

Back to top
Posted: Jun 12, 19, 7:27 damentz
 Status: Assistant
Joined: 09 Sep 2008
Posts: 1135
Reply Quote
It looks like to me that some release candidate patches are causing problems with your GPU configuration with nouveau:

:: Code ::
drm-nouveau-disp-dp-respect-sink-limits-when-selecti.patch
drm-nouveau-fix-duplication-of-nv50_head_atom-struct.patch
drm-nouveau-kms-gf119-gp10x-push-headsetcontroloutpu.patch
drm-nouveau-kms-gv100-fix-spurious-window-immediate-.patch


Have you tried running nvidia's proprietary drivers? I know your GPU is considered legacy by nvidia, but it might have better behavior with suspend.
Back to top
Posted: Jun 12, 19, 9:47 phd
 Status: Interested
Joined: 20 Dec 2018
Posts: 15
Reply Quote
I have blacklisted the nouveau driver, but the issue still occurs. Same symptoms.

:: Code ::
# cat /proc/cmdline
audit=0 rcupdate.rcu_expedited=1 rcu_nocbs=0-64 BOOT_IMAGE=/boot/vmlinuz-5.1.0-9.1-liquorix-amd64 root=UUID=1046a1c2-e20f-4522-9463-35668ec4166a ro quiet splash logo.nologo vt.handoff=1 modprobe.blacklist=nouveau

:: Code ::
# lsmod | grep nouveau | wc -l
0

:: Code ::
$ inxi -b
System:    Host: lap Kernel: 5.1.0-9.1-liquorix-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.16.0
           Distro: Ubuntu 19.04 (Disco Dingo)
Machine:   Type: Laptop System: Acer product: Aspire 5750G v: V1.11 serial: <root required>
           Mobo: Acer model: JE50_HR serial: <root required> BIOS: Acer v: 1.11 date: 05/24/2011
Battery:   ID-1: BAT0 charge: 19.5 Wh condition: 21.7/48.8 Wh (44%)
CPU:       Dual Core: Intel Core i3-2310M type: MT MCP speed: 909 MHz min/max: 800/2100 MHz
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel
           Device-2: NVIDIA GF119M [GeForce GT 520M] driver: N/A
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.0.2
Network:   Device-1: Broadcom and subsidiaries NetLink BCM57785 Gigabit Ethernet PCIe driver: tg3
           Device-2: Broadcom and subsidiaries BCM43227 802.11b/g/n driver: wl
Drives:    Local Storage: total: 465.76 GiB used: 136.38 GiB (29.3%)
Info:      Processes: 268 Uptime: 10m Memory: 3.71 GiB used: 1.24 GiB (33.5%) Shell: bash inxi: 3.0.33

Back to top
Posted: Jun 12, 19, 18:33 damentz
 Status: Assistant
Joined: 09 Sep 2008
Posts: 1135
Reply Quote
Hmm, well there is one thing I'll change immediately. I was pretty sure I removed this section from the kernel cmdline options but xconfig didn't persist the change to the filesystem:

:: Code ::
rcupdate.rcu_expedited=1 rcu_nocbs=0-64


A new release will be out in a few hours for you to try. I don't think it will help but it's definitely _not_ helping.
Back to top
Posted: Jun 13, 19, 1:13 phd
 Status: Interested
Joined: 20 Dec 2018
Posts: 15
Reply Quote
I've updated to 5.1.0-9.3, but as you predicted, this didn't affect this problem.

There is also another issue I have with all releases of 5.1.0-9.x on every one of my 3 computers (specs below).
On reboot/halt they reach the end of the procedure:
:: Code ::
...
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
[ OK ] Started Reboot.
[ OK ] Reached target Reboot.
and then wait for 180 seconds.
Then another message appears:
:: Code ::
[5548]: Failed to unmount /var: Device or resource busy
and computer reboots/halts.
With 5.1.0-8 and previous this never happened.

laptop:
:: Code ::
System:    Host: lap Kernel: 5.1.0-9.3-liquorix-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.16.0
           Distro: Ubuntu 19.04 (Disco Dingo)
Machine:   Type: Laptop System: Acer product: Aspire 5750G v: V1.11 serial: <root required>
           Mobo: Acer model: JE50_HR serial: <root required> BIOS: Acer v: 1.11 date: 05/24/2011
Battery:   ID-1: BAT0 charge: 21.7 Wh condition: 21.7/48.8 Wh (44%)
CPU:       Dual Core: Intel Core i3-2310M type: MT MCP speed: 1159 MHz min/max: 800/2100 MHz
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel
           Device-2: NVIDIA GF119M [GeForce GT 520M] driver: nouveau v: kernel
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.0.2
Network:   Device-1: Broadcom and subsidiaries NetLink BCM57785 Gigabit Ethernet PCIe driver: tg3
           Device-2: Broadcom and subsidiaries BCM43227 802.11b/g/n driver: wl
Drives:    Local Storage: total: 465.76 GiB used: 136.23 GiB (29.2%)
Info:      Processes: 273 Uptime: 4m Memory: 3.71 GiB used: 1.15 GiB (31.1%) Shell: bash inxi: 3.0.33
PC1:
:: Code ::
System:    Host: phd Kernel: 5.1.0-9.3-liquorix-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.16.0
           Distro: Ubuntu 19.04 (Disco Dingo)
Machine:   Type: Desktop Mobo: MSI model: Z170A-G43 PLUS (MS-7970) v: 1.0 serial: <root required>
           UEFI [Legacy]: American Megatrends v: 3.20 date: 11/03/2015
CPU:       Quad Core: Intel Core i5-6600K type: MCP speed: 1402 MHz min/max: 800/3900 MHz
Graphics:  Device-1: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 430.26
           Display: x11 server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 430.26
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
Drives:    Local Storage: total: 2.63 TiB used: 863.89 GiB (32.1%)
Info:      Processes: 262 Uptime: 1h 25m Memory: 15.63 GiB used: 2.35 GiB (15.0%) Shell: bash inxi: 3.0.33
PC2:
:: Code ::
System:    Host: hd Kernel: 5.1.0-9.3-liquorix-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.16.0
           Distro: Ubuntu 19.04 (Disco Dingo)
Machine:   Type: Desktop Mobo: Gigabyte model: P35-DS3L v: x.x serial: <root required> BIOS: Award v: F9 date: 06/19/2009
CPU:       Quad Core: Intel Core2 Quad Q6600 type: MCP speed: 1600 MHz min/max: 1600/2400 MHz
Graphics:  Device-1: NVIDIA G94 [GeForce 9600 GT] driver: nouveau v: kernel
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa tty: N/A
           OpenGL: renderer: NV94 v: 3.3 Mesa 19.0.2
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
Drives:    Local Storage: total: 456.46 GiB used: 308.73 GiB (67.6%)
Info:      Processes: 271 Uptime: 1h 45m Memory: 7.79 GiB used: 2.15 GiB (27.5%) Shell: bash inxi: 3.0.33

Back to top
Posted: Jun 13, 19, 5:37 cdysthe
 Status: Interested
Joined: 05 Sep 2011
Posts: 20
Location: Gloucester, MA
Reply Quote
I can confirm this issue with Ubuntu 19.04 on a Thinkpad T460s. I'm not able to do a clean shut-down either. The process freezes at end of shut-down and I have cycle with power button.
Back to top
Posted: Jun 13, 19, 6:13 damentz
 Status: Assistant
Joined: 09 Sep 2008
Posts: 1135
Reply Quote
phd, cdsythe, thanks for the feedback.

I just got done reverting all the 5.1.10 release candidate patches and a new release should be up in the next 2-3 hours.

When the next official update comes out, I'll look for any indication that the offending patch causing suspend / shutdown bugs was removed / reverted before updating Liquorix. Worst case, it'll be up to 2 weeks before we see reports in kernel.org's bugzilla or LKML.
Back to top
Posted: Jun 13, 19, 8:03 phd
 Status: Interested
Joined: 20 Dec 2018
Posts: 15
Reply Quote
@damentz

5.1.0-9.4 halts/restarts properly.
Also the hibernation problem is fixed.

Thanks!
Back to top
Posted: Jun 13, 19, 11:02 cdysthe
 Status: Interested
Joined: 05 Sep 2011
Posts: 20
Location: Gloucester, MA
Reply Quote
Confirmed suspend and power off works. Thanks!
Back to top
Display posts from previous:   

All times are GMT - 8 Hours
Contact Us
Hosting: Pair Networks: 0.037
Forum Style © techpatterns.com
info

tech forums