From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 67315] System lockup with X consuming all CPU
Date: Fri, 26 Jul 2013 18:30:10 +0000 [thread overview]
Message-ID: <bug-67315-8800-dbRu7RGoBO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67315-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1135 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67315
--- Comment #4 from Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to comment #3)
>
> There is no xorg.conf file. This is a fresh, virgin install of Fedora
> 19, then updated.
>
AFAICS I've asked you to try using an xorg.conf, rather than "Are you using one
how?" :P
>
> I stated that it appears to occur when the screen saver starts and I did
> include the dmesg data that started to spew out when the problem occurs.
> That being said, I will restart everything and disable the screen saver
> completely.
>
You mentioned "possibly when the screen saver kicks in", which indicates a wild
guess :P With that confirmed which screen saver you're talking about -
bubble3d, etc.
There is a reason I've requested dmesg output, the one you attached is at
rather unknown point with absolutely no information as to how nouveau handles
your card :\. That's why I've mentioned a _complete_ dmesg. If you feel there
is something confidential inside if clearly strip it out
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2006 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2013-07-26 18:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 17:59 [Bug 67315] New: System lockup with X consuming all CPU bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-67315-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-07-25 18:01 ` [Bug 67315] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-26 0:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-26 18:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-26 18:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-07-26 18:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-26 20:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-26 21:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-29 16:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-29 16:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-29 17:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-29 20:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-29 20:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-29 21:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 0:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 0:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 0:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 18:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 20:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 20:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-31 15:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-31 16:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-30 21:06 ` [Bug 67315] [NVAA] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-25 12:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-18 20:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-19 12:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-19 13:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-20 11:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:34 ` 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-67315-8800-dbRu7RGoBO@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.