From: Joe <joecool1029@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Valdis.Kletnieks@vt.edu, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-rc3-mm1-V0.7.33-03 and NVidia wierdness, with workaround...
Date: Sun, 19 Dec 2004 21:46:15 -0500 [thread overview]
Message-ID: <d4757e60041219184662648df@mail.gmail.com> (raw)
In-Reply-To: <1103473203.4143.9.camel@localhost.localdomain>
On Sun, 19 Dec 2004 11:20:03 -0500, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 2004-12-17 at 17:42 -0500, Valdis.Kletnieks@vt.edu wrote:
>
> > Most likely, the fact you have SMP/HT and I'm just on a PREEMPT-UP kernel is
> > what's making the difference. There's almost certainly a '#ifdef CONFIG_SMP'
> > involved here somehow....
>
> Yep! I just compiled my system without SMP and I was able to start up X
> with NVidia on my HT laptop (with V0.7.33-04).
>
> Ingo, do you think this is a bug with NVidia (bad proprietary module) or
> might be with something in the RT SMP side? I'll look a little more on
> Monday, but if you know of something, let me know. I'm curious to why
> it works fine without RT but will not work with RT (and SMP). I
> shouldn't say NVidia bug, since it only is a problem with the RT SMP, so
> I should say incompatibility w.r.t. RT SMP and NVidia.
>
> If you are one of those that don't want anything to do with the NVidia
> driver, and don't care less if it works or not, let me know that too.
> That way I won't bother you with this anymore and will only communicate
> with Valdis :-)
>
> Thanks,
>
> -- Steve
Nope, I've experianced the same problem without SMP. It also appears
to be a bug where if make menuconfig is not run after using an old
kernel, for some odd reason CONFIG_SPINLOCK_BKL is set to be on.
Anyways, I just wanted to reassure you, this is NOT an SMP bug.
next prev parent reply other threads:[~2004-12-20 2:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 16:26 2.6.10-rc3-mm1-V0.7.33-03 and NVidia wierdness, with workaround Valdis.Kletnieks
2004-12-17 16:19 ` Steven Rostedt
2004-12-17 17:03 ` Steven Rostedt
2004-12-17 18:10 ` Valdis.Kletnieks
2004-12-17 20:04 ` Steven Rostedt
2004-12-17 21:49 ` Valdis.Kletnieks
2004-12-17 21:55 ` Steven Rostedt
2004-12-17 21:52 ` Steven Rostedt
2004-12-17 22:42 ` Valdis.Kletnieks
2004-12-19 16:20 ` Steven Rostedt
2004-12-20 2:46 ` Joe [this message]
2004-12-20 4:22 ` Steven Rostedt
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=d4757e60041219184662648df@mail.gmail.com \
--to=joecool1029@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox