Last question.
Is necessary to disable interrupts or do some other
activites in the reboot callout different than simple
reboot procedure?
Thank you,
Jacek
Uzytkownik “Sunil Kittur” <skittur@qnx.com> napisal w wiadomosci
news:d7h7tm$p1e$1@inn.qnx.com…
The “Out of interrupt events!” message is because you
probably still have interrupts enabled. The kernel
does not disable interrupts (via the CPSR I bit) when
it calls the reboot callout, so any interrupt that
can cause sigevents to be queued (eg. clock) will
eventually cause that message since nothing is running
that can consume the events.
Sunil.
Jacek Rudnicki wrote:
Hi Sunil,
There was a little mess inside startup source.
So, I rebuilt my project and did some tests
once again.
Now the “busy loop” reboot callout is working fine:
→ QNX 6.2.1
shutdown -vvv
Shutting down apps…
sh
Shutting down daemons…
io-net
Shutting down filesystems…
pipe
devf-viper
As we see system stops here in never-ending loop.
→ QNX 6.3
shutdown -vvv
Shutting down apps…
sh
Shutting down daemons…
io-net
Shutting down filesystems…
pipe
devf-viper
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
…
What does mean this message?
Is there something wrong with the
board configuration?
I will send to you my reboot callout code (which
works perfect under QNX 6.2.1) today.
Jacek Rudnicki wrote:
Last question.
Is necessary to disable interrupts or do some other
activites in the reboot callout different than simple
reboot procedure?
It depends on what you need to do to trigger the reboot.
For some boards, just hitting a control register will
trigger the reboot so you don’t necessarily need to
disable interrupts. However, in general, it’s probably
safe and a good idea to disable interrupts before you
start the reboot to ensure that there are no possible
side-effects from interrupts during the sequence of
operations your callout needs to do.
Sunil.
Thank you,
Jacek
Uzytkownik “Sunil Kittur” <> skittur@qnx.com> > napisal w wiadomosci
news:d7h7tm$p1e$> 1@inn.qnx.com> …
The “Out of interrupt events!” message is because you
probably still have interrupts enabled. The kernel
does not disable interrupts (via the CPSR I bit) when
it calls the reboot callout, so any interrupt that
can cause sigevents to be queued (eg. clock) will
eventually cause that message since nothing is running
that can consume the events.
Sunil.
Jacek Rudnicki wrote:
Hi Sunil,
There was a little mess inside startup source.
So, I rebuilt my project and did some tests
once again.
Now the “busy loop” reboot callout is working fine:
→ QNX 6.2.1
shutdown -vvv
Shutting down apps…
sh
Shutting down daemons…
io-net
Shutting down filesystems…
pipe
devf-viper
As we see system stops here in never-ending loop.
→ QNX 6.3
shutdown -vvv
Shutting down apps…
sh
Shutting down daemons…
io-net
Shutting down filesystems…
pipe
devf-viper
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
Out of interrupt events!
…
What does mean this message?
Is there something wrong with the
board configuration?
I will send to you my reboot callout code (which
works perfect under QNX 6.2.1) today.