[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080701202014.GA77013@atlantis.8hz.com>
Date: Tue, 1 Jul 2008 20:20:14 +0000
From: Sean Young <sean@...s.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Jeremy Fitzhardinge <jeremy@...p.org>,
Rusty Russell <rusty@...tcorp.com.au>,
linux-kernel@...r.kernel.org
Subject: Re: Regression: boot failure on AMD Elan TS-5500
On Tue, Jul 01, 2008 at 07:59:42PM +0000, Sean Young wrote:
> On Mon, Jun 30, 2008 at 03:42:47PM -0700, H. Peter Anvin wrote:
> > diff --git a/arch/x86/boot/pmjump.S b/arch/x86/boot/pmjump.S
> > index ab049d4..141b6e2 100644
> > --- a/arch/x86/boot/pmjump.S
> > +++ b/arch/x86/boot/pmjump.S
> > @@ -33,6 +33,8 @@ protected_mode_jump:
> > movw %cs, %bx
> > shll $4, %ebx
> > addl %ebx, 2f
> > + jmp 1f # Short jump to serialize on 386/486
> > +1:
> >
> > movw $__BOOT_DS, %cx
> > movw $__BOOT_TSS, %di
> > @@ -40,8 +42,6 @@ protected_mode_jump:
> > movl %cr0, %edx
> > orb $X86_CR0_PE, %dl # Protected mode
> > movl %edx, %cr0
> > - jmp 1f # Short jump to serialize on 386/486
> > -1:
> >
> > # Transition to 32-bit mode
> > .byte 0x66, 0xea # ljmpl opcode
>
> I'm afraid it doesn't work. Maybe I can find something in the AMD Elan
> documentation. Would a fence make sense?
I was just trying to confirm this with postive and negative tests which
is failing. I'm probably being an idiot, please let systematically test
this.
This does not seem like the heisenbug category, or is it?
Sean
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists