public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Post install 2.4.29 causes many apps to seg fault.
Date: Fri, 4 Feb 2005 20:40:46 +0000	[thread overview]
Message-ID: <200502042040.46367.nick@linicks.net> (raw)

>> Is there something more that I need to compile besides the kernel for 
>> compatability or is this a sign of some type of bug.  I do realize that 
RHEL3 
>> itself has some proprietary items added to their kernel but replacing it 
>> shouldn't make other applications fails.
>> 
>> Any assistance would be greatly appreciated.
>> 
> If lots of things fail in strange places, I would wonder if your glibc
> is compatible with your kernel. I suggest you take it up on a redhat
> mailinglist.

Yes, I had a similar problems at work when I  up2date'd the latest GLIBC for 
RHEL 3 late last year.  A colleague in Montreal (I am in UK) sussed what was 
going on.  I will _presume_ you are seeing similar problems with a kernel 
build.

Here is the link that explains it... what to do with many processes 
segfaulting, I don't know.  RHEL support is _very_ good - give them a ring.

http://people.redhat.com/drepper/assumekernel.html

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

             reply	other threads:[~2005-02-04 20:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 20:40 Nick Warne [this message]
2005-02-05  2:01 ` Post install 2.4.29 causes many apps to seg fault Gary Smith
2005-02-05 12:59   ` Nick Warne
  -- strict thread matches above, loose matches on Subject: below --
2005-02-04 19:10 Gary Smith
2005-02-04 19:43 ` Jurriaan
2005-02-05  2:19 ` Barry K. Nathan

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=200502042040.46367.nick@linicks.net \
    --to=nick@linicks.net \
    --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