linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Regression] Bug 216371 - acpi wake up with black screen with msg "amd_gpio AMDI0030:00: failed to get iomux index" #forregzbot
Date: Sun, 18 Sep 2022 18:24:47 +0200	[thread overview]
Message-ID: <b6aeaf85-c88f-c526-30c8-e040b99c66ea@leemhuis.info> (raw)
In-Reply-To: <849a07ba-a53c-3f10-e2ec-25421c1e40ee@leemhuis.info>

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

On 25.08.22 11:42, Thorsten Leemhuis wrote:

> To quote from https://bugzilla.kernel.org/show_bug.cgi?id=216371 :
> 
>>  neoe 2022-08-17 01:50:41 UTC
>>
>> just upgrade from 5.18 to 6.0.0-rc1
>>
>> `acpitool -s` 
>> to set to sleep, it seems a little slow.
>>
>> then wake up, black screen,
>>
>> everything works fine before.
>>
>> AMD 3900X
>>
>> [reply] [−] Comment 1 neoe 2022-08-22 02:39:12 UTC
>>
>> dmesg
>>
>> amd_gpio AMDI0030:00: failed to get iomux index
> See the ticket for details.

#regzbot backburner: likely bad bisect and reporter apparently ignoring
the issue for now

  parent reply	other threads:[~2022-09-18 16:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 10:42 [Regression] Bug 216371 - acpi wake up with black screen with msg "amd_gpio AMDI0030:00: failed to get iomux index" Thorsten Leemhuis
2022-08-25 11:50 ` Natikar, Basavaraj
2022-09-18 16:24 ` Thorsten Leemhuis [this message]
2023-03-15 10:57   ` [Regression] Bug 216371 - acpi wake up with black screen with msg "amd_gpio AMDI0030:00: failed to get iomux index" #forregzbot Linux regression tracking #update (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=b6aeaf85-c88f-c526-30c8-e040b99c66ea@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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).