From: sl@9front.org
To: 9front@9front.org
Subject: stats(1) suicide
Date: Wed, 6 Aug 2014 22:51:35 -0400 [thread overview]
Message-ID: <44fe6f6965c52b3475c55ac98002217a@x301.inri> (raw)
I run stats(1) on a diskless pc64 terminal with the following command:
window -r 836 1 1339 85 stats -Ll fs cpu.stanleylieber.com ttr gl mars2 tn $sysname
Lately, stats(1) suicides every day or so. I don't know when this started, but
I've noticed it a few times in the last couple of weeks. Today, I noticed it happened
again and I managed to capture some information:
stats 593: suicide: sys: trap: fault write addr=0xffffffff8258d1b0 pc=0x204cc7
; acid 593
/proc/593/text:amd64 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/amd64
acid: lstk()
notejmp(ret=0x1,j=0x40ac90)+0x13 /sys/src/libc/amd64/notejmp.c:10
alarmed(a=0xffffffff8258d1b0,s=0x7ffffeffea58)+0x3f /sys/src/cmd/stats.c:718
notifier+0x3e /sys/src/libc/port/atnotify.c:15
acid:
The system is connected over wifi and sometimes the network drops out long enough
that various programs (webfs, etc.) will time out. The dropouts are usually short
and most programs usually recover without needing to be restarted. Might this
stats(1) behavior be related to network problems?
sl
next reply other threads:[~2014-08-07 2:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 2:51 sl [this message]
2014-08-07 11:56 ` [9front] " cinap_lenrek
2014-08-08 7:45 ` arisawa
2014-08-08 16:01 ` sl
2014-08-08 21:30 ` arisawa
2014-08-08 21:44 ` sl
2014-08-08 22:35 ` arisawa
2014-08-08 22:57 ` cinap_lenrek
2014-08-09 6:05 ` arisawa
2014-08-09 15:42 ` cinap_lenrek
2014-08-09 22:46 ` arisawa
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=44fe6f6965c52b3475c55ac98002217a@x301.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).