From: sl@9front.org
To: 9front@9front.org
Subject: no image after reclaim
Date: Mon, 24 Feb 2014 00:58:12 -0500 [thread overview]
Message-ID: <99013c63f63808ca066ed0c715e6eec7@x230.inri> (raw)
A while back I wrote an rss feed reader in go (the
parser is a pre-existing library, which is the reason
I chose to write the program in go)[0]. This runs twice
an hour on my cpu server, instigated by cron.
Result:
Every day or two my cpu server locks up. Remote sessions
stall. The console stops responding to keys being pressed on
the keyboard. The console screen fills up with this message,
repeated over and over:
no image after reclaim
The error message seems to be triggered in
/sys/src/9/port/segment.c.
I never had this problem before I started running my
go program. The problem first appeared around the
same time I started running my go program. I'm not sure
if I'm doing something stupid in my program, if something
is wrong with the go runtime, if something is wrong with
the 9front kernel, or some combination of the above.
sl
[0] http://code.google.com/p/rrss
next reply other threads:[~2014-02-24 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 5:58 sl [this message]
2014-02-24 7:18 ` [9front] " cinap_lenrek
2014-02-24 21:47 ` sl
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=99013c63f63808ca066ed0c715e6eec7@x230.inri \
--to=sl@9front.org \
--cc=9front@9front.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).