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: Mon, 29 Jan 2018 16:16:52 +0000 [thread overview]
Message-ID: <bug-104274-502-dRM7kF9YWF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104274-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 398 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104274
--- Comment #5 from Harry Wentland <harry.wentland@amd.com> ---
Can you try with the latest amd-staging-drm-next from
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
We just fixed a bunch of driver unload issues. It should be fixed now.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1424 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-01-29 16:16 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 [this message]
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
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-dRM7kF9YWF@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