From: "Julian Calaby" <julian.calaby@gmail.com>
To: Stefan Boresch <stefan@mdy.univie.ac.at>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org
Subject: Re: aic79xx problems
Date: Fri, 21 Sep 2007 11:16:52 +1000 [thread overview]
Message-ID: <646765f40709201816v7d60cfbem8d348238db5e6b11@mail.gmail.com> (raw)
In-Reply-To: <20070920145336.GH1606@loop.mdy.univie.ac.at>
On 9/21/07, Stefan Boresch <stefan@mdy.univie.ac.at> wrote:
>
> I will try, but a very dumb question first. If I have a kernel that
> crashes because of a disk problem ..., how do I get to save the output?
> (Never worked with a serial console, but there might be a first time
> for everything ...) But maybe there is an obvious solution that I overlook?
>
> Or should I just try to watch and look for certain messages (ordering of
> messages), which given the huge amount of output seems a bit daunting ...
Ok, in response to your dumb question, an answer from another dumb user: (me)
Firstly, serial consoles aren't that difficult to set up - all you
need is a null modem cable and suitable software on the other end.
Then ensure that it's built in and pass "console=ttyS0" (or
"console=ttyS1" if you're using serial port #2) when you boot.
There is a network console - but I'm not sure whether that is useful
for boot messages.
Hope that helps =)
--
Julian Calaby
Email: julian.calaby@gmail.com
next prev parent reply other threads:[~2007-09-21 1:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 13:04 aic79xx problems Stefan Boresch
2007-09-20 14:01 ` James Bottomley
2007-09-20 14:15 ` James Bottomley
2007-09-20 14:34 ` Stefan Boresch
2007-09-20 14:41 ` James Bottomley
2007-09-20 14:53 ` Stefan Boresch
2007-09-21 1:16 ` Julian Calaby [this message]
2007-09-21 23:01 ` James Bottomley
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=646765f40709201816v7d60cfbem8d348238db5e6b11@mail.gmail.com \
--to=julian.calaby@gmail.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stefan@mdy.univie.ac.at \
/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