From: Eric Valette <eric.valette@free.fr>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.2.19 kernel panic does not enter KDB
Date: Sun, 10 Jun 2012 13:38:44 +0200 [thread overview]
Message-ID: <4FD48744.3000602@free.fr> (raw)
In-Reply-To: <20120610123420.52af4e1a@pyramind.ukuu.org.uk>
On 10/06/2012 13:34, Alan Cox wrote:
>
> I think you are on the wrong list. Nvidia have kernel source code, we
> don't have code to their proprietary stuff. Only they can help you.
>
> It's quite possible the box is hanging so hard that kdb can't help you.
> In that case you'll again need someone with their proprietary Nvidia
> source to help you.
Maybe you are still annoyed by the picture linus has posted but that
type of answer helps nothing. I know nobody there is going to debug
nvidia driver but I'm not even sure its not something else. Neither are you.
So the bug is still that KDB is not entered.
--eric
next prev parent reply other threads:[~2012-06-10 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 11:22 Linux 3.2.19 kernel panic does not enter KDB Eric Valette
2012-06-10 11:34 ` Alan Cox
2012-06-10 11:38 ` Eric Valette [this message]
2012-06-10 12:37 ` richard -rw- weinberger
2012-06-10 14:15 ` Eric Valette
2012-06-11 10:54 ` Alan Cox
2012-06-11 11:11 ` Eric Valette
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=4FD48744.3000602@free.fr \
--to=eric.valette@free.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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