Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Jun 2022 14:02:57 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 264867] kevent EVFILT_TIMER, timer expiration with twice the period
Message-ID:  <bug-264867-227-x9KDWTIvU9@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-264867-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-264867-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264867

--- Comment #2 from felice.tufo@gmail.com ---
Hi Mark

thanks for the answer.

The output of the sysctl command is as follows:

kern.eventtimer.choice: LAPIC(600) HPET(550) i8254(100) RTC(0)
kern.eventtimer.et.i8254.quality: 100
kern.eventtimer.et.i8254.frequency: 1193182
kern.eventtimer.et.i8254.flags: 1
kern.eventtimer.et.RTC.quality: 0
kern.eventtimer.et.RTC.frequency: 32768
kern.eventtimer.et.RTC.flags: 17
kern.eventtimer.et.HPET.quality: 550
kern.eventtimer.et.HPET.frequency: 24000000
kern.eventtimer.et.HPET.flags: 7
kern.eventtimer.et.LAPIC.quality: 600
kern.eventtimer.et.LAPIC.frequency: 2903994335
kern.eventtimer.et.LAPIC.flags: 7
kern.eventtimer.periodic: 0
kern.eventtimer.timer: LAPIC
kern.eventtimer.idletick: 0
kern.eventtimer.singlemul: 2

I did not try other systems because the HW cannot be changed (the applicati=
on
has to work on that industrial pc), but I could run some tests on other sys=
tems
just to see if it is reproducible also on other platforms.

I'm sorry but a test of just few minutes is not enough, I usually let it run
for hours; in one run the issue happened after nearly 1 day and half from t=
he
start.

Also, I never tried 14.0-CURRENT, only 12.2 and 13.1.

Thanks,
Felice

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264867-227-x9KDWTIvU9>