public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Elstner <daniel.elstner@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.4 SMP: spurious EOVERFLOW "Value too large for defined data type"
Date: Mon, 30 Apr 2001 20:56:09 +0200	[thread overview]
Message-ID: <20010430205609.36599ccd.daniel@master.daniel.homenet> (raw)

Hi,

With kernel 2.4.4 SMP, I get some spurios errors from several
user-space programs. Unfortunately it's hard to reproduce, I had most
luck with the XFree86-4.0.3 build. When doing `make World', soon cpp0
(called by imake) dies with the following error message:

cpp0: : Value too large for defined data type

The message seems to correspond to EOVERFLOW in gcc's libiberty.
When calling imake directly, it fails 1 out of 10-20 times.
I couldn't reproduce this with calling cpp directly.

I also got a lot of that messages once at shutdown,
as init was trying to umount /proc.

The error occurs neither with 2.4.3 SMP nor with 2.4.4 UP.
(I'm using reiserfs, too.)

ABIT VP6
dual P3 866
gcc version 2.95.4 20010319 (prerelease)
binutils 2.11
glibc 2.2.3

Could you please give me further advice how to track this down?

Thanks,
-- Daniel

             reply	other threads:[~2001-04-30 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30 18:56 Daniel Elstner [this message]
2001-04-30 20:09 ` 2.4.4 SMP: spurious EOVERFLOW "Value too large for defined data type" Daniel Elstner
2001-04-30 20:55   ` reiserfs+lndir problem [was: 2.4.4 SMP: spurious EOVERFLOW "Value too large for defined data type"] Daniel Elstner
2001-05-01  1:03     ` Chris Mason
2001-05-01 22:41       ` Daniel Elstner
2001-05-01 22:48         ` Chris Mason
2001-05-02 20:41           ` Daniel Elstner

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=20010430205609.36599ccd.daniel@master.daniel.homenet \
    --to=daniel.elstner@gmx.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