From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106456] [regression][bisected] Mutex deadlock in nouveau (nv50_display.c)
Date: Wed, 09 May 2018 20:24:29 +0000 [thread overview]
Message-ID: <bug-106456-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1196 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106456
Bug ID: 106456
Summary: [regression][bisected] Mutex deadlock in nouveau
(nv50_display.c)
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/other
Assignee: dri-devel@lists.freedesktop.org
Reporter: john@jlindgren.net
Since linux 4.14, the nouveau driver deadlocks at boot.
Downstream report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763189?comments=all
The culprit is this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=af2405af07d168e2905f2ac9494d3a804a549f0f
In short, drm_fb_helper_add_one_connector() and
drm_fb_helper_remove_one_connector() were incompatibly changed to add locking
of a mutex that previously the caller was expected to lock. The i915 and
radeon drivers were updated to no longer lock the mutex, but nouveau was not
updated.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2709 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 reply other threads:[~2018-05-09 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 20:24 bugzilla-daemon [this message]
2018-05-09 20:26 ` [Bug 106456] [regression][bisected] Mutex deadlock in nouveau (nv50_display.c) bugzilla-daemon
2018-05-09 22:12 ` bugzilla-daemon
2018-05-09 23:05 ` bugzilla-daemon
2018-05-12 13:29 ` 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-106456-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.