Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932166AbVKUBnn (ORCPT ); Sun, 20 Nov 2005 20:43:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932168AbVKUBnm (ORCPT ); Sun, 20 Nov 2005 20:43:42 -0500 Received: from mail01.syd.optusnet.com.au ([211.29.132.182]:23961 "EHLO mail01.syd.optusnet.com.au") by vger.kernel.org with ESMTP id S932166AbVKUBnm (ORCPT ); Sun, 20 Nov 2005 20:43:42 -0500 From: Con Kolivas To: "Zorglub Olsen" Subject: Re: Oops on 2.6.14 Date: Mon, 21 Nov 2005 12:43:36 +1100 User-Agent: KMail/1.8.3 Cc: linux-kernel@vger.kernel.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511211243.36810.kernel@kolivas.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 864 Lines: 22 On Mon, 21 Nov 2005 12:41, Zorglub Olsen wrote: > Hi, > > Con Kolivas wrote: > >Unfortunately we can only provide support for code we wrote and have > > access to. The nvidia and other proprietary binary only drivers cause > > bugs that we are unable to debug. Please try to reproduce the problem > > without any binary only drivers. > > Thank you for your answer. I understand about the binary, I just wasn't > able to see that it was the sole cause of the oops. That's an understandable misconception. Drivers can cause corruption anywhere, even if the stack trace does not look related to the driver. Regards, Con - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/