Created attachment 49239 [details] dmesg file System Environment: -------------------------- Arch: x86_64 Platform: piketon Libdrm: (master)2.4.26-1-g8d055890d90c3d92647e3d8b98d32630ef87c2c8 Mesa: (master)1cf06218e483c1e673e2f19df9116e60478edf30 Xserver: (master)xorg-server-1.10.99.901-106-g82f5521a6d91ebcd2a4400f6c221ad625edc99a1 Xf86_video_intel: (master)2.15.0-203-g212fa9868767637e8f430485eeb522c99e63fd16 Kernel: (drm-intel-next)6e96e7757a0133a9a66fd9b86cd04b5e7b88122a Bug detailed description: ------------------------- With latest drm-intel-next kernel, Call Trace appears when system start up. It only happens on piketon. The last known good commit is a7f08958d7ca69e26ec85fe49c0be3568a565493. The last known bad commit is 6fe5a7e3cac5b60774186a95bbb7555fa604080c. Reproduce steps: ---------------- 1. start system with latest drm-intel-next kernel 2. dmesg
"drm/i915: don't use uninitialized EDID bpc values when picking pipe bpp" on intel-gfx
*** Bug 39466 has been marked as a duplicate of this bug. ***
A patch referencing this bug report has been merged in Linux v3.1-rc1: commit 62ac41a6e443ef26b9de862c6e20c088e2b04dde Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Thu Jul 28 12:55:14 2011 -0700 drm/i915: don't use uninitialized EDID bpc values when picking pipe bpp
Verified with kernel(drm-intel-next) 4e6343898fe7eed6b3c0c3c809347bc88d5b4a1e.
Closing old verified.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.