From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 67878] New: Hardware freeze after resume from suspend
Date: Wed, 07 Aug 2013 21:48:12 +0000 [thread overview]
Message-ID: <bug-67878-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67878
Priority: medium
Bug ID: 67878
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: Hardware freeze after resume from suspend
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: critical
Classification: Unclassified
OS: Linux (All)
Reporter: bgamari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: Driver/nouveau
Product: xorg
Created attachment 83798
--> https://bugs.freedesktop.org/attachment.cgi?id=83798&action=edit
dmesg output from boot to attempted resume
On a Dell Latitude E6400 with nVidia G98M and 3.10 kernel I find that the
machine will reproducibly resume from suspend with a non-responsive X session.
Given attempts I can eventually get to a somewhat functional VT. dmesg output
attached.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2544 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 reply other threads:[~2013-08-07 21:48 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 21:48 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-67878-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-08-07 21:49 ` [Bug 67878] Hardware freeze after resume from suspend bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-07 21:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-07 21:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-07 22:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-09 1:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-09 2:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-09 2:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-09 14:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-09 16:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-09 17:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-09 17:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-09 17:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-09 17:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-09 18:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-10 16:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-10 21:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-10 22:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 7:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 7:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 8:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 8:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 8:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 14:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 15:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 15:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 15:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 15:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 15:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 15:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 15:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 15:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 15:54 ` [Bug 67878] [BISECTED] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-11 23:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-30 23:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-30 23:08 ` [Bug 67878] [NV98] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-08 16:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-08 17:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-08 20:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-19 20:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-30 8:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 6:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 6:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 7:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-27 15:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-27 15:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-27 16:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-27 16:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-27 16:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-27 17:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 17:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 18:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 18:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 18:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 19:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-17 14:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-17 14:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-18 23:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:35 ` 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-67878-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.