linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David L. Craig" <dlc.usa@gmail.com>
To: Javier Sanz <jsanza@gmail.com>, "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 20:32:27 -0400	[thread overview]
Message-ID: <20120824003227.GA17167@dlc-dt.home> (raw)
In-Reply-To: <20120823225044.GA14991@dlc-dt.home>

On 12Aug23:1850-0400, David L. Craig wrote:
> 
> 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?

I'm looking at the nvidia forum's guidelines for reporting
bugs and will let you know what I determine to do.
-- 
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_________________

  reply	other threads:[~2012-08-24  0:32 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
2012-08-24  0:32             ` David L. Craig [this message]
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=20120824003227.GA17167@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).