From: Sean Russell <ser@ser1.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org, nipsy@bitgnome.net
Subject: Re: 2.6.1[01] freeze on x86_64
Date: Tue, 22 Mar 2005 03:15:12 -0500 [thread overview]
Message-ID: <423FD410.2050607@ser1.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0503221317220.10134@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>>Er... by serial console, I assume you mean via a serial cable and some other
>>device. If so, then no, I don't have that capability. I didn't know about
>>netconsole before you mentioned it; I'll do some research and set it up. I do
>>
>>
>Serial console -- only requires a serial cable, available in the next computer
>store -- also works with non-Linux, non-x86 and (mostly) systems-w/o-compiler.
>
>
Well, that and the knowledge of how to monitor it on the other end,
which I lack :-). And does one need a null-modem cable? I haven't used
serial cables since USB was introduced. Is serial monitoring preferred
over netconsole?
In any case, I've figured out how to get netconsole working, and have
started monitoring it from my wife's laptop. I just need to reboot and
make sure it is working (that I got the UDP addresses right), and then
wait for a crash. I won't get to this until this evening, probably.
Mark, I'm going to start CC'ing you, and I'll forward you the previous
emails.
Thanks, everybody, for responding.
--- SER
next prev parent reply other threads:[~2005-03-22 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 22:57 2.6.1[01] freeze on x86_64 Sean Russell
2005-03-22 9:02 ` Andi Kleen
2005-03-22 7:02 ` Sean Russell
2005-03-22 12:20 ` Jan Engelhardt
2005-03-22 8:15 ` Sean Russell [this message]
2005-03-22 13:11 ` Mark Nipper
2005-05-17 11:37 ` Sean E. Russell
2005-05-17 11:55 ` Andi Kleen
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=423FD410.2050607@ser1.net \
--to=ser@ser1.net \
--cc=ak@muc.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nipsy@bitgnome.net \
/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