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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 12 Jan 2011 14:31:33 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.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, 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.

> Are these both desktop type machines with DVI attached monitors?

DVI on the Core i5, plain analog VGA on the sandybridge one (I can
hear you asking "Why?". Because the silly intel motherboard doesn't
_have_ DVI out, and I didn't have a hdmi cable)

> If it's an FDI or transcoder problem, something like the below may give
> us more info.

See above. It's long-term, it was just the video behavior that made me
originally think it was temporary.

> Can you take a picture of the corruption?

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

                  Linus
--
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/