From: benh@kernel.crashing.org
To: Stefan Jeglinski <jeglin@4pi.com>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: xmon feature? (was Re: crash on sleep with 2.4.19-pre4-ben0)
Date: Thu, 28 Mar 2002 18:19:53 +0100 [thread overview]
Message-ID: <20020328171953.1200@mailhost.mipsys.com> (raw)
In-Reply-To: <p0510030ab8c8fb48c50c@[63.220.231.138]>
>I tried this once but never got it to work. No doubt because I don't
>know much about what I'm doing in kernel programming yet.
>
>I'd like to suggest this feature: that by default xmon prints a
>backtrace when it is invoked. A user can then ask it for any more
>info they want (including the backtrace again).
>
>This would largely alleviate the general problem of losing keyboard
>control and having to powercycle without getting much info out.
>
>Is there a reason to object to this idea? xmon maintainers won't go
>for it? Automatic backtraces might be too large? Other reasons I
>might never imagine on my own? The kernel automatically does it on a
>boot panic, I know that much.
I think it didn't work because for some reason, the backtrace
didn't work at this point (that is it wouldn't have worked from
xmon prompt neither). THat can happen in some situations.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-28 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 8:44 crash on sleep with 2.4.19-pre4-ben0 Michel Lanners
2002-03-28 12:24 ` benh
2002-03-28 13:37 ` Michel Lanners
2002-03-28 14:14 ` benh
2002-03-28 17:02 ` xmon feature? (was Re: crash on sleep with 2.4.19-pre4-ben0) Stefan Jeglinski
2002-03-28 17:19 ` benh [this message]
2002-03-30 16:25 ` crash on sleep with 2.4.19-pre4-ben0 Michel Lanners
2002-03-29 4:57 ` Benjamin Herrenschmidt
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=20020328171953.1200@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=jeglin@4pi.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).