From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 29583] New: nouveau freeze Xorg on NV34
Date: Sun, 15 Aug 2010 06:45:45 -0700 (PDT) [thread overview]
Message-ID: <bug-29583-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29583
Summary: nouveau freeze Xorg on NV34
Product: xorg
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: drdarkraven-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
The bug was first sighted when resize a 'fake transparent' rxvt window.
This action freeze Xorg.
And with some further investigation, I discovered that the bug is reproducible
by running:
x11perf -compwinwin500
(And it's fine when running x11perf -putimage500)
And not only Xorg is frozen,it seems the whole system is frozen,too.
The cursor can't be moved,and ssh connection is lost.
I'm using a snapshot kernel,the bug appeared after I updated my kernel tree at
Aug 7.
And there is no such bug in nouveau kernel tree.
Here is my kernel log output.
--
Configure bugmail: https://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-08-15 13:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 13:45 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-29583-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-08-15 13:46 ` [Bug 29583] nouveau freeze Xorg on NV34 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15 13:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15 13:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15 15:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15 15:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-17 8:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-17 8:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-17 8:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-17 8:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-18 0:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-24 6:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-25 22:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 5:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 9:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 10:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-26 10:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 12:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 12:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 12:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 13:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 13:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 13:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 13:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 15:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 15:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-27 15:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-28 11:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-28 12:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-28 14:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-28 15:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-28 23:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-28 23:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-29 1:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-29 17:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-30 18:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-30 18:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-01 2:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-01 12:05 ` 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-29583-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.