From: Andrew Morton <akpm@osdl.org>
To: kmannth@us.ibm.com
Cc: lkml <linux-kernel@vger.kernel.org>, Andi Kleen <ak@suse.de>,
efalk@google.com
Subject: Re: [BUG] 2.6.18-rc4-mm3 x86_64-mm-spin-irqs-enabled causes problems
Date: Tue, 29 Aug 2006 17:14:53 -0700 [thread overview]
Message-ID: <20060829171453.3921337e.akpm@osdl.org> (raw)
In-Reply-To: <1156895977.5654.17.camel@keithlap>
On Tue, 29 Aug 2006 16:59:36 -0700
keith mannthey <kmannth@us.ibm.com> wrote:
> I moved to mm2 to mm3 and had trouble booting again with my hardware.
> In -mm3 the kernel boots but about the time init starts the whole box
> just stops doing anything. Sysrq works and I dumped the tasks but
> nothing look too far out of place.
>
> I did a bisection of -mm3 and found x86_64-mm-spin-irqs-enabled.patch to
> be the cause.
Yes, Hugh was hitting that today and the following has emerged...
From: Andrew Morton <akpm@osdl.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
---
include/asm-x86_64/spinlock.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -puN include/asm-x86_64/spinlock.h~x86_64-mm-spin-irqs-enabled-fix include/asm-x86_64/spinlock.h
--- a/include/asm-x86_64/spinlock.h~x86_64-mm-spin-irqs-enabled-fix
+++ a/include/asm-x86_64/spinlock.h
@@ -51,7 +51,7 @@ static inline void __raw_spin_lock_flags
{
asm volatile(
"\n1:\t"
- LOCK_PREFIX "; decb %0\n\t"
+ LOCK_PREFIX "; decl %0\n\t"
"js 2f\n\t"
LOCK_SECTION_START("")
"2:\t"
@@ -60,7 +60,7 @@ static inline void __raw_spin_lock_flags
"sti\n\t"
"3:\t"
"rep;nop\n\t"
- "cmpb $0, %0\n\t"
+ "cmpl $0, %0\n\t"
"jle 3b\n\t"
"cli\n\t"
"jmp 1b\n"
_
next parent reply other threads:[~2006-08-30 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1156895977.5654.17.camel@keithlap>
2006-08-30 0:14 ` Andrew Morton [this message]
2006-08-30 7:28 ` Andi Kleen
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=20060829171453.3921337e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=efalk@google.com \
--cc=kmannth@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®