[REGRESSION,KMS,INTEL] Wrong resolution in console and XWindow
diff mbox

Message ID 20120725092928.GD5396@phenom.ffwll.local
State New, archived
Headers show

Commit Message

Daniel Vetter July 25, 2012, 9:29 a.m. UTC
On Wed, Jul 25, 2012 at 10:54:25AM +0200, Maciej Rutecki wrote:
> On ?roda, 25 lipca 2012 o 10:29:26 Daniel Vetter wrote:
> > On Wed, Jul 25, 2012 at 10:20:47AM +0200, Maciej Rutecki wrote:
> > > Last known good: 3.4.4
> > > First bad: 3.5.0
> > > 
> > > When booting 3.5.0 resolution (in console, and after in KDE) is set to
> > > 1024x768 (60Hz). In 3.4.4 was correct: 1440x900 (60Hz).
> > 
> > Can you please attach the output of xrandr --verbose for both kernels?
> > Also, please boot with drm.debug=0xe added to your kernel cmdline and grab
> > the dmesg (again for both kernels).
> > 
> 
> Thanks for the ansfer.
> 
> Here xrandr and dmesg outputs for 3.4.4 and 3.5.0
> 
> http://mrutecki.pl/download/kernel/3.5/swinka/debug/

Can you please test this quick hack:




Thanks, Daniel

Comments

Maciej Rutecki July 25, 2012, 10:57 a.m. UTC | #1
On ?roda, 25 lipca 2012 o 11:29:28 Daniel Vetter wrote:
> On Wed, Jul 25, 2012 at 10:54:25AM +0200, Maciej Rutecki wrote:
> > On ?roda, 25 lipca 2012 o 10:29:26 Daniel Vetter wrote:
> > > On Wed, Jul 25, 2012 at 10:20:47AM +0200, Maciej Rutecki wrote:
> > > > Last known good: 3.4.4
> > > > First bad: 3.5.0
> > > > 
> > > > When booting 3.5.0 resolution (in console, and after in KDE) is set
> > > > to 1024x768 (60Hz). In 3.4.4 was correct: 1440x900 (60Hz).
> > > 
> > > Can you please attach the output of xrandr --verbose for both kernels?
> > > Also, please boot with drm.debug=0xe added to your kernel cmdline and
> > > grab the dmesg (again for both kernels).
> > 
> > Thanks for the ansfer.
> > 
> > Here xrandr and dmesg outputs for 3.4.4 and 3.5.0
> > 
> > http://mrutecki.pl/download/kernel/3.5/swinka/debug/
> 
> Can you please test this quick hack:
> 
> 
> diff --git a/drivers/gpu/drm/i915/intel_i2c.c
> b/drivers/gpu/drm/i915/intel_i2c.c index 1991a44..abe1611 100644
> --- a/drivers/gpu/drm/i915/intel_i2c.c
> +++ b/drivers/gpu/drm/i915/intel_i2c.c
> @@ -405,7 +405,7 @@ clear_err:
>  	 * timing out seems to happen when there _is_ a ddc chip present, but
>  	 * it's slow responding and only answers on the 2nd retry.
>  	 */
> -	ret = -ENXIO;
> +	ret = 0;
>  	if (wait_for((I915_READ(GMBUS2 + reg_offset) & GMBUS_ACTIVE) == 0,
>  		     10)) {
>  		DRM_DEBUG_KMS("GMBUS [%s] timed out after NAK\n",
> 
> 
> Thanks, Daniel

Still the same.

PS. Unfortunately, this afternoon I have small a surgical operation and 
further tests will be possible only after 2-3 days.

Regards
Daniel Vetter July 25, 2012, 11:55 a.m. UTC | #2
On Wed, Jul 25, 2012 at 12:57 PM, Maciej Rutecki
<maciej.rutecki@gmail.com> wrote:
> On ?roda, 25 lipca 2012 o 11:29:28 Daniel Vetter wrote:
>> On Wed, Jul 25, 2012 at 10:54:25AM +0200, Maciej Rutecki wrote:
>> > On ?roda, 25 lipca 2012 o 10:29:26 Daniel Vetter wrote:
>> > > On Wed, Jul 25, 2012 at 10:20:47AM +0200, Maciej Rutecki wrote:
>> > > > Last known good: 3.4.4
>> > > > First bad: 3.5.0
>> > > >
>> > > > When booting 3.5.0 resolution (in console, and after in KDE) is set
>> > > > to 1024x768 (60Hz). In 3.4.4 was correct: 1440x900 (60Hz).
>> > >
>> > > Can you please attach the output of xrandr --verbose for both kernels?
>> > > Also, please boot with drm.debug=0xe added to your kernel cmdline and
>> > > grab the dmesg (again for both kernels).
>> >
>> > Thanks for the ansfer.
>> >
>> > Here xrandr and dmesg outputs for 3.4.4 and 3.5.0
>> >
>> > http://mrutecki.pl/download/kernel/3.5/swinka/debug/
>>
>> Can you please test this quick hack:
>>
>>
>> diff --git a/drivers/gpu/drm/i915/intel_i2c.c
>> b/drivers/gpu/drm/i915/intel_i2c.c index 1991a44..abe1611 100644
>> --- a/drivers/gpu/drm/i915/intel_i2c.c
>> +++ b/drivers/gpu/drm/i915/intel_i2c.c
>> @@ -405,7 +405,7 @@ clear_err:
>>        * timing out seems to happen when there _is_ a ddc chip present, but
>>        * it's slow responding and only answers on the 2nd retry.
>>        */
>> -     ret = -ENXIO;
>> +     ret = 0;
>>       if (wait_for((I915_READ(GMBUS2 + reg_offset) & GMBUS_ACTIVE) == 0,
>>                    10)) {
>>               DRM_DEBUG_KMS("GMBUS [%s] timed out after NAK\n",
>>
>>
>> Thanks, Daniel
>
> Still the same.

Hm, can you attach the dmesg again (with drm.debug=0xe)? If I haven't
botched up something, we should now retry at least the ddc transfer
...
-Daniel

>
> PS. Unfortunately, this afternoon I have small a surgical operation and
> further tests will be possible only after 2-3 days.
>
> Regards
> --
> Maciej Rutecki
> http://www.mrutecki.pl

Patch
diff mbox

diff --git a/drivers/gpu/drm/i915/intel_i2c.c b/drivers/gpu/drm/i915/intel_i2c.c
index 1991a44..abe1611 100644
--- a/drivers/gpu/drm/i915/intel_i2c.c
+++ b/drivers/gpu/drm/i915/intel_i2c.c
@@ -405,7 +405,7 @@  clear_err:
 	 * timing out seems to happen when there _is_ a ddc chip present, but
 	 * it's slow responding and only answers on the 2nd retry.
 	 */
-	ret = -ENXIO;
+	ret = 0;
 	if (wait_for((I915_READ(GMBUS2 + reg_offset) & GMBUS_ACTIVE) == 0,
 		     10)) {
 		DRM_DEBUG_KMS("GMBUS [%s] timed out after NAK\n",