public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Andi Kleen <ak@suse.de>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Intel x86-64 support patch breaks amd64
Date: Thu, 19 Feb 2004 13:14:25 -0800	[thread overview]
Message-ID: <20040219211425.GA8282@atomide.com> (raw)
In-Reply-To: <20040220202914.40ef613b.ak@suse.de>

* Andi Kleen <ak@suse.de> [040219 13:02]:
> On Thu, 19 Feb 2004 12:45:19 -0800
> "Siddha, Suresh B" <suresh.b.siddha@intel.com> wrote:
> >
> > Andi, Appended patch should fix the problem reported by Tony.
> 
> Which change exactly is supposed to fix it? And why? 
> 
> For me the UP kernel boots just fine.

Thanks Suresh, that did it. I bet it's the GDT_ENTRIES change in segment.h
that was the real cause of my system not booting.

That's what I meant with having all parts of the original cset undone,
except for the *.h file changes. Even with only the *.h parts of the cset
included in my tree would cause the system _not_ boot.

Let me know if you need more patches tested, gotta do some work now that the
system runs again :)

Anybody got any information why the ioapic interrupt programming fails on VIA
based K8 boards, BTW?

Regards,

Tony

  reply	other threads:[~2004-02-19 21:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 20:45 Intel x86-64 support patch breaks amd64 Siddha, Suresh B
2004-02-20 19:29 ` Andi Kleen
2004-02-19 21:14   ` Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-19 21:14 Siddha, Suresh B
2004-02-20 20:12 ` Andi Kleen
2004-02-19 18:34 Tony Lindgren
2004-02-20 16:13 ` Andi Kleen
2004-02-19 19:36   ` Jakub Jelinek
2004-02-20 16:44     ` Andi Kleen
2004-02-19 21:20       ` Philippe Elie
2004-02-19 20:39   ` Tony Lindgren
2004-02-20 19:02     ` 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=20040219211425.GA8282@atomide.com \
    --to=tony@atomide.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.com \
    /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