From: "Iain Sandoe" <iain@sandoe.co.uk>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: network stack oops 2.4.1/gcc 2.95.3
Date: Mon, 29 Jan 2001 19:12:36 +0000 [thread overview]
Message-ID: <20010129191225.AB75C2EFD2@apollo.valhalla.net> (raw)
> Has there been any follow up to this problem report? Is this a
> regression from gcc-2.95.2 behavior? Franz's pre-releases do not exactly
> correspond to the GCC development pre-releases, so I have no idea when
> this problem began or whether it is local to the linuxppc branch.
It is not a regression test. It would not be particularly easy, either to
put 2.95.2 back up and wind back the system to the build conditions...
but the version used was 2.95.3-test2. and the bk pull was 2.4.1-pre10.
The only reason I associated gcc at all (and copied this to Franz) was that
I don't recall ever seeing an Illegal Instruction oops before.
Unfortunately, (or fortunately depending on your POV) it is not reproducible
to order. It seems to depend on network load - maybe one time in 20 with a
heavily loaded network?
The system is booted OK
It is in the transition from single to init 5 (where portmap & named are
launched in my set-up).
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-29 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 19:12 Iain Sandoe [this message]
2001-01-29 19:18 ` network stack oops 2.4.1/gcc 2.95.3 David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2001-02-01 0:53 Iain Sandoe
2001-01-30 15:45 Iain Sandoe
2001-01-29 23:54 Iain Sandoe
2001-01-30 12:39 ` Franz Sirl
2001-01-30 17:52 ` David Edelsohn
2001-01-29 19:05 David Edelsohn
2001-01-27 13:36 Iain Sandoe
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=20010129191225.AB75C2EFD2@apollo.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=dje@watson.ibm.com \
--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).