From: "David E. Weekly" <dweekly@legato.com>
To: "ML-linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch
Date: Thu, 18 Oct 2001 17:06:43 -0700 [thread overview]
Message-ID: <016a01c15831$ef51c5c0$5c044589@legato.com> (raw)
Hey all,
I was trying to speed up kernel compiles experimentally by moving the source
tree into tmpfs and compiling there. It seemed to work okay and crunched
through the dep phase and most of the main build phase just fine, but then
it hit a file, got an internal segfault, and stopped. I tried again -- this
time make itself segfaulted. Three more times of make segfaulting -- a
strace on make didn't reveal what was failing. Then strace started
segfaulting. Eventually "ls" segfaulted and the machine needed to be
manually rebooted. Ouch!
I ran the full memtest86 suite on the machine, and it passed with flying
colors. So the memory proper is okay.
I come to one of two conclusions: this is a wierd problem with my north
bridge, or there's something funky going on with tmpfs.
Is tmpfs stable?
Yours,
-david
next reply other threads:[~2001-10-19 0:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 0:06 David E. Weekly [this message]
2001-10-19 0:22 ` Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch Davide Libenzi
2001-10-19 1:26 ` safemode
2001-10-19 5:12 ` Daniel T. Chen
2001-10-19 8:28 ` Christoph Rohland
2001-10-20 15:17 ` Jan-Frode Myklebust
2001-10-21 8:25 ` Christoph Rohland
2001-10-21 10:07 ` Jan-Frode Myklebust
2001-10-20 22:35 ` wild pointer!!!!! Kalyan
2001-10-21 12:21 ` Paul Mackerras
2001-10-21 12:15 ` Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch safemode
[not found] ` <E15vHVx-0001Nc-00@ii.uib.no>
2001-10-21 12:34 ` Jan-Frode Myklebust
2001-10-21 12:53 ` safemode
[not found] ` <E15vI6n-0001oC-00@ii.uib.no>
2001-10-21 13:10 ` bk regression fails on tmpfs /tmp, was: " Jan-Frode Myklebust
2001-10-21 13:36 ` safemode
2001-10-21 16:35 ` Larry McVoy
2001-10-21 17:50 ` Linus Torvalds
2001-10-21 20:15 ` Daniel Phillips
2001-10-22 17:03 ` bill davidsen
2001-10-22 17:12 ` Larry McVoy
2001-10-22 17:29 ` Alexander Viro
2001-10-23 5:25 ` Keith Owens
2001-10-22 9:44 ` Christoph Rohland
2001-10-22 10:01 ` Alexander Viro
2001-10-22 13:29 ` Wayne Scott
2001-10-22 17:31 ` bill davidsen
2001-10-30 17:29 ` Theodore Tso
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='016a01c15831$ef51c5c0$5c044589@legato.com' \
--to=dweekly@legato.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