Re: timing failure on an s390x, SuSE Linux Enterprise Server

Dne Friday 02 December 2005 18:31 jste napsal(a):
> Try editing TETROOT/tetexec.cfg and replace
> VSX_AL_ACCURACY= (if it exists)
> with
>
> VSX_AL_ACCURACY=1
>
> or just add it if it does not exist.
> This may be the same as other problems we have seen
> elsewhere.

Thank you very much, it works with this setting.

However, now I'm not sure if it is a good sign, or a bad one? :)

Is it a test suite error, or our kernel has too imprecise timing? Can we 
certify the system with this behavior?

Best regards,

    Jiri Dluhos