All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: jordan <triplesquarednine@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: nvidia bug or RT bug?
Date: Tue, 08 May 2012 11:15:00 -0400	[thread overview]
Message-ID: <1336490100.14207.183.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <CAOcfFMwkXC1Ozs3+QhKUU18JY4KDzNaxAuLq34r+PQOCipSFSg@mail.gmail.com>

On Sun, 2012-05-06 at 21:17 -0400, jordan wrote:
> Hey everyone.
> 
> I've been using linux-rt-3.0 series, which has been very stable using
> the nvidia proprietary drivers (pretty much flawlessly, actually). I
> had used rt-3.0 with nvidia all the way upto nvidia version 290.35. I
> never experienced any problems relating to nvidia, at all... But
> external/other reasons, recently I have upgraded to rt-3.2 which also
> seems to be working quite well. At the same time, i also upgraded my
> nvidia driver to the latest available driver, which is 302.07 (beta).
> 
> I know many of the RT devs aren't huge fans of the nvidia blob, but i
> would like to know whether this is an nvidia bug or rt bug;
> 
> [143335.564097] BUG: scheduling while atomic: irq/19-nvidia/1141/0x00000002

[..]

> 
> if this is an nvidia problem (which i assume it is), i would like to
> report it to them (and obviously, if it is an rt related bug - i would
> like to report it here.

It's both, but we don't care. Sorry. Seems that the nvidia driver is not
compatible with some of the changes that -rt has done. One is that you
can not call spinlocks after disabling preemption. If the nvidia driver
does this, it will break.

> 
> I am using an rt-patch for the nvidia driver. I simply adapted an
> existing package for my distro (Archlinux). the patch is available
> here, in case it matters;

Bring up the bug with the nvidia rt patch maintainer. That's about all
I'll say on this matter.

-- Steve




  reply	other threads:[~2012-05-08 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07  1:17 nvidia bug or RT bug? jordan
2012-05-08 15:15 ` Steven Rostedt [this message]
2012-05-08 15:46   ` jordan
2012-05-08 15:58     ` Steven Rostedt
2012-06-05 23:32 ` Glenn Elliott
2012-06-06  0:03   ` Glenn Elliott
2012-06-06  0:25     ` jordan

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=1336490100.14207.183.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=triplesquarednine@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.