# 1 tick delayed task start after portSUPPRESS\_TICKS\_AND\_SLEEP

**URL:** <https://forums.freertos.org/t/1-tick-delayed-task-start-after-portsuppress-ticks-and-sleep/6498>\
**Category:** Kernel\
**Created:** [April 5, 2017, 6:25pm UTC](https://forums.freertos.org/t/1-tick-delayed-task-start-after-portsuppress-ticks-and-sleep/6498 "2017-04-05T18:25:42Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\
**Post date:** [April 20, 2017, 2:02pm UTC](https://forums.freertos.org/t/1-tick-delayed-task-start-after-portsuppress-ticks-and-sleep/6498/19 "2017-04-20T14:02:07Z")

</div>

**[davedoors](https://sourceforge.net/u/davedoors/)** wrote on [Thursday, April 20, 2017](https://sourceforge.net/p/freertos/discussion/382005/thread/237a82ca/#0e71):

Interrupts get enabled as soon as possible to maximize responsiveness. Coming out of a low power mode can take the hardware a long time and most people want the interrupt that woke the chip to execute as soon as physically possible. The latest version in SVN goes further, enabling interrupts so they can execute asap, then disabling them again while the catch up is done.

---

_[View the full topic](https://forums.freertos.org/t/1-tick-delayed-task-start-after-portsuppress-ticks-and-sleep/6498)._