mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: dwalker@mvista.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: l2.6.14-rc2-rt7 - build problems - mce?
Date: Thu, 29 Sep 2005 19:36:28 -0700	[thread overview]
Message-ID: <5bdc1c8b0509291936u2d2036e6ic91f68f33db5342d@mail.gmail.com> (raw)
In-Reply-To: <1128046979.987.36.camel@dhcp153.mvista.com>

On 9/29/05, Daniel Walker <dwalker@mvista.com> wrote:
> On Thu, 2005-09-29 at 19:07 -0700, Mark Knecht wrote:
> > Hi,
> >    Any ideas how I could configure the kernel to get past this
> > problem? Currently the config file says this about MCE:
> >
> > CONFIG_GART_IOMMU=y
> > CONFIG_SWIOTLB=y
> > CONFIG_X86_MCE=y
> > # CONFIG_X86_MCE_INTEL is not set
> >
> > Can I safely set CONFIG_X86_MCE to no or not set? Or is this something
> > else completely?
>
> I think it's something else completely .. You would be better off
> turning on complete preemption .
>
> Daniel

Thanks.

make allnoconfig   builds
make defconfig fails as per my earlier message

make defconfig and then turning on complete preemption is doing this:

  CC      mm/fadvise.o
  CC      mm/page_alloc.o
  CC      mm/page-writeback.o
  CC      mm/pdflush.o
  CC      mm/readahead.o
  CC      mm/slab.o
mm/slab.c:2404: error: conflicting types for 'kmem_cache_alloc_node'
include/linux/slab.h:122: error: previous declaration of
'kmem_cache_alloc_node' was here
mm/slab.c:2404: error: conflicting types for 'kmem_cache_alloc_node'
include/linux/slab.h:122: error: previous declaration of
'kmem_cache_alloc_node' was here
make[1]: *** [mm/slab.o] Error 1
make: *** [mm] Error 2
lightning linux-2.6.14-rc2-rt7 #

I will continue on. Thanks very much for your help.

Thanks,
Mark

  reply	other threads:[~2005-09-30  2:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30  2:07 Mark Knecht
2005-09-30  2:22 ` Daniel Walker
2005-09-30  2:36   ` Mark Knecht [this message]
2005-09-30  2:43     ` Mark Knecht

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=5bdc1c8b0509291936u2d2036e6ic91f68f33db5342d@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=dwalker@mvista.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®