linux-kernel - Re: [PULL] drm-intel-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] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.00.1408171605170.29877@twin.jikos.cz>
Date:	Sun, 17 Aug 2014 16:08:10 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Daniel Vetter <daniel.vetter@...ll.ch>
cc:	Dave Airlie <airlied@...il.com>, intel-gfx@...ts.freedesktop.org,
	dri-devel@...ts.freedesktop.org,
	Jani Nikula <jani.nikula@...ux.intel.com>,
	torvalds@...ux-foundation.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PULL] drm-intel-fixes

On Fri, 8 Aug 2014, Daniel Vetter wrote:

> Big fix is the duct-tape for ring init on g4x platforms, we seem to have
> found the magic again to make those machines as happy as before (not
> perfect though unfortunately, but that was never the case).

I unfortunately don't agree with the last part; there are older kernels 
(such as 3.7) where I have never ever seen this ring initialization 
failure, despite it being excercised very heavily (hundreds of 
suspend/resume cycles on the machine I am debugging this problem on).

As I said in the bugzilla already, the affected machine will be physically 
present in my bag at the Kernel Summit, in case it helps you guys from 
Intel to debug it.

-- 
Jiri Kosina
SUSE Labs

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