From: Vasant Hegde <vasant.hegde@amd.com>
To: David Wang <00107082@163.com>,
jsnitsel@redhat.com, joro@8bytes.org,
suravee.suthikulpanit@amd.com
Cc: baolu.lu@linux.intel.com, jroedel@suse.de, kevin.tian@intel.com,
linux-kernel@vger.kernel.org, sivanich@hpe.com
Subject: Re: [Regression] 6.10-rc1: Fail to resurrect from suspend.
Date: Mon, 10 Jun 2024 19:14:02 +0530 [thread overview]
Message-ID: <682dfa6e-7f81-48cf-920e-14d4f2c46fc1@amd.com> (raw)
In-Reply-To: <20240610131550.53651-1-00107082@163.com>
Hi David,
On 6/10/2024 6:45 PM, David Wang wrote:
> Hi,
>
> This still happens with 6.10-rc3...
> I think this is a serious problem for AMD users who used to `suspend`...
I am sorry. Can you tell us which issue youare referring?
Is this `ILLEGAL_DEV_TABLE_ENTRY` (one described in bugzilla [1])? -OR-
the kernel panic in amd_iommu_enable_faulting() path?
If its kernel panic, then patch [2] didn't make it into rc3 fixes.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=218900
[2]
https://lore.kernel.org/linux-iommu/lsahbfrt26ysjzgg6p6ezcrf525b25d7nnuqxgis5k6g3zsnzt@qsmzecwdjnen/T/#t
-Vasant
next prev parent reply other threads:[~2024-06-10 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 12:01 [Regression] 6.10-rc1: Fail to resurrect from suspend David Wang
2024-05-30 12:14 ` Dimitri Sivanich
2024-05-30 14:09 ` David Wang
2024-06-10 13:15 ` David Wang
2024-06-10 13:44 ` Vasant Hegde [this message]
2024-06-10 13:54 ` David Wang
2024-06-10 14:07 ` Vasant Hegde
-- strict thread matches above, loose matches on Subject: below --
2024-05-30 11:49 David Wang
2024-06-13 11:04 ` Pavel Machek
2024-06-13 11:44 ` Linux regression tracking (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=682dfa6e-7f81-48cf-920e-14d4f2c46fc1@amd.com \
--to=vasant.hegde@amd.com \
--cc=00107082@163.com \
--cc=baolu.lu@linux.intel.com \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=jsnitsel@redhat.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sivanich@hpe.com \
--cc=suravee.suthikulpanit@amd.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