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]
Date:	Tue, 28 Jul 2009 09:23:19 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Paul Rolland <rol@...917.net>
Cc:	Frans Pop <elendil@...net.nl>, linux-kernel@...r.kernel.org,
	rol@...be.net
Subject: Re: Linux-2.6.31-rc4 - shut the annoying "failed to acquire
 vblank..."

On Tue, 28 Jul 2009 14:53:59 +0200
Paul Rolland <rol@...917.net> wrote:

> Hi Frans,
> 
> On Tue, 28 Jul 2009 12:44:12 +0200
> Frans Pop <elendil@...net.nl> wrote:
> 
> > > I sent a mail long ago about this message :
> > > tux kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank
> > > counter, -22 showing up more than 10 times per second, but was
> > > told that I had some old userspace apps running... As I was using
> > > an old FC8, I forgot about it.
> > 
> > The message does not only show with old applications, it also shows:
> > - every time I suspend my notebook
> > - every time I start a second X session to log in as a different
> > user
> Well, with the so-called "old apps", it's 20 times per second, as
> long as the app is running, which really makes it painful, because it
> causes all the logs to show off quickly :(
>  
> > I agree that the message is very annoying and would be glad to be
> > rid of it, especially as the only comment from the maintainers so
> > far has been to just ignore it.
> Well, I'd really like some feedback from the maintainer... because if
> no one cares, I agree it should be removed.
> 
> > IMHO, If it is "ignoreable", then it is also "suppressable".
> Seconded, unless someone is using it to try to fix the problem ?

It indicates a userland problem, and yes we shouldn't print that
message.  I've also posted a patch to quiet it a few times, but Dave
hasn't picked it up yet.  Feel free to send it straight to Linus with
my Reviewed-by if you want.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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