Attachment #58212 | |||||
---|---|---|---|---|---|
dmesg, xorg, xrandr output of working and failing scenarios | text/plain | 2012-03-08 15:09:01 UTC | 210.56 KB | no flags | Details |
Attachment #58213 | |||||
---|---|---|---|---|---|
dmesg of working and non-working runs with drm.debug=0xe | text/plain | 2012-03-08 15:12:39 UTC | 171.55 KB | no flags | Details |
Attachment #59087 | |||||
---|---|---|---|---|---|
intel_reg_dumper, ok run 1 | text/plain | 2012-03-26 13:06:32 UTC | 11.80 KB | no flags | Details |
Attachment #59088 | |||||
---|---|---|---|---|---|
intel_reg_dumper, fail run | text/plain | 2012-03-26 13:07:53 UTC | 11.80 KB | no flags | Details |
Attachment #59089 | |||||
---|---|---|---|---|---|
intel_reg_dumper, ok run 2 | text/plain | 2012-03-26 13:09:25 UTC | 11.81 KB | no flags | Details |
Attachment #59101 | |||||
---|---|---|---|---|---|
intel_reg_dumper, fail run, boot with i915.lvds_use_ssc=0 cmdline arg | text/plain | 2012-03-26 21:07:17 UTC | 11.81 KB | no flags | Details |
Attachment #59156 | |||||
---|---|---|---|---|---|
Complete dmesg output with drm.debug=0xe | text/plain | 2012-03-28 05:19:54 UTC | 297.06 KB | no flags | Details |
Attachment #59162 | |||||
---|---|---|---|---|---|
properly clear SSC1 | patch | 2012-03-28 08:25:36 UTC | 851 bytes | no flags | Details |
Attachment #59226 | |||||
---|---|---|---|---|---|
Complete dmesg output with drm.debug=0xe with "Properly clear ssc1" patch applied | text/plain | 2012-03-29 07:28:10 UTC | 293.93 KB | no flags | Details |
Attachment #59280 | |||||
---|---|---|---|---|---|
intel_reg_dumper, fail run, with "properly clear SSC1" patch applied | text/plain | 2012-03-30 08:20:59 UTC | 11.80 KB | no flags | Details |
Attachment #59299 | |||||
---|---|---|---|---|---|
intel_reg_dumper, ok, with 3.3 kernel and backported drm/i2c from 9613bebb223dea3179c265dc31e1bb41ae39f321 | patch | 2012-03-30 15:41:41 UTC | 11.80 KB | no flags | Details |
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.