Re: [REGRESSION] Asus X541UAK hangs on suspend and poweroff (v6.1.6 onward)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Thorsten
> why do you pass pci=nomsi
It's a workaround for another issue i've been facing for about 2 or 3
years, since when I first tried out Linux (started with loading Kubuntu
and Mint live images). Without that workaround Kubuntu didn't boot for
me - on kernel 5.8 it only reached the graphic installer part, but hung
after language selection menu, on 5.4 and 5.11 - didn't even reach the
graphic session. With Mint it was more severe - the screen was flooded
with PCIe errors, like so:

	Apr 10 18:47:08 bong last message buffered 3 times
	Apr 10 18:47:08 bong kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask000001/00002000
	Apr 10 18:47:08 bong kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
	Apr 10 18:47:08 bong last message buffered 5 times
	Apr 10 18:47:08 bong kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask000001/00002000
	Apr 10 18:47:08 bong kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
	Apr 10 18:47:08 bong last message buffered 13 times
	Apr 10 18:47:08 bong kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask000001/00002000
	Apr 10 18:47:08 bong kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
	Apr 10 18:47:08 bong last message buffered 5 times
	Apr 10 18:47:08 bong kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask000001/00002000
	Apr 10 18:47:08 bong kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
	Apr 10 18:47:08 bong last message buffered 6 times

`pci=nomsi` saved me also during Debian installation - without it the
live ISO just crashed mid-installation.

But it wasn't a complete cure for Debian- and Ubuntu-based distros, and
they still crashed even with this parameter (I don't know how exactly,
at least they didn't flood with PCIe bus errors).

Since I moved to Manjaro, Void, Arch and now to Gentoo (which bases its
config on the Fedora one), PCIe errors were my only trouble, which was
easily mitigated with `pci=nomsi`. Recently I discovered that without it
one of the kernel modules (irq/124-aerdrv) had high CPU load, so double
useful.

https://forums.linuxmint.com/viewtopic.php?p=2237628
Just googled and there's a guy with a very similar model as me (UVK
instead of UAK) and same issues, but `noaer` and `nomsi` work identically
for me (I found `nomsi` in a different thread).

Since I'm building my own kernel for the last 3 months, I've disabled
the MSI in kernel config - and with that, a big part of IOMMU part as well:
https://git.sr.ht/~acid-bong/kernel/commit/cac5c09dec0bea919ca071a9b738108b0d8a8ee5
but I did it _after_ I first experienced the issue I described in the
thread head, hoping that it'll save me from these hangs as well. It
didn't.

I'm keeping it in the bootloader config for cases when I boot with a
prebuilt Gentoo kernel, and add every time I'm booting with Arch or Void
live USB for rescue purposes. It's not a constant issue tho, happens every
other time.

---
> Bagas
> Have you tried testing latest mainline?
Just built and will boot in a moment. But we'll gotta wait for a couple
of days, since the hanging is unexpected.



[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]
  Powered by Linux