From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] No regression tests
Date: Wed, 26 Mar 2014 15:13:50 -0400 [thread overview]
Message-ID: <2e616d063ebde1c9d56818fa0f789f0e@chula.quanstro.net> (raw)
In-Reply-To: <53331BD0.8050903@mail.com>
> Here mount /srv/bcscan /n/bc gives a readable /n/bc/bcU0/data.
>
> Then the reader is unplugged
>
> bootes 12 0:00 0:00 336K Pread bcscan
> bootes 13 0:00 0:00 336K Rendez bcscan
> bootes 14 0:00 0:00 336K Rendez bcscan
>
> Plaese note that here we see a different case. There are three
> spurious processes. On the plant (same test) there is only one.
>
> Then the reader is plugged in again
>
> bootes 13 0:00 0:00 336K Rendez bcscan
> bootes 14 0:00 0:00 336K Rendez bcscan
> bootes 432 0:00 0:00 336K Rendez bcscan
> bootes 434 0:00 0:00 336K Pread bcscan
> bootes 435 0:00 0:00 336K Rendez bcscan
> bootes 436 0:00 0:00 336K Rendez bcscan
> bootes 437 0:00 0:00 336K Open bcscan
i should learn chess so i don't ask questions in serial.
with acid, you can get a backtrace of process 12 and get the fd
it is reading. /proc/12/fd should have the file descriptor bcscan
thinks is open. if it
also, since process 13 and 14 did not wake from rendezvous,
there is a second issue. maybe you can see how 12 could exit
and leave 13 and 14 hanging.
- erik
next prev parent reply other threads:[~2014-03-26 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 5:50 Adriano Verardo
2014-03-25 12:33 ` erik quanstrom
2014-03-25 23:11 ` Adriano Verardo
2014-03-26 14:46 ` erik quanstrom
2014-03-26 18:26 ` Adriano Verardo
2014-03-26 19:13 ` erik quanstrom [this message]
2014-03-26 19:45 ` Adriano Verardo
2014-03-26 19:48 ` erik quanstrom
[not found] <214392e810a42ad8a4958929ca150ed5@proxima.alt.za>
2014-03-25 21:38 ` Adriano Verardo
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=2e616d063ebde1c9d56818fa0f789f0e@chula.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).