public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org
Subject: Re: Regression: boot failure on AMD Elan TS-5500
Date: Tue, 1 Jul 2008 20:20:14 +0000	[thread overview]
Message-ID: <20080701202014.GA77013@atlantis.8hz.com> (raw)
In-Reply-To: <20080701195942.GA76608@atlantis.8hz.com>

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

  reply	other threads:[~2008-07-01 20:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 12:11 Regression: boot failure on AMD Elan TS-5500 Sean Young
2008-06-16 13:27 ` Rusty Russell
2008-06-16 13:37   ` Jeremy Fitzhardinge
2008-06-16 16:19     ` Sean Young
2008-06-16 17:06       ` H. Peter Anvin
2008-06-16 17:58         ` Sean Young
2008-06-16 18:16           ` H. Peter Anvin
2008-06-16 17:06       ` H. Peter Anvin
2008-06-16 17:07       ` Jeremy Fitzhardinge
2008-06-30 21:43       ` Sean Young
2008-06-30 21:52         ` Jeremy Fitzhardinge
2008-06-30 22:04           ` H. Peter Anvin
2008-06-30 22:14             ` H. Peter Anvin
2008-06-30 22:36               ` Jeremy Fitzhardinge
2008-06-30 22:45                 ` H. Peter Anvin
2008-06-30 22:31             ` Sean Young
2008-06-30 22:34             ` Jeremy Fitzhardinge
2008-06-30 22:42               ` H. Peter Anvin
2008-07-01 19:59                 ` Sean Young
2008-07-01 20:20                   ` Sean Young [this message]
2008-07-01 20:24                     ` Jeremy Fitzhardinge
2008-07-01 20:25                     ` H. Peter Anvin
2008-07-15 22:23                     ` Sean Young
2008-07-15 22:30                       ` H. Peter Anvin
2008-07-01 20:22                   ` Jeremy Fitzhardinge
2008-07-01 20:23                   ` H. Peter Anvin
2008-07-01 20:29                     ` Jeremy Fitzhardinge
2008-07-01 20:39                       ` H. Peter Anvin
2008-07-06 13:21                       ` Pavel Machek
2008-06-30 22:09           ` Sean Young
2008-07-06  2:41             ` Eric W. Biederman
2008-07-06  3:07               ` H. Peter Anvin

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=20080701202014.GA77013@atlantis.8hz.com \
    --to=sean@mess.org \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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