From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] system crash during compile
Date: Sun, 9 Jul 2006 11:57:33 -0700 [thread overview]
Message-ID: <ee9e417a0607091157m51a4dbfah48698f7ab158b801@mail.gmail.com> (raw)
In-Reply-To: <7d3530220607090901h24130f23tcf35bc054bb6534f@mail.gmail.com>
> Hi everyone.
> I've been trying to compile a new kernel (9pccpuf), but whenever it
> gets to the "size 9pccpuf" point, I get the following error and a
> system crash:
>
> panic: executeio: page out I/O error
> dumpstack disabled
> cpu0: exiting
>
> Admittedly, this system is not the most up to date (can't get dialup
> working), so it could be a bug which is fixed now. However, with my
> slow connection, I would rather not re-download the cd image. Has
> anybody else seen this problem? It looks like it has something to do
> with swap, but the swap had been working OK up until that point.
> Thanks
You're running out of memory during the 8l command that
precedes the size command in the final linking recipe.
You might also be running out of swap. You could try running
stats to watch your memory and swap usage during the mk
and see if swap fills.
Russ
next prev parent reply other threads:[~2006-07-09 18:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 16:01 John Floren
2006-07-09 18:57 ` Russ Cox [this message]
2006-07-09 21:41 ` John Floren
2006-07-11 5:05 ` John Floren
2006-07-11 5:21 ` andrey mirtchovski
2006-07-11 15:15 ` John Floren
2006-07-11 18:41 ` Francisco J Ballesteros
2006-07-11 22:46 ` David Leimbach
2006-07-12 0:46 ` John Floren
2006-07-12 0:59 ` andrey mirtchovski
2006-07-12 14:51 ` John Floren
2006-07-12 21:10 ` Russ Cox
2006-07-13 0:15 ` John Floren
2006-07-13 0:17 ` Francisco J Ballesteros
2006-07-13 2:27 ` John Floren
2006-07-13 4:09 ` Russ Cox
2006-07-13 4:10 ` Russ Cox
2006-07-13 13:44 ` Brantley Coile
2006-07-13 14:52 ` John Floren
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=ee9e417a0607091157m51a4dbfah48698f7ab158b801@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).