From: Thomas Schauss <schauss@tum.de>
To: Steven Rostedt <rostedt@goodmis.org>
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 18:41:29 +0100 [thread overview]
Message-ID: <4ED90DC9.9090206@tum.de> (raw)
In-Reply-To: <1322666431.24563.2.camel@frodo>
On 11/30/2011 04:20 PM, Steven Rostedt wrote:
> On Wed, 2011-11-30 at 16:07 +0100, Thomas Schauss wrote:
>
>> On 3.0.9-rt25 (which I have been using here) patch 30765b92 is already
>> applied. And it is also present in patch-3.0.10-rt27.patch.
>
> I'm such a fscking idiot!
>
> I've been working on a port of a patch in 2.6.33-rt, and I didn't
> realize that I was still in that kernel, applying these patches. As I
> said, I thought the one Peter had was already applied. It was, I'm the
> idiot that didn't realize I was in the wrong kernel!
>
>>
>> So the original patch from Peter
>> (http://article.gmane.org/gmane.linux.kernel.mm/70863/match=) applies
>> cleanly here.
>
> Yeah, thanks. That's the patch you want.
>
> -- Steve
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello,
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.
If anyone has any further ideas on debugging this issue I would be
really thankful.
Best Regards,
Thomas
next prev parent reply other threads:[~2011-12-02 17:41 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 [this message]
2011-12-02 19:37 ` Steven Rostedt
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=4ED90DC9.9090206@tum.de \
--to=schauss@tum.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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).