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
Subject: Re: [pre-2.6.23 REGRESSION] 2.6.23-rc3-git1 crash/stuck on VIA CN700 system
Date: Wed, 5 Sep 2007 18:37:24 +0200 [thread overview]
Message-ID: <20070905163724.GC31880@one.firstfloor.org> (raw)
In-Reply-To: <46DECDC9.9050407@nokia.com>
> flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge cmov pat
> clflush acpi mmx fxsr sse sse2 tm up pni est tm2 rng rng_en ace ace_en
Hmm, I can't really see anything wrong. This means the original
version of the patch you found had a few problems, but they
were all fixed later and only applied with CONFIG_PARAVIRT enabled anyways.
As a stab in the dark since the CPU has clflush can you please
comment out the
if (cpu_has_clflush)
asm("clflush (%0) " :: "r" (addr) : "memory");
statement in arch/i386/kernel/alternative.c and see if it makes a difference?
Perhaps your CPU doesn't like that (it seems to have clflush)
If that doesn't help it might be needed to revert the patch
hunk by hunk to see which text_poke() invocation caused it.
-Andi
next prev parent reply other threads:[~2007-09-05 16: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 [this message]
2007-09-05 19:24 ` Stefan Becker
2007-09-06 5:36 ` Andi Kleen
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=20070905163724.GC31880@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=Stefan.Becker@nokia.com \
--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