stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: Jordan Leppert <jordanleppert@protonmail.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"labre@posteo.de" <labre@posteo.de>,
	"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: Crash on resume after suspend (5.17.5 and 5.15.36)
Date: Wed, 4 May 2022 20:31:25 +0200	[thread overview]
Message-ID: <888dd07b-89b3-6620-820a-74f497ddc223@applied-asynchrony.com> (raw)
In-Reply-To: <0e53891e-418f-ce94-2204-060c35b32a2d@applied-asynchrony.com>

On 2022-05-04 19:50, Holger Hoffstätte wrote:
> On 2022-05-04 17:07, Jordan Leppert wrote:
>> Hi,
>>
>> A changed was added to both version 5.17.5 and 5.15.36 which causes my computer to freeze when resuming after a suspend. This happens every time I suspend and then resume.
>>
>> I've bisected the change to commit: cbe6c3a8f8f4315b96e46e1a1c70393c06d95a4c (net: atlantic: invert deep par in pm functions, preventing null derefs)
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.17.y&id=cbe6c3a8f8f4315b96e46e1a1c70393c06d95a4c
>>
>> My computer details that might be relevant:
>> OS: Arch Linux
>> CPU: AMD 5950X
>> GPU: AMD 6800XT
>>
>> As expected I have an Aquantia ethernet controller listed in lspci:
>>
>> 05:00.0 Ethernet controller: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02)
>>
>> Please let me know if there is any more info I can give that will help.
>>
>> Regards,
>> Jordan
>>
> 
> Just a quick note that I have the same issue (same card model); since recently
> (5.15.36) the hang after resume is 100% reliable. IIRC it used to be hit-and-miss
> before that. I'm currently building .38 with the mentioned commit reverted and
> will report back. Thanks for bringing this up.

With said commit reverted and 5.15.38 I got 1 successful resume and 1 lockup.
Difference is that with the patch reverted, the locked-up system can be pinged
(unlike with the patch applied), though resume still does not finish properly and
now probably runs into the problem that the patch was trying to fix.
Any network services like ssh are still dead though.
This used to work every time, all the time..looks like I'll try removing the
module before suspend.

-h

  reply	other threads:[~2022-05-04 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <refZ3y2HAXztrRkMMmFbBaF7Dz1CctWgjchSdBtcSNlpk-TL0fqLepVVHfw9qXtIQF9uFzBvFdjQiiX9Jv2zW9oaWej952s1IYwu61d1REo=@protonmail.com>
2022-05-04 15:07 ` Crash on resume after suspend (5.17.5 and 5.15.36) Jordan Leppert
2022-05-04 16:38   ` Jordan Leppert
2022-05-04 17:50   ` Holger Hoffstätte
2022-05-04 18:31     ` Holger Hoffstätte [this message]
2022-05-04 19:25   ` Manuel Ullmann
2022-05-04 20:58     ` Holger Hoffstätte
2022-05-04 22:10       ` Manuel Ullmann
     [not found]     ` <vcehgVc5mzweaw_ru0o1up63In2GGa9jtEWuaH8op7p2753Wfr2ezPhxFJdMPFxmpiPmrUB4XnH2nakuhC_BJby3wFa87cbpdLV-lDDb6Ko=@protonmail.com>
2022-05-04 22:21       ` Manuel Ullmann
2022-05-05 10:41         ` Jordan Leppert
2022-05-05  7:43   ` Thorsten Leemhuis

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=888dd07b-89b3-6620-820a-74f497ddc223@applied-asynchrony.com \
    --to=holger@applied-asynchrony.com \
    --cc=davem@davemloft.net \
    --cc=jordanleppert@protonmail.com \
    --cc=labre@posteo.de \
    --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).