You are not logged in.

#1 2019-10-28 05:06:15

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

System freezing on suspend

Hi guys,

I'm running Arch Linux with GNOME on my computer, with an Nvidia video card (maybe it's relevant), and it has been freezing on my for some time now when I try to suspend the system through the GNOME suspend button (power menu + Alt click). It doesn't happen always, though; if I just rebooted my computer, it usually suspends just fine, but after some time running it, maybe a few days, I try to suspend it and it freezes before suspending.

I can't see anything suspicious in the boot journal where the freeze happened:

$ journalctl -b -1 | tail -50
                                                       lock@resource:///org/gnome/shell/ui/screenShield.js:1318:9
                                                       LockAsync@resource:///org/gnome/shell/ui/shellDBus.js:360:9
                                                       _handleMethodCall@resource:///org/gnome/gjs/modules/overrides/Gio.js:371:9
                                                       _wrapJSObject/<@resource:///org/gnome/gjs/modules/overrides/Gio.js:404:16
out 28 01:16:24 diogobaeder-desktop gnome-shell[6772]: Usage of object.actor is deprecated for ButtonBox
                                                       get@resource:///org/gnome/shell/ui/environment.js:249:29
                                                       destroyTray@/home/diogobaeder/.local/share/gnome-shell/extensions/tray-icons@zhangkaizhao.com/extension.js:160:5
                                                       disable@/home/diogobaeder/.local/share/gnome-shell/extensions/tray-icons@zhangkaizhao.com/extension.js:25:5
                                                       _callExtensionDisable@resource:///org/gnome/shell/ui/extensionSystem.js:78:13
                                                       _disableAllExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:498:17
                                                       _disableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:497:13
                                                       _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:515:13
                                                       _emit@resource:///org/gnome/gjs/modules/signals.js:135:27
                                                       _sync@resource:///org/gnome/shell/ui/sessionMode.js:205:9
                                                       pushMode@resource:///org/gnome/shell/ui/sessionMode.js:167:9
                                                       activate@resource:///org/gnome/shell/ui/screenShield.js:1269:17
                                                       lock@resource:///org/gnome/shell/ui/screenShield.js:1318:9
                                                       LockAsync@resource:///org/gnome/shell/ui/shellDBus.js:360:9
                                                       _handleMethodCall@resource:///org/gnome/gjs/modules/overrides/Gio.js:371:9
                                                       _wrapJSObject/<@resource:///org/gnome/gjs/modules/overrides/Gio.js:404:16
out 28 01:16:24 diogobaeder-desktop gnome-shell[6772]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed
out 28 01:16:28 diogobaeder-desktop kernel: usb 5-1: reset high-speed USB device number 2 using xhci_hcd
out 28 01:16:28 diogobaeder-desktop NetworkManager[674]: <info>  [1572236188.6876] manager: sleep: sleep requested (sleeping: no  enabled: yes)
out 28 01:16:28 diogobaeder-desktop NetworkManager[674]: <info>  [1572236188.6877] manager: NetworkManager state is now ASLEEP
out 28 01:16:28 diogobaeder-desktop NetworkManager[674]: <info>  [1572236188.6880] device (enp7s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
out 28 01:16:28 diogobaeder-desktop gnome-shell[1921]: Screen lock is locked down, not locking
out 28 01:16:28 diogobaeder-desktop evolution[7547]: Network disconnected.  Forced offline.
out 28 01:16:28 diogobaeder-desktop dbus-daemon[673]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=674 comm="/usr/bin/NetworkManager --no-daemon ")
out 28 01:16:28 diogobaeder-desktop systemd[1]: Starting Network Manager Script Dispatcher Service...
out 28 01:16:28 diogobaeder-desktop dbus-daemon[673]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
out 28 01:16:28 diogobaeder-desktop systemd[1]: Started Network Manager Script Dispatcher Service.
out 28 01:16:28 diogobaeder-desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
out 28 01:16:28 diogobaeder-desktop kernel: audit: type=1130 audit(1572236188.714:261): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
out 28 01:16:28 diogobaeder-desktop NetworkManager[674]: <info>  [1572236188.7182] device (enp7s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
out 28 01:16:28 diogobaeder-desktop avahi-daemon[671]: Withdrawing address record for fe80::8d08:7fa6:6f8:95b0 on enp7s0.
out 28 01:16:28 diogobaeder-desktop avahi-daemon[671]: Leaving mDNS multicast group on interface enp7s0.IPv6 with address fe80::8d08:7fa6:6f8:95b0.
out 28 01:16:28 diogobaeder-desktop NetworkManager[674]: <info>  [1572236188.7209] dhcp4 (enp7s0): canceled DHCP transaction
out 28 01:16:28 diogobaeder-desktop avahi-daemon[671]: Interface enp7s0.IPv6 no longer relevant for mDNS.
out 28 01:16:28 diogobaeder-desktop NetworkManager[674]: <info>  [1572236188.7209] dhcp4 (enp7s0): state changed bound -> done
out 28 01:16:28 diogobaeder-desktop avahi-daemon[671]: Withdrawing address record for 192.168.1.104 on enp7s0.
out 28 01:16:28 diogobaeder-desktop avahi-daemon[671]: Leaving mDNS multicast group on interface enp7s0.IPv4 with address 192.168.1.104.
out 28 01:16:28 diogobaeder-desktop avahi-daemon[671]: Interface enp7s0.IPv4 no longer relevant for mDNS.
out 28 01:16:28 diogobaeder-desktop NetworkManager[674]: <info>  [1572236188.7424] device (enp7s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
out 28 01:16:28 diogobaeder-desktop kernel: r8169 0000:07:00.0 enp7s0: Link is Down
out 28 01:16:28 diogobaeder-desktop gsd-sharing[7339]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
out 28 01:16:28 diogobaeder-desktop systemd[1068]: Stopping gnome-user-share WebDAV server...
out 28 01:16:28 diogobaeder-desktop systemd[1]: Reached target Sleep.
out 28 01:16:28 diogobaeder-desktop systemd[1]: Starting Suspend...
out 28 01:16:28 diogobaeder-desktop systemd-sleep[111387]: Suspending system...
out 28 01:16:28 diogobaeder-desktop kernel: PM: suspend entry (deep)

This is what I have here in terms of video:

$ sudo lshw -c video
  *-display               
       description: VGA compatible controller
       product: GP107 [GeForce GTX 1050 Ti]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:54 memory:fa000000-faffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:e000(size=128) memory:c0000-dffff

And some info about the versions I have here:

$ uname -a
Linux diogobaeder-desktop 5.3.7-arch1-1-ARCH #1 SMP PREEMPT Fri Oct 18 00:17:03 UTC 2019 x86_64 GNU/Linux
$ pacman -Qi nvidia | grep -i versão
Versão               : 435.21-13
$ pacman -Qi gnome-shell | grep -i versão
Versão               : 1:3.34.1+5+g072a9a484-1

Does anybody have any idea what might be going on? Any suggestions of how I can find what the problem is?

Thanks!
Diogo

Offline

#2 2019-10-31 03:21:01

efexos
Member
Registered: 2019-08-30
Posts: 8

Re: System freezing on suspend

Does PC completly freezes i.e. no cursor movement no Caps led no any thing? Does the fan blows harder after its frozen? Maybe there is some application using 100% of the CPU it freezes the system sometimes. Ruling this out might be the good idea by opening htop and try to suspend see what befalls.

So some logs will be much appriciated.
try suspending with terminal
# systemctl suspend
OR
# pm-suspend

if you dont have pm try it from aur pm-utils
and do.
# PM_DEBUG=true (might need root if user has no permission)

after that try suspending with pm-suspend if it freezes again check
# cat /var/log/pm-suspend.log

Also upload the log here.

Offline

#3 2019-10-31 06:33:42

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

I forgot to mention: I usually suspend after locking my screen. Do you think this might have any relationship with the issue?

I'll try your suggestions, thanks! Will keep you up-to-date to my findings.

Offline

#4 2019-10-31 07:20:30

seth
Member
Registered: 2012-09-03
Posts: 12,905

Re: System freezing on suspend

it freezes before suspending

Please elaborate on this: does it freeze and then not suspend at all (ie. the output remains fed a video signal, fans keep spinning, etc.)? If so, can you still move the mousecursor when this happens?
Or do you infer it must have frozen before the suspend because it doesn't wake up later on? If so, does the time spent in S3 matter (long sleeps fail to wake up, short sleeps - couple of seconds - work fine)?

Offline

#5 2019-11-02 07:26:16

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

Hi guys, sorry for the delay to reply here.

In the latest few days this hasn't happened, but next time it does, I'll take note of every detail I can find. Here's what I recall from previous instances of the issue:
1. I first lock my desktop environment - so that it's still locked when I wake it up later (got cats at home and they apparently like programming too)
2. Then I click the suspend button
3. The screen goes blank, the fan keeps working kinda busy (sounds like there's some CPU consumption going on)
4. The computer doesn't respond to any command, not even trying to get into shell sessions, I can only either reset it or force-power-off (I haven't tried REISUB yet, though - will try it next time)

I'll update you guys as soon as I'm able to reproduce the issue again. If for some reason I can't, it will probably mean that the issue went away with the latest updates I did to my local packages (I've been updating more frequently in the last few days).

Thanks a lot for your help so far, guys! :-)

Offline

#6 2019-11-02 07:38:49

seth
Member
Registered: 2012-09-03
Posts: 12,905

Re: System freezing on suspend

For this description, really try (if the problem re-emerges) whether you can reliably suspend skipping the locker and directly running "systemctl suspend" to rule out any interference from the screenlocker.

Offline

#7 2019-11-04 05:33:02

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

Hi guys,

I haven't yet tried suspending without locking, but I'll do this from now on and check if the problem happens if I rule out the locker.

However, I just tried again to suspend after locking, and could reproduce the problem again, so I took some notes:

1. The CPU fan seems to be running, not fast but not idle either (so I have the impression that there's some processing going on)
2. The monitor goes to standby mode - blinking as it's not receiving video signal
3. The desktop case LED keeps full on (when suspend works, this LED goes into blinking mode)
4. Alt+PrintScr+REISUB doesn't work (tried with ~4sec between each key, then tried faster, neither worked) - I expected it to work, maybe the kernel got unresponsive?

Anyway, I'll keep on trying but now by suspending with systemctl directly (will avoid using the GNOME button for it). Will report here my other findings.

Thanks again!

Offline

#8 2019-11-04 08:04:42

seth
Member
Registered: 2012-09-03
Posts: 12,905

Re: System freezing on suspend

Reg. (4) - did you enable the sysreq?
https://wiki.archlinux.org/index.php/Ke … uts#Kernel

Offline

#9 2019-11-04 13:53:27

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

I did, yeah:

$ cat /proc/sys/kernel/sysrq
1

Offline

#10 2019-11-05 01:21:26

cfeedback
Member
From: Portland, OR
Registered: 2019-05-11
Posts: 11

Re: System freezing on suspend

I would suggest running FIrmware Test Suites (fwts-git on the AUR) which will most likely inform you that your BIOS was written by a bunch of monkeys who were just as likely to produce Shakespeare as they were an error free DSDT.

It can, however, give you some clues to point you in the right direction. (If your BIOS gives you the option to pick between S1 or S3 sleep states you might try whichever isn't currently selected)


Design is a funny word. Some people think design means how it looks. But, of course, if you dig deeper, it’s how it really works. You have to grok what it is all about.

― S. Jobs

Offline

#11 2019-11-05 04:32:58

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

OK, I just managed to reproduce the issue by running fwts (thanks for the tip!!!). Here's a tail of the logs, which seems to give a clue of what might be going on:

$ tail results.log
6 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.
================================================================================

s4: S4 hibernate/resume test.
--------------------------------------------------------------------------------
Test 1 of 1: S4 hibernate/resume test.
Defaulted to run 1 test, run --s4-multiple=N to run more S4 cycles 
S4 cycle 1 of 1 
Using logind as the default power method.
Requesting Hibernate action 

which means, it didn't resume from hibernation. I ran this earlier too, and it crashed at the same point ("Requesting Hibernate action" - I ran it earlier because I didn't notice I would need to install "msr" to have more CPU information).

This problem, however, has started to happen a bit recently, I've been running Arch on this computer for a few years by locking+suspending successfully. However, I've always thought that hitting "suspend" while my screen is locked did suspend the computer, so maybe something happened that is switching to hibernation instead ("S4"). Maybe not even in all situations - because sometimes I can get the computer to suspend and then wake it up via my keyboard.

Here's a bit more info about my tests, in case it's useful:

$ grep FAILED results.log
FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel message: [ 3.858278] ACPI
FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel message: [ 3.858303] ACPI
FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel message: [ 3.858346] ACPI
FAILED [LOW] KlogAcpiSystemIOConflictLpcIchWatchDogTimer: Test 1, LOW Kernel
FAILED [HIGH] SMBIOSNoEntryPoint: Test 1, Could not find any SMBIOS Table Entry
FAILED [HIGH] SbbrSmbiosNoStruct: Test 4, Cannot find SMBIOS30 table entry.
FAILED [CRITICAL] SBBR RSDP:: Test 1, Structure of RSDP Table is not consistent
FAILED [MEDIUM] NoDSDT: Test 1, Could not read ACPI DSDT table.
FAILED [LOW] NoLIDPath: Test 1, No lid interface available: cannot test.
FAILED [HIGH] acpi_table_check_test4: Test 2, Test DSDT table is NOT
FAILED [CRITICAL] PmDevicesFailedToSuspend: Test 1, CRITICAL Kernel message: [
$ grep -E '[1-9] failed' -B3 results.log
Found 4 unique errors in kernel log.

================================================================================
0 passed, 4 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.
--
FAILED [HIGH] SbbrSmbiosNoStruct: Test 4, Cannot find SMBIOS30 table entry.

================================================================================
6 passed, 2 failed, 0 warning, 0 aborted, 1 skipped, 0 info only.
--
with ACPI 6.0 or later and/or does not use 64 bit xsdt addresses.

================================================================================
0 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.
--
FAILED [MEDIUM] NoDSDT: Test 1, Could not read ACPI DSDT table.

================================================================================
0 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.
--
WARNING: Test 3, SBBR Recommended ACPI table "PCCT" not found.

================================================================================
0 passed, 1 failed, 15 warnings, 0 aborted, 0 skipped, 0 info only.
--
PASSED: Test 1, All resumes took less than 15.00 seconds.

================================================================================
6 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.

Thanks a bunch for the help so far!

Offline

#12 2019-11-05 04:37:38

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

This might be more useful:

klog: Scan kernel log for errors and warnings.
--------------------------------------------------------------------------------
Test 1 of 1: Kernel log error check.
Kernel message: [ 0.663258] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

ADVICE: This is not exactly a failure but a warning from the kernel. The
MSR_IA32_ENERGY_PERF_BIAS was initialized and defaulted to a high performance
bias setting. The kernel has detected this and changed it down to a 'normal'
bias setting.

FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel message: [ 3.858278] ACPI
Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with
OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.SBRG.GPBX) (20190703
/utaddress-204)

ADVICE: ACPI AML interpreter has found some non-conforming AML code. This should
be investigated and fixed.

FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel message: [ 3.858303] ACPI
Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with
OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.SBRG.GPBX) (20190703
/utaddress-204)

ADVICE: ACPI AML interpreter has found some non-conforming AML code. This should
be investigated and fixed.

FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel message: [ 3.858346] ACPI
Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with
OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.SBRG.GPBX) (20190703
/utaddress-204)

ADVICE: ACPI AML interpreter has found some non-conforming AML code. This should
be investigated and fixed.

FAILED [LOW] KlogAcpiSystemIOConflictLpcIchWatchDogTimer: Test 1, LOW Kernel
message: [ 3.858356] lpc_ich: Resource conflict(s) found affecting gpio_ich

ADVICE: A resource conflict has occurred between ACPI OperationRegions and the
same I/O region used by the lpc_ich driver for the General Purpose I/O (GPIO)
region. Sometimes this GPIO region is used by the firmware for rfkill or LED
controls or very rarely for the Embedded Controller System Control Interrupt.
This may require deeper inspection to check if the conflict will lead to any
real issues. However, in the vast majority of cases this warning can be ignored
as no harm will occur.

Found 4 unique errors in kernel log.

Offline

#13 2019-11-05 05:39:42

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

OK, sorry for the flood of replies here, but I found a few more things that I was not paying attention to, which might be related with the issue:

1. I didn't have the hibernation feature enable at all! I thought I did, but neither the hook was added to mkinitcpio or the device added to the kernel parameters. I made sure both were added now, tested and now hibernation does work (tested with "systemctl hibernate")

2. I noticed a strange parameter within the kernel parameters: "acpi_osi=", exactly like this - no value to the right. I searched a bit about it, and found that if I set it to "linux", it enables workarounds to make ACPI work better with Linux. So I set it to "acpi_osi=linux", hoping it might help with avoiding the original problem I raised on this thread.

I'm hoping that these changes fix the issue. I'll come back in a few days, after testing locking+suspend, will let you guys know if it worked.

P.S.: Thanks a lot for the hint on "fwts", that's helping me out indeed :-)

Offline

#14 2019-11-05 05:48:45

cfeedback
Member
From: Portland, OR
Registered: 2019-05-11
Posts: 11

Re: System freezing on suspend

diogobaeder wrote:

which means, it didn't resume from hibernation. I ran this earlier too, and it crashed at the same point ("Requesting Hibernate action" - I ran it earlier because I didn't notice I would need to install "msr" to have more CPU information).

This problem, however, has started to happen a bit recently, I've been running Arch on this computer for a few years by locking+suspending successfully. However, I've always thought that hitting "suspend" while my screen is locked did suspend the computer, so maybe something happened that is switching to hibernation instead ("S4"). Maybe not even in all situations - because sometimes I can get the computer to suspend and then wake it up via my keyboard.

Things are always changing...drivers get added or updated or depreceated, a lot of times one change has a cascade effect. Not that it's the root of the problem, but I don't think you need to lock before suspend most DE's give you that option automatically? re: msr,I suggest as a general rule adding these modules for diagnostic purposes:

/etc/modules-load.d/extramodules.conf
-----
msr
cpuid
eeprom
i2c-dev

The AML kernel errors you listed aren't anything to worry about usually. Some of the other errors are serious though... you can't not have a DSDT (I'm generalising here), for example. It basically runs the show for all your hardware. DId you run FWTS as root? I'd suggest making sure you're running the newest BIOS(UEFI) your vendor or motherboard has. Also you can try adding to your kernel parameters either  acpi_osi='Windows 20009' or acpi_osi='Windows 2012'... there's quite a few different options that could be tried there, but those are the most likely to make a difference.

Could also be hardware related....these type of symptoms could indicate bad RAM or a dying power supply. Might try running memtest86 overnight, you should always in theory have 0 errors over any length of time in a completely stable system.


Design is a funny word. Some people think design means how it looks. But, of course, if you dig deeper, it’s how it really works. You have to grok what it is all about.

― S. Jobs

Offline

#15 2019-11-05 05:54:11

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

Yep, I ran it as root. I hadn't run at first, but on the second run it was as root, which is from where I got the logs I pasted here.

I ended up adding

acpi_osi=Linux

, seems to be the most sensible value I guess.

Thanks again!

Offline

#16 2019-11-05 06:57:15

cfeedback
Member
From: Portland, OR
Registered: 2019-05-11
Posts: 11

Re: System freezing on suspend

diogobaeder wrote:

Yep, I ran it as root. I hadn't run at first, but on the second run it was as root, which is from where I got the logs I pasted here.

I ended up adding

acpi_osi=Linux

, seems to be the most sensible value I guess.

Thanks again!

Glad to help! The kernel specifically answers NO to LInux if asked, because in the past lazy bios writers would use it as a way to disable features they didn't want to test on other platforms... typically you'll see something in the ACPI code along the lines of if "OSI=<insert current Windows version here>" the BIOS will say "Yeah, we support trendy feature: HPET HotPlug ASPM etc etc you name it we got it", and then everyone else gets lumped into some generic Windows XP & friends dunce corner. But some BIOSes do actually work better answering yes to Linux...I've noticed it with Dells at times.

Last edited by cfeedback (2019-11-05 06:57:50)


Design is a funny word. Some people think design means how it looks. But, of course, if you dig deeper, it’s how it really works. You have to grok what it is all about.

― S. Jobs

Offline

#17 2019-11-10 02:16:15

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

Hi guys,

It was all fine this week, the problem seemed to be gone, but it happened again today. These are the last log lines from my previous boot (when the freeze happened):

nov 09 16:49:29 diogobaeder-desktop gnome-shell[2261]: Usage of object.actor is deprecated for ButtonBox
                                                       get@resource:///org/gnome/shell/ui/environment.js:249:29
                                                       destroyTray@/home/diogobaeder/.local/share/gnome-shell/extensions/tray-icons@zhangkaizhao.com/extension.js:160:5
                                                       disable@/home/diogobaeder/.local/share/gnome-shell/extensions/tray-icons@zhangkaizhao.com/extension.js:25:5
                                                       _callExtensionDisable@resource:///org/gnome/shell/ui/extensionSystem.js:78:13
                                                       _disableAllExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:498:17
                                                       _disableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:497:13
                                                       _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:515:13
                                                       _emit@resource:///org/gnome/gjs/modules/signals.js:135:27
                                                       _sync@resource:///org/gnome/shell/ui/sessionMode.js:205:9
                                                       pushMode@resource:///org/gnome/shell/ui/sessionMode.js:167:9
                                                       activate@resource:///org/gnome/shell/ui/screenShield.js:1269:17
                                                       lock@resource:///org/gnome/shell/ui/screenShield.js:1318:9
                                                       LockAsync@resource:///org/gnome/shell/ui/shellDBus.js:360:9
                                                       _handleMethodCall@resource:///org/gnome/gjs/modules/overrides/Gio.js:371:9
                                                       _wrapJSObject/<@resource:///org/gnome/gjs/modules/overrides/Gio.js:404:16
nov 09 16:49:29 diogobaeder-desktop gnome-shell[2261]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed
nov 09 16:49:32 diogobaeder-desktop NetworkManager[686]: <info>  [1573328972.9743] manager: sleep: sleep requested (sleeping: no  enabled: yes)
nov 09 16:49:32 diogobaeder-desktop NetworkManager[686]: <info>  [1573328972.9744] manager: NetworkManager state is now ASLEEP
nov 09 16:49:32 diogobaeder-desktop NetworkManager[686]: <info>  [1573328972.9746] device (enp7s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
nov 09 16:49:32 diogobaeder-desktop gnome-shell[1945]: Screen lock is locked down, not locking
nov 09 16:49:32 diogobaeder-desktop evolution[2610]: Network disconnected.  Forced offline.
nov 09 16:49:32 diogobaeder-desktop evolution[2610]: offline_alert_network_available_cb: assertion 'extension->alert == NULL' failed
nov 09 16:49:32 diogobaeder-desktop dbus-daemon[685]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=686 comm="/usr/bin/NetworkManager --no-daemon ")
nov 09 16:49:32 diogobaeder-desktop systemd[1]: Starting Network Manager Script Dispatcher Service...
nov 09 16:49:33 diogobaeder-desktop dbus-daemon[685]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
nov 09 16:49:33 diogobaeder-desktop systemd[1]: Started Network Manager Script Dispatcher Service.
nov 09 16:49:33 diogobaeder-desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov 09 16:49:33 diogobaeder-desktop NetworkManager[686]: <info>  [1573328973.0023] device (enp7s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
nov 09 16:49:33 diogobaeder-desktop NetworkManager[686]: <info>  [1573328973.0028] dhcp4 (enp7s0): canceled DHCP transaction
nov 09 16:49:33 diogobaeder-desktop avahi-daemon[684]: Withdrawing address record for fe80::8d08:7fa6:6f8:95b0 on enp7s0.
nov 09 16:49:33 diogobaeder-desktop NetworkManager[686]: <info>  [1573328973.0029] dhcp4 (enp7s0): state changed bound -> done
nov 09 16:49:33 diogobaeder-desktop avahi-daemon[684]: Leaving mDNS multicast group on interface enp7s0.IPv6 with address fe80::8d08:7fa6:6f8:95b0.
nov 09 16:49:33 diogobaeder-desktop avahi-daemon[684]: Interface enp7s0.IPv6 no longer relevant for mDNS.
nov 09 16:49:33 diogobaeder-desktop kernel: audit: type=1130 audit(1573328973.000:223): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov 09 16:49:33 diogobaeder-desktop avahi-daemon[684]: Withdrawing address record for 192.168.1.104 on enp7s0.
nov 09 16:49:33 diogobaeder-desktop avahi-daemon[684]: Leaving mDNS multicast group on interface enp7s0.IPv4 with address 192.168.1.104.
nov 09 16:49:33 diogobaeder-desktop avahi-daemon[684]: Interface enp7s0.IPv4 no longer relevant for mDNS.
nov 09 16:49:33 diogobaeder-desktop NetworkManager[686]: <info>  [1573328973.0139] device (enp7s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
nov 09 16:49:33 diogobaeder-desktop kernel: r8169 0000:07:00.0 enp7s0: Link is Down
nov 09 16:49:33 diogobaeder-desktop systemd[1048]: Stopping gnome-user-share WebDAV server...
nov 09 16:49:33 diogobaeder-desktop gsd-sharing[2464]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
nov 09 16:49:33 diogobaeder-desktop systemd[1]: Reached target Sleep.
nov 09 16:49:33 diogobaeder-desktop systemd[1]: Starting Suspend...
nov 09 16:49:33 diogobaeder-desktop systemd-sleep[150204]: Suspending system...
nov 09 16:49:33 diogobaeder-desktop kernel: PM: suspend entry (deep)

Now this coming week I'll try with suspend only, without locking first, and see how my system behaves.

Offline

#18 2019-11-11 05:57:15

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

Hi again guys,

Got an update: I just tried to only suspend (no locking first) my computer and the problem happened. So it's clearly not a problem with the locking of the screen.

Here are the last few lines of my previous boot:

$ journalctl -b-1 | tail -10
nov 11 02:51:20 diogobaeder-desktop avahi-daemon[716]: Leaving mDNS multicast group on interface enp7s0.IPv4 with address 192.168.1.104.
nov 11 02:51:20 diogobaeder-desktop avahi-daemon[716]: Interface enp7s0.IPv4 no longer relevant for mDNS.
nov 11 02:51:20 diogobaeder-desktop NetworkManager[720]: <info>  [1573451480.9167] device (enp7s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
nov 11 02:51:20 diogobaeder-desktop kernel: r8169 0000:07:00.0 enp7s0: Link is Down
nov 11 02:51:20 diogobaeder-desktop systemd[1084]: Stopping gnome-user-share WebDAV server...
nov 11 02:51:20 diogobaeder-desktop gsd-sharing[2486]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
nov 11 02:51:20 diogobaeder-desktop systemd[1]: Reached target Sleep.
nov 11 02:51:20 diogobaeder-desktop systemd[1]: Starting Suspend...
nov 11 02:51:20 diogobaeder-desktop systemd-sleep[87285]: Suspending system...
nov 11 02:51:20 diogobaeder-desktop kernel: PM: suspend entry (deep)

I'll try disabling the remote-desktop and webdav services and see if they have any effect.

Cheers,
Diogo

Offline

#19 2019-11-11 06:10:53

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

I tried again to lock+suspend, and it worked fine; then, I turned off my power suply to forcefully interrupt the kernel so that I could see the last log entries before a successful suspend:

$ journalctl -b-1 | tail -20
nov 11 03:05:00 diogobaeder-desktop systemd[1]: Started Network Manager Script Dispatcher Service.
nov 11 03:05:00 diogobaeder-desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov 11 03:05:00 diogobaeder-desktop NetworkManager[688]: <info>  [1573452300.2160] device (enp7s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
nov 11 03:05:00 diogobaeder-desktop avahi-daemon[685]: Withdrawing address record for fe80::8d08:7fa6:6f8:95b0 on enp7s0.
nov 11 03:05:00 diogobaeder-desktop avahi-daemon[685]: Leaving mDNS multicast group on interface enp7s0.IPv6 with address fe80::8d08:7fa6:6f8:95b0.
nov 11 03:05:00 diogobaeder-desktop kernel: audit: type=1130 audit(1573452300.213:155): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov 11 03:05:00 diogobaeder-desktop avahi-daemon[685]: Interface enp7s0.IPv6 no longer relevant for mDNS.
nov 11 03:05:00 diogobaeder-desktop NetworkManager[688]: <info>  [1573452300.2195] dhcp4 (enp7s0): canceled DHCP transaction
nov 11 03:05:00 diogobaeder-desktop NetworkManager[688]: <info>  [1573452300.2195] dhcp4 (enp7s0): state changed bound -> done
nov 11 03:05:00 diogobaeder-desktop avahi-daemon[685]: Withdrawing address record for 192.168.1.104 on enp7s0.
nov 11 03:05:00 diogobaeder-desktop avahi-daemon[685]: Leaving mDNS multicast group on interface enp7s0.IPv4 with address 192.168.1.104.
nov 11 03:05:00 diogobaeder-desktop avahi-daemon[685]: Interface enp7s0.IPv4 no longer relevant for mDNS.
nov 11 03:05:00 diogobaeder-desktop NetworkManager[688]: <info>  [1573452300.2360] device (enp7s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
nov 11 03:05:00 diogobaeder-desktop kernel: r8169 0000:07:00.0 enp7s0: Link is Down
nov 11 03:05:00 diogobaeder-desktop gsd-sharing[2457]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
nov 11 03:05:00 diogobaeder-desktop systemd[1016]: Stopping gnome-user-share WebDAV server...
nov 11 03:05:00 diogobaeder-desktop systemd[1]: Reached target Sleep.
nov 11 03:05:00 diogobaeder-desktop systemd[1]: Starting Suspend...
nov 11 03:05:00 diogobaeder-desktop systemd-sleep[7309]: Suspending system...
nov 11 03:05:00 diogobaeder-desktop kernel: PM: suspend entry (deep)

I can't find anything relevantly different from a failed session. So I have the impression that there's a chance that my RAM might be corrupted. Therefore I'll leave my computer running memtest tonight, let's see if I can catch something.

Thanks again, and sorry for the flood of replies here, guys.
Diogo

Offline

#20 2019-11-12 19:10:40

diogobaeder
Member
Registered: 2012-01-02
Posts: 24

Re: System freezing on suspend

My RAM is fine. I ran memtest86 overnight, and got no errors.

Offline

Board footer

Powered by FluxBB