Launchpad has imported 9 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=35103.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-03-07T18:42:56+00:00 Bo-b-wang wrote: Created attachment 44218 dmesg.txt is the bug's dmesg information System Environment: -------------------------- Platform: Sugarbay Libdrm: (master)2.4.24-6-g3b04c73650b5e9bbcb602fdb8cea0b16ad82d0c0 Mesa: (7.10)68cdea9fb2c33aba5459fd79f57faadf9800e5bb Xserver: (master)xorg-server-1.10.0 Xf86_video_intel: (master)2.14.901 Cairo: (master)f1d313e042af89b2f5f5d09d3eb1703d0517ecd7 Kernel: (drm-intel-fixes)91355834646328e7edc6bd25176ae44bcd7386c7 Bug detailed description: ------------------------- When I do “ echo mem >/sys/power/state” ,the memory can be suspended. And Then I press power button to wake up memory, the Memory can be waked up normally. However, An error “[drm:pch_irq_handler] *ERROR* PCH poison interrupt”message appears in the terminal. This issue occurs in Sugarbar rev09 GT2 every time. But never have occurred int Sugarbar rev09 GT1. It’s kernel regression. Reproduce steps: ---------------- 1. Don’t start X 2. echo mem>/sys/power/state 3. press power button to wake up Reply at: https://bugs.launchpad.net/linux/+bug/1031630/comments/0 ------------------------------------------------------------------------ On 2011-03-07T18:51:14+00:00 Gordon Jin wrote: The "bad" PCH for the "Sugarbay rev09 GT2" is DH SDP board. The "working" PCH for the "Sugarbay rev09 GT1" is Intel DH67CL board. Reply at: https://bugs.launchpad.net/linux/+bug/1031630/comments/1 ------------------------------------------------------------------------ On 2011-03-07T23:50:52+00:00 Chris Wilson wrote: It's not a regression, as since we weren't checking for the PCH interrupts earlier we have no idea if this was recently introduced. I've seen these on a i5-2500 which is a GT1 device. Reply at: https://bugs.launchpad.net/linux/+bug/1031630/comments/2 ------------------------------------------------------------------------ On 2011-03-08T01:02:18+00:00 Gordon Jin wrote: right, it should not be regression. It's a new machine for us. Reply at: https://bugs.launchpad.net/linux/+bug/1031630/comments/3 ------------------------------------------------------------------------ On 2011-05-30T19:22:50+00:00 Gordon Jin wrote: Chris, can you evaluate the impact of this bug? Reply at: https://bugs.launchpad.net/linux/+bug/1031630/comments/4 ------------------------------------------------------------------------ On 2011-06-08T11:31:29+00:00 Jesse Barnes wrote: Not sure what it means, but reading poisoned memory sounds like a serious issue... But it could also be a spurious interrupt from resume. Reply at: https://bugs.launchpad.net/linux/+bug/1031630/comments/5 ------------------------------------------------------------------------ On 2011-06-17T00:58:53+00:00 Mengmeng-meng wrote: The problem also exists on our IvyBridge . ----------------------------------------------------- Libdrm: (master)2.4.26 Mesa: (master)8875dd58719b978283e89acf04422a4eaf9b021d Xserver: (server-1.10-branch)xorg-server-1.10.2-11-g9551f5041915fa00ca243a279efb55de2ff11a00 Xf86_video_intel:(master)2.15.0-96-ga1ee4b930846d4ba9274028c08800b882fc926f1 Cairo: (master)3b9c8744898823a4b09917f0540a324318fef726 Libva: (master)3c1b6875b589f3a40709a889da85b979e34db625 Kernel: (drm-intel-fixes)6a574b5b9b186e28abd3e571dfd1700c5220b510 Reply at: https://bugs.launchpad.net/linux/+bug/1031630/comments/6 ------------------------------------------------------------------------ On 2011-09-12T20:43:57+00:00 Yi-sun wrote: After running the testdisplay with HDMI and VGA on IVB platform, we unplug the VGA monitor. Then the error information will appears. Reply at: https://bugs.launchpad.net/linux/+bug/1031630/comments/7 ------------------------------------------------------------------------ On 2012-06-06T15:05:42+00:00 Daniel-ffwll wrote: Should be fixed with commit 23e81d691a813839020f6e516b398d0f9369fe8b Author: Adam Jackson <[email protected]> Date: Wed Jun 6 15:45:44 2012 -0400 drm/i915: pch_irq_handler -> {ibx, cpt}_irq_handler in drm-intel-fixes. It's simply a matter of us complaining about an interrupt with new (but harmless) meaning. Reply at: https://bugs.launchpad.net/linux/+bug/1031630/comments/8 ** Changed in: linux Status: Unknown => Fix Released ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1031630 Title: “[drm:pch_irq_handler] *ERROR* PCH poison interrupt” shows after S3 resume when connecting with an external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1031630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
