[Bug 64764] New: 845G: crtc active state doesn't match with hw state

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=64764

          Priority: medium
            Bug ID: 64764
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: 845G: crtc active state doesn't match with hw state
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: minor
    Classification: Unclassified
                OS: Linux (All)
          Reporter: mlsemon35 at gmail.com
          Hardware: x86 (IA32)
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Hi!  For a while, I've been battling a problem that I call "xfstests + DRM +
console blanking = bad results that show when lock debugging is turned on in
the kernel."  This applies strongly to the i845g framebuffer and somewhat to
the old i810 framebuffer as well.  However, everybody's been hard at work
fixing bugs for the past 6-8 months, and helpful tty fixes have been rolling
into stable kernels since 3.8.8.  What's left on i845g are two closely related
"soft" oopses when the PC is left alone in console mode for long periods of
time.  At this point, it happens reliably on an idle system.

If I knew how to keep the i915 DRM framebuffer setup from using power
management on the monitor, I wouldn't bother filing a bug report.  This could
go into the category of "informative message, don't even worry about this
ancient hardware."

The kernel here is a recent kernel git with an XFS git merged in--advertised as
"3.10.0-rc1+"--plus a few file system patches.  The installed graphics packages
in this slackware-current (not updated this week) are these:

libdrm-2.4.42-i486-1
intel-gpu-tools-1.3-i486-1
xf86-video-intel-2.21.6-i486-2
mesa-9.1.1-i486-1

For the next week, a kernel bisect would be a bad idea that would wreak havoc
here.  However, I could be convinced to pull in some DRM git code, if it would
help and still be within the range of a novice git user.

Anyway, a push in the right direction would be appreciated.  Thanks!

Michael

[Note: The PC was rebooted between the first oops and the second oops.]

------------[ cut here ]------------
WARNING: at drivers/gpu/drm/i915/intel_display.c:7942
intel_modeset_check_state+0x512/0x714()
crtc active state doesn't match with hw state (expected 0, found 1)
CPU: 0 PID: 16362 Comm: kworker/0:0 Not tainted 3.10.0-rc1+ #11
Hardware name: Dell Computer Corporation Dimension 2350/07W080, BIOS A01
12/17/2002
Workqueue: events console_callback
 e0e61b90 e0e61b90 e0e61b58 c14cb944 e0e61b80 c1025bd1 c163e148 e0e61bac
 00001f06 c130e9b8 c130e9b8 ef414000 eed70654 ef53a000 e0e61b98 c1025c38
 00000009 e0e61b90 c163e148 e0e61bac e0e61da8 c130e9b8 c163d05c 00001f06
Call Trace:
 [<c14cb944>] dump_stack+0x16/0x18
 [<c1025bd1>] warn_slowpath_common+0x54/0x6b
 [<c130e9b8>] ? intel_modeset_check_state+0x512/0x714
 [<c130e9b8>] ? intel_modeset_check_state+0x512/0x714
 [<c1025c38>] warn_slowpath_fmt+0x2e/0x30
 [<c130e9b8>] intel_modeset_check_state+0x512/0x714
 [<c1311f70>] intel_crt_dpms+0x63/0x87
 [<c12cc905>] drm_fb_helper_dpms.isra.9+0xcc/0x114
 [<c10401a1>] ? __blocking_notifier_call_chain+0x42/0x56
 [<c12cd740>] drm_fb_helper_blank+0x58/0x5f
 [<c1265eb5>] fb_blank+0x45/0x8b
 [<c126faf9>] fbcon_blank+0x21d/0x2be
 [<c10438ef>] ? sched_clock_local.constprop.3+0x39/0x131
 [<c10446e2>] ? update_curr.constprop.48+0x55/0x95
 [<c1044906>] ? dequeue_task_fair+0xbd/0xc5
 [<c1041f35>] ? dequeue_task+0x39/0x40
 [<c14ce8bc>] ? __schedule+0x192/0x3e7
 [<c12b79bd>] do_blank_screen+0x112/0x21d
 [<c12b7fc9>] console_callback+0x5a/0x145
 [<c1037483>] process_one_work+0xd7/0x305
 [<c10366c0>] ? destroy_worker+0x5c/0x88
 [<c10370be>] ? manage_workers.isra.33+0x18a/0x219
 [<c103779b>] worker_thread+0xea/0x2f8
 [<c10376b1>] ? process_one_work+0x305/0x305
 [<c103c113>] kthread+0x8e/0x90
 [<c14cfcb7>] ret_from_kernel_thread+0x1b/0x28
 [<c103c085>] ? __kthread_parkme+0x58/0x58
---[ end trace 983ed25759656968 ]---

------------[ cut here ]------------
WARNING: at drivers/gpu/drm/i915/intel_display.c:7942
intel_modeset_check_state+0x517/0x719()
crtc active state doesn't match with hw state (expected 0, found 1)
CPU: 0 PID: 3558 Comm: kworker/0:2 Not tainted 3.10.0-rc1+ #28
Hardware name: Dell Computer Corporation Dimension 2350/07W080, BIOS A01
12/17/2002
Workqueue: events console_callback
 de9f7b38 de9f7b38 de9f7b00 c158bd4b de9f7b28 c1029e91 c1766824 de9f7b54
 00001f06 c13a00b5 c13a00b5 eec15000 eecf34c0 ee2cc000 de9f7b40 c1029f02
 00000009 de9f7b38 c1766824 de9f7b54 de9f7d50 c13a00b5 c1765738 00001f06
Call Trace:
 [<c158bd4b>] dump_stack+0x16/0x18
 [<c1029e91>] warn_slowpath_common+0x59/0x70
 [<c13a00b5>] ? intel_modeset_check_state+0x517/0x719
 [<c13a00b5>] ? intel_modeset_check_state+0x517/0x719
 [<c1029f02>] warn_slowpath_fmt+0x33/0x35
 [<c13a00b5>] intel_modeset_check_state+0x517/0x719
 [<c13a3727>] intel_crt_dpms+0x68/0x8c
 [<c1369fec>] ? drm_modeset_lock_all+0x3d/0x4c
 [<c1358eb5>] drm_fb_helper_dpms+0xd5/0x11d
 [<c104ba26>] ? __blocking_notifier_call_chain+0x47/0x5b
 [<c1359de1>] drm_fb_helper_blank+0x22/0x53
 [<c12ea0e9>] fb_blank+0x4a/0x90
 [<c12f42cc>] fbcon_blank+0x220/0x2c1
 [<c10528bb>] ? update_curr.constprop.41+0x9f/0x162
 [<c104b56b>] ? down+0x13/0x3e
 [<c134299e>] ? console_callback+0x11/0x154
 [<c13423bd>] do_blank_screen+0x11c/0x227
 [<c13429ec>] console_callback+0x5f/0x154
 [<c1040e05>] process_one_work+0x18e/0x427
 [<c1040dc8>] ? process_one_work+0x151/0x427
 [<c1041191>] worker_thread+0xf3/0x316
 [<c104109e>] ? process_one_work+0x427/0x427
 [<c104694b>] kthread+0x9e/0xa0
 [<c1592bb7>] ret_from_kernel_thread+0x1b/0x28
 [<c10468ad>] ? __kthread_parkme+0x5b/0x5b
---[ end trace 3c7867f395b5fea7 ]---

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130519/4046c0cf/attachment-0001.html>