well, the printf is already under ifdef DEBUG, I'm not sure what more
I can do right away without just removing it.  I don't want to remove it
since it's still useful if people are seeing it.

if it's causing you problems I'd recommend removing it in your local tree.
I will look at what dbench does to trigger it, but there a lot of problems
right now and I'm swamped just trying to get caught up from my time away
in india.

-Chuck


On Sun, Feb 04, 2001 at 11:34:56AM -0800, Matthew Jacob wrote:
> 
> It made the system so unresponsive that I had to power cycle it.
> 
> 
> On Sun, 4 Feb 2001, Chuck Silvers wrote:
> 
> > that's a debug printf, complaining that we're trying to flush pages after EOF.
> > nothing bad, just silly.  I should give dbench a try and see where we're
> > going wrong.  that'll be quite a way down the todo list, though.
> > 
> > -Chuck
> > 
> > 
> > On Sat, Jan 27, 2001 at 12:46:08PM -0800, Matthew Jacob wrote:
> > > 
> > > I'm running a neat little stress tester (dbench- quite useful for stressing a
> > > system: ftp://samba.org/pub/tridge/dbench) on top of tree NetBSD on an
> > > alpha....
> > > 
> > > A dbench 128 on a 128MB memory PC164 runs it out of memory pretty quick...
> > > things sort of freeze up, but continue along... what's more alarming is this-
> > > I'm getting continuous streams of these now:
> > > 
> > > uvn_flush: oor vp 0xfffffc000206e550 start 0x0 stop 0x8000 size 0x0
> > > 
> > > with various stop addressses and vnode pointers....
> > > 
> > > Was is das?
> > > 
> > > 
> >