From: Chris Mason <mason@suse.com>
To: Mircea Damian <dmircea@kappa.ro>, linux-kernel@vger.kernel.org
Subject: Re: Kernel crash - reboot or hang
Date: Thu, 08 Mar 2001 10:36:01 -0500 [thread overview]
Message-ID: <477090000.984065761@tiny> (raw)
In-Reply-To: <20010308161723.A9138@linux.kappa.ro>
On Thursday, March 08, 2001 04:17:23 PM +0200 Mircea Damian
<dmircea@kappa.ro> wrote:
>
> Hello,
>
> I NEED TO TRACE THIS!!!
>
> I had two crashes with 2.4.2 and 2.4.2-pre2 on my local
> SMTP/POP3/SAMBA/WWW server (once under some load and the second one -
> with 2.4.2-pre2 - while it was almost idle).
>
> The machine is an HP Netserver LHII without the standard raid card that
> comes with it (see bellow for dmesg output for a better description of
> hardware).
>
> I do not see any corruption nor any messages in logs.
>
>
> Should I use kdb or just remote logging would do the job?
A serial console is probably your best bet. You if your mail spool is on
reiserfs, you probably want to apply the dir fsync patch (included in
2.4.3pre and the latest ac stuff).
-chris
next prev parent reply other threads:[~2001-03-08 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 14:17 Kernel crash - reboot or hang Mircea Damian
2001-03-08 15:36 ` Chris Mason [this message]
2001-03-09 3:47 ` Keith Owens
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=477090000.984065761@tiny \
--to=mason@suse.com \
--cc=dmircea@kappa.ro \
--cc=linux-kernel@vger.kernel.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