From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105051] circular locking,
Date: Mon, 12 Feb 2018 07:00:17 +0000 [thread overview]
Message-ID: <bug-105051-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1525 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105051
Bug ID: 105051
Summary: circular locking,
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/other
Assignee: dri-devel@lists.freedesktop.org
Reporter: bugzilla@colorremedies.com
4.16.0-0.rc0.git9.1.fc28.x86_64 which is "linux-next" git f9f1e414128e
[ 9.523799] switcheroo-cont/889 is trying to acquire lock:
[ 9.523799] (console_lock){+.+.}, at: [<000000002c1cc7fb>]
vga_switchto_stage2+0x93/0x130
[ 9.523806]
but task is already holding lock:
[ 9.523807] (vgasr_mutex){+.+.}, at: [<000000007e504e29>]
vga_switcheroo_debugfs_write+0x6b/0x360
[ 9.523810]
which lock already depends on the new lock.
[ 9.523810]
the existing dependency chain (in reverse order) is:
[ 9.523810]
-> #3 (vgasr_mutex){+.+.}:
[ 9.523812]
-> #2 (&helper->lock){+.+.}:
[ 9.523814]
-> #1 ((fb_notifier_list).rwsem){++++}:
[ 9.523816]
-> #0 (console_lock){+.+.}:
[ 9.523818]
other info that might help us debug this:
[ 9.523818] Chain exists of:
console_lock --> &helper->lock --> vgasr_mutex
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2844 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-02-12 7:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 7:00 bugzilla-daemon [this message]
2018-02-12 7:01 ` [Bug 105051] circular locking, switcheroo-cont/889 is trying to acquire lock vga_switchto_stage2, but vga_switcheroo_debugfs_write already has lock bugzilla-daemon
2018-02-12 7:02 ` bugzilla-daemon
2018-02-12 7:02 ` bugzilla-daemon
2018-02-12 7:03 ` bugzilla-daemon
2018-02-12 7:03 ` bugzilla-daemon
2018-03-10 9:06 ` bugzilla-daemon
2019-10-14 13:20 ` 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-105051-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox