From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 29583] nouveau freeze Xorg on NV34
Date: Fri, 27 Aug 2010 05:20:00 -0700 (PDT) [thread overview]
Message-ID: <20100827122000.7F18C1302C7@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29583-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=29583
--- Comment #12 from DarkRaven <drdarkraven-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2010-08-27 05:19:59 PDT ---
The all-is-frozen situation described in the comment only appeared once.
During my bisecting,while Xorg is frozen,I'm still able to move mouse and
network is still working.
So according to the definition of 'Hardlockups':
Hardlockups are bugs that cause the CPU to loop in kernel mode
for more than 60 seconds, without letting other interrupts have a
chance to run.
I don't think this is a hardlockup.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-08-27 12:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 13:45 [Bug 29583] New: nouveau freeze Xorg on NV34 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-29583-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-08-15 13:46 ` [Bug 29583] " 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 [this message]
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=20100827122000.7F18C1302C7@annarchy.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.