From: Kernel Panic <cinap_lenrek@gmx.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] new venti qemu / hang after sync... continued...
Date: Tue, 18 Sep 2007 16:39:36 +0200 [thread overview]
Message-ID: <46EFE328.6060108@gmx.de> (raw)
hello
just added some debug prints into venti and found out some more details
about the "sync..." hang problem.
ok, the main thread is spinning and kicking in icache.c / icachealloc()
because all blocks (20) in the cache seem dirty and need to be flushed,
but that
never happens. the icache.ndirty count goes never down and the
icachewritecoord thread doesnt flush anything... i dont know why yet.
icache.as.arena is 0 in icachewrite.c / icachewritecoord().
for what is that check? who is setting that field?
if i comment that test out i see "donewrite err=0" messages but the
icache.ndirty doesnt decrease. it should be decremented in icacheclean()
called from icachwrite.c / icachewritesect()... but icachewritesect()
doesnt
then enter the while(iedirty) loop...
"icachewritesect enter 0 4294967295 0" and
"icachewritesect done"
i hope that maybe helps a little bit :-(
cinap_lenrek
reply other threads:[~2007-09-18 14:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46EFE328.6060108@gmx.de \
--to=cinap_lenrek@gmx.de \
--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).