Bug 13144
| Summary: | resume from suspend fails using video card i915 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | C Sights (csights) |
| Component: | Video(Other) | Assignee: | drivers_video-other |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | bug19, jbarnes |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.29 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 12398 | ||
| Attachments: |
config file used to compile v2.6.29
xorg log of an unable to wake-up system |
||
|
Description
C Sights
2009-04-21 17:03:25 UTC
Does this also fail with 2.6.30-rc2? Found out the following:
There is no suspend/resume probem in 2.6.30-rc3 AND 2.6.29 if
Enable modesetting on intel by default = n
(# CONFIG_DRM_I915_KMS is not set)
The resume problem above was reported with 2.6.29
Enable modesetting on intel by default = y
(CONFIG_DRM_I915_KMS=y)
2.6.30-rc3 fails to suspend with
Enable modesetting on intel by default = y
(CONFIG_DRM_I915_KMS=y)
(I.e. fails earlier in the suspend/resume cycle than original report.)
I no longer know whether to consider this a regression. The kernel menuconfig help says "Running old userspaces with this [modesetting] enabled will cause pain." Having suspend/resume fail is certainly pain! :)
On the other hand, perhaps having a change in behavior after a commit which says paraphrase "removing this shouldn't matter" should still be investigated. There may have been a logic error.
Thanks!
C.
Since nothing has happened here for some time now, may I ask what can be done to track the problem down? I can say that it is still not working in 2.6.29.3. I still have a black screen after having had a random line at the top of the screen for a short time, when coming out from sleep in 2.6.30-rc6-git5. Despite recent patch which was supposed to fix sleep, this bug is still in the same state with 2.6.31-rc1-git7. This is beginning to be really boring, since KMS is enabled by default in the kernel I use (archlinux - eeepc kernel), and I can't put the eeepc in sleep mode, nor use the VGA output. Can you attach your X log and dmesg from when this happens? Can you still ssh into the system after resume? Created attachment 22185 [details]
xorg log of an unable to wake-up system
The full xorg log is attached, from the boot to the crash.
Xorg log doesn't seems useful... Here are i915 messages in the dmesg: dmesg: [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 i915 0000:00:02.0: PCI INT A disabled ehci_hcd 0000:00:1d.7: PME# disabled ACPI: Preparing to enter system sleep state S3 Back to C! Disabling lock debugging due to kernel taint [...] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 i915 0000:00:02.0: setting latency timer to 64 [...] I don't know if that is useful either. What else can I collect? This is still not working. I thought it would be fixed by the fix of https://bugs.freedesktop.org/show_bug.cgi?id=26266 but it seems that it's not the same bug. I'm still not able to use my laptop's sleep mode, now that kms is mandatory with intel driver... It seems to be fixed by the i915.powersave=0 option, but not for my chipset: http://bugs.archlinux.org/task/18298 . What can I do? Finally, I found what was the problem, and it was not related to the kernel but to the OS, more precisely to the suspend script being in an old version and doing something that new kernels don't like. You can close the bug, it's working fine, as reported by many, as well as the VGA output and 3D acceleration with KMS. Sorry. Thanks for the update. |