Bug#689268: linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze

[Javier Cantero]

I can also confirm this bug. My hardware: i5-3570K MoBo: MSI Z77A-G65.

If it helps, I am using now linux-image-3.5-trunk-amd64
(3.5.2-1~experimental.1) kernel with no freezes since the change.

-- 
   Saludos de Javier 




signature.asc
Description: Digital signature

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

[Javier Cantero]

Sorry, I didn't receive the last 2 msgs in my mailbox, (especifically the
questions Ingo asks me). Here the answers:

a) Yes, I am using iceweasel.
b) my phisical RAM is 8 GB

The related kernel info is below, first kernel 3.5 related and then
standard wheezy 3.2 kernel related. Note that with kernel 3.5 I don't
have the "MTRR allocation failed" error.

My integrated graphics BIOS configuration:

Virtu Technology   [Disabled]
Integrated Graphics Share Memory   [64MB]
DVMT Memory   [256MB]
IGD Multimonitor   [Disabled]


--
  Kernel 3.5
--

$ dmesg | grep mtrr
$

$ dmesg | grep drm
[3.749099] [drm] Initialized drm 1.1.0 20060810
[3.947156] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[3.947156] [drm] Driver supports precise vblank timestamp query.
[4.004585] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[4.373533] fbcon: inteldrmfb (fb0) is primary device
[4.554815] fb0: inteldrmfb frame buffer device
[4.554817] drm: registered panic notifier
[4.555909] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0

$ dmesg | grep i915
[3.690617] i915 :00:02.0: setting latency timer to 64
[3.707470] i915 :00:02.0: irq 43 for MSI/MSI-X
[4.328751] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0

$ dmesg | grep agp
[0.459118] Linux agpgart interface v0.103
[0.459169] agpgart-intel :00:00.0: Intel Ivybridge Chipset
[0.459210] agpgart-intel :00:00.0: detected gtt size: 2097152K total, 
262144K mappable
[0.459842] agpgart-intel :00:00.0: detected 65536K stolen memory
[0.459931] agpgart-intel :00:00.0: AGP aperture is 256M @ 0xe000


The memory info:

$ cat /proc/mtrr
reg00: base=0x0 (0MB), size= 8192MB, count=1: write-back
reg01: base=0x2 ( 8192MB), size=  512MB, count=1: write-back
reg02: base=0x0e000 ( 3584MB), size=  512MB, count=1: uncachable
reg03: base=0x0dc00 ( 3520MB), size=   64MB, count=1: uncachable
reg04: base=0x0db80 ( 3512MB), size=8MB, count=1: uncachable
reg05: base=0x21f80 ( 8696MB), size=8MB, count=1: uncachable
reg06: base=0x21f60 ( 8694MB), size=2MB, count=1: uncachable

$ cat /proc/meminfo
MemTotal:8081148 kB
MemFree: 7392304 kB
Buffers:   14852 kB
Cached:   280924 kB
SwapCached:0 kB
Active:   395024 kB
Inactive: 214096 kB
Active(anon): 313884 kB
Inactive(anon):42596 kB
Active(file):  81140 kB
Inactive(file):   171500 kB
Unevictable:   0 kB
Mlocked:   0 kB
SwapTotal:   7811068 kB
SwapFree:7811068 kB
Dirty:12 kB
Writeback: 0 kB
AnonPages:313372 kB
Mapped:64608 kB
Shmem: 43120 kB
Slab:  26992 kB
SReclaimable:  11196 kB
SUnreclaim:15796 kB
KernelStack:1808 kB
PageTables:10844 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit:11851640 kB
Committed_AS:1004672 kB
VmallocTotal:   34359738367 kB
VmallocUsed:  366716 kB
VmallocChunk:   34359355879 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
HugePages_Total:   0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
DirectMap4k:   55296 kB
DirectMap2M: 7192576 kB


--
  Kernel 3.2
--

$ dmesg | grep mtrr
[5.001176] mtrr: type mismatch for e000,1000 old: write-back new: 
write-combining

$ cat /proc/mtrr
reg00: base=0x0 (0MB), size= 8192MB, count=1: write-back
reg01: base=0x2 ( 8192MB), size=  512MB, count=1: write-back
reg02: base=0x0e000 ( 3584MB), size=  512MB, count=1: uncachable
reg03: base=0x0dc00 ( 3520MB), size=   64MB, count=1: uncachable
reg04: base=0x0db80 ( 3512MB), size=8MB, count=1: uncachable
reg05: base=0x21f80 ( 8696MB), size=8MB, count=1: uncachable
reg06: base=0x21f60 ( 8694MB), size=2MB, count=1: uncachable

$ dmesg | grep drm
[4.960827] [drm] Initialized drm 1.1.0 20060810
[5.001178] [drm] MTRR allocation failed.  Graphics performance may suffer.
[5.001350] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[5.001351] [drm] Driver supports precise vblank timestamp query.
[5.344345] fbcon: inteldrmfb (fb0) is primary device
[5.523815] fb0: inteldrmfb frame buffer device
[5.523816] drm: registered panic notifier
[5.585070] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0

$ dmesg | grep i915
[4.973200] i915 :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[4.973202] i915 :00:02.0: setting latency timer to 64
[5.001347] i915 :00:02.0: irq 43 for MSI/MSI-X
[5.585070] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0

$ dmesg | grep agp
[0.977765] Linux agpg

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

[Javier Cantero]

Just a little bit of info I found reading the last changes to the
X intel driver:

"Release 2.20.9 (2012-09-29)
===
And so it came to pass that a critical bug was uncovered in UXA. The
kernel does not like to pageflip when the pipe is off, yet due to the
delayed nature of a pageflip and the relaxed checking performed by UXA,
we could request a pageflip after turning off the display (DPMS). The
kernel rejected that pageflip and the error handling path failed to
restore sanity, and when the screen came back it was stuck on the image
seen before it went to sleep. (Note that there are also some related
kernel bugs, but this update should prevent the most conspicious of the
freezes.) Many thanks to Timo Aaltonen for his efforts in tracking down
the issue.
[...]"

This is not the kernel bug, but the graphics bug. However, maybe is not
a bad idea to upgrade the X driver and see what happen with 3.2.x.

-- 
   Saludos de Javier 




signature.asc
Description: Digital signature