From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Galbraith Subject: Re: linux rt 3.4.8-rt16 and nv 302.17, and system freezes, does nvidia strike again? Date: Fri, 24 Aug 2012 08:26:33 +0200 Message-ID: <1345789593.4331.42.camel@marge.simpson.net> References: <1345264436.8439.15.camel@marge.simpson.net> <20120818070110.GA26476@dlc-dt.home> <20120818110637.GA30911@dlc-dt.home> <20120823225044.GA14991@dlc-dt.home> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Javier Sanz , RT To: "David L. Craig" Return-path: Received: from mailout-de.gmx.net ([213.165.64.22]:36491 "HELO mailout-de.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751647Ab2HXG0h (ORCPT ); Fri, 24 Aug 2012 02:26:37 -0400 In-Reply-To: <20120823225044.GA14991@dlc-dt.home> Sender: linux-rt-users-owner@vger.kernel.org List-ID: On Thu, 2012-08-23 at 18:50 -0400, David L. Craig wrote: > I have asked for suggestions > on this list and in the Debian bug report about > next steps but thus far have received no responses. Once you report a black box (proprietary) driver problem to black box manufacturer, your next and only step is to wait for same to produce a new black box. Nobody else can fix the problem, even if the source of that problem lies in the well illuminated kernel. It's dark inside the black box, and only it's manufacturer can flip the light switch. -Mike