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: <20121006072704.GA22465@1wt.eu>
Date:	Sat, 6 Oct 2012 09:27:04 +0200
From:	Willy Tarreau <w@....eu>
To:	Dave Airlie <airlied@...il.com>
Cc:	Chris Wilson <chris@...is-wilson.co.uk>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	linux-kernel@...r.kernel.org
Subject: Re: 3.5 regression on i915

On Sat, Oct 06, 2012 at 01:58:45AM +0200, Willy Tarreau wrote:
> On Sat, Oct 06, 2012 at 09:48:57AM +1000, Dave Airlie wrote:
> > Any reason you don't have KMS, you'll keep hitting these non-kms bugs
> > since it has no users anymore really.
> > 
> > Granted they'll get fixed, but I suspect its a losing battle over time.
> 
> Well, back in old times every time I tried to enable it, I only ran into
> problems so I got used to disable it, which made sense since it didn't
> bring me any benefit.

OK I found why in the end. When I enable KMS, my X server fails to start
and segfaults in intel_drv.so. So I think that the comment in Kconfig
below is quite appropriate :

   config DRM_I915_KMS
        bool "Enable modesetting on intel by default"
        depends on DRM_I915
        help
          Choose this option if you want kernel modesetting enabled by default,
          and you have a new enough userspace to support this. Running old
          userspaces with this enabled will cause pain.  Note that this causes
          the driver to bind to PCI devices, which precludes loading things
          like intelfb.

Regards,
Willy

--
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