From: Bjorn Helgaas <helgaas@kernel.org>
To: Acid Bong <acidbong@tilde.cafe>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Bagas Sanjaya <bagasdotme@gmail.com>,
stable@vger.kernel.org, linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: [REGRESSION] Asus X541UAK hangs on suspend and poweroff (v6.1.6 onward)
Date: Mon, 15 May 2023 15:51:18 -0500 [thread overview]
Message-ID: <ZGKbRo9shUcR0myC@bhelgaas> (raw)
In-Reply-To: <CRWCUOAB4JKZ.3EKQN1TFFMVQL@bong>
[+cc linux-pci; thread at
https://lore.kernel.org/r/CRVU11I7JJWF.367PSO4YAQQEI@bong]
On Fri, Apr 14, 2023 at 12:07:42PM +0300, Acid Bong wrote:
> > 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/mask
> 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/mask
> 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/mask
> 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/mask
> 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.
Likely "pci=nomsi" or "pci=noaer" are not related to the
suspend/poweroff issue, but I'd really like to fix the AER problem
anyway.
Can you collect the complete dmesg log and output of "sudo lspci -vv"
and post them somewhere (https://bugzilla.kernel.org is a good place)?
Ideally the dmesg would be from the most recent kernel you have.
Bjorn
next prev parent reply other threads:[~2023-05-15 20:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 19:35 [REGRESSION] Asus X541UAK hangs on suspend and poweroff (v6.1.6 onward) Acid Bong
2023-04-14 7:51 ` Bagas Sanjaya
2023-04-14 8:15 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-14 9:07 ` Acid Bong
2023-04-14 18:51 ` Acid Bong
2023-04-15 7:37 ` Bagas Sanjaya
2023-04-15 8:06 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-15 20:51 ` Bjorn Helgaas [this message]
2023-05-16 10:26 ` Acid Bong
2023-05-16 19:32 ` Bjorn Helgaas
2023-04-17 7:37 ` Acid Bong
2023-04-17 10:56 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-01 12:50 ` Bagas Sanjaya
2023-05-01 21:02 ` Acid Bong
2023-05-03 4:31 ` Bagas Sanjaya
2023-06-09 11:09 ` Acid Bong
2023-06-09 16:55 ` Bjorn Helgaas
2023-06-14 8:53 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-05-13 10:50 ` Acid Bong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZGKbRo9shUcR0myC@bhelgaas \
--to=helgaas@kernel.org \
--cc=acidbong@tilde.cafe \
--cc=bagasdotme@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox