[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37775bf2-d571-434c-8670-827631e2eb12@amd.com>
Date: Tue, 22 Apr 2025 13:58:39 +0530
From: Bharata B Rao <bharata@....com>
To: Balbir Singh <balbirs@...dia.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, luto@...nel.org,
peterz@...radead.org, tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
x86@...nel.org, hpa@...or.com, nikunj@....com, kees@...nel.org,
alexander.deucher@....com
Subject: Re: AMD GPU driver load hitting BUG_ON in sync_global_pgds_l5()
On 22-Apr-25 12:44 PM, Balbir Singh wrote:
> On 4/22/25 16:34, Bharata B Rao wrote:
>
> Could you please confirm if this is a new issue? Sounds like your hitting it on 6.8.12+?
> I've never tested this on a system with 5 levels of page tables, but with 5 levels you get
> 52 bits of VA and you'll need to look at the KASLR logic (max_pfn + padding) to see where
> your ranges are getting assigned.
I haven't been able to test this on latest upstream. Will get back on
this as it can take considerable time to recreate.
Same or similar-look bugs have been discussed earlier too:
https://gitlab.freedesktop.org/drm/amd/-/issues/3244
Disabling 5 level tables seemed to have solved the issue though.
>
> I'd start by dumping the kaslr_regions array.
Sure, Thanks.
Regards,
Bharata.
Powered by blists - more mailing lists