Random hang on suspend

andreasathome · 2023-08-06 14:14:52

Sometimes when I try to suspend, the system doesn't fully suspend (fans don't stop, power light is still on). Only a hard reset helps (as far as I know). Unfortunately, I didn't find anything obvious in the journal.

The last output of such a hang event generated by

journalctl -b -1

can be found here:

https://0x0.st/H_8n.txt

Therefore I have two questions:
1. Did I miss something in the journal?
2. Are there any other log files that can be used to find the reason for that error?

Kind regards

Andreas

V1del · 2023-08-06 14:50:54

Blacklist nouveau/install the proprietary driver according to instructions in: https://wiki.archlinux.org/title/NVIDIA#Installation

andreasathome · 2023-08-06 16:55:10

Thanks, @V1del.

I installed nvidia-lts and rebooted. Until now, everything seems to be fine. Nevertheless, I don't understand the meaning of https://wiki.archlinux.org/title/NVIDIA#Custom_kernel. Can I skip this section?

Kind regards

Andreas

andreasathome · 2023-08-08 15:55:32

After more than a day without any (visible) problems there was a similar hang (fans still running, power light on) while trying to shutdown

The result of

journalctl -b -1

can be found here:
https://0x0.st/H_1r.txt

is that still related to NVIDIA or is there another problem?

Kind regards

Andreas

Last edited by andreasathome (2023-08-08 15:56:23)

andreasathome · 2023-08-16 12:39:16

System still not stable...

Log-Files of the most recent hangs occurred:

12.08.23
13.08.23
16.08.23

Please, share your ideas...

Kind regards

Andreas

seth · 2023-08-16 13:59:40

Aug 16 09:49:37 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[1723]: ACPI action undefined: ACPI0003:00
Aug 16 09:49:37 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[1749]: ACPI action undefined: PNP0C0A:00
Aug 16 09:49:37 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[1751]: ACPI action undefined: PNP0C0A:00
Aug 16 09:49:53 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[1834]: ACPI action undefined: ACPI0003:00
Aug 16 09:49:54 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[1860]: ACPI action undefined: PNP0C0A:00
Aug 16 09:49:54 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[1862]: ACPI action undefined: PNP0C0A:00
Aug 16 11:02:57 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[4261]: ACPI action undefined: PNP0C0A:00
Aug 16 11:02:57 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[4271]: ACPI action undefined: ACPI0003:00
Aug 16 11:02:58 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[4314]: ACPI action undefined: PNP0C0A:00
Aug 16 11:02:59 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[4328]: ACPI action undefined: ACPI0003:00
Aug 16 11:03:00 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[4354]: ACPI action undefined: PNP0C0A:00
Aug 16 11:03:00 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[4388]: ACPI action undefined: PNP0C0A:00
Aug 16 11:17:05 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[6347]: ACPI action undefined: PNP0C0A:00
Aug 16 11:41:23 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[9889]: ACPI action undefined: PNP0C0A:00
Aug 16 11:46:22 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[10539]: ACPI action undefined: ACPI0003:00
Aug 16 11:46:23 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[10565]: ACPI action undefined: PNP0C0A:00
Aug 16 11:46:23 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[10567]: ACPI action undefined: PNP0C0A:00
Aug 16 11:46:29 AlphaInfinity-N85-N87-HJ-HJ1-HK1 root[10587]: ACPI action undefined: PNP0C0A:00

That's not https://archlinux.org/packages/extra/x86_64/root/ is it?

Aug 16 09:46:01 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: starting up with netlink and the input layer
Aug 16 09:46:01 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: 2 rules loaded
Aug 16 09:46:01 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: waiting for events: event logging is off
Aug 16 09:46:01 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: client connected from 627[0:0]
Aug 16 09:46:01 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: 1 client rule loaded
Aug 16 09:46:01 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: client 627[0:0] has disconnected
Aug 16 09:46:07 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: client connected from 698[0:0]
Aug 16 09:46:07 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: 1 client rule loaded
Aug 16 09:46:08 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: client connected from 698[0:0]
Aug 16 09:46:08 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: 1 client rule loaded
Aug 16 11:02:57 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: client 698[0:0] has disconnected
Aug 16 11:02:57 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: client 698[0:0] has disconnected
Aug 16 11:02:57 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: client connected from 698[0:0]
Aug 16 11:02:57 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: 1 client rule loaded
Aug 16 11:02:58 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: client connected from 698[0:0]
Aug 16 11:02:58 AlphaInfinity-N85-N87-HJ-HJ1-HK1 acpid[493]: 1 client rule loaded

Do you use acpid to trigger the suspend (eg. via the lid)?

Aug 05 17:31:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: DMI: XMG N85_N87,HJ,HJ1,HK1/N85_N87,HJ,HJ1,HK1, BIOS 1.05.10 03/23/2017

Rather old BIOS

1. see whether there's a more recent BIOS/Firmware available for your system
2. try to suspend w/o acpid and whatever that "root" process is (ever) running.

andreasathome · 2023-08-17 09:12:11

Thanks, @seth,

seth wrote:

That's not https://archlinux.org/packages/extra/x86_64/root/ is it?

Uh... I don't have any idea where this "root" process come from. Is it possible that it means the root user? There should be no packages "root" installed:

pacman -Qqe > pkglist.txt

and

LC_ALL=C pacman -Qi | awk '/^Name/{name=$3} /^Installed Size/{print $4$5, name}' | sort -h > all_packages.txt

give pkglist.txt and all_packages.txt respectively. Digging in some really old Log-Files I saved some days after fresh install I found that this "root" process was already active. I extracted all kinds of messages it produced (it flooded the journal with them):

root[...] ACPI group/action undefined: thermal_zone / LNXTHERM:00
root[...] ACPI group/action undefined: button/up / UP
root[...] ACPI group/action undefined: button/down / DOWN
root[...] ACPI group/action undefined: button/kpenter / KPENTER
root[...] ACPI group/action undefined: button/right / RIGHT
root[...] ACPI group/action undefined: button/left / LEFT
root[...] ACPI group/action undefined: processor / LNXCPU:00
root[...] ACPI group/action undefined: processor / LNXCPU:01
root[...] ACPI group/action undefined: processor / LNXCPU:02
root[...] ACPI group/action undefined: processor / LNXCPU:03
root[...] ACPI group/action undefined: processor / LNXCPU:04
root[...] ACPI group/action undefined: processor / LNXCPU:05
root[...] ACPI group/action undefined: processor / LNXCPU:06
root[...] ACPI group/action undefined: processor / LNXCPU:07
root[...] ACPI action undefined: ACPI0003:00
root[...] ACPI action undefined: PNP0C0A:00

Following the wiki (https://wiki.archlinux.org/title/acpid# … key_events) I already dropped the events for the buttons.
How can I find out what this "root" process actually is? Is it possible to disable (or blacklist ...) it?

seth wrote:

Do you use acpid to trigger the suspend (eg. via the lid)?

I trigger the suspend always via lxde-logout (lxsession-logout) via the graphical interface. Do these executables involve acpid?

seth wrote:

Rather old BIOS

Unfortunately I didn't found any more recent BIOS on the manufacturer website.

What might be the next step?

acpi=off

as kernel parameter?

Kind regards

Andreas

V1del · 2023-08-17 11:24:01

Those "root" messages are from a change in the default scripts for acpid: https://bbs.archlinux.org/viewtopic.php?id=280638

What are you using acpid for? And if you don't know, try disabling/stopping it.

seth · 2023-08-17 13:12:44

What might be the next step? acpi=off as kernel parameter?

Rather not.

I trigger the suspend always via lxde-logout (lxsession-logout) via the graphical interface. Do these executables involve acpid?

Unlikely, but try to use "sudo systemctl suspend" to trigger the problem nevertheless.

Oh, and just to be sure: no parallel windows installation, is there?

andreasathome · 2023-09-12 15:05:51

First of all, sorry for the long silence, unfortunately, I was quite busy the last weeks...
I try to remember what I have done during the installation of my Arch Linux. Obviously I followed the german wiki at some points, there was the section
https://wiki.archlinux.de/title/Anleitu … he_Dienste
where some services were defined "useful"... acpid was among that group of services...

So, I don't know if I really need ACPI. Nevertheless, I tested

# systemctl suspend

and it does not necessarily result in a hang (it worked 5 times in 2023_08_22_Sucessful_ACPI_Suspend_tested.log but failed in 2023_08_21_Failed_Suspend.log)

There is no parallel windows installation (the build-in SSD don't even know about this 'virus' because I purchased a laptop without any pre-installed OS).

On the other hand... how do we find out, if an update randomly fix the problem - i.e. if the problem does not occur for a longer period of time, how do we find out if it is "just luck" or if it is solved?

Kind regards

Andreas

V1del · 2023-09-12 16:41:49

acpid is a specific piece of software reacting to ACPI events, there are many others. It isn't a strict requirement to handle ACPI events from the system which are useful and are not something you want to disable globally. However acpid also will not really do much other than spam your logs if you don't actively configure it for something so it's unlikely to be related but in order to rule it out I suggest you stop/disable acpid (the software daemon, not the kernel subsystem).

andreasathome · 2023-10-03 09:04:48

Everything went fine the last weeks, as an example log without acpid (and without errors) see:
2023_09_23-25_Without_Errors.log

Nevertheless, yesterday I had a strange "early wake event". See the log file, it is at Okt 02 23:34:31:
2023_10_02_Early_Wake.log

Are the freezes when I tried to suspend in the past in fact failed "early wake events"? How to avoid them? I noticed that

xhci_hcd

reported some errors:

Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: xhci_hcd 0000:00:14.0: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: xhci_hcd 0000:00:14.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend async: error -16

Fortunately, the system survived this time so the error is logged. All old logs with freeze events ended with

kernel: PM: suspend entry (deep)

Kind regards

Andreas

seth · 2023-10-03 12:53:51

Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: xhci_hcd 0000:00:14.0: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: xhci_hcd 0000:00:14.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend async: error -16
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: sd 0:0:0:0: [sda] Stopping disk
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: PM: Some devices failed to suspend, or early wake event detected

It indeed seems to be very much some usb device.

Okt 02 09:17:49 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-2: Manufacturer: SunplusIT Inc
Okt 02 09:17:49 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-7: Manufacturer: EgisTec
Okt 02 10:18:18 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 2-4: Manufacturer: JetFlash
Okt 02 11:57:48 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 4-1: Manufacturer: Western Digital
Okt 02 13:12:05 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 2-4: Manufacturer: JetFlash
Okt 02 13:45:06 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-7: Manufacturer: EgisTec
Okt 02 15:35:51 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-7: Manufacturer: EgisTec
Okt 02 19:35:35 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-7: Manufacturer: EgisTec
Okt 02 21:48:03 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 4-1: Manufacturer: Western Digital
Okt 02 22:03:11 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-4: Manufacturer: JetFlash
Okt 02 22:11:20 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-4: Manufacturer: JetFlash
Okt 03 09:44:14 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-7: Manufacturer: EgisTec

lspci -tvnn
lsusb -tv

And it seems to be very much the JetFlash device that afaict only was present during the failed suspend?

andreasathome · 2023-10-03 19:03:01

Thanks, @seth,

lspci -tvnn

returns

-[0000:00]-+-00.0  Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910]
           +-01.0-[01]--+-00.0  NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d]
           |            \-00.1  NVIDIA Corporation GP107GL High Definition Audio Controller [10de:0fb9]
           +-02.0  Intel Corporation HD Graphics 630 [8086:591b]
           +-14.0  Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f]
           +-14.2  Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131]
           +-16.0  Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a]
           +-17.0  Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] [8086:a103]
           +-1c.0-[02]----00.0  ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
           +-1c.4-[03]--+-00.0  Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287]
           |            \-00.1  Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168]
           +-1c.6-[04]----00.0  Intel Corporation Wireless 8265 / 8275 [8086:24fd]
           +-1f.0  Intel Corporation HM175 Chipset LPC/eSPI Controller [8086:a152]
           +-1f.2  Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121]
           +-1f.3  Intel Corporation CM238 HD Audio Controller [8086:a171]
           \-1f.4  Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123]

and

lsusb -tv

returns

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 4: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
        ID 8564:1000 Transcend Information, Inc. JetFlash
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 2: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
        ID 04f2:b5a7 Chicony Electronics Co., Ltd 
    |__ Port 2: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
        ID 04f2:b5a7 Chicony Electronics Co., Ltd 
    |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=, 12M
        ID 8087:0a2b Intel Corp. Bluetooth wireless interface
    |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=, 12M
        ID 8087:0a2b Intel Corp. Bluetooth wireless interface
    |__ Port 7: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
        ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe Fingerprint Sensor

Indeed, I use JetFlash quite often: I use it to save temporary/unfinished stuff. On the other hand there are some bootable linux-images saved on it (I created them using multisystem on ubuntu) the storage can be used for boths, data and booting a live system. Does that cause problems?

Kind regards

Andreas

seth · 2023-10-03 19:10:28

I don't think the content of the drive matters at all, but it seems to inhibit the suspend or maybe just waking the system immediately by responding to it.

Have you ever caused this while it was present?
And can you force the failure by eg. using it directly before the suspend?

Also

cat /proc/acpi/wakeup

andreasathome · 2023-10-04 15:45:55

The last hang-event was yesterday (JetFlash pluged in, I am not sure, if it was mounted at that time), see logfile here:
2023-10-03_hang-event.log

Unfortunately, I was not able to reproduce the error, see log file:
2023-10-03_reproduce_trials.log

cat /proc/acpi/wakeup

returns:
wakeup.log

and there is another suspicious thing: JetFlash often "wants" an fsck and often the message is

fsck von util-linux 2.39.2
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
[123?q]?

It is always

65:01/00

Is that relevant for the problem?

Kind regards

Andreas

seth · 2023-10-04 16:27:39

XHC	  S3	*enabled   pci:0000:00:14.0

Since the trigger seems always on that bus (it's one of your USB hubs) you could simply try to disable it as mitigation

echo XHC | sudo tee /proc/acpi/wakeup
grep XHC /proc/acpi/wakeup

It is always

Did you ever "fix" that by selecting one of the boot sectors?
The cause is an unsynced retract, ie. you didn't unmount the device before unplugging it - or it was mounted when the suspend failed and you resorted to some hard reboot?

Okt 02 22:11:20 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-4: new high-speed USB device number 9 using xhci_hcd
Okt 02 22:11:20 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-4: New USB device found, idVendor=8564, idProduct=1000, bcdDevice=10.75
Okt 02 22:11:20 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Okt 02 22:11:20 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-4: Product: Mass Storage Device
Okt 02 22:11:20 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-4: Manufacturer: JetFlash
Okt 02 22:11:20 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 1-4: SerialNumber: 2139443889
Okt 02 22:11:20 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb-storage 1-4:1.0: USB Mass Storage device detected
Okt 02 22:11:20 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: scsi host3: usb-storage 1-4:1.0
Okt 02 22:11:21 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: scsi 3:0:0:0: Direct-Access     JetFlash Transcend 32GB   1.00 PQ: 0 ANSI: 6
Okt 02 22:11:21 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: sd 3:0:0:0: [sdb] 61734912 512-byte logical blocks: (31.6 GB/29.4 GiB)
Okt 02 22:11:21 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: sd 3:0:0:0: [sdb] Write Protect is off
Okt 02 22:11:21 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00
Okt 02 22:11:21 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: sd 3:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
Okt 02 22:11:21 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel:  sdb: sdb1
Okt 02 22:11:21 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: sd 3:0:0:0: [sdb] Attached SCSI removable disk
Okt 02 22:11:26 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Okt 02 23:34:30 AlphaInfinity-N85-N87-HJ-HJ1-HK1 systemd-logind[498]: The system will suspend now!
Okt 02 23:34:30 AlphaInfinity-N85-N87-HJ-HJ1-HK1 systemd[1]: Reached target Sleep.
Okt 02 23:34:30 AlphaInfinity-N85-N87-HJ-HJ1-HK1 systemd[1]: Starting System Suspend...
Okt 02 23:34:30 AlphaInfinity-N85-N87-HJ-HJ1-HK1 systemd-sleep[39356]: Entering sleep state 'suspend'...
Okt 02 23:34:30 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: PM: suspend entry (deep)
Okt 02 23:34:30 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: Filesystems sync: 0.005 seconds
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: Freezing user space processes
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: OOM killer disabled.
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: Freezing remaining freezable tasks
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: wlan0: deauthenticating from e0:28:6d:c3:0f:67 by local choice (Reason: 3=DEAUTH_LEAVING)
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: xhci_hcd 0000:00:14.0: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: xhci_hcd 0000:00:14.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend async: error -16
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: sd 0:0:0:0: [sda] Stopping disk
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: PM: Some devices failed to suspend, or early wake event detected
Okt 02 23:34:31 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: sd 0:0:0:0: [sda] Starting disk

But the plot on that little fella thickens…

andreasathome · 2023-10-04 19:21:57

Just to be sure that I understand it:

echo XHC | sudo tee /proc/acpi/wakeup

disables the wakeup-trigger XHC (pci:0000:00:14.0) and

grep XHC /proc/acpi/wakeup

confirms that wakeup caused by XHC is now disabled, right?

seth wrote:

Did you ever "fix" that by selecting one of the boot sectors?

Yes. I choosed option 2) the last few fsck-runs as far as I remember. Re-running fsck confirms that there are no errors left.

seth wrote:

The cause is an unsynced retract, ie. you didn't unmount the device before unplugging it - or it was mounted when the suspend failed and you resorted to some hard reboot?

Hard reboots (with JetFlash being mounted) definitely happened but I never unplug my USB devices without unmounting. I even power it off (via gnome-disks) after unmounting. I guess that it also want to be fsck'ed after I used it as a live medium - maybe I should check that.

Kind regards

Andreas

seth · 2023-10-04 19:32:12

Just to be sure that I understand it

Right. Writing the 3/4 letter code into acpi/wakeup toggles the state for the device.

From the lsusb output in #14, the JetFlash is (was at the time) the only USB device on that bus.

andreasathome · 2023-10-05 15:41:12

That is strange... I not requested an unmount but JetFlash suddenly was unmounted... after that, an fsck gave the well known

65:01/00

difference in the boot sector... why did it unmount? Maybe an hardware issue?

Log-File: sudden_JetFlash_unmount.log

seth · 2023-10-05 18:50:19

Okt 05 14:38:14 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 2-4: new SuperSpeed USB device number 2 using xhci_hcd
Okt 05 14:38:14 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 2-4: New USB device found, idVendor=8564, idProduct=1000, bcdDevice=10.75
Okt 05 14:38:14 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Okt 05 14:38:14 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 2-4: Product: Mass Storage Device
Okt 05 14:38:14 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 2-4: Manufacturer: JetFlash
Okt 05 14:38:14 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 2-4: SerialNumber: 2139443889
Okt 05 17:03:50 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: usb 2-4: USB disconnect, device number 2
Okt 05 17:03:50 AlphaInfinity-N85-N87-HJ-HJ1-HK1 systemd[1]: Unmounting /media/JetFlash_32GB...
Okt 05 17:03:50 AlphaInfinity-N85-N87-HJ-HJ1-HK1 kernel: FAT-fs (sdb1): unable to read boot sector to mark fs as dirty
Okt 05 17:03:50 AlphaInfinity-N85-N87-HJ-HJ1-HK1 systemd[1]: media-JetFlash_32GB.mount: Deactivated successfully.
Okt 05 17:03:50 AlphaInfinity-N85-N87-HJ-HJ1-HK1 systemd[1]: Unmounted /media/JetFlash_32GB.

It disconnects and then "unmouted", from the symptoms I'd say the connection is loose and the device "drops out" of the slot?

Arch Linux

#1 2023-08-06 14:14:52

Random hang on suspend

#2 2023-08-06 14:50:54

Re: Random hang on suspend

#3 2023-08-06 16:55:10

Re: Random hang on suspend

#4 2023-08-08 15:55:32

Re: Random hang on suspend

#5 2023-08-16 12:39:16

Re: Random hang on suspend

#6 2023-08-16 13:59:40

Re: Random hang on suspend

#7 2023-08-17 09:12:11

Re: Random hang on suspend

#8 2023-08-17 11:24:01

Re: Random hang on suspend

#9 2023-08-17 13:12:44

Re: Random hang on suspend

#10 2023-09-12 15:05:51

Re: Random hang on suspend

#11 2023-09-12 16:41:49

Re: Random hang on suspend

#12 2023-10-03 09:04:48

Re: Random hang on suspend

#13 2023-10-03 12:53:51

Re: Random hang on suspend

#14 2023-10-03 19:03:01

Re: Random hang on suspend

#15 2023-10-03 19:10:28

Re: Random hang on suspend

#16 2023-10-04 15:45:55

Re: Random hang on suspend

#17 2023-10-04 16:27:39

Re: Random hang on suspend

#18 2023-10-04 19:21:57

Re: Random hang on suspend

#19 2023-10-04 19:32:12

Re: Random hang on suspend

#20 2023-10-05 15:41:12

Re: Random hang on suspend

#21 2023-10-05 18:50:19

Re: Random hang on suspend

Board footer