Hi all

I've built a few systems recently and although the hardware seems ok (passed 24hr memtest etc), I'm getting corruption on the console.

These are Intel Z77 systems with a Core i7 3770 CPU so using the graphics built into the CPU.

Any ideas what this could be?
Does it look like a hardware issue to you or could it be the driver?

The intel drivers are so common I figure its pretty unlikely but really want to get this fixed.

I'm using kernel 3.4.28

Screenshots: (Taken on KVM, but happens on monitor too)

http://img72.imageshack.us/img72/2223/corruptionr.jpg

http://img515.imageshack.us/img515/6732/corruption2.jpg

Thanks

Are these VMs or real boxes where the corruption shows?

In the interests of speed, some of the that is not changed is optionally not redrawn. This can lead to messing. I would go straight for the video driver - the kernel module, if there is one. I'm taKing it things are feeding up incorrectly - i.e. a blank line is passed up & becomes rubbish.

I would say it is the graphics card or driver. Checks the logs for any messages (/var/log).

This is on the physical machine, VM's are fine

In dmesg we have:

ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88007876b2f8), AE_NOT_FOUND (20120320/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff88007876b2f8), AE_NOT_FOUND (20120320/psparse-536)

Is this graphics related?

Graphics driver is i915.ko, if I blacklist this will it fall back to a generic driver? That would be fine as we dont need X on these systems.

Thanks

Find out what GPU is in the i7 - probably a hd 4000 ivy bridge.
From This_Link it seems like kvm and kvm_intel are the ones you should go after first.

The intel drivers might be common, but support for the newer cards isnt that great. It will be probably when the 3.8 kernel will be mainline...

From the first glance it really seems like a hardware issue, but with the intel linux drivers you never know...

This is not related to this thread, the topic of the link is Virtualbox, not Intel graphics.

@Chris E: If you don't use X just try it with disabling Kernel Mode Setting (KMS) with adding the kernel option nomodeset to the bootloader configuration.