From: Werner Sembach <wse@tuxedocomputers.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: ggo@tuxedocomputers.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Avoid putting some root ports into D3 on some Ryzen chips
Date: Tue, 17 Dec 2024 16:58:39 +0100 [thread overview]
Message-ID: <7a9353d3-b9db-4499-a054-c7050bc7b4d5@tuxedocomputers.com> (raw)
In-Reply-To: <4dac3ff2-e3ab-42c0-b39f-379d5badca42@amd.com>
Am 17.12.24 um 15:11 schrieb Mario Limonciello:
> On 12/17/2024 08:07, Werner Sembach wrote:
>
>>> '''
>>> Platform may hang resuming. Upgrade your firmware or add pcie_port_pm=off
>>> to kernel command line if you have problems
>>> '''
>> Yes, full log attached (kernel 6.13-rc3 one time without sudo one time with
>> sudo)
>
> Yes; I see it in your log.
>
>>> "quirk: disabling D3cold for suspend"
>> On the fixed BIOS I see that line. On the unfixed BIOS it aborts the
>> functions at "if (pm_suspend_target_state == PM_SUSPEND_ON)". Skipping the
>> check on the unfixed BIOS it still hangs on resume.
>>>
>>> I'm /suspecting/ you do see it, but you're having problems with another root
>>> port.
>>>
>>> I mentioned this in my previous iterations of patches that eventually landed
>>> on that quirk, but Windows and Linux handle root ports differently at
>>> suspend time and that could be why it's exposing your BIOS bug.
>>>
>>> If you can please narrow down which root ports actually need the quirk for
>>> your side (feel free to do a similar style to 7d08f21f8c630) I think we
>>> could land on something more narrow and upstreamable.
>>>
>>> At a minimum what you're doing today is covering both Rembrandt and Phoenix
>>> and it should only apply to Phoenix.
>>
>> I also try to find out how many devices where actually shipped with this very
>> first BIOS version.
>
> OK.
Ok found out that the initial bios actually works, then there is one in between
bios where it doesn't and the next one it works again.
So i need to find out if the the in between bios was actually shipped, if not,
this issue is actually void.
next prev parent reply other threads:[~2024-12-17 15:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 19:36 Werner Sembach
2024-12-09 19:45 ` Mario Limonciello
2024-12-10 15:24 ` Werner Sembach
2024-12-10 16:00 ` Mario Limonciello
2024-12-11 12:47 ` Werner Sembach
2024-12-11 21:24 ` Mario Limonciello
2024-12-12 18:47 ` Werner Sembach
2024-12-12 19:01 ` Mario Limonciello
2024-12-13 10:05 ` Richard Hughes
2024-12-16 23:37 ` Werner Sembach
2024-12-17 10:10 ` Richard Hughes
2024-12-17 11:58 ` Werner Sembach
2024-12-17 14:12 ` Mario Limonciello
2024-12-17 14:07 ` Werner Sembach
2024-12-17 14:11 ` Mario Limonciello
2024-12-17 15:58 ` Werner Sembach [this message]
2024-12-17 16:08 ` Werner Sembach
2024-12-17 16:18 ` Mario Limonciello
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=7a9353d3-b9db-4499-a054-c7050bc7b4d5@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=bhelgaas@google.com \
--cc=ggo@tuxedocomputers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
/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
all inboxes | Powered by JetHome®