From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>, Oliver.Schersand@BASF-IT-Services.com
Cc: Alessandro Suardi <alessandro.suardi@oracle.com>,
use-oracle@suse.com, suse-linux-e@suse.com,
linux-kernel@vger.kernel.org
Subject: Re: Antwort: Re: Kernel Hangs 2.4.16 on heay io Oracle and Tivolie TSM
Date: Tue, 05 Mar 2002 12:06:43 -0500 [thread overview]
Message-ID: <322850000.1015348003@tiny> (raw)
In-Reply-To: <3C838DA7.4050807@namesys.com>
In-Reply-To: <OFE7517866.AA039B23-ONC1256B72.0027B52F@bcs.de> <3C838DA7.4050807@namesys.com>
On Monday, March 04, 2002 06:07:19 PM +0300 Hans Reiser <reiser@namesys.com> wrote:
> Wasn't 2.4.16 the known unstable vm release of 2.4? Why do you go to
> such effort to stick with a bad kernel? Go to 2.4.18.
I'm not sure exactly which vm problems you mean, but He's running the
suse 2.4.16, which is heavily patched. When your running big production
databases, upgrading to the kernel of the week isn't an option.
I think we've found the bug, it looks like a race in the proc code.
Oliver, someone will contact you a little later with instructions on
getting a kernel with the fix. If you only see this oops during backups,
make sure you aren't trying to backup /proc.
-chris
next prev parent reply other threads:[~2002-03-05 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 7:35 Antwort: Re: Kernel Hangs 2.4.16 on heay io Oracle and Tivolie TSM Oliver.Schersand
2002-03-04 15:07 ` Hans Reiser
2002-03-05 17:06 ` Chris Mason [this message]
2002-03-07 7:14 ` Petro
2002-03-07 7:13 ` Petro
-- strict thread matches above, loose matches on Subject: below --
2002-03-08 23:07 James Washer
2002-03-11 8:16 Oliver.Schersand
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=322850000.1015348003@tiny \
--to=mason@suse.com \
--cc=Oliver.Schersand@BASF-IT-Services.com \
--cc=alessandro.suardi@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=suse-linux-e@suse.com \
--cc=use-oracle@suse.com \
/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