From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93199] IGT: Couldn't map MMIO region
Date: Fri, 31 Aug 2018 07:02:11 +0000 [thread overview]
Message-ID: <bug-93199-502-ICX4Kolxmi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93199-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1016 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93199
Jani Nikula <jani.nikula@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTOURBUG
Status|NEEDINFO |RESOLVED
--- Comment #27 from Jani Nikula <jani.nikula@intel.com> ---
Based on an IRC chat with Joonas and Dave, looks like this is indeed kernel
lockdown on UEFI secure boot doing its magic. The kernel lockdown patches
haven't been merged upstream, so you should not be able to reproduce this on
kernel.org upstream kernels. Please file your bugs against your distro if this
remains an issue for you.
See e.g. https://mjg59.dreamwidth.org/50577.html for background.
Sorry it took us so long to get this; we're obviously not running non-upstream
kernels with lockdown enabled.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2526 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-08-31 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93199-502@http.bugs.freedesktop.org/>
2017-03-29 12:39 ` [Bug 93199] IGT: Couldn't map MMIO region bugzilla-daemon
2017-10-02 21:34 ` bugzilla-daemon
2017-10-02 21:35 ` bugzilla-daemon
2018-05-09 21:07 ` bugzilla-daemon
2018-08-31 7:02 ` bugzilla-daemon [this message]
2018-08-31 7:02 ` bugzilla-daemon
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=bug-93199-502-ICX4Kolxmi@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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