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: Mon, 11 Jun 2012 13:11:36 +0200 [thread overview]
Message-ID: <4FD5D268.6040503@Free.fr> (raw)
In-Reply-To: <20120611115414.06759ae3@pyramind.ukuu.org.uk>
On 06/11/2012 12:54 PM, Alan Cox wrote:
> kdb not getting entered is not itself a bug - its a limitation.
Ok. I'm still wondering if KDB is not broken on 3.2.19. If on a working
system I do
echo g > /proc/sysrq-trigger
even from a tty all I see is the help and I'm back to the login shell.
Actions like
echo t > /proc/sysrq-trigger
are logged but I cannot really enter the debugger...
-- eric
prev parent reply other threads:[~2012-06-11 11:18 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
2012-06-11 10:54 ` Alan Cox
2012-06-11 11:11 ` Eric Valette [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=4FD5D268.6040503@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