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: <CA+icZUWLLs5U0JQs_k-9Bz6rA5-WeKyQKLiZ9-jKuBK7JM8AZA@mail.gmail.com>
Date:	Tue, 13 Aug 2013 22:25:17 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Chris Wilson <chris@...is-wilson.co.uk>,
	Sedat Dilek <sedat.dilek@...il.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Dave Airlie <airlied@...il.com>,
	DRI <dri-devel@...ts.freedesktop.org>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>
Subject: Re: linux-next: Tree for Aug 13 [ screen corruption in graphical mode ]

On Tue, Aug 13, 2013 at 10:20 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
> On Tue, Aug 13, 2013 at 10:16:10PM +0200, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 10:10 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
>> > On Tue, Aug 13, 2013 at 09:05:41PM +0200, Sedat Dilek wrote:
>> >> On Tue, Aug 13, 2013 at 8:53 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
>> >> > On Tue, Aug 13, 2013 at 08:40:37PM +0200, Sedat Dilek wrote:
>> >> >> On Tue, Aug 13, 2013 at 8:01 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
>> >> >> > On Tue, Aug 13, 2013 at 07:53:25PM +0200, Sedat Dilek wrote:
>> >> >> >> Files attached.
>> >> >> >
>> >> >> > Can you also please attach a full dmesg so I can check for anything
>> >> >> > unusual?
>> >> >> >
>> >> >
>> >> > Nothing scarred me on a couple of read throughs.
>> >> >
>> >> > What happens if you try:
>> >> >
>> >> > diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c b/drivers/gpu/drm/i915/i915_gem_stolen.c
>> >> > index 112c5e1..9828d9b 100644
>> >> > --- a/drivers/gpu/drm/i915/i915_gem_stolen.c
>> >> > +++ b/drivers/gpu/drm/i915/i915_gem_stolen.c
>> >> > @@ -284,7 +284,7 @@ i915_gem_object_create_stolen(struct drm_device *dev, u32 size)
>> >> >                 return NULL;
>> >> >
>> >> >         ret = drm_mm_insert_node(&dev_priv->mm.stolen, stolen, size,
>> >> > -                                4096, DRM_MM_SEARCH_DEFAULT);
>> >> > +                                1024*1024, DRM_MM_SEARCH_DEFAULT);
>> >> >         if (ret) {
>> >> >                 kfree(stolen);
>> >> >                 return NULL;
>> >> >
>> >> > --
>> >>
>> >> Now, 2/3 till 3/4 of my LightDM greeter screen is a black bar (seen
>> >> from the top).
>> >> On the bottom I can read "Ubuntu 12.04 LTS" with the known background.
>> >> So-to-say 3/4 "blind".
>> >
>> > That implies that the scanout is always reading from the base of stolen.
>> > Can you grab intel_reg_dumper so that I can check what values the
>> > transcoder is set to?
>> >
>> > At the moment, I am guessing that the display never sees the updated
>> > surface offset and so persists with the value programmed by the BIOS -
>> > which will be 0 and set to the base of stolen memory in the GTT. A
>> > drm.debug=6 dmesg would help here as well.
>> >
>> > If you forced a mode change, I think that too would restore the output.
>>
>> With which kernel? Vanilla next-20130813? With any of your patches?
>
> Any but the working one ;-)

Damn Gmail, they switched again the UI, f***.

This is d-i-n with Revert "drm/i915: Allocate LLC ringbuffers from
stolen" <--- "working one" (no screen corruptions).

- Sedat -

View attachment "dmesg_3.11.0-rc5-2-din-small_drm-debug-6.txt" of type "text/plain" (144985 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ