linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Emde <Carsten.Emde@osadl.org>
To: ulmo@sonic.net
Cc: linux-rt-users@vger.kernel.org
Subject: Re: 2.6.31.12-rt20:  BUG: sleeping function called from invalid context at kernel/rtmutex.c:684
Date: Tue, 16 Feb 2010 00:38:14 +0100	[thread overview]
Message-ID: <4B79DAE6.9010500@osadl.org> (raw)
In-Reply-To: <f1abefc50f3730ba8ff4b099170c9a85.squirrel@webmail.sonic.net>

On 02/14/2010 07:26 PM, ulmo@sonic.net wrote:
> I'm getting plenty of dmesg errors in 2.6.31.12-rt20, a stock 2.6.31.12
> with rt20 patch applied.  Reviewing lkml (google pointed me that way, not
> surprisingly), I see that it's been happening variously for a few years.
Triggered from different places.

> My first theory is that it is started by X somehow.  I noted the "tainted"
> in the output, so I do have to mention I have nvidia driver 190.53-r1
> installed.  It happened first at 3266.451642 seconds kernel running, at
> Feb 13 13:25:04.  Looking for processes aged that much, I see that "kdm"
> started at 13:23, and some others:
> [..]
> It happened well after I loaded the nvidia driver, but perhaps using it is
> what causes it, since it happened first two minutes after starting X.  The
> fact that the kernel ran for 3266.451641 seconds without trouble then
> suddenly starts having lots of them when X starts indicates that X is very
> related to the problem.
You did a perfect job. Based on the evidence you provided, your
assumption appears correct that the nvidia driver is triggering kernel
BUG messages. However, fixing this bug requires access to the driver
sources which Nvidia refuses to provide. Alternatively, a company may
decide to provide appropriate documentation to let a community write a
Linux driver. But Nvidia fails to do so as well. Many people decide not
to buy from such manufacturers.

Open source support for ATI Radeon graphic boards is much better now.
The X1950 Pro, for example, perfectly runs Compiz, Torcs and other 3D
applications on 2.6.31.12-rt20 and does not interfere with the real-time
capabilities of the kernel. If you are lucky, you may get one at an
online marketplace for less than 30 bucks.

	Carsten.

      reply	other threads:[~2010-02-15 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 18:26 2.6.31.12-rt20: BUG: sleeping function called from invalid context at kernel/rtmutex.c:684 ulmo
2010-02-15 23:38 ` Carsten Emde [this message]

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=4B79DAE6.9010500@osadl.org \
    --to=carsten.emde@osadl.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=ulmo@sonic.net \
    /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;
as well as URLs for NNTP newsgroup(s).