From: Chris Mason <mason@suse.com>
To: Johan Ekenberg <johan@ekenberg.se>, linux-kernel@vger.kernel.org
Subject: Re: Lockups with 2.4.14 and 2.4.16
Date: Tue, 11 Dec 2001 19:47:39 -0500 [thread overview]
Message-ID: <2502410000.1008118058@tiny> (raw)
In-Reply-To: <000901c1829b$b38e1720$050010ac@FUTURE>
In-Reply-To: <000901c1829b$b38e1720$050010ac@FUTURE>
On Wednesday, December 12, 2001 12:29:38 AM +0100 Johan Ekenberg
<johan@ekenberg.se> wrote:
> We recently upgraded 10 servers from 2.2.19 to 2.4.14/2.4.16. Since then,
> several servers have experienced severe lockups forcing hardware resets. The
> machines are Intel PIII (Dual) SMP running Epox motherboards. Here are the
> details:
>
>## Kernel:
> - 2.4.14 and 2.4.16
> - Patched for reiserfs-quota with patches found at
> ftp://ftp.suse.com/pub/people/mason/patches/reiserfs/quota-2.4/
> ( * 50_quota-patch
> * dquota_deadlock
> * nesting
> * reiserfs-quota )
For the 2.4.16 kernel, you used the quota patches from my 2.4.16 dir?
> - Complete kernel-config found here:
> http://www.ekenberg.se/2.4-trouble/2.4.16-config
> - Boot parameters are: "ether=0,0,eth1 panic=60 noapic"
>
>## Filesystems:
> - ReiserFS (3.6) except /boot which is ext2
>
>## General
> - The servers are used mainly for:
> * Apache/PHP with ~1000 VHosts
> * Mail (Sendmail, imap, pop3)
> * MySQL
Anyone know offhand if mysql uses mmap for writing to the database files?
The docs mention it for readonly compressed tables.
The fastest way to rule out filesystem deadlocks is to hook up a serial
console and send me the decoded output of sysrq-t.
-chris
next prev parent reply other threads:[~2001-12-12 0:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 23:29 Lockups with 2.4.14 and 2.4.16 Johan Ekenberg
2001-12-11 23:47 ` Alan Cox
2001-12-11 23:56 ` SV: " Johan Ekenberg
2001-12-12 0:36 ` Alan Cox
2001-12-14 16:49 ` Chris Mason
2001-12-14 17:26 ` Andrew Morton
2001-12-14 17:53 ` Chris Mason
2001-12-14 18:32 ` Andrea Arcangeli
2001-12-14 18:55 ` Chris Mason
2001-12-14 18:57 ` Andrew Morton
2001-12-14 19:16 ` Andrea Arcangeli
2001-12-20 13:29 ` Chris Mason
[not found] ` <1624652704.1008906979@tiny>
[not found] ` <3C22CC54.D4F5B01@zip.com.au>
2001-12-21 13:29 ` [PATCH] " Chris Mason
2001-12-14 19:26 ` Jan Kara
2001-12-14 19:21 ` Jan Kara
2001-12-12 0:56 ` SV: " Johan Ekenberg
2001-12-12 1:22 ` Alan Cox
2001-12-12 0:12 ` Brad Dameron
2001-12-12 0:47 ` Chris Mason [this message]
2001-12-12 1:01 ` SV: " Johan Ekenberg
2001-12-12 1:10 ` Hans Reiser
2001-12-12 1:15 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2001-12-12 0:38 Johan Ekenberg
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=2502410000.1008118058@tiny \
--to=mason@suse.com \
--cc=johan@ekenberg.se \
--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