From: Eric Valette <eric.valette@free.fr>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
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 16:15:24 +0200 [thread overview]
Message-ID: <4FD4ABFC.1060008@free.fr> (raw)
In-Reply-To: <CAFLxGvwtCDCdWoXCBr2nytm93Kyei-pLoioGGxhu_+TMFfdNzQ@mail.gmail.com>
On 10/06/2012 14:37, richard -rw- weinberger wrote:
>> So the bug is still that KDB is not entered.
>
> The problem with proprietary code is that *anything* can happen.
> If the crash happened within the Nvidia binary blob you are toasted...
>
Yes. I just want to be sure it is the case. Even if display it dead, I
expect that keyboard may help to reboot, sync disk but unless I dot not
hit the correct key sequence it doesn't.
--eric
next prev parent reply other threads:[~2012-06-10 14:15 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
2012-06-10 12:37 ` richard -rw- weinberger
2012-06-10 14:15 ` Eric Valette [this message]
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=4FD4ABFC.1060008@free.fr \
--to=eric.valette@free.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.