Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
> Am 10.01.2013 09:39, schrieb Riku Voipio:
>
> > getting hangs on anything other than the Debian 3.2.32-1 has
> > been challenging. If if's just timing based, I might just have
> > been lucky during my bisects.
>
> Here vanilla 3.4.24 from kernel.org runs absolutely stable since a few
> weeks. But me came up another idea:
>
> 'modinfo i916' list an option which appears to be a watchdog function:
>
> "parm: enable_hangcheck:Periodically check GPU activity for
> detecting hangs. WARNING: Disabling this can cause system wide hangs.
> (default: true) (bool)"
>
> which actually describes the symptoms. Could it be that in the
> Debian-kernel either the hangs are not detected securely, or that it
> just fails to reset the module?
>
> /Ingo
Hi guys,
Well I have the same issue on my Ivybridge system:
$ lspci -nnv | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
$ cat /var/log/Xorg.0.log | grep "Graphics Chipset"
[…]
[ 8.388] (II) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2)
On my system I observed this behavior:
Debian 3.2.35-2: random hangs (at least one per day)
Upstream 3.2.37: random hangs (at least one per day)
Upstream 3.3-rc1+: no hangs (tested for 2 weeks)
So that seems to be close to Riku's experience.
Anyway what strikes me a bell is the last Ingo's comment about 'enable_hangcheck' module parameter
which was introduced in v3.1-rc1:
$ git tag --contains 6e96e7757a01
v3.1-rc1
[…]
v3.8-rc4
So I peeked about what kind of "hangcheck" changes could have been introduced in v3.3-rc1
and I found an interesting patch:
commit e6bfaf854272ec4641a9ef7b1cb1ca963031ba95
drm/i915: don't bail out of intel_wait_ring_buffer too early
The commit message is particularly interesting!
I'll give it a try but if someone could beat me to it that would be cool (ULV CPU here).
Cheers,
Vincent
PS: Also, could you give a try to Julien Cristau's kernel images with DRM/KMS subsystem backported from 3.4
which might hit Wheezy?
http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.35-3~jcristau.1_amd64.deb
sha1sum f6711fe6d0d924aab82ec82fe1a86102a69a8c32
(There are i686 and i486 flavours if you want)
Reply to: