Bug 26938 - Modeset code fails to set proper display resolution
Summary: Modeset code fails to set proper display resolution
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Jesse Barnes
QA Contact:
Keywords: NEEDINFO
Depends on:
Reported: 2010-03-07 08:23 UTC by maximlevitsky
Modified: 2017-07-24 23:08 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

intel_reg_dumper output (10.37 KB, text/plain)
2010-03-07 08:30 UTC, maximlevitsky
no flags Details
video bios dump (48.00 KB, application/octet-stream)
2010-07-03 17:49 UTC, maximlevitsky
no flags Details
xrandr -q --verbose output (3.06 KB, application/octet-stream)
2010-07-03 17:50 UTC, maximlevitsky
no flags Details

Description maximlevitsky 2010-03-07 08:23:02 UTC

drm:        581cafbc2493ad97ada41f03c8dd70f9ec4bf19d
mesa:       465fee75ee8991349da742e5a1a5be3cd179bb62
X server:   bbae92795c7eab062e6722c42fa7915e0cee5d69
xf86_intel: 1cd556420277f103c47ade422f3ec8f8efb2d282
kernel:     4da0b66c6e9ea7ba78a19f9f186779826d89f8b0

DG965RY Intel motherboard with VGA connector connected to an LCD

I do:
(The above turns on Xrandr support in the SDL, because xvidmode was removed)

I start neverball (only an example, happens with other SDL based applications).
It starts full screen.

I change screen resolution from one resolution to another, I repeat that process many times. At one point, my LCD will show message about out of range input signal.

I switch to console and back, and see normal resolution. Sometimes this doesn't work, and I am forced to reboot the system.

I attack the output of intel_reg_dumper when screen output goes out of range.
Comment 1 maximlevitsky 2010-03-07 08:30:45 UTC
Created attachment 33832 [details]
intel_reg_dumper output
Comment 2 Jesse Barnes 2010-04-06 11:44:40 UTC
Yakui, can you take a look (assuming this still happens).
Comment 3 ykzhao 2010-04-06 17:49:35 UTC
    Will you  add the boot option of "drm.debug=0x04" and attach the output of dmesg? (It will be better that i915 is compiled as built-in kernel module)
    It will be great if you can also attach the following outputs:
    a. xrandr -q --verbose
    b. vbios.dump. It can be obtained by using the following commands:
      1. echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom
    2. cat /sys/devices/pci0000:00/0000:00:02.0/rom >vbios.dump
    3. echo 0 > /sys/devices/pci0000:00/0000:00:02.0/rom

Comment 4 ykzhao 2010-06-07 19:40:28 UTC
As there is no response for more than two months, this bug will be rejected.

If the issue still exists, please reopen it again.
Comment 5 maximlevitsky 2010-06-29 13:21:45 UTC
This bug does still exist.

Sorry for no cooperation, it is really my fault.

I don't have much time now, but I do all tests eventually.
Comment 6 maximlevitsky 2010-07-03 17:49:50 UTC
Created attachment 36732 [details]
video bios dump
Comment 7 maximlevitsky 2010-07-03 17:50:20 UTC
Created attachment 36733 [details]
xrandr -q --verbose output
Comment 8 maximlevitsky 2010-07-03 18:43:11 UTC
I can't seem to reproduce that currently.
Stars aren't aligned or something like that....

I keep drm.debug=0x04 around untill this shows up again
Comment 9 Jesse Barnes 2010-07-15 11:21:45 UTC
Hopefully it'll stay fixed, thanks.
Comment 10 maximlevitsky 2010-07-15 12:03:30 UTC

Despite a lot more tries, this bug just disappeared.
The only thing I updated then was libX11....

So indeed, this is right to close that bug

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.