From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 26796] New: Circular locking dependency error on NV43
Date: Sun, 28 Feb 2010 01:07:03 -0800 (PST) [thread overview]
Message-ID: <bug-26796-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26796
Summary: Circular locking dependency error on NV43
Product: xorg
Version: 7.5
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: TomasMiljenovic-Ah+7SPImtolBDgjK7y7TUQ@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=33635)
--> (http://bugs.freedesktop.org/attachment.cgi?id=33635)
dmesg output
While
- starting or running an X session
- using DirectFB to e.g. play movies in vlc or mplayer from a console login
circular locking dependency warnings appear in dmesg.
Afterwards, X can hang or crash outright but at other times does not appear
affected. Video output in framebuffer is always highly corrupted (not sure if
this is a separate bug).
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-02-28 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 9:07 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-26796-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-02-28 9:57 ` [Bug 26796] Circular locking dependency error on NV43 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-28 9:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-24 11:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-26796-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.