From: David Chambers <davidc@ccmi.salk.edu>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test{2,4}, gcc, smp problem
Date: Wed, 3 Sep 2003 08:37:13 -0700 [thread overview]
Message-ID: <20030903083713.009d4b1b.davidc@ccmi.salk.edu> (raw)
Hi,
I have recently been trying the 2.6.0-test kernels on an up-to-date Red Hat 9 system (Dual Xeon, 2 GB RAM, Tyan 7505 motherboard). Being lazy :-) I downloaded arjanv's source RPMs and built from those. These RPMs apply 2 small patches, one framebuffer related and one implements a noninteractive "make oldconfig", otherwise the 2.6.0 source is untouched.
Compilation of the initial 2.6.0-test2 with gcc 3.2 (Red Hat released version) (while running 2.4.21) went perfectly. I booted the new 2.6.0-test2 and I have to say I never want to go back to 2.4! Desktop responsiveness is **much** improved - superb job, guys!.
However... When I tried to compile 2.6.0-test2 again, (running under 2.6.0-test2) I get irreproducible internal compiler errors or segmentation faults. I have tracked this down to the use of "make -j4" during the build. If I disable the multiple job compilation, everything works. If I so much as use "make -j2" I get the errors again.
Same thing happens with 2.6.0-test4. I tried upgrading gcc to 3.3.1 (Rawhide rpm) and this has made no difference. I have not yet tried this with anything but the smp kernel, btw.
So... What am I looking at here? Problem with hardware? kernel? gcc? Any comments and suggestions gratefully received!!
- David Chambers
reply other threads:[~2003-09-03 15:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030903083713.009d4b1b.davidc@ccmi.salk.edu \
--to=davidc@ccmi.salk.edu \
--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
all inboxes | Powered by JetHome®