From: Axel Siebenwirth <axel@hh59.org>
To: Christoph Hellwig <hch@infradead.org>,
Dave Kleikamp <shaggy@austin.ibm.com>,
JFS-Discussion <jfs-discussion@www-124.southbury.usf.ibm.com>,
linux-kernel@vger.kernel.org
Cc: rml@tech9.net, akpm@zip.com.au
Subject: Re: [OOPS:2.5.33] Re: [Jfs-discussion] crash with JFS assert
Date: Fri, 6 Sep 2002 02:16:02 +0200 [thread overview]
Message-ID: <20020906001602.GA393@prester.freenet.de> (raw)
In-Reply-To: <20020906010641.A24706@infradead.org>
Hi Christoph!
On Fri, 06 Sep 2002, Christoph Hellwig wrote:
> This is 2.5.33 + akpm's patchkit, right? CONFIG_PREEMPT worries me,
> although I wonder whether JFS might be affected by similar problem NFS
> is, although I can't see any relation.
Yes. It's 2.5.33 + 2.5.33-mm2 (by Andrew Morton [is that what you meant?]).
Aaaah! I got it. I just wanted to write an email expressing that for some
strange reason latest 2.4 kernels (2.4.19-ac4, 2.4.20-pre5+latest ACPI)
work without a problem.
You know what the difference to my 2.5 kernels is..... CONFIG_PREEMPT is not
enabled with my 2.4 kernels but with 2.5 it is!
Here we go.
Maybe someone can now get an idea on what the problem is and maybe how to
fix it?!
My best regards,
Axel Siebenwirth
next prev parent reply other threads:[~2002-09-06 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.43.0209051006480.887-100000@leo.uni-sw.gwdg.de>
[not found] ` <3D771308.6030009@hh59.org>
[not found] ` <200209050755.06015.shaggy@austin.ibm.com>
2002-09-06 0:00 ` [OOPS:2.5.33] Re: [Jfs-discussion] crash with JFS assert Axel Siebenwirth
2002-09-06 0:02 ` Axel Siebenwirth
2002-09-06 0:06 ` Christoph Hellwig
2002-09-06 0:16 ` Axel Siebenwirth [this message]
2002-09-06 12:44 ` Dave Kleikamp
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=20020906001602.GA393@prester.freenet.de \
--to=axel@hh59.org \
--cc=akpm@zip.com.au \
--cc=hch@infradead.org \
--cc=jfs-discussion@www-124.southbury.usf.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=shaggy@austin.ibm.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