RE: [Regression] Bug 216371 - acpi wake up with black screen with msg "amd_gpio AMDI0030:00: failed to get iomux index"

["Natikar, Basavaraj" <Basavaraj.Natikar@amd.com>]

[AMD Official Use Only - General]

Yes this error message is additional message that it supports gpio not an iomux. Not releated to any functionality changes.
I will change error message to info like  "IOMUX not supported".
Which is unrelated to acpi wake up with black screen issue.

Thanks,
Basavaraj



-----Original Message-----
From: Thorsten Leemhuis <regressions@leemhuis.info>
Sent: Thursday, August 25, 2022 4:13 PM
To: Natikar, Basavaraj <Basavaraj.Natikar@amd.com>; Limonciello, Mario <Mario.Limonciello@amd.com>
Cc: hi2@n101n.xyz; open list:GPIO SUBSYSTEM <linux-gpio@vger.kernel.org>; LKML <linux-kernel@vger.kernel.org>; regressions@lists.linux.dev
Subject: [Regression] Bug 216371 - acpi wake up with black screen with msg "amd_gpio AMDI0030:00: failed to get iomux index"

Hi, this is your Linux kernel regression tracker.

I noticed a regression report in bugzilla.kernel.org that afaics nobody acted upon since it was reported. That's why I decided to forward it by mail to those that afaics should handle this.

To quote from https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.kernel.org%2Fshow_bug.cgi%3Fid%3D216371&amp;data=05%7C01%7CBasavaraj.Natikar%40amd.com%7C66809b990a564200874c08da86869038%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637970209757244824%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=pEO9Lc0qwP5LHhohuFHAg9oawn3TWs%2BM9enXl9e%2Ba%2BE%3D&amp;reserved=0 :

>  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.

Please look into the issue if you're among the main recipients of this mail (and not just CCed). I hope I picked the right people to sent this to, if not, just let everyone know (and apologies!). Basavaraj, unless my quick analysis of the situation went haywire it seems that you recently added code with the error message noticed by the reporter.

Anyway, to ensure this is not forgotten lets get this tracked by the the Linux kernel regression tracking bot:

#regzbot introduced: v5.19..v6.0-rc2
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.kernel.org%2Fshow_bug.cgi%3Fid%3D216371&amp;data=05%7C01%7CBasavaraj.Natikar%40amd.com%7C66809b990a564200874c08da86869038%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637970209757244824%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=pEO9Lc0qwP5LHhohuFHAg9oawn3TWs%2BM9enXl9e%2Ba%2BE%3D&amp;reserved=0
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already discussed somewhere else? It was fixed already? You want to clarify when the regression started to happen? Or point out I got the title or something else totally wrong? Then just reply -- ideally with also telling regzbot about it, as explained here:
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinux-regtracking.leemhuis.info%2Ftracked-regression%2F&amp;data=05%7C01%7CBasavaraj.Natikar%40amd.com%7C66809b990a564200874c08da86869038%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637970209757244824%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=XL%2BSaOlHIX23MQYzV5ZjefUdBAHiA%2FNEz9frARy9pss%3D&amp;reserved=0

Reminder for developers: When fixing the issue, add 'Link:' tags pointing to the report in bugzilla, as the kernel's documentation calls for; above page explains why this is important for tracked regressions.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.