9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] disabling swap
Date: Mon, 14 Sep 2009 20:51:35 -0400	[thread overview]
Message-ID: <5b6b79c8e69dd3203cf6f4bbf72998e3@quanstro.net> (raw)
In-Reply-To: <4ad0ed66d8a903a2b940d7d4a10914be@quintile.net>

On Mon Sep 14 20:09:25 EDT 2009, steve@quintile.net wrote:
> I have just hit a fossil deadlock. the symptom is simple enough,
> fossil wedged, stats continued to be updated and I could run whatis
> in a rio window but any attempt to access the local fossil caused
> the command to hang.
[..]
> If anyone is interested I have put my 9pccpuf and a phone camera
> image of ^t^t^p of the hang in http://www.quintile.net/doorstep/deadlock.jpg
> and http://www.quintile.net/doorstep/9pccpuf.

wasn't there a recent report of fossil hanging when sync was
done on the console with lots of io on the fs?

i could be missing something, but i don't see evidence that
swap (more accurately, demand paging) has anything to do
with the problem.  qpc and lpc just point to the pc of the
last blocking qlock or splhi.  that could be a very long way
(and time) from the current pc.

the fossil procs are in rendez, which could be any number
of vtLocks.

have you applied cinap's patch to periodic.c?
i would be very interested if that solves the problem.
(http://9fans.net/narchive/2009/03/487, /n/sources/patch/fossil-sleep-stress)

he wasn't seen a lockup, but i could see how a number
of spinning periodic threads could give the appearance
of making no progress since they would spin in a lock
acquiring a lock that a thread with something to do
may need.

- erik



      reply	other threads:[~2009-09-15  0:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  0:07 Steve Simon
2009-09-15  0:51 ` erik quanstrom [this message]

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=5b6b79c8e69dd3203cf6f4bbf72998e3@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).