> Nov 29 17:57:56 EST 2009 local.c 5559 [bootes]
> local.c:227 c /n/dump/2009/1129/sys/src/9/boot/local.c:227
> < run("/boot/venti", "-c", f[0], "-m", "20", "-a", f[1],
> "-h", f[2], 0);
> ---
> > run("/boot/venti", "-c", f[0], "-a", f[1], "-h", f[2],
> > 0
On a hint from Geoff I did this:
Nov 29 17:57:56 EST 2009 local.c 5559 [bootes]
local.c:227 c /n/dump/2009/1129/sys/src/9/boot/local.c:227
< run("/boot/venti", "-c", f[0], "-m", "20", "-a", f[1],
"-h", f[2], 0);
---
> run("/boot/venti", "-c", f[0], "-a"
> one thing that I don't understand: when it starts up I get a line like this:
> mem -1 bcmem 0 icmem 0
>
> Does this point to misconfiguration or will venti do something reasonable
> here?
it looks like a little bit of misconfiguration, which the current
code makes too easy. i'm not sure this
OK, I'm seeing the following: 1500 syscalls/second, steady disk
activity, pegged really, while I'm not really doing anything, tends to
climb to 1 (!). This just started 2 days ago when I upgraded ...
it had been a while. dma is enabled.
I'm suspecting venti or fossil or interaction but ... wha
