All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: i386 doublefault handler is broken with CONFIG_DEBUG_SPINLOCK
Date: Fri, 10 Aug 2007 01:16:18 +0200	[thread overview]
Message-ID: <20070809231618.GC1845@one.firstfloor.org> (raw)
In-Reply-To: <46BB5F9B.6050808@redhat.com>

On Thu, Aug 09, 2007 at 02:40:27PM -0400, Chuck Ebbert wrote:
> On 08/09/2007 01:49 PM, Andi Kleen wrote:
> > Chuck Ebbert <cebbert@redhat.com> writes:
> >> Initializing FS in the doublefault_tss should fix it.
> >>
> >> Signed-off-by: Chuck Ebbert <cebbert@redhat.com>
> >>
> >> ---
> >>
> >>  NOTE: not even compile tested.
> > 
> > Can you please test it?
> > 
> 
> It compiles but I can't really test it further right now.

I tested it. Even on a box without spin lock debugging I get a hard
hang after

double fault, gdt at c1404000 [255 bytes]

even though it should have printed the registers.
So it looks like there is more broken in the DF handler than just
this.

-Andi

  parent reply	other threads:[~2007-08-09 23:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 16:49 i386 doublefault handler is broken with CONFIG_DEBUG_SPINLOCK Chuck Ebbert
2007-08-09 17:49 ` Andi Kleen
2007-08-09 18:40   ` Chuck Ebbert
2007-08-09 19:00     ` Jeremy Fitzhardinge
2007-08-09 23:16     ` Andi Kleen [this message]
2007-08-09 23:35       ` Chuck Ebbert
2007-08-10  8:23         ` Andi Kleen
2007-08-10 19:11           ` Chuck Ebbert

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=20070809231618.GC1845@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=cebbert@redhat.com \
    --cc=jeremy@goop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.