From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jiri Slaby <jslaby@suse.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: daniel.vetter@ffwll.ch, LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
Linux PM mailing list <linux-pm@vger.kernel.org>
Subject: Re: -next: no resume from suspend
Date: Wed, 16 Jan 2013 11:20:43 +0200 [thread overview]
Message-ID: <87fw21wkk4.fsf@intel.com> (raw)
In-Reply-To: <50F3FFE6.4090108@suse.cz>
On Mon, 14 Jan 2013, Jiri Slaby <jslaby@suse.cz> wrote:
> On 01/14/2013 01:56 PM, Rafael J. Wysocki wrote:
>> On Monday, January 14, 2013 11:11:52 AM Jiri Slaby wrote:
>>> Hi,
>>>
>>> since friday's -next (the last known to be working is the last monday's)
>>> I cannot resume from suspend. The last thing I see with
>>> no_console_suspend is:
>>> i915: No ACPI video bus found
>>>
>>> But I used to see the message always, so this is no difference. Any idea
>>> before I start bisecting?
>>
>> Well, what's the next message you normally see with no_console_suspend?
>
> [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
>
> Adding DRM and intel guys.
Hi Jiri, the dmesgs for both cases with drm.debug=0xe module param might
give us some clues.
Does it work without no_console_suspend?
BR,
Jani.
next prev parent reply other threads:[~2013-01-16 9:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 10:11 Jiri Slaby
2013-01-14 12:56 ` Rafael J. Wysocki
2013-01-14 12:53 ` Jiri Slaby
2013-01-16 9:20 ` Jani Nikula [this message]
2013-01-16 10:36 ` Jiri Slaby
2013-01-16 10:43 ` Jiri Slaby
2013-01-16 11:02 ` Jiri Slaby
2013-01-16 14:00 ` Rafael J. Wysocki
2013-01-16 22:48 ` Jiri Slaby
2013-01-16 23:01 ` Bjorn Helgaas
2013-01-16 23:13 ` Rafael J. Wysocki
2013-01-14 12:53 Sedat Dilek
2013-01-14 13:36 ` Sedat Dilek
2013-01-14 14:06 ` Sedat Dilek
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=87fw21wkk4.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®