Re: Timer issues?

[Frank Wille <frank%phoenix.owl.de@localhost>]

Michael L. Hitch wrote:

> [...]
>   I just tried adjusting the prev_hardclock value if it is greater than 
> the current hardclock_ticks, and it has signifcantly reduced the times
> the return value goes backwards.  I've only seen message once so far,
> where before I got quite a few of them.
> 
> scsibus0: waiting 2 seconds for devices to settle...
> vax_mfpr_get_counter wrapped: prev=40077, cur=30117 diff=9960
>                            : prev=4/77, cur=(2)3/117
> sd0 at scsibus0 target 0 lun 0: <FUJITSU, MXF3364LC, 0318> disk fixed
> 
> 
>   Here's my current vax change with the check code included:
> 
> Index: sys/arch/vax/vax/clock.c
> [...]

I noticed you have not commited your changes for vax, and I didn't dare doing
it for amiga either. Any news about it?

I made a long-term test over more than 24h this weekend, and it seems that
I'm still getting such overflow messages every 1-2 hours, when the 32-bit
counter wraps.

-- 
Frank Wille