From: James Morris <jmorris@namei.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Greg KH <greg@kroah.com>,
Hugh Dickins <hugh@veritas.com>, Jeff Garzik <jeff@garzik.org>
Subject: Re: Top kernel oopses/warnings for the week of May 30th 2008
Date: Mon, 2 Jun 2008 10:02:41 +1000 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0806020955570.8594@us.intercode.com.au> (raw)
In-Reply-To: <48402DAA.60202@linux.intel.com>
On Fri, 30 May 2008, Arjan van de Ven wrote:
> Rank 4: task_has_capability (warning)
> Reported 181 times (202 total reports)
> [out of tree] Bug in the proprietary firegl driver
> warning only shows up in tainted kernels
> This warning was last seen in version 2.6.25.3, and first seen in
> 2.6.25.
> More info:
> http://www.kerneloops.org/searchweek.php?search=task_has_capability
This is a shining example of why people should avoid binary drivers. I'd
guess that the bug is related to the new 64-bit capability code.
It'd be really interesting to know what this driver is doing with
capabilities in the first place.
If anyone is using this driver, the output of the following command as a
non-root user from gnome-terminal or similar may be of interest:
$ cat /proc/self/status |grep ^Cap
It should generally be all zeroes.
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2008-06-02 0:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 16:39 Top kernel oopses/warnings for the week of May 30th 2008 Arjan van de Ven
2008-05-30 19:19 ` Hugh Dickins
2008-05-30 21:43 ` Linus Torvalds
2008-05-30 21:49 ` Arjan van de Ven
2008-05-30 22:17 ` Arjan van de Ven
2008-05-30 22:00 ` Arjan van de Ven
2008-05-30 22:30 ` Linus Torvalds
2008-05-30 22:34 ` Arjan van de Ven
2008-05-30 22:55 ` Linus Torvalds
2008-05-31 0:41 ` Dave Jones
2008-06-02 23:44 ` Hugh Dickins
2008-06-03 0:00 ` Andrew Morton
2008-06-03 0:41 ` Hugh Dickins
2008-06-03 1:19 ` Andrew Morton
2008-06-09 16:32 ` Ingo Molnar
2008-06-10 12:42 ` Hugh Dickins
2008-05-30 22:34 ` Jochen Voß
2008-05-30 22:36 ` Arjan van de Ven
2008-06-02 0:02 ` James Morris [this message]
2008-06-02 2:27 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Xine.LNX.4.64.0806020955570.8594@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=greg@kroah.com \
--cc=hugh@veritas.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox