[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <373a0740.2481.190026d9d87.Coremail.00107082@163.com>
Date: Mon, 10 Jun 2024 21:54:16 +0800 (CST)
From: "David Wang" <00107082@....com>
To: "Vasant Hegde" <vasant.hegde@....com>
Cc: jsnitsel@...hat.com, joro@...tes.org, suravee.suthikulpanit@....com,
baolu.lu@...ux.intel.com, jroedel@...e.de, kevin.tian@...el.com,
linux-kernel@...r.kernel.org, sivanich@....com
Subject: Re: [Regression] 6.10-rc1: Fail to resurrect from suspend.
At 2024-06-10 21:44:02, "Vasant Hegde" <vasant.hegde@....com> wrote:
>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?
Oh, I was mentioning this thread: https://lore.kernel.org/lkml/20240530120110.22141-1-00107082@163.com/
>
>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
Yes, it is the patch[2]; sad to hear it didn't make into rc3.... I have to patch my system manually ever since rc1.....
Thx
David
Powered by blists - more mailing lists