search for: timers

Alright I really need some help with this. I have been trying to get Roblox running for my Son and this has proved to be extremely difficult.. (Wine really does make you want to whine.. lol) I try to run Roblox.exe and Robloxapp.exe and I get this terminal output: Code: ons/version-b7d710b83ef74c14/RobloxApp.exe' fixme:advapi:RegisterEventSourceW ((null),L"PDH"): stub

I am doing some testing of openwrt'd wireless access points, using madwifi-ng'd atheros radios. In the test configuration, I have three devices in a triangle, each has wds links to the other two devices. The ath0 interface is in ap mode, ath1 is a wds link to one device, and ath2 is a wds link to the other device. All three interfaces (and an ethernet interface) are in a bridge (br-lan)

Hi, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

Hi, we're running the standard linux bridge setup (redundant bridge) for 5 years now. So first of all, thanks to everyone involved for implementing the bridging feature in Linux. Now I'm trying to bridge hosts connected to VLAN'ed Cisco switches using linux bridge. I'm testing the following setup (Kernel 2.6.19, bridge-utils 1.2 on both bridges)

It''s everytime when cpufreq_ondemand or cpufreq-set changes the frequency, aprox. 3 messages per event. Is that occasional? I tend to say: no. Please see an excerpt below. And if it''s not occasional, what could I do? And by the way: I found no code that TSC will get adjusted, so I think it will get worse over the time... Thanks, Carsten. messages.0:Jan 9 12:25:15 data kernel:

Hello, I've seen this upgrade error posted before: https://lists.samba.org/archive/samba/2013-January/171022.html but either there is a different issue or I'm misreading the post. Basically when I run the classicupgrade (samba3 to 4) on a test machine, I get the following (the full debug output will be at the end of my post): ....... key added: key=CurrentVersion,key=Windows

...... > I've made some additions to clarify things on the timer, and complete the script: > https://github.com/networkupstools/nut/compare/upssched-doc?expand=1 Hi Arnaud, Your change to the documentation clears up what I had mis-understood. The new text makes it clear that the upssched timers are an in-memory device, and that they can only be turned on and off with upssched.conf declarations such as ??? AT ONBATT * START-TIMER onbattwarn 30 ??? AT ONLINE * CANCEL-TIMER onbattwarn > Is there some other way of forcing routine cancel_timer from a script or a configuration file...

Hi, I'm trying to get a better understanding of what a timer is, so I added the following line to upssched.conf # Debug - turn on long-running timer to find out where upssched puts it AT ONBATT * START-TIMER where-am-I 1000 I can then start this timer by pulling the power cord from the wall for just a few seconds. I now have 1000 seconds to find the timer. I don't see it in

...On Jun 3, 2016, at 6:48 AM, Roger Price <roger at rogerprice.org> wrote: >> ... the timer. I don't see it in /var/lib/ups where the locate tool >> finds upsd.pid, and I don't see it in /run or /var/run where I see >> upsmon.pid. >> > ... it seems that the timers are only stored in memory. See > checktimers(): > https://github.com/networkupstools/nut/blob/master/clients/upssched.c#L129 Hello Charles, thanks for the link. If timers are only stored in memory then the example given at http://networkupstools.org/docs/user-manual.chunked/ar01s07.html...

Hi all, I've not been able to find the answer to my timer problem in the faq or the archives. (or google) Basically, I can't get timers to fire. They fire ignoring the timer value, as if the timer was set to 0. I'm using the OpenFiler distribution, patched to the latest and greatest. upsmon 2.2.2 When I pull the power plug, I see the text "Im In Battery" instantly, instead of after 20s. Power returned after 55 secon...

...he path is ok. The command is ok. her is my upssched.conf > # the script to be executed > CMDSCRIPT /root/scripts/upsalert > > # mandatory fields that must be set before AT commands > PIPEFN /var/run/upssched/upssched.pipe > LOCKFN /var/run/upssched/upssched.lock > > # the timers, here 30 sec after the ONBATT (ups on battery) event > AT ONBATT * START-TIMER phone_alert 15 > AT ONBATT * START-TIMER onbatt 900 > > # cancel the countdown if power is back > AT ONLINE * CANCEL-TIMER onbatt > AT ONLINE * CANCEL-TIMER phone_alert Any idea? thanks ahead Laure...

Add a way to disable the timer IRQ routing check via a boot option. The VMI timer code uses this to avoid triggering the pester Mingo code, which probes for some very unusual and broken motherboard routings. It fires 100% of the time when using a paravirtual delay mechanism instead of using a realtime delay, since there is no elapsed real time, and the 4 timer IRQs have not yet been delivered.

Add a way to disable the timer IRQ routing check via a boot option. The VMI timer code uses this to avoid triggering the pester Mingo code, which probes for some very unusual and broken motherboard routings. It fires 100% of the time when using a paravirtual delay mechanism instead of using a realtime delay, since there is no elapsed real time, and the 4 timer IRQs have not yet been delivered.

CPUIDLE: Avoid remnant LAPIC timer intr while force hpetbroadcast LAPIC will stop during C3, and resume to work after exit from C3. Considering below case: The LAPIC timer was programmed to expire after 1000us, but CPU enter C3 after 100us and exit C3 at 9xxus. 0us: reprogram_timer(1000us) 100us: entry C3, LAPIC timer stop 9xxus: exit C3 due to unexpected event, LAPIC timer continue running

Hi, When using lapic as timer source the hypervisor delivers timer interrupts late. In the source xen/arch/x86/hvm/vpt.c function create_periodic_time creates a timer element with a "bonus" of 50% of the desired time until the interrupt: pt->scheduled = NOW() + period; /* * Offset LAPIC ticks from other timer ticks. Otherwise guests which use * LAPIC ticks for

NUT 2.8.01 When I pull the USB cable from the UPS, I get two notifications of the nocomm-timer expired. The first notification is in the proper sequence, the second notification occurs after 'commok' occurs. Seems somehow that upssched-cmd is getting a second nocomm-timer expired delayed. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:

...tdown with 'upsmon -c fsd', sending a page by +Ultimately, the CMDSCRIPT upssched-cmd does the actual useful work, whether +that's initiating an early shutdown with 'upsmon -c fsd', sending a page by calling sendmail, or opening a subspace channel to V'ger. Establishing timers @@ -176,12 +178,12 @@ Executing commands immediately ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ As an example, consider the scenario where a UPS goes onto battery power. -However, the users are not informed until 60 seconds later - using a timer as +However, the users are not informed until 30 seconds lat...

On Sat, Feb 1, 2014 at 1:16 PM, Alexandre Courbot <acourbot at nvidia.com> wrote: > GK20A's timer is directly attached to the system timer and cannot be > calibrated. Skip the calibration phase on that chip since the > corresponding registers do not exist. Just a curiosity: What timer resolution does the HW initialise at? > > Signed-off-by: Alexandre Courbot <acourbot

...vHPET to vpt, for single HVM RHEL 5u1 guest idle case, our box will consume ~0.8W more power than before. The reason is two periodical vpts'' expires are hard to be aligned in the 50us soft timer SLOP. So we are considering a vpt specific enhancement which could try to just align periodical timers within vpt. A generic enhancement is to add a new interface like align_timer: (create_periodic_time) if ( period ) pt->scheduled = align_timer(NOW() + delta) ... set_timer(&pt->timer, pt->scheduled); Then align_timer tries to find another timer closest to expected expiration, and...

On Mon, Mar 24, 2014 at 05:42:24PM +0900, Alexandre Courbot wrote: > GK20A's timer is directly attached to the system timer and cannot be > calibrated. Skip the calibration phase on that chip since the > corresponding registers do not exist. > > Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> > --- > drivers/gpu/drm/nouveau/core/subdev/timer/nv04.c | 19