From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 27720] New: Hard Hang on suspend - 8600M GS
Date: Sat, 17 Apr 2010 22:53:05 -0700 (PDT) [thread overview]
Message-ID: <bug-27720-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=27720
Summary: Hard Hang on suspend - 8600M GS
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: jimsantelmo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=35138)
--> (https://bugs.freedesktop.org/attachment.cgi?id=35138)
Nouveau dmesg chatter
Hard hang on suspend. X not involved; happens in single-user with nouveau
loaded and providing framebuffer console, suspend done via pm-suspend (also
hangs in X if suspend attempted).
System locked up, no response to alt-sysrq magic keys, full CPU burn (judging
from fan). Nouveau-related dmesg chatter attached; more info on request.
Other than that, driver performs well for ordinary use. Chip runs hotter and
fan-speed stays higher, but visuals are about the same as the proprietary
nvidia driver.
Machine is an Everex laptop, Turion X2 x68-64, nvidia chipset.
--
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-04-18 5:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 5:53 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-27720-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-04-18 5:57 ` [Bug 27720] Hard Hang on suspend - 8600M GS bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-18 8:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-18 16:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-18 16:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-20 3:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-21 2:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-21 3:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18: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-27720-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.