From: Andi Kleen <andi@firstfloor.org>
To: Stefan Becker <Stefan.Becker@nokia.com>
Cc: ext Andi Kleen <andi@firstfloor.org>,
ext Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org, davej@codemonkey.org.uk
Subject: Re: [pre-2.6.23 REGRESSION] 2.6.23-rc3-git1 crash/stuck on VIA CN700 system
Date: Thu, 6 Sep 2007 07:36:54 +0200 [thread overview]
Message-ID: <20070906053654.GD31880@one.firstfloor.org> (raw)
In-Reply-To: <46DF0257.5050303@nokia.com>
> This kernel boots up OK. Looking at the preprocessed C code the
I assume you tested it a few times to make sure it really was the
problem? Perhaps reenable it also once again and see if it hangs
again just to be sure.
> So what can we do about the clflush on this CPU?
I'll just remove that CLFLUSH statement. It was just supposed
to be an optimization, but is not strictly needed.
The only thing that worries me is that CLFLUSH might be broken
in more ways on those VIA CPUs and we also use it in other places.
Of course it would be possible to remove it from the kernel capabilities
but we can't really stop user space using it. We don't know how many
VIA CPU models are affected by this problem. Dave, didn't you have Centaur
contacts that could be asked? It seems like CLFLUSH causes kernel
hangs
-Andi
next prev parent reply other threads:[~2007-09-06 5:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 17:37 [pre-2.6.23 REGRESSION] 2.6.23-rc3-git1 crash/stuck on VIA CN700 system Stefan Becker
2007-08-28 5:15 ` Stefan Becker
2007-09-03 5:59 ` Stefan Becker
2007-09-03 16:57 ` Randy Dunlap
2007-09-03 23:02 ` Andi Kleen
2007-09-04 18:26 ` Stefan Becker
2007-09-05 10:25 ` Andi Kleen
2007-09-05 15:39 ` Stefan Becker
2007-09-05 16:37 ` Andi Kleen
2007-09-05 19:24 ` Stefan Becker
2007-09-06 5:36 ` Andi Kleen [this message]
2007-09-06 14:19 ` Stefan Becker
2007-09-12 16:59 ` Stefan Becker
2007-09-06 10:41 ` Dave Jones
2007-09-06 10:44 ` Stefan Becker
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=20070906053654.GD31880@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=Stefan.Becker@nokia.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.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