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: Tue, 16 May 2023 14:32:45 -0500 [thread overview]
Message-ID: <ZGPaXfV6+RUb6fXs@bhelgaas> (raw)
In-Reply-To: <A5B9D233-A082-4C60-9DCB-2B0A2081C089@tilde.cafe>
On Tue, May 16, 2023 at 01:26:23PM +0300, Acid Bong wrote:
> >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)?
> `lspci -vvnn` output is linked in the head of the thread. Append .txt to make it readable in the browser (I only understood it after the upload).
>
> >Ideally the dmesg would be from the most recent kernel you have.
>
> Speaking of that, a couple of questions:
>
> 1) Should I post them with or without pci=nomsi/noaer? The problem
> with disabling it is that it floods the logs so fast, that they
> reach 700M in 5-7 minutes, and, when rotation is enabled (my
> parameters are default, up to 10 copies 10M each), all pre-flood
> data is lost instantly.
You're seeing AER logging, and that's what I'm interested in, so if
you could do one quick boot *without* "pci=nomsi" and "pci=noaer",
that would be great. Then turn it off again so you don't drown in
logs.
The snippet from [1] shows a few messages related to 00:1c.5, and it
would be useful to know if there are errors related to other devices
as well.
Something like "head -c500K /var/log/dmesg > file" should be plenty.
> Also I'm currently bisecting the kernel with MSI disabled in the
> config. But I'm keeping the parameter in the bootloader for cases
> when I'm using Gentoo's prebuilt kernel.
>
> 2) Can I delete messages by ufw? They contain MACs of my router,
> laptop and cellphone and I don't really wanna share them
Sure, delete those.
> 3) I'm not savvy in logs, how exactly should I share dmesg? `dmesg >
> file`? /var/log/syslog? I already know kern.log doesn't contain
> logind and some other messages that are present in dmesg
>
> 4) Should we continue in this thread or rather start a new one?
Good point, a new thread would probably be better.
Bjorn
[1] https://lore.kernel.org/all/CRWCUOAB4JKZ.3EKQN1TFFMVQL@bong/
next prev parent reply other threads:[~2023-05-16 19:32 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
2023-05-16 10:26 ` Acid Bong
2023-05-16 19:32 ` Bjorn Helgaas [this message]
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=ZGPaXfV6+RUb6fXs@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;
as well as URLs for NNTP newsgroup(s).