public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@amd.com>
To: Balbir Singh <balbirs@nvidia.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	luto@kernel.org, peterz@infradead.org, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com,
	nikunj@amd.com, kees@kernel.org, alexander.deucher@amd.com
Subject: Re: AMD GPU driver load hitting BUG_ON in sync_global_pgds_l5()
Date: Wed, 23 Apr 2025 12:10:32 +0530	[thread overview]
Message-ID: <35f08d6c-cc90-43fd-a24a-195b5d0e6d32@amd.com> (raw)
In-Reply-To: <ad725f4b-6e45-42e4-ba6d-919534bc99a4@nvidia.com>

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'd start by dumping the kaslr_regions array.

Here is how the ranges look like for the upstream kernel for two boots:

Iteration 1:
kaslr_region: base[0] ff4552df80000000 size_tb 1000
kaslr_region: end[0] fffffffffffff
kaslr_region: base[1] ff69c69640000000 size_tb 3200
kaslr_region: base[2] ffd3140680000000 size_tb 40

Iteration 2:
kaslr_region: base[0] ff3a9c84c0000000 size_tb 1000
kaslr_region: end[0] fffffffffffff
kaslr_region: base[1] ff73d27480000000 size_tb 3200
kaslr_region: base[2] fff01edb40000000 size_tb 40

Regards,
Bharata.

  parent reply	other threads:[~2025-04-23  6:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  6:34 AMD GPU driver load hitting BUG_ON in sync_global_pgds_l5() Bharata B Rao
2025-04-22  7:14 ` Balbir Singh
2025-04-22  8:28   ` Bharata B Rao
2025-04-23  6:40   ` Bharata B Rao [this message]
2025-04-22 15:13 ` Dave Hansen
2025-04-23  9:30   ` Bharata B Rao
2025-04-23 16:01     ` Dave Hansen
2025-04-24 12:54       ` Bharata B Rao

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=35f08d6c-cc90-43fd-a24a-195b5d0e6d32@amd.com \
    --to=bharata@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=balbirs@nvidia.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nikunj@amd.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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