From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 40572] [nvac] Nouveau drm causes failure to resume from suspend with any kernel newer than 2.6.36
Date: Sat, 3 Sep 2011 03:25:33 -0700 (PDT) [thread overview]
Message-ID: <20110903102533.161F91301B1@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-40572-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=40572
--- Comment #6 from Daniel Lindgren <dali.spam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2011-09-03 03:25:33 PDT ---
(In reply to comment #5)
> Ok. So this commit is unlikely to be the culprit.
> 2 another ideas:
> - does suspend/resume works at all without nouveau?
> - can netconsole catch anything after failed resume?
Blacklisted nouveau with 3.0.4, the screen is still black after resume but the
machine is alive and I can ssh into it. No reboot.
Netconsole didn't produce anything after resume. Verified that it worked by
inserting a USB stick before resume, but nothing logged after. No ping
responses either, the network's probably gone.
Starting netconsole however changed the behaviour a bit, the machine reboots a
little faster, about 20 seconds after I hit the power button to resume. Without
netconsole it takes 40 seconds until it reboots.
--
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:[~2011-09-03 10:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 7:03 [Bug 40572] New: Nouveau drm causes failure to resume from suspend with any kernel newer than 2.6.36 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-40572-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-09-02 7:04 ` [Bug 40572] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-02 16:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-03 7:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-03 7:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-03 8:53 ` [Bug 40572] [nvac] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-03 10:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2011-09-03 10:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-03 10:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-03 14:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-03 16:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` 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=20110903102533.161F91301B1@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.