public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
To: q-funk@iki.fi
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86 Geode issues in kernel >= 2.6.23 and >= 2.6.31-rc4
Date: Mon, 03 Aug 2009 15:19:36 +0200	[thread overview]
Message-ID: <4A76E3E8.30902@nets.rwth-aachen.de> (raw)
In-Reply-To: <11fae7c70908030558r28773beatd1dca702d490a57d@mail.gmail.com>

Martin-Éric Racine wrote:
> (non-subscriber post; please keep me in CC)
> 
> Greetings,
> 
> Having previously reported two issues via Ubuntu's bug tracker and not
> found any answer, I thought I'd approach the LKML with the issues at
> stake.
> 
> 1) Since kernel 2.6.23, one cannot boot hardware based on the Geode
> SCx200 series. Partial answers about the most plausible cause have
> been found by the target hardware's manufacturer as explained at
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/241307
> 
> 2) Since kernel 2.6.31-rc4, one cannot boot hardware based on the
> Geode LX800 as described at
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/396286
> 
> In case either of these issues was already reported and there is a
> know fix or work-around, I'd love to hear more. Otherwise, please feel
> free to contact me for additional details.
> 

Just to give a data point:
2.6.31-rc1,2,3,4,5 were/are running all fine on my Geode LX800
(http://www.pcengines.ch/alix2d2.htm) so it seems something
board or .config specific.

Best regards,
Arnd


  reply	other threads:[~2009-08-03 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 12:58 x86 Geode issues in kernel >= 2.6.23 and >= 2.6.31-rc4 Martin-Éric Racine
2009-08-03 13:19 ` Arnd Hannemann [this message]
2009-08-03 13:24   ` Martin-Éric Racine
2009-08-03 13:31     ` Arnd Hannemann
2009-08-18 18:47       ` Martin-Éric Racine
2009-08-19  7:49         ` Arnd Hannemann

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=4A76E3E8.30902@nets.rwth-aachen.de \
    --to=hannemann@nets.rwth-aachen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=q-funk@iki.fi \
    /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