linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* -next: no resume from suspend
@ 2013-01-14 10:11 Jiri Slaby
  2013-01-14 12:56 ` Rafael J. Wysocki
  0 siblings, 1 reply; 14+ messages in thread
From: Jiri Slaby @ 2013-01-14 10:11 UTC (permalink / raw)
  To: Linux PM mailing list, LKML

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?

It is x86_64, core 2 duo, intel g33 GPU, 6G RAM.

thanks,
-- 
js
suse labs

^ permalink raw reply	[flat|nested] 14+ messages in thread
* Re: -next: no resume from suspend
@ 2013-01-14 12:53 Sedat Dilek
  2013-01-14 13:36 ` Sedat Dilek
  0 siblings, 1 reply; 14+ messages in thread
From: Sedat Dilek @ 2013-01-14 12:53 UTC (permalink / raw)
  To: Jiri Slaby
  Cc: LKML, linux-next, Linux PM List, Linux ACPI, Rafael J. Wysocki,
	Len Brown, Stephen Rothwell, Daniel Vetter

Hi Jiri,

[ QUOTE ]
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?

It is x86_64, core 2 duo, intel g33 GPU, 6G RAM.
[ /QUOTE ]

Before starting any git-bisection I would try drm-intel-nightly GIT branch.
It includes drm-intel-fixes + drm-intel-next + drm-intel-next-queued
and applied here (mostly) cleanly against Linux (upstream) and/or
Linux-Next.

$ cd linux-next/

$ git pull git://people.freedesktop.org/~danvet/drm-intel drm-intel-nightly

I remember I had no problems with i915 with next-20130109 (WED) and
next-20130110 (THU), so I am curious if I will hit the problem as
well.

Kernel-config and some logs (dmesg) or hwinfos (lspci) might be helpful :-).

If this does not help, I would recommend to create diffs between
latest known (-rcX and next-X.good) and (-rcX and next-X.bad) and
compare (i915||acpi||pm) the changes.
But this also means you have to know which of the -next releases was
good and bad.
If you are building Linux-Next daily, this is good.
NOTE: Helpful is in this strategy that your -rcX should be the same
(here: v3.8-rc3).

Hope this helps you (I know bisecting Linux-Next is a bit of a pain).

Regards,
- Sedat -

[1] http://cgit.freedesktop.org/~danvet/drm-intel/log/?h=drm-intel-nightly

^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2013-01-16 23:07 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-14 10:11 -next: no resume from suspend Jiri Slaby
2013-01-14 12:56 ` Rafael J. Wysocki
2013-01-14 12:53   ` Jiri Slaby
2013-01-16  9:20     ` Jani Nikula
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
  -- strict thread matches above, loose matches on Subject: below --
2013-01-14 12:53 Sedat Dilek
2013-01-14 13:36 ` Sedat Dilek
2013-01-14 14:06   ` Sedat Dilek

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).