From: Ingo Rohloff <rohloff@in.tum.de>
To: epic@scyld.com, linux-kernel@vger.kernel.org
Subject: epic100.c, gcc-2.95.2 compiler bug!
Date: Fri, 7 Sep 2001 16:03:15 +0200 [thread overview]
Message-ID: <20010907160315.D621@lxmayr6.informatik.tu-muenchen.de> (raw)
In-Reply-To: <20010903130404.B1064@lxmayr6.informatik.tu-muenchen.de> <20010907160159.C621@lxmayr6.informatik.tu-muenchen.de>
In-Reply-To: <20010907160159.C621@lxmayr6.informatik.tu-muenchen.de>; from rohloff@lxmayr6.informatik.tu-muenchen.de on Fri, Sep 07, 2001 at 04:01:59PM +0200
Hi,
I posted an error report about the epic100.c module about one
week before.
The sympotms were lot's of messages of this in /var/log/messages:
"kernel: eth0: Too much work at interrupt, IntrStatus=0x008d0004"
After one week of really frustrating debugging and incrementally
morphing the working version of the driver I got into the (for
me) non-working linux-2.4.9 version I finally found out what was
going on: the linux-2.4.9 driver has no bug!
BEWARE: DON'T USE gcc-2.95.2!
I compiled the linux-2.4.9 version with gcc-2.95.2.
And I can _definitely_ confirm that epic100.c triggers a compiler
bug. (I have the erronous assembler code on my harddisk if anyone is
interested.)
Compile the same module with gcc-2.95.3 and the bug is gone
(at least in my case. The assembler code is different and correct.)
conclusion:
Don't use gcc-2.95.2 to compile your kernel!
so long
Ingo Rohloff
next prev parent reply other threads:[~2001-09-07 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 11:04 epic100.c, SMC EtherPower II, SMC83c170/175 "EPIC" Ingo Rohloff
2001-09-07 14:01 ` Ingo Rohloff
2001-09-07 14:03 ` Ingo Rohloff [this message]
2001-09-07 14:13 ` epic100.c, gcc-2.95.2 compiler bug! antirez
2001-09-07 14:26 ` Jakub Jelinek
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=20010907160315.D621@lxmayr6.informatik.tu-muenchen.de \
--to=rohloff@in.tum.de \
--cc=epic@scyld.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;
as well as URLs for NNTP newsgroup(s).