linux-kernel - Re: [REGRESSION] [KMS] [INTEL] Wrong resolution in console and XWindow

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201207251257.50064.maciej.rutecki@gmail.com>
Date:	Wed, 25 Jul 2012 12:57:49 +0200
From:	Maciej Rutecki <maciej.rutecki@...il.com>
To:	Daniel Vetter <daniel@...ll.ch>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	dri-devel@...ts.freedesktop.org
Subject: Re: [REGRESSION] [KMS] [INTEL] Wrong resolution in console and XWindow

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
-- 
Maciej Rutecki
http://www.mrutecki.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/