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

Thanks for the reply, Steven. ( i didn't even think i would get that)

> 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 see. I know how to reproduce this issue, and how to completely avoid
it from affecting me, anyway - so it's not a huge deal. It's only
happened twice, in both circumstances i use using VDPAU with Adobe
flash <sarcasm>surprise, surprise!</sarcasm>, also in both
circumstances my uptime had been several days. ie: it doesn't happen
very often, at all.

I understand why you don't care about nvidia, but if it is a bug in RT
- should it not be fixed? anyways, I will report it to nvidia once i
get a chance to. it would nice if they addressed RT-related problems
in their driver being as some folks do require proper/good 3d
acceleration / real performance / Opengl 4.2 which (obviously) Nouveau
does not provide, nor is it anywhere near providing in the foreseeable
future :\ (not that this is news to anyone who has used them both).

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

No problem. I know the author of the patch, anyway. I just wanted some
verification, rather than just making my own assumptions.

take care, and thanks again.

jordan

  reply	other threads:[~2012-05-08 15:46 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
2012-05-08 15:46   ` jordan [this message]
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=CAOcfFMx1J05oxWaXxBMSaMiMc0SWDpD57C9OtzqXtvRrsQBORw@mail.gmail.com \
    --to=triplesquarednine@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.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 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.