From: cinap_lenrek@gmx.de
To: 9fans@cse.psu.edu
Subject: [9fans] new venti qemu / hang after sync...
Date: Tue, 18 Sep 2007 01:17:03 +0200 [thread overview]
Message-ID: <988569a5e89460ae2b2ace8e0902c119@gmx.de> (raw)
Hello!
Some guy at IRC installed current iso with fossil+venti on qemu. The
first boot into the new installed system works, but on the 2nd boot
time venti hangs with:
conf...httpd tcp!127.1!8000...init...sync...
I installed it today and could reproduce the problem.
Tried running Plan9 from live cd to see whats happening gets the same
problem:
ip/ipconfig
venti/venti -d -L -c /dev/sdC0/arenas -a 'tcp!*!17034' -h 'tcp!*!8000'
conf...httpd tcp!127.1!8000...init...sync...
...
And then looking at the logs shows:
(sorry, removed timestamps because i typed this manualy)
hget 'http://10.0.2.15:8000/log?log=all' | htmlfmt
proc main: kick icache
work icachewritecoord: start
proc icachewritecoord: icachewritecoord kick dcache
work flushproc: start
proc flushproc: build t=131
proc flushproc: writeblocks t=991
proc flushproc: writeblocks.1 t=1632
proc flushproc: writeblocks.2 t=2296
proc flushproc: writeblocks.3 t=2944
proc flushproc: undirty.4 t=3564
work flushproc: finish
proc icachewritecoord: kick dcache
proc icachewritecoord: icachewritecoord kicked dcache
proc icachewritecoord: icachewritecoord start flush
proc icachewritecoord: icachedirty enter
proc icachewritecoord: icachedirty exit
proc icachewritecoord: icachewritecoord sleep
proc main: kick icache
...the stuff repeats again...
The log fills all the time... All processes alive none broken.
Starting venti with the -r option seems to work without such problems.
(because syncindex() is not called?)
Any suggestions what I should to to debug this problem further? Would
be interesting to know if this happens on qemu only...
cinap_lenrek
reply other threads:[~2007-09-17 23:17 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=988569a5e89460ae2b2ace8e0902c119@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).