From: Dave Jones <davej@suse.de>
To: "Peter Wächtler" <pwaechtler@loewe-komp.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oopses in scheduler on Linux-2.4.17-xfs
Date: Wed, 16 Jan 2002 00:54:50 +0100 [thread overview]
Message-ID: <20020116005450.K32088@suse.de> (raw)
In-Reply-To: <3C44B260.D1FA47BF@loewe-komp.de>
In-Reply-To: <3C44B260.D1FA47BF@loewe-komp.de>; from pwaechtler@loewe-komp.de on Tue, Jan 15, 2002 at 11:51:12PM +0100
On Tue, Jan 15, 2002 at 11:51:12PM +0100, Peter Wächtler wrote:
>
> I recently get oopses on 2.4.14-xfs and 2.4.17-xfs.
> box is SMP with old Pentium Pro
> There were some changes with erratas of the Pro ans something
> with "cacheline alignment" and a fence.
In 2.4.14, the errata workaround wasn't even activated.
The cacheline alignment should cause anything like this either.
Can you repeat without xfs, kdb and whatever else you have
compiled in ?
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-01-15 23:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 22:51 Oopses in scheduler on Linux-2.4.17-xfs Peter Wächtler
2002-01-15 23:54 ` Dave Jones [this message]
2002-01-16 1:28 ` Alan Cox
2002-02-26 14:43 ` Peter Wächtler
[not found] ` <3C44B40E.FEDE24C8@zip.com.au>
2002-01-16 22:50 ` Peter Wächtler
2002-01-17 16:09 ` Peter Wächtler
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=20020116005450.K32088@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pwaechtler@loewe-komp.de \
/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