On 30 Jan 2001 eeh@netbsd.org wrote:

> 
> 	> if is->is_flush really is 0x100000000, either the code generation
> 	> is broken, or the value was set between the test and the printf ()
> 	> call.  Maybe you should just increase the timeout a bit.
> 
> 	I can compile without optimization, it helped me before with 
> 	code generation. Don't understand yet that 'timeout' magic. 
> 
> Hm.  It should work.  is_flush is volatile.  Could be D$
> coherency issues.  Try adding a call to `blast_vcache()' just
> before the test of `is->is_flush' to see if it fixes the problem
> (this is DIAGNOSTIC code, after all.)

Don't know what hepled, I did both noopt for iommu.c and blast_vcache 
magic, my simple test which broke before(newfs, ftp distribution, untar) passed
now. Wow, cool.  Unfortunately I've got to go. 

Thanks,
	Andrey