From: Con Kolivas <kernel@kolivas.org>
To: "Zorglub Olsen" <zorglub_olsen@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops on 2.6.14
Date: Mon, 21 Nov 2005 12:43:36 +1100 [thread overview]
Message-ID: <200511211243.36810.kernel@kolivas.org> (raw)
In-Reply-To: <BAY109-F294DF1CED8A03C75F7DBC190530@phx.gbl>
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
prev parent reply other threads:[~2005-11-21 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 22:26 Oops on 2.6.14 Zorglub
2005-11-21 1:13 ` Con Kolivas
2005-11-21 1:41 ` Zorglub Olsen
2005-11-21 1:43 ` Con Kolivas [this message]
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=200511211243.36810.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zorglub_olsen@hotmail.com \
/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