From: Borislav Petkov <bp@alien8.de>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: Re: i915 resume-from-hibernation problems on resume with current Linus' tree
Date: Wed, 5 Mar 2014 18:06:40 +0100 [thread overview]
Message-ID: <20140305170640.GE28317@pd.tnic> (raw)
In-Reply-To: <20140304134509.GA5427@pd.tnic>
On Tue, Mar 04, 2014 at 02:45:09PM +0100, Borislav Petkov wrote:
> On Mon, Mar 03, 2014 at 03:20:11PM +0100, Jiri Kosina wrote:
> > I encountered this again with -rc5.
> >
> > If there is anything I can do to help debug this, please let me know.
>
> I have a similar issue where the screen blanks after the machine idle
> timeout expires (not suspending the box - just leaving it idle) and then
> when I press any button to wake up the screen, it remains off. The box
> is otherwise alive, I can log into it and restart X. Then the screen is
> back on. This started appearing in the -rc3-4 timeframe AFAICT.
>
> My GPU is
>
> 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
> Subsystem: Lenovo Device 21fa
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 42
> Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
> Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
> Region 4: I/O ports at 4000 [size=64]
> Expansion ROM at <unassigned> [disabled]
> Capabilities: <access denied>
> Kernel driver in use: i915
> 00: 86 80 66 01 07 04 90 00 09 00 00 03 00 00 00 00
> 10: 04 00 00 f0 00 00 00 00 0c 00 00 e0 00 00 00 00
> 20: 01 40 00 00 00 00 00 00 00 00 00 00 aa 17 fa 21
> 30: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00
>
> Maybe I should say that I'm booting the box with
>
> [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14.0-rc5+ root=/dev/sdb2 ro root=/dev/sdb2 ignore_loglevel log_buf_len=10M resume=/dev/sdb1 i915.i915_enable_rc6=4 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.powersave=1
>From looking at
http://lkml.kernel.org/r/1394011994-30604-1-git-send-email-daniel.vetter@ffwll.ch
it looks like I should stop using the rc6/fbc settings?
:-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-03-05 17:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 11:04 i915 resume-from-hibernation problems on resume with current Linus' tree Jiri Kosina
2014-02-27 13:12 ` Jiri Kosina
2014-03-03 14:20 ` Jiri Kosina
2014-03-04 13:45 ` Borislav Petkov
2014-03-05 17:06 ` Borislav Petkov [this message]
2014-03-05 17:15 ` Daniel Vetter
2014-03-05 17:22 ` Jiri Kosina
2014-03-10 14:25 ` Jiri Kosina
2014-03-10 14:38 ` Daniel Vetter
2014-03-10 14:41 ` Jiri Kosina
2014-03-21 15:23 ` Jiri Kosina
2014-03-21 15:55 ` Daniel Vetter
2014-03-24 13:39 ` Jiri Kosina
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=20140305170640.GE28317@pd.tnic \
--to=bp@alien8.de \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.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