linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Arnd Hannemann <hannemann@i4.informatik.rwth-aachen.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.24-rc8-git does not boot on Geode LX
Date: Sun, 20 Jan 2008 18:13:10 +0100	[thread overview]
Message-ID: <20080120171309.GA12572@1wt.eu> (raw)
In-Reply-To: <47934FC8.1030800@i4.informatik.rwth-aachen.de>

Hi Arnd,

On Sun, Jan 20, 2008 at 02:42:32PM +0100, Arnd Hannemann wrote:
> > I've just pulled latest -git and tried this morning in on one of my ALIX
> > mobos equipped with an AMD Geode LX800 + CS5536. HEAD is a7da60f41551*.
> 
> We boot 2.6.24-rc8 on these mainboards, which BIOS version do you use?

Just checked: 0.98

> Did you try to boot with nomfgpt?

Just did, it works perfectly that way, thanks very much!

I will try to investigate why this is necessary now. Last 2.6.22.X I used
was patched with a geode-mfgpt patch I found which enabled the watchdog
(and which worked). So I believe that it will not work anymore right now.

> In my experiments disabling CONFIG_GEODE_MFGPT_TIMER won't be enough to
> boot 2.6.24-rc8 on a v0.98 bios or on a v0.99 bios with MFGPT workaround
> turned on in the bios menu.
> Otherwise the system will hang in arch/x86/kernel/mfgpt_32.c while
> trying to detect MFGPT timers.
> To clearify, for us the following works:
> v0.99 bios, MFGPT workaround turned off in bios and
> CONFIG_GEODE_MFGPT_TIMER=n

I will also check BIOS v0.99 sometime later.

Thanks very much for your quick and insightful response!

Willy


  parent reply	other threads:[~2008-01-20 17:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-20  8:14 2.6.24-rc8-git does not boot on Geode LX Willy Tarreau
2008-01-20  9:13 ` Ingo Molnar
2008-01-20  9:25   ` Willy Tarreau
2008-01-20 13:42 ` Arnd Hannemann
2008-01-20 14:37   ` Willy Tarreau
2008-01-20 17:13   ` Willy Tarreau [this message]
2008-01-21 22:25 ` Andres Salomon

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=20080120171309.GA12572@1wt.eu \
    --to=w@1wt.eu \
    --cc=hannemann@i4.informatik.rwth-aachen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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;
as well as URLs for NNTP newsgroup(s).