From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Schauss <schauss@tum.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
John Kacur <jkacur@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: 3.2-rc1 and nvidia drivers
Date: Fri, 02 Dec 2011 14:37:22 -0500 [thread overview]
Message-ID: <1322854643.30977.53.camel@frodo> (raw)
In-Reply-To: <4ED90DC9.9090206@tum.de>
On Fri, 2011-12-02 at 18:41 +0100, Thomas Schauss wrote:
> this patch does indeed get rid of the lockdep-splat.
>
> Regarding the original subject of the post:
>
> Running startx with the nvidia binary driver fails on 3.0.9-rt25 and
> 3.2-rc2-rt3 when CONFIG_PREEMPT_RT_FULL=y and works fine for
> CONFIG_PREEMPT_RTB=y. There is no lockdep-warning, kernel oops/bug,
> etc., neither in any log-files nor on the serial console.
>
> This happens on several machines which ran fine with 2.6.33-rt29.
>
> I know many people here are no big fans of the nvidia driver (and
> rightly so). Unfortunately we really need this.
The biggest problem with nvidia is that it's a black box for us. We have
no idea what's happening behind the scenes. Once the nvidia drive takes
over, we're in the dark and can't do much about it. If you depend on
nvidia so much, perhaps you could contact them. Their engineers may be
able to help you here.
>
> If anyone has any further ideas on debugging this issue I would be
> really thankful.
Perhaps kick off nmi_watchdog and hope that it produces something?
-- Steve
next prev parent reply other threads:[~2011-12-02 19:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 9:10 3.2-rc1 and nvidia drivers Javier Sanz
2011-11-16 9:40 ` Thomas Schauss
2011-11-16 15:06 ` Thomas Gleixner
2011-11-28 10:08 ` Thomas Schauss
2011-11-28 11:31 ` John Kacur
2011-11-29 14:31 ` John Kacur
2011-11-30 2:36 ` Steven Rostedt
2011-11-30 8:23 ` John Kacur
2011-11-30 11:14 ` Peter Zijlstra
2011-11-30 14:14 ` Steven Rostedt
2011-11-30 14:16 ` Peter Zijlstra
2011-11-30 14:28 ` Steven Rostedt
2011-11-30 14:31 ` Steven Rostedt
2011-11-30 14:34 ` Peter Zijlstra
2011-11-30 15:07 ` Thomas Schauss
2011-11-30 15:20 ` Steven Rostedt
2011-12-02 17:41 ` Thomas Schauss
2011-12-02 19:37 ` Steven Rostedt [this message]
2011-11-30 13:34 ` Steven Rostedt
2011-11-30 13:39 ` John Kacur
2011-11-30 13:49 ` Steven Rostedt
2011-11-30 13:53 ` John Kacur
2011-11-30 9:06 ` Thomas Schauss
2011-11-16 9:52 ` Mike Galbraith
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=1322854643.30977.53.camel@frodo \
--to=rostedt@goodmis.org \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=schauss@tum.de \
--cc=tglx@linutronix.de \
/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).