linux-kernel - Re: [Bug #13667] drm: display arifacts when X.Org is stopped

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: <20090709100914.2502763a@jbarnes-g45>
Date:	Thu, 9 Jul 2009 10:09:14 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Frans Pop <elendil@...net.nl>
Cc:	Dave Airlie <airlied@...il.com>, "Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
Subject: Re: [Bug #13667] drm: display arifacts when X.Org is stopped

On Thu, 9 Jul 2009 03:28:52 +0200
Frans Pop <elendil@...net.nl> wrote:

> On Thursday 09 July 2009, Dave Airlie wrote:
> > > [1] I'd even go so far as to feel it should be a standard test
> > > case for video driver developers, given that this is the third
> > > time it's shown regressions :-) For the third case the bug was in
> > > the X.Org i830 driver:
> > > http://bugs.freedesktop.org/show_bug.cgi?id=14481.
> >
> > It might surprise you to learn this, but vesafb has never been
> > considered supportable by the X.org community, and you'll notice not
> > very many distros ship with it enabled, it breaks suspend/resume on
> > many machines for example.
> 
> I beg to disagree.
> - Debian does have it enabled by default.
> - I have always used it on all my machines without any problems.
> - Both my laptops and my desktop suspend and resume perfectly with
> vesafb and X.Org.
> - Jesse Barnes seems to disagree with you. To quote from the BR cited
>   above (comment #11): "and you're right, making things work with
> vesafb isn't unreasonable".

Since my ears are burning I figured I'd better qualify this: I made
that statement before we had KMS upstream.  Supporting the case where
multiple drivers try to bang on the same device has always been a big
pain.  In a KMS configuration we don't support it at all.

> Yes, and I really welcome the great progress being made there. But
> for me it's not yet an option as I run Debian stable on these boxes.

Sounds like that's not an option for you though... which means
debugging where the interaction is going wrong...

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