[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Feb 28 02:01:35 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=104274
Luke McKee <hojuruku at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hojuruku at gmail.com
--- Comment #11 from Luke McKee <hojuruku at 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 at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20180228/91ea5deb/attachment.html>
More information about the dri-devel
mailing list