From: Franz Sirl <Franz.Sirl-ppc@lauterbach.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: insmod ipv6 freezes current linuxppc-2.5 and 2.5-benh
Date: Tue, 02 Dec 2003 17:21:41 +0100 [thread overview]
Message-ID: <6.0.1.1.2.20031202171803.02dcd420@mail.lauterbach.com> (raw)
In-Reply-To: <20031130155530.GK26749@obroa-skai.de.gnumonks.org>
At 16:55 30.11.2003, Harald Welte wrote:
>On Fri, Nov 21, 2003 at 04:32:52PM +0100, Harald Welte wrote:
> >
> > On Fri, Nov 21, 2003 at 02:54:38PM +1100, Benjamin Herrenschmidt wrote:
> >
> > > Interesting. Same machine here and I use 2.6 everyday :)
> >
> > The problem seems to be gcc-related. Debian testing seems to have
> > installed gcc-3.3.2 (yes, maybe not the best compiler for a kernel
> > anyway) per default.
> >
> > compiling the same kernel with gcc-2.95 results in a working ipv6
> > module.
>
>I did some more testing:
>
>Compiles with gcc-3.3.2 and gcc-3.2.3 result in a broken kernel,
>gcc-3.0.4 and gcc-2.95.4 work fine.
Works fine for me with bk linuxppc-2.5 (test9/10/11), gcc-3.3.2 and
binutils-2.14.90.0.6. gcc is built from the gcc-3_3-rhl-branch, binutils as
in fedora development.
Franz.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-12-02 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 20:12 insmod ipv6 freezes current linuxppc-2.5 and 2.5-benh Harald Welte
2003-11-21 3:54 ` Benjamin Herrenschmidt
2003-11-21 15:33 ` Harald Welte
2003-11-30 15:55 ` Harald Welte
2003-12-02 15:59 ` Michel Dänzer
2003-12-13 9:03 ` Harald Welte
2003-12-14 10:38 ` Michel Dänzer
2003-12-02 16:21 ` Franz Sirl [this message]
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=6.0.1.1.2.20031202171803.02dcd420@mail.lauterbach.com \
--to=franz.sirl-ppc@lauterbach.com \
--cc=benh@kernel.crashing.org \
--cc=laforge@gnumonks.org \
--cc=linuxppc-dev@lists.linuxppc.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).