kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin-Éric Racine" <q-funk-X3B1VOXEql0@public.gmane.org>
To: Arnd Hannemann
	<hannemann-JasiFyN5vQG662+jY7v6MhvVK+yQ3ZXh@public.gmane.org>
Cc: "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Kernel Testers List
	<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: x86 Geode issues in kernel >= 2.6.23 and >= 2.6.31-rc4
Date: Tue, 18 Aug 2009 21:47:28 +0300	[thread overview]
Message-ID: <11fae7c70908181147k4384478crc9909ec8256db868@mail.gmail.com> (raw)
In-Reply-To: <4A76E6AA.2040608-JasiFyN5vQG662+jY7v6MhvVK+yQ3ZXh@public.gmane.org>

On Mon, Aug 3, 2009 at 4:31 PM, Arnd
Hannemann<hannemann-JasiFyN5vQG662+jY7v6MhvVK+yQ3ZXh@public.gmane.org> wrote:
> Martin-Éric Racine wrote:
>> On Mon, Aug 3, 2009 at 4:19 PM, Arnd
>> Hannemann<hannemann-JasiFyN5vQG662+jY7v6MhvVK+yQ3ZXh@public.gmane.org> wrote:
>>> 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.
>>
>> Thank you for your answer, Arnd.
>>
>> Could you please send me a copy of your .config so that I can compare
>> it with the one used on Ubuntu kernels?
>
> Sure. Config for 2.6.31-rc5 is attached.

Could you try enabling CONFIG_FS_POSIX_ACL in your config and building
a new kernel? Does it still boot?

Martin-Éric

       reply	other threads:[~2009-08-18 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11fae7c70908030558r28773beatd1dca702d490a57d@mail.gmail.com>
     [not found] ` <4A76E3E8.30902@nets.rwth-aachen.de>
     [not found]   ` <11fae7c70908030624q11ffd29ened3c77ec4c4ca79a@mail.gmail.com>
     [not found]     ` <4A76E6AA.2040608@nets.rwth-aachen.de>
     [not found]       ` <4A76E6AA.2040608-JasiFyN5vQG662+jY7v6MhvVK+yQ3ZXh@public.gmane.org>
2009-08-18 18:47         ` Martin-Éric Racine [this message]
     [not found]           ` <11fae7c70908181147k4384478crc9909ec8256db868-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-19  7:49             ` x86 Geode issues in kernel >= 2.6.23 and >= 2.6.31-rc4 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=11fae7c70908181147k4384478crc9909ec8256db868@mail.gmail.com \
    --to=q-funk-x3b1voxeql0@public.gmane.org \
    --cc=hannemann-JasiFyN5vQG662+jY7v6MhvVK+yQ3ZXh@public.gmane.org \
    --cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).