From: Chuck Hemker <n2por@amsat.org>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel@vger.kernel.org, Luc Lalonde <llalonde@giref.ulaval.ca>
Subject: Re: Adaptec SCSI driver lockups
Date: Fri, 13 Jul 2001 04:46:17 -0400 (EDT) [thread overview]
Message-ID: <XFMail.010713044617.n2por@amsat.org> (raw)
In-Reply-To: <200107122226.f6CMQVU64270@aslan.scsiguy.com>
On 12-Jul-01 Justin T. Gibbs wrote:
>>Hello Justin and Alan,
>>
>>There was some garbage printed to the /var/log/messages before the
>>lockup but it is unreadable.
>
> It may have been corrupted by the hang/crash. This is why using
> a serial console is *always* the best bet for tracking down these
> kinds of issues.
>
>>If I use the append="aic7xxx=verbose"
>>in my lilo.conf will it log extra messages in /var/log/messages?
>
> The messages are printed to the console and, if syslogd is running,
> will be recorded in /var/log/messages. However, there is always
> a delay between the error being printed and syslogd getting that
> text to disk. A serial console doesn't have this problem.
>
>>If so,
>>will it be useful enough to figure out what the problem is?
>
> I'll let you know when I see the messages. ;-)
>
> --
> Justin
If the message looks like it's getting as far as the messages file, but getting
corrupt by the lockup, what about configuring syslog to send the messages over
the net to another machine. Maybe it will get the UDP packet out before the
lockup. Also, this could be done without rebooting the machine. Might be
worth a try first.
next prev parent reply other threads:[~2001-07-13 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 21:21 Luc Lalonde
2001-07-12 21:32 ` Justin T. Gibbs
2001-07-12 21:54 ` Luc Lalonde
2001-07-12 22:26 ` Justin T. Gibbs
2001-07-13 8:46 ` Chuck Hemker [this message]
2001-07-12 21:33 ` Alan Cox
2001-07-12 22:06 ` Jussi Laako
2001-07-12 22:10 ` Luc Lalonde
2001-07-13 21:55 ` Stefan Jaschke
2001-07-13 22:39 ` Justin T. Gibbs
2001-07-13 23:30 ` Luc Lalonde
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=XFMail.010713044617.n2por@amsat.org \
--to=n2por@amsat.org \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llalonde@giref.ulaval.ca \
/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
all inboxes | Powered by JetHome®