| Summary: | [i915] blank screen with 2.6.29-rc kernels | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Sami Kerola <kerolasa> | ||||
| Component: | DRM/Intel | Assignee: | Jesse Barnes <jbarnes> | ||||
| Status: | CLOSED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | medium | Keywords: | NEEDINFO, regression | ||||
| Version: | XOrg git | ||||||
| Hardware: | x86-64 (AMD64) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Sami Kerola
2009-03-16 01:36:11 UTC
(In reply to comment #0) Results with 2.6.29-rc8-00124 are different. > Mode switching. When switching modes nearly 50% of times when I come back to X > screen is blank. Retry works fine. 100% of switches work. > Deattach from dock while system running test. After this X was never blank, but > console mode was always. The console mode was perfectly usable. Same as reattach. > Reattach to dock. System freeze without stacktrace and the Magic SysRq keys did > nothing. All of my reattachment tries has always caused this, and because > behavior is so annoying I have done this only three times. Screen is not blank, it is frozen with what ever there happens to be. Input does nothing including SysRq stuff. (In reply to comment #1) > (In reply to comment #0) > > > Reattach to dock. System freeze without stacktrace and the Magic SysRq keys did > > nothing. All of my reattachment tries has always caused this, and because > > behavior is so annoying I have done this only three times. > > Screen is not blank, it is frozen with what ever there happens to be. Input > does nothing including SysRq stuff. I was having problems with docking on a different laptop (Thinkpad X60) that were because of acpi bugs. Can you check syslog to make sure this is drm causing the issue and not another subsystem? I was getting a flood of events that essentially made the system lock up. After recompiling with following as yes CONFIG_PM_DEBUG CONFIG_ACPI_DEBUG CONFIG_PCI_DEBUG CONFIG_DEBUG_DRIVER CONFIG_DEBUG_KERNEL CONFIG_DEBUG_BUGVERBOSE CONFIG_DEBUG_INFO and making acpi to output more echo 0x1F >/sys/module/acpi/parameters/debug_level echo 0x1F >/sys/module/acpi/parameters/debug_layer I still do not see anything in syslog and I am not sure what is causing the problem. Initial problems with blank screen seemed like graphics driver issue, but reattach to dock may very well be something else. Lets see will I be able to figure out what, if I do I let you know. Does this still exist in 2.6.30 or 2.6.31-rcX? My testing environment stopped working properly so I do not know. I hope to have time within week or two to get environment fixed so that I can say something more reliable. Would be good if you could test a distro kernel w/KMS enabled too, or try a kernel config based on a distro config, that way you're likely to be trying well tested options. Closing due to inactivity. If you still see this problem (hopefully it's been fixed) it may be due to ACPI docking activity. We have some hooks to use to reprogram the outputs in that case, so it may be easy to fix. Closing resolved+invalid, no activity in 7 years. |
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.