From: "David L. Craig" <dlc.usa@gmail.com>
To: Javier Sanz <jsanza@gmail.com>
Cc: "David L. Craig" <dlc@radix.net>, Mike Galbraith <efault@gmx.de>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: linux rt 3.4.8-rt16 and nv 302.17, and system freezes, does nvidia strike again?
Date: Thu, 23 Aug 2012 18:50:44 -0400 [thread overview]
Message-ID: <20120823225044.GA14991@dlc-dt.home> (raw)
In-Reply-To: <CAOLSsAx3z9CY1Y8H6TqfFMJ49OS0E2XrE6LXKp5MZn-JF-86uw@mail.gmail.com>
On 12Aug23:1047+0200, Javier Sanz wrote:
>
> You say that there is a message,
> [6.993495] Disabling lock debugging due to kernel taint
>
> how do you get it ?
This and other pertinent messages are logged (under
Debian) in /var/log/kern.log and are crucial for
understanding what is going on. Compare yours to the
one I attached to the Debian bug report.
> have you sent this information any nvidia forums?
> no answer? how can we fix it ?
>
> Yesterday, testing with kernel 3.4.9-rt17 with nvidia
> 304.37 drivers ... nvidia gt 240 ... all blocked ..
> i am at same point ...
>
> So, what is the next step? mails? forums?
>
> What do you suggest?
The nvidia driver, not being libre source, "taints"
the kernel environment, and policy mandates disabling
spin lock debugging logic as a consequence. Some
interaction between nvidia and the rt kernel is the
most likely cause of the blocking encountered since
it doesn't manifest with comparable non-rt kernels.
Also, the problem has been introduced since the code
levels in the Linux Mint environment I documented in
the Debian bug report. This is an area programmed
and debugged by well-studied kernel developers.
Mere mortals are not equipped to tackle such matters.
I have already done what I suggested in my previous
messages. If an rt and/or nvidia developer does
not take an interest in this behaviour, it must be
hoped the misbehavior induces other problems they are
motivated to investigate. I have asked for suggestions
on this list and in the Debian bug report about
next steps but thus far have received no responses.
While I do think I could learn enough to expertly
dig into this in a couple man-months, I do not think
I will be compelled to actually make it a priority
unless my circumstances significantly change; e.g.,
somebody offers me some financial incentive to do so.
I'll ask this list again: should this become an rt
kernel or nvidia bug report somewhere or should I
just let it percolate up from Debian?
In the meantime I don't use nvidia with the rt kernel
except with my Linux Mint partition, and that only to
run FlightGear (not very often anymore).
--
May the LORD God bless you exceedingly abundantly!
Dave_Craig______________________________________________
"So the universe is not quite as you thought it was.
You'd better rearrange your beliefs, then.
Because you certainly can't rearrange the universe."
__--from_Nightfall_by_Asimov/Silverberg_________________
next prev parent reply other threads:[~2012-08-23 22:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 20:40 linux rt 3.4.8-rt16 and nv 302.17, and system freezes, does nvidia strike again? Javier Sanz
2012-08-18 4:33 ` Mike Galbraith
2012-08-18 7:01 ` David L. Craig
2012-08-18 9:52 ` Javier Sanz
2012-08-18 11:06 ` David L. Craig
2012-08-23 8:47 ` Javier Sanz
2012-08-23 9:26 ` Sven-Thorsten Dietrich
2012-08-23 9:38 ` Javier Sanz
2012-08-23 22:50 ` David L. Craig [this message]
2012-08-24 0:32 ` David L. Craig
2012-08-24 1:33 ` David L. Craig
2012-08-24 6:26 ` Mike Galbraith
2012-08-24 11:48 ` David L. Craig
2012-08-24 12:01 ` David L. Craig
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=20120823225044.GA14991@dlc-dt.home \
--to=dlc.usa@gmail.com \
--cc=dlc@radix.net \
--cc=efault@gmx.de \
--cc=jsanza@gmail.com \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).