From: "Ortwin Glück" <odi-L693kI9kcNY@public.gmane.org>
To: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: "nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [BUG] nouveau regression: ext monitor dead after resume
Date: Fri, 19 Sep 2014 20:43:36 +0200 [thread overview]
Message-ID: <541C7958.7050603@odi.ch> (raw)
In-Reply-To: <CAKb7Uvi_BN5WZPUA55Ma_2i5nQceryrnjJW54tCXU1hm0KVC4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 09/19/2014 07:01 PM, Ilia Mirkin wrote:
> Thanks! Hopefully you still have those kernels handy, as your logs got
> cut off.
Yeah, I noticed and hoped it wouldn't matter as it is mostly the boot log that's
been cut off until syslog came up (it's from /var/log/messages). So
suspend/resume cycle should be complete. But I can give it another try on Monday
when I'm back in the office.
Ortwin
next prev parent reply other threads:[~2014-09-19 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 14:07 [BUG] nouveau regression: ext monitor dead after resume Ortwin Glück
2014-09-18 14:54 ` Ortwin Glück
[not found] ` <541AE737.8070009-L693kI9kcNY@public.gmane.org>
2014-09-18 14:58 ` Ilia Mirkin
[not found] ` <CAKb7UvjcYsFm7TWzKXdWHVDVRDO1rFtcCTZoChYssDKqLMDGWw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-19 14:41 ` Ortwin Glück
[not found] ` <541C40AA.4060206-L693kI9kcNY@public.gmane.org>
2014-09-19 15:58 ` Ilia Mirkin
[not found] ` <CAKb7Uvjm7vFxd-aTtuh4=XE-4JONRJgAt8n93vDHZnARsg+yiw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-19 16:52 ` Ortwin Glück
2014-09-19 17:01 ` Ilia Mirkin
[not found] ` <CAKb7Uvi_BN5WZPUA55Ma_2i5nQceryrnjJW54tCXU1hm0KVC4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-19 18:43 ` Ortwin Glück [this message]
2014-09-22 9:21 ` Ortwin Glück
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=541C7958.7050603@odi.ch \
--to=odi-l693ki9kcny@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).