Bug#601081: does #601081 still occur in linux-image-2.6.32-5-686_2.6.32-27?

To: 601081@bugs.debian.org
Cc: Johannes Rohr <jorohr@gmail.com>
Subject: Bug#601081: does #601081 still occur in linux-image-2.6.32-5-686_2.6.32-27?
From: Tomáš Pospíšek <tpo@sourcepole.ch>
Date: Sat, 20 Nov 2010 12:04:23 +0100 (CET)
Message-id: <[🔎] alpine.DEB.2.00.1011201201240.24299@localhost>
Reply-to: Tomáš Pospíšek <tpo@sourcepole.ch>, 601081@bugs.debian.org

In http://bugs.debian.org/601081 you report a resume failure on a i915system with kernel v2.6.32-25. However v2.6.32-27 contains speficallyfixes for i915 systems:


  * Add drm changes from 2.6.32.24+drm33.11:
    - i915: return -EFAULT if copy_to_user fails.
    - drm/i915: Prevent double dpms on
    - drm: Only decouple the old_fb from the crtc is we call mode_set*
    - drm/i915: Unset cursor if out-of-bounds upon mode change (v4)
    - drm/i915,agp/intel: Add second set of PCI-IDs for B43

Does your resume problem still occur with the latest sqeeze kernel?
*t

Reply to:

Follow-Ups:
- Bug#601081: does #601081 still occur in linux-image-2.6.32-5-686_2.6.32-27?
  - From: Johannes Rohr <jorohr@gmail.com>

Prev by Date: Bug#584314: please add lspci info to bugreport #584314
Next by Date: Bug#570517: does #570517 still occur with latest squeeze kernel?
Previous by thread: Bug#584314: please add lspci info to bugreport #584314
Next by thread: Bug#601081: does #601081 still occur in linux-image-2.6.32-5-686_2.6.32-27?
Index(es):
- Date
- Thread