linux-kernel - Re: i915 resume-from-hibernation problems on resume with current Linus' tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140305171558.GM17001@phenom.ffwll.local>
Date:	Wed, 5 Mar 2014 18:15:58 +0100
From:	Daniel Vetter <daniel@...ll.ch>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Daniel Vetter <daniel.vetter@...ll.ch>,
	Jani Nikula <jani.nikula@...ux.intel.com>,
	Jiri Kosina <jkosina@...e.cz>, linux-kernel@...r.kernel.org,
	intel-gfx@...ts.freedesktop.org
Subject: Re: i915 resume-from-hibernation problems on resume with current
 Linus' tree

On Wed, Mar 05, 2014 at 06:06:40PM +0100, Borislav Petkov wrote:
> 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?
> 
> :-)

Indeed. If going back to defaults fixes your issues, then it's not a real
bug. There are reasons the defaults are as-is ...
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/