From: Roland Dreier <rdreier@cisco.com>
To: "Dan Upton" <upton.dan.linux@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: debugging an oops that kills the system
Date: Tue, 21 Oct 2008 11:39:27 -0700 [thread overview]
Message-ID: <adar669okrk.fsf@cisco.com> (raw)
In-Reply-To: <ba7d8f720810211014g472c3e83oba511c24e1c2eb97@mail.gmail.com> (Dan Upton's message of "Tue, 21 Oct 2008 13:14:02 -0400")
> I'm hoping for some pointers on debugging an oops that ultimately
> hangs the system. I'm doing some scheduler work and I can fairly
> reliably duplicate the error on my machine, but the output is too
> large for one screen and the system becomes unresponsive after the
> crash so I can't scroll the console. I tried purchasing a USB->DB9
> cable to log to a remote terminal, but so far I haven't had any luck
> getting that to work. Using kdump/kexec doesn't work either--I got
> the second kernel to boot successfully using the magic sysrq example
> in the documentation, but the second kernel doesn't boot with my
> actual crash. Any other suggestions for what I might do?
If you have two machines (it sounds like you do) and serial console is
not working for you (could be a setup problem -- do you have a
"console=" line on your kernel command line?), then netconsole might be
a good way to debug: Documentation/networking/netconsole.txt
- R.
next prev parent reply other threads:[~2008-10-21 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 17:14 debugging an oops that kills the system Dan Upton
2008-10-21 18:39 ` Roland Dreier [this message]
2008-10-21 19:44 ` Dan Upton
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=adar669okrk.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=upton.dan.linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox