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: <20120603132731.GA4696@phenom.ffwll.local>
Date:	Sun, 3 Jun 2012 15:27:47 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	Paulo Zanoni <przanoni@...il.com>
Cc:	Dave Jones <davej@...hat.com>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	dri-devel@...ts.freedesktop.org,
	Intel Graphics Development <intel-gfx@...ts.freedesktop.org>
Subject: Re: Lots of i915/drm spew on 3.4

On Thu, May 31, 2012 at 11:43:21AM -0300, Paulo Zanoni wrote:
> 2012/5/30 Dave Jones <davej@...hat.com>:
> > On Wed, May 30, 2012 at 05:58:48PM -0400, Dave Jones wrote:
> >  > On Wed, May 30, 2012 at 11:51:54PM +0200, Daniel Vetter wrote:
> >  >  > On Wed, May 30, 2012 at 11:31 PM, Dave Jones <davej@...hat.com> wrote:
> >  >  > > On this hardware:
> >  >  > >
> >  >  > > 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
> >  >  > >
> >  >  > > I get this every boot with Linus current tree (up to af56e0aa35f3ae2a4c1a6d1000702df1dd78cb76)
> >  >  >
> >  >  > Just a quick question, is this a regression?
> >  >
> >  > seems so, I don't see it on 3.3
> >  >
> >  >  > If so, can you please
> >  >  > attach the output of xrandr --verbose from a noisy and a quite kernel
> >  >  > (otherwise just please attach it from this noisy kernel).
> >  >
> >  > this machine runs headless, so has no X installed right now, I'll get it in a while.
> >
> > Attached.
> >
> 
> Just a little more information: you have a lot of connector properties
> because for some reason the driver thinks you have TV1, TV2 and TV3.
> Each TV connector has a lot of properties... With kernel 3.3 you have
> only TV1 and TV2. Maybe instead of increasing the maximum property
> count we should try to investigate why there's a new TV connector in
> the new kernel (and maybe this is also not a bug/regression...).

I've merged a patch from Chris to detect additional sdvo TV outputs:

commit a0b1c7a5197293d6206b245b45edc3f508aadab6
Author: Chris Wilson <chris@...is-wilson.co.uk>
Date:   Fri Sep 30 22:56:41 2011 +0100

    drm/i915/sdvo: Include YRPB as an additional TV output type

So that explains that hopefully.
-Daniel
-- 
Daniel Vetter
Mail: daniel@...ll.ch
Mobile: +41 (0)79 365 57 48
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ