Re: 2.6.18-git7 freezes solid on boot

[Andrew Morton <akpm@osdl.org>]

On Wed, 27 Sep 2006 12:31:52 +0000
"Alessandro Suardi" <alessandro.suardi@gmail.com> wrote:

> Dell D610 running FC5, works fine with -git5, locks up
>  in less than a second after selecting the GRUB entry
>  for -git7, with NumLock on and nothing else working,
>  SysRq included, except for the power switch (no need
>  to keep it down for 10 secs though - it powers off
>  right away).
> 
> Since bzdiffing patch-2.6.18-git5 and -git7 shows there
>  are framebuffer changes, I'm wondering whether anyone
>  had already stumbled into similar issues.
> 
> Video card is an Intel i915GM.
> 

You probably want this..

From: Andi Kleen <ak@suse.de>

i386: Use early clobbers for semaphores now

The new code does clobber the result early, so make sure to tell
gcc to not put it into the same register as a input argument

Signed-off-by: Andi Kleen <ak@suse.de>

Index: linux/include/asm-i386/semaphore.h
===================================================================
--- linux.orig/include/asm-i386/semaphore.h
+++ linux/include/asm-i386/semaphore.h
@@ -126,7 +126,7 @@ static inline int down_interruptible(str
 		"lea %1,%%eax\n\t"
 		"call __down_failed_interruptible\n"
 		"2:"
-		:"=a" (result), "+m" (sem->count)
+		:"=&a" (result), "+m" (sem->count)
 		:
 		:"memory");
 	return result;
@@ -148,7 +148,7 @@ static inline int down_trylock(struct se
 		"lea %1,%%eax\n\t"
 		"call __down_failed_trylock\n\t"
 		"2:\n"
-		:"=a" (result), "+m" (sem->count)
+		:"=&a" (result), "+m" (sem->count)
 		:
 		:"memory");
 	return result;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/