archive mirror
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <>
To: Xi Ruoyao <>
Cc: Kees Cook <>,
	Jani Nikula <>,
	David Airlie <>, Jessica Yu <>,,,,,
Subject: Re: kernel oops loading i915 after "x86/asm: Pin sensitive CR4 bits" (873d50d58)
Date: Wed, 10 Jul 2019 11:46:56 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


On Wed, Jul 10, 2019 at 01:44:17PM +0800, Xi Ruoyao wrote:
> Hello,
> When I try to build and run the latest mainline kernel, it Oops loading i915
> module:
> BUG: unable to handle page fault for address: ffffffff9edc1598
> #PF: supervisor write access in kernel mode
> #PF: error_code(0x0003) - permissions violation
> PGD 1a20c067 P4D 1a20c067 PUD 1a20d063 PMD 8000000019e000e1 
> Oops: 0003 [#1] SMP PTI
> The complete log is attached.
> Bisection tells "x86/asm: Pin sensitive CR4 bits" (873d50d58) is the first "bad"
> commit.  I can revert it and also "x86/asm: Pin sensitive CR0 bits" (8dbec27a2)
> to make the kernel "seems to" work.
> I'm not a kernel expert so I can't tell if there is a bug in Kees' patch, or his
> patch exploits a bug in i915 or module loader.

This seems to be a kernel bug introduced after v5.2, see


      reply	other threads:[~2019-07-10  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10  5:44 kernel oops loading i915 after "x86/asm: Pin sensitive CR4 bits" (873d50d58) Xi Ruoyao
2019-07-10  8:46 ` Dmitry V. Levin [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).