public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: eclark <eclark@alabanza.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with new kernel
Date: Fri, 30 Jun 2006 13:10:47 -0400	[thread overview]
Message-ID: <200606301310.48075.eclark@alabanza.com> (raw)
In-Reply-To: <1151685938.11434.51.camel@laptopd505.fenrus.org>

Excellent! How do I get NPTL built into the kernel. I had already been 
tohttp://people.redhat.com/~drepper/ this morning after googling my straces 
for a few hours, but nothing that indicated what needed to be done to get it 
into the kernel. Any assistance would be superb!
  
On Friday 30 June 2006 12:45 pm, Arjan van de Ven wrote:
> On Fri, 2006-06-30 at 10:46 -0400, eclark wrote:
> > Previous, I was using a RH stock kernel. This was rebuilt to be
> > monolithic with allthe required modules. However, now any binary which
> > uses set_thread_area segfaults. I know this is a kernel issue, as other
> > kernels I have used do not have this same issue. I am running 2.4.33-pre.
> > Below is an example strace of nslookup, one of the relevant binaries now
> > segfaulting. Above the big strace (total strace of nslookup) is where I
> > believe the problem is coming from. Any help would be appreciated, as I
> > have no clue what went wrong with this kernel build.
>
> Hi,
>
> you're running a kernel without NPTL support on a distribution that
> apparently expects NPTL support to be in the kernel... the failure mode
> isn't nice but failure at all isn't totally unexpected...... NPTL is
> needed for certain functionality and if a distribution expects that to
> be there.. things may well go very wonky if absent. (yes glibc tries to
> emulate this but the emulation is quite limited and not really possible)
>
> One example of such thing is cross-process mutexes and other locks; NPTL
> allows that (via futexes on shared pages), and things like rpm use this
> extensively. Another example is thread local storage; emulation is
> fragile via LDT's and such.
>
> Greetings,
>    Arjan van de Ven

  reply	other threads:[~2006-06-30 17:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-30 14:46 problem with new kernel eclark
2006-06-30 16:45 ` Arjan van de Ven
2006-06-30 17:10   ` eclark [this message]
2006-06-30 17:22     ` Arjan van de Ven
2006-06-30 17:13   ` eclark

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=200606301310.48075.eclark@alabanza.com \
    --to=eclark@alabanza.com \
    --cc=arjan@infradead.org \
    --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