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]
Date:	Thu, 24 Apr 2014 06:50:23 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Pavel Machek <pavel@....cz>
Cc:	Daniel Vetter <daniel.vetter@...ll.ch>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	kernel list <linux-kernel@...r.kernel.org>,
	Jiri Kosina <jikos@...os.cz>
Subject: Re: 3.15-rc2: i915 regression: only top 20% of screen works in X

On Thu, Apr 24, 2014 at 12:09:52AM +0200, Pavel Machek wrote:
> Hi!
> 
> > > After update to 3.15-rc2, only top 20% of screen works on X.
> > >
> > > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > > Integrated Graphics Controller (rev 03)
> > >
> > > 00:02.1 Display controller: Intel Corporation 4 Series Chipset
> > > Integrated Graphics Controller (rev 03)
> > >            Subsystem: Intel Corporation Device d614
> > >            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
> > >            Region 0: Memory at d0400000 (64-bit, non-prefetchable)
> > >            [size=1M]
> > >            Capabilities: <access denied>
> > >
> > > This worked before. I believe it worked in 3.14. It definitely works
> > > in 3.11-rc2.
> > 
> > Screenshot or more detailed description of what "only top 20% of
> > screen works in X" means?
> > Anything in dmesg?
> 
> Actually yes, dmesg suggests it is quite
> sick. drivers/gpu/drm/drm_mm.c:767 warning triggered
> repeatedly. Also.. initial framebuffer does not work ; I don't seem to
> see anything before X start up. (This is Debian 6.0.9)

That says that i915.ko failed to initialise the GPU (or rather the GPU
wasn't responding) and bailed during module load. The key line here is

[drm:init_ring_common] *ERROR* render ring initialization failed ctl
0001f001 head 00002034 tail 00000000 start 0012f000

Jiri has been seeing a similar issue creep in during resume, but it is
not reliable enough to bisect. Is your boot failure reliable enough to
bisect? Also drm-intel-nightly should mitigate this failure and allow
i915.ko to continue to load and run X, which would be worth testing to
make sure that works as intended.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
--
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/

Powered by blists - more mailing lists