linux-kernel - Re: [git pull] drm intel only fixes

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: <20110112150640.2a41602c@jbarnes-desktop>
Date:	Wed, 12 Jan 2011 15:06:40 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Dave Airlie <airlied@...ux.ie>,
	Chris Wilson <chris@...is-wilson.co.uk>,
	linux-kernel@...r.kernel.org,
	DRI mailing list <dri-devel@...ts.freedesktop.org>
Subject: Re: [git pull] drm intel only fixes

On Wed, 12 Jan 2011 14:31:33 -0800
Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Wed, Jan 12, 2011 at 2:22 PM, Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
> >
> > Ah, ok.  So it could be our internal FDI link is underrunning; it goes
> > between the CPU and PCH and carries display bits.
> 
> I'm not sure it's an underrun or anything like that: the corruption is
> long-term in the non-video case. So I take back the "looks like memory
> bandwidth problems", because it really looks more like a corrupted
> blit operation there.

Ah ok if it's long running then yeah it's more likely to be a rendering
issue.  It could also be the FDI link getting its timings messed up
though, and consistently delivering the wrong bits; that could show up
in the same place on the screen each time, or it might move in a
pattern across the screen (usually from top to bottom).

> Will do. I'll have to reboot to the broken kernel (my bisection ended
> in a non-broken case)

Great, thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/