public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: Rainer Mager <rmager@vgkk.com>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Is this kernel related (signal 11)?
Date: Tue, 23 Jan 2001 02:47:35 +0000	[thread overview]
Message-ID: <3A6CF0C7.E0D836E3@linux.com> (raw)
In-Reply-To: <NEBBJBCAFMMNIHGDLFKGOEKCCNAA.rmager@vgkk.com>

Rainer Mager wrote:

> > Would this be an SMP IA32 box with glibc 2.2? I have two such boxen
> > showing exactly the same behaviour, although I can't reproduce it at will.
>
> Close, it is actually an SMP IA32 box with glibc 2.1.3. But you've now
> convinced me to not upgrade glibc yet  ;-)

Upgrade -past- 2.2, get 2.2.1.  2.2 causes numerous segfaults, notably sendmail
and apache stop working.

-d

--
  There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
  The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-23  2:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19 22:27 [patch] smbfs cache rewrite for 2.4.1-pre Urban Widmark
2001-01-22  5:17 ` Is this kernel related (signal 11)? Rainer Mager
2001-01-22  7:34   ` David Woodhouse
2001-01-22  8:03     ` Rainer Mager
2001-01-23  2:47       ` David Ford [this message]
2001-01-23  8:37         ` Rainer Mager
2001-01-24  0:56           ` Rainer Mager
2001-01-25  0:45             ` Rainer Mager
2001-01-22  7:53   ` Rogier Wolff
2001-01-22 21:47     ` Russell King
2001-01-23  0:15       ` Paul Jakma
2001-01-22 14:27   ` 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=3A6CF0C7.E0D836E3@linux.com \
    --to=david@linux.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmager@vgkk.com \
    /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