From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: "M. Grabert" <xam@cs.ucc.ie>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Kernel crash when loggin in via ssh
Date: Wed, 11 Dec 2002 01:33:21 -0500 [thread overview]
Message-ID: <20021211063321.GB10185@systemhalted> (raw)
In-Reply-To: <Pine.LNX.4.44.0212110410060.6654-100000@sal.ucc.ie>
> Reading my previous post about the change in the Voodoo3 issue (Nov 26),
> I realized that linux-2.4.20-rc1-pa7 obviously also worked.
> This kernel was definitely compiled with gcc-3.0.4 (the one that
> was in sid as of Nov 26).
>
> Yes, it might be a gcc issue ... haven't thought of that ...
> I'll try to recompile the latest kernel with a gcc-3.0.4 - tomorrow!
So the urban legend goes that gcc-3.2 compiled kernels may infact
produce mildly incorrect results in the networking code.
I have yet to verify this, and JDA seems to indicate that he has working
kernels with gcc-3.2. While I've only recently tested gcc-3.0.x and
gcc-3.1.x based compiles.
I don't like urban legends >:} *Added item to Chrismas todo list*
c.
next prev parent reply other threads:[~2002-12-11 6:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 3:24 [parisc-linux] Kernel crash when loggin in via ssh M. Grabert
2002-12-11 3:57 ` Carlos O'Donell
2002-12-11 4:02 ` M. Grabert
2002-12-11 4:16 ` M. Grabert
2002-12-11 6:33 ` Carlos O'Donell [this message]
2002-12-11 13:51 ` [parisc-linux] another kernel compilation error Tim Kemna
2002-12-11 16:54 ` Paul Bame
2002-12-11 23:09 ` Tim Kemna
2002-12-11 16:57 ` Thibaut VARENE
2002-12-11 17:37 ` Grant Grundler
2002-12-11 23:29 ` [parisc-linux] Re: Solved: Kernel crash when loggin in via ssh M. Grabert
2002-12-11 23:40 ` John David Anglin
2002-12-11 23:56 ` M. Grabert
2002-12-12 0:05 ` Randolph Chung
2002-12-12 8:36 ` Thibaut VARENE
2002-12-12 7:32 ` Randolph Chung
2002-12-12 16:52 ` John David Anglin
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=20021211063321.GB10185@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=xam@cs.ucc.ie \
/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