From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)
Date: Wed, 28 Feb 2018 02:01:35 +0000 [thread overview]
Message-ID: <bug-104274-502-WyyPUtEoj8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104274-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1809 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104274
Luke McKee <hojuruku@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hojuruku@gmail.com
--- Comment #11 from Luke McKee <hojuruku@gmail.com> ---
I fixed this. I was going to open another ticket.
Just mentioned it before.
Still dc=1 isn't yet usable due to this:
https://bugs.freedesktop.org/show_bug.cgi?id=103953#c7
I found out that the breakage was occurring due to kernel configuration
options. I can provide a working and broken kconfig, but my money is on it
wanting the amd iommu gart support even though the hardware isn't installed.
This is loaded on demand by the amdgpu module. Disabling agpart didn't do much
harm though. Would that affect performance if intel_iommu is enabled?
Feb 28 08:08:35 hojuruku kernel: AMD IOMMUv2 driver by Joerg Roedel
<jroedel@suse.de>
Feb 28 08:08:35 hojuruku kernel: AMD IOMMUv2 functionality not available on
this system
Feb 28 08:08:35 hojuruku kernel: CRAT table not found
Feb 28 08:08:35 hojuruku kernel: Virtual CRAT table created for CPU
Feb 28 08:08:35 hojuruku kernel: Parsing CRAT table with 1 nodes
If users sensibly choose what hardware they have installed to reduce compile
times, or build monolithic kernels they are going to run into trouble here.
Ask me for the .config's for the kernel if you need them to replicate the
defect if you need them. That's what triggered the error in my last comment I
think though in that kernel I had ORC off and no symbols.
You might want to review / tweak your Kconfig depends clauses.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3571 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-02-28 2:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 3:01 [Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock) bugzilla-daemon
2017-12-15 4:27 ` bugzilla-daemon
2017-12-15 9:17 ` bugzilla-daemon
2017-12-15 15:59 ` bugzilla-daemon
2017-12-21 19:41 ` bugzilla-daemon
2018-01-29 16:16 ` bugzilla-daemon
2018-02-22 19:28 ` bugzilla-daemon
2018-02-22 20:50 ` bugzilla-daemon
2018-02-25 5:44 ` bugzilla-daemon
2018-02-26 8:09 ` bugzilla-daemon
2018-02-26 21:46 ` bugzilla-daemon
2018-02-28 2:01 ` bugzilla-daemon [this message]
2018-02-28 17:26 ` bugzilla-daemon
2018-04-05 13:12 ` bugzilla-daemon
2018-04-05 13:16 ` bugzilla-daemon
2018-06-05 3:39 ` bugzilla-daemon
2018-06-17 6:17 ` bugzilla-daemon
2019-11-19 8:27 ` 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-104274-502-WyyPUtEoj8@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