Shutdown problem on QNX6.3

MNg1 · May 24, 2005, 1:51am

Does anyone know the root (or cause) of this shutdown message?
Shutdown[0,0] S/C/F=11/1/11 C/D=f00151f5/f005a52D state(c0)= now
lock.
Is this an inherent QNX problem?
Please help.

MNg

Colin_Burgess1 · May 24, 2005, 2:14am

It’s a kernel crash. There is a technote that comes with the 6.3 docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.html

MNg wrote:

Does anyone know the root (or cause) of this shutdown message?
Shutdown[0,0] S/C/F=11/1/11 C/D=f00151f5/f005a52D state(c0)= now
lock.
Is this an inherent QNX problem?
Please help.

MNg

–
cburgess@qnx.com

Jacek_Rudnicki · May 24, 2005, 9:00am

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00 1a 00
00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <cburgess@qnx.com> napisal w wiadomosci
news:42928DF7.4090504@qnx.com…

It’s a kernel crash. There is a technote that comes with the 6.3 docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

–
cburgess@qnx.com

Colin_Burgess1 · May 24, 2005, 12:00pm

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00 1a 00
00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:> 42928DF7.4090504@qnx.com> …

It’s a kernel crash. There is a technote that comes with the 6.3 docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.
html

–
cburgess@qnx.com
\

–
cburgess@qnx.com

Colin_Burgess1 · May 24, 2005, 12:35pm

BTW - r8 has value 0xfe1503a3 which is unaligned, hence the sigbus
(signal 10)

Colin Burgess wrote:

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00
1a 00
00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:> 42928DF7.4090504@qnx.com> …

It’s a kernel crash. There is a technote that comes with the 6.3 docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

–
cburgess@qnx.com

\

–
cburgess@qnx.com

Jacek_Rudnicki · May 24, 2005, 1:02pm

Yes, the reboot callout was written by us.
Can I contact with you via separate e-mail?

Jacek

Uzytkownik “Colin Burgess” <cburgess@qnx.com> napisal w wiadomosci
news:d6v4g1$d4c$2@inn.qnx.com…

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:
Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00 1a
00
00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:> 42928DF7.4090504@qnx.com> …

It’s a kernel crash. There is a technote that comes with the 6.3 docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.
html

–
cburgess@qnx.com

\

cburgess@qnx.com

Colin_Burgess1 · May 24, 2005, 1:57pm

I really don’t know anything about the specifics of ARM, unfortunately,
so I wouldn’t be of much help.

Support@qnx.com would be the best route for direct support.

Jacek Rudnicki wrote:

Yes, the reboot callout was written by us.
Can I contact with you via separate e-mail?

Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:d6v4g1$d4c$> 2@inn.qnx.com> …

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00 1a

00

00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:> 42928DF7.4090504@qnx.com> …

It’s a kernel crash. There is a technote that comes with the 6.3 docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

\

cburgess@qnx.com

\

cburgess@qnx.com
\

–
cburgess@qnx.com

Jacek_Rudnicki · May 24, 2005, 2:00pm

The reboot callout code is the same for QNX 6.2.1 & 6.3.
But above Shutdown[] lines appear only under 6.3.

Is there any difference in callouts definition/implementation?

Jacek

Uzytkownik “Colin Burgess” <cburgess@qnx.com> napisal w wiadomosci
news:d6v6id$d4c$3@inn.qnx.com…

BTW - r8 has value 0xfe1503a3 which is unaligned, hence the sigbus
(signal 10)

Colin Burgess wrote:
Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00
1a 00
00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:> 42928DF7.4090504@qnx.com> …

It’s a kernel crash. There is a technote that comes with the 6.3 docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

–
cburgess@qnx.com

\

cburgess@qnx.com

Jacek_Rudnicki · May 24, 2005, 2:05pm

I really don’t know anything about the specifics of ARM, unfortunately,
so I wouldn’t be of much help.

Support@qnx.com > would be the best route for direct support.

I have tried this way, but no response from support since about one week.

Jacek

Jacek Rudnicki wrote:
Yes, the reboot callout was written by us.
Can I contact with you via separate e-mail?

Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:d6v4g1$d4c$> 2@inn.qnx.com> …

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00 1a

00

00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:> 42928DF7.4090504@qnx.com> …

It’s a kernel crash. There is a technote that comes with the 6.3 docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

\

cburgess@qnx.com

\

cburgess@qnx.com

\

cburgess@qnx.com

Rodney_Dowdall1 · May 24, 2005, 2:16pm

Hello Jacek

Did you get a ticket for the support question? Did you include your
support plan information in the email that you sent to support?

Thanks,
Rodney

Jacek Rudnicki wrote:

I really don’t know anything about the specifics of ARM, unfortunately,
so I wouldn’t be of much help.

Support@qnx.com > would be the best route for direct support.

I have tried this way, but no response from support since about one week.

Jacek

Jacek Rudnicki wrote:

Yes, the reboot callout was written by us.
Can I contact with you via separate e-mail?

Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:d6v4g1$d4c$> 2@inn.qnx.com> …

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00 1a

00

00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:> 42928DF7.4090504@qnx.com> …

It’s a kernel crash. There is a technote that comes with the 6.3 docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

\

cburgess@qnx.com

\

cburgess@qnx.com

\

cburgess@qnx.com

Jacek_Rudnicki · May 24, 2005, 4:33pm

Uzytkownik “Rodney Dowdall” <rdowdall@qnx.com> napisal w wiadomosci
news:d6vcdu$ias$1@inn.qnx.com…

Hello Jacek

Did you get a ticket for the support question? Did you include your
support plan information in the email that you sent to support?

Yes, I did. Even we were exchanging some e-mails until support kept quiet.

Maybe here I will be a more lucky ?

Regards,
Jacek

Thanks,
Rodney

Jacek Rudnicki wrote:
I really don’t know anything about the specifics of ARM, unfortunately,
so I wouldn’t be of much help.

Support@qnx.com > would be the best route for direct support.

I have tried this way, but no response from support since about one week.

Jacek

Jacek Rudnicki wrote:

Yes, the reboot callout was written by us.
Can I contact with you via separate e-mail?

Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:d6v4g1$d4c$> 2@inn.qnx.com> …

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00
1a

00

00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:> 42928DF7.4090504@qnx.com> …

It’s a kernel crash. There is a technote that comes with the 6.3
docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

\

cburgess@qnx.com

\

cburgess@qnx.com

\

cburgess@qnx.com

Rodney_Dowdall1 · May 24, 2005, 4:39pm

Jacek Rudnicki wrote:

Uzytkownik “Rodney Dowdall” <> rdowdall@qnx.com> > napisal w wiadomosci
news:d6vcdu$ias$> 1@inn.qnx.com> …

Hello Jacek

Did you get a ticket for the support question? Did you include your
support plan information in the email that you sent to support?

Yes, I did. Even we were exchanging some e-mails until support kept quiet.

What is the support ticket number?

Rodney

Maybe here I will be a more lucky ?

Regards,
Jacek

Thanks,
Rodney

Jacek Rudnicki wrote:

I really don’t know anything about the specifics of ARM, unfortunately,
so I wouldn’t be of much help.

Support@qnx.com > would be the best route for direct support.

I have tried this way, but no response from support since about one week.

Jacek

Jacek Rudnicki wrote:

Yes, the reboot callout was written by us.
Can I contact with you via separate e-mail?

Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:d6v4g1$d4c$> 2@inn.qnx.com> …

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00
1a

00

00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:> 42928DF7.4090504@qnx.com> …

It’s a kernel crash. There is a technote that comes with the 6.3
docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

\

cburgess@qnx.com

\

cburgess@qnx.com

\

cburgess@qnx.com

Jacek_Rudnicki · May 24, 2005, 4:43pm

TicketID69217 “Difference in callouts definition”

Jacek

Uzytkownik “Rodney Dowdall” <rdowdall@qnx.com> napisal w wiadomosci
news:d6vkql$nrd$1@inn.qnx.com…

Jacek Rudnicki wrote:
Uzytkownik “Rodney Dowdall” <> rdowdall@qnx.com> > napisal w wiadomosci
news:d6vcdu$ias$> 1@inn.qnx.com> …

Hello Jacek

Did you get a ticket for the support question? Did you include your
support plan information in the email that you sent to support?

Yes, I did. Even we were exchanging some e-mails until support kept
quiet.

What is the support ticket number?

Rodney

Maybe here I will be a more lucky ?

Regards,
Jacek

Thanks,
Rodney

Jacek Rudnicki wrote:

I really don’t know anything about the specifics of ARM, unfortunately,
so I wouldn’t be of much help.

Support@qnx.com > would be the best route for direct support.

I have tried this way, but no response from support since about one
week.

Jacek

Jacek Rudnicki wrote:

Yes, the reboot callout was written by us.
Can I contact with you via separate e-mail?

Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:d6v4g1$d4c$> 2@inn.qnx.com> …

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your
own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00
1a

00

00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:> 42928DF7.4090504@qnx.com> …

It’s a kernel crash. There is a technote that comes with the 6.3
docs
on interpreting them.

The most common causes are faults in your interrupt handler.

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

\

cburgess@qnx.com

\

cburgess@qnx.com

\

cburgess@qnx.com

Sunil_Kittur1 · May 24, 2005, 5:02pm

The crash is inside the low-level interrupt handling code.
In that particular piece of code, r4 is the interrupt vector
(in this case 0x1a → OS timer 0 interrupt), and r8 is a
pointer to an internal data structure used to manage the
interrupt source. That address is calculated based on the
address of a kernel data structure, so I don’t see how/why it
would be misaligned.

However, the PID-TID in the crash message below is bogus, which
seems to indicate some kind of corruption of kernel data.

Do you get the crash if you replace your callout with one that
simply does a busy loop?

If that works OK, it would be useful to see your reboot callout
code to see if there’s anything that might be affected by the
differences between 621 and 630.

Sunil.

Jacek Rudnicki wrote:

Yes, the reboot callout was written by us.
Can I contact with you via separate e-mail?

Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:d6v4g1$d4c$> 2@inn.qnx.com> …

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00 1a

00

00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Jacek_Rudnicki · May 25, 2005, 9:43am

The crash is inside the low-level interrupt handling code.
In that particular piece of code, r4 is the interrupt vector
(in this case 0x1a → OS timer 0 interrupt), and r8 is a
pointer to an internal data structure used to manage the
interrupt source. That address is calculated based on the
address of a kernel data structure, so I don’t see how/why it
would be misaligned.

However, the PID-TID in the crash message below is bogus, which
seems to indicate some kind of corruption of kernel data.

Do you get the crash if you replace your callout with one that
simply does a busy loop?

With the “busy loop” reboot callout routine
0: b 0b
and the same runtime as below I get:

under QNX 6.2.1

Shutdown[0,0] S/C/F=4/1/1 C/D=fe005de0/fe048500 state(c0)= now lock
[0]PID-TID=1-7? P/T FL=00019001/05020000 “proc/boot/procnto”
[0]ASPACE PID=24579 PF=00000010 “proc/boot/shutdown”
armle context[ff7f5f98]:
0000: fc404000 00000000 fc4040a0 fe0480c0 00000000 fe0480c4 ff7ed008
00000001
0020: 00000000 0000000c fe046448 ff7f5fec ff7f5fdc ff7f5fdc fe01f174
fc4044d8
0040: 00000013
instruction[fc4044d8]:
58 46 40 fc 00 90 28 00 b0 46 40 fc d8 46 40 fc 00 47 40 fc 00 00 00 00 00
00
stack[ff7f5fdc]:
0000: ff7fd550 ff7f5ffc ff7f5ff0 fe031694 fe01f140 ff7eef1c ff7f6000
fe01f5dc
0020: fe031678 ff7f62a8 00000008 e88d000f e24e1004 e14f2000 e1a0300d
e10f0000
0040: e3c0001f e3800013 e129f000 e59f0078 e5900000 e3300000 059f0074
11a0000d
0060: 05900000 02800f43 e9200006 e202201f e3320013 19606000 09206000
e1a0d000

under QNX 6.3

Shutdown[0,0] S/C/F=4/1/1 C/D=fe005f98/fe050ec8 state(c0)= now lock
[0]PID-TID=1-4? P/T FL=00019001/05020000 “proc/boot/procnto”
[0]ASPACE PID=90114 PF=00000000 “bin/shutdown”
armle context[fe05af98]:
0000: fc404000 00000000 fc4040a0 fe050458 00000000 fe05045c fe28b008
00000001
0020: 00000000 0000000d fe04e488 fe05afec fe05afdc fe05afdc fe022d38
fc4044e8
0040: 00000013
instruction[fc4044e8]:
68 46 40 fc 00 90 28 00 c0 46 40 fc e8 46 40 fc 10 47 40 fc 00 00 00 00 00
00
stack[fe05afdc]:
0000: fe054880 fe05affc fe05aff0 fe0363c4 fe022d04 fe28aefc fe05b000
fe0231a0
0020: fe0363a8 fe05b070 00000030 fe05b00d fe05b011 fe05b015 fe05b019
fe05b01d
0040: 00000001 fe05b210 00000010 a3da8b14 00000000 00000000 fc404000
a3dacb14
0060: 00000000 fe053f50 00000000 00000000 00000000 00000000 00000000
00000000

If that works OK, it would be useful to see your reboot callout
code to see if there’s anything that might be affected by the
differences between 621 and 630.

Where should I send my reboot callout code?
Directly to you or maybe to support?

Jacek

Sunil.

Jacek Rudnicki wrote:
Yes, the reboot callout was written by us.
Can I contact with you via separate e-mail?

Jacek

Uzytkownik “Colin Burgess” <> cburgess@qnx.com> > napisal w wiadomosci
news:d6v4g1$d4c$> 2@inn.qnx.com> …

Well, the instruction it fauled on was at 0xfe05d154, and it was an

ldrh r7, [r8, #14]

(0xe1d870be)

I suspect it’s a fault in the reboot callout - did you write your own?

Jacek Rudnicki wrote:

Hi Colin,

Can you help me with the following Shutdown[] lines interpretation ?

pidina a

pid Arguments
1 proc/boot/procnto
2 devc-serpxa250 -e 0x40100000,22 0x40200000,21 0x40700000,20
4103 sh
28675 pidin a

shutdown -vvvvv

Shutting down apps…
sh

Shutdown[0,0] S/C/F=10/1/5 C/D=fe005f98/fe050ec8 state(41)= lock 1
[0]PID-TID=-509599743-2? P/T FL=e31c0402/fe02ffac " R á?ß-é°LâÐMâ"
[0]ACTIVE PID=1 PF=00019001 “proc/boot/procnto”
[0]ASPACE PID=32771 PF=00000000 “bin/shutdown”
armle context[fe054908]:
0000: 00000000 00000001 00000028 a00000d3 0000001a fc404000 fe286008
00000001
0020: fe1503a3 0000000d fe04e488 fe285efc fe058e2c fe05494c fe058e20
fe05d154
0040: a00000d3
instruction[fe05d154]:
be 70 d8 e1 90 c0 a0 e3 05 cc 8c e3 0c c0 85 e0 00 00 37 e3 04 00 00 1a

00

00
stack[fe05494c]:
0000: 00000000 f86dc173 fc4040a0 fe050458 00000000 00000000 fe286008
00000001
0020: 00000000 0000000d fe04e488 fe285efc fc407018 fe285eec fe022d38
fe022d7c
0040: 8000001f fe054aa0 fe0539e0 02ffff00 00000005 00000000 00000000
00000000
0060: 05020000 00000000 0000000e 00000002 00000000 00000001 0000000e
00000000

QNX 6.3.0 IPL
…

Is it a kernel crash too? It happens during system restart.
Under QNX 6.2.1 we don’t see these messages.

Regards,
Jacek

Sunil_Kittur1 · May 25, 2005, 1:12pm

Jacek Rudnicki wrote:

With the “busy loop” reboot callout routine
0: b 0b
and the same runtime as below I get:

under QNX 6.2.1

Shutdown[0,0] S/C/F=4/1/1 C/D=fe005de0/fe048500 state(c0)= now lock
[0]PID-TID=1-7? P/T FL=00019001/05020000 “proc/boot/procnto”
[0]ASPACE PID=24579 PF=00000010 “proc/boot/shutdown”
armle context[ff7f5f98]:
0000: fc404000 00000000 fc4040a0 fe0480c0 00000000 fe0480c4 ff7ed008
00000001
0020: 00000000 0000000c fe046448 ff7f5fec ff7f5fdc ff7f5fdc fe01f174
fc4044d8
0040: 00000013
instruction[fc4044d8]:
58 46 40 fc 00 90 28 00 b0 46 40 fc d8 46 40 fc 00 47 40 fc 00 00 00 00 00
00
stack[ff7f5fdc]:
0000: ff7fd550 ff7f5ffc ff7f5ff0 fe031694 fe01f140 ff7eef1c ff7f6000
fe01f5dc
0020: fe031678 ff7f62a8 00000008 e88d000f e24e1004 e14f2000 e1a0300d
e10f0000
0040: e3c0001f e3800013 e129f000 e59f0078 e5900000 e3300000 059f0074
11a0000d
0060: 05900000 02800f43 e9200006 e202201f e3320013 19606000 09206000
e1a0d000

This is attempting to execute something in the syspage that is
not executable code. I’m guessing it’s calling the reboot callout,
but for some reason it is jumping to the wrong location in the
syspage. If you do a startup -vvv to show the syspage contents,
is the reboot callout at 0xfc4044d8?

under QNX 6.3

Shutdown[0,0] S/C/F=4/1/1 C/D=fe005f98/fe050ec8 state(c0)= now lock
[0]PID-TID=1-4? P/T FL=00019001/05020000 “proc/boot/procnto”
[0]ASPACE PID=90114 PF=00000000 “bin/shutdown”
armle context[fe05af98]:
0000: fc404000 00000000 fc4040a0 fe050458 00000000 fe05045c fe28b008
00000001
0020: 00000000 0000000d fe04e488 fe05afec fe05afdc fe05afdc fe022d38
fc4044e8
0040: 00000013
instruction[fc4044e8]:
68 46 40 fc 00 90 28 00 c0 46 40 fc e8 46 40 fc 10 47 40 fc 00 00 00 00 00
00
stack[fe05afdc]:
0000: fe054880 fe05affc fe05aff0 fe0363c4 fe022d04 fe28aefc fe05b000
fe0231a0
0020: fe0363a8 fe05b070 00000030 fe05b00d fe05b011 fe05b015 fe05b019
fe05b01d
0040: 00000001 fe05b210 00000010 a3da8b14 00000000 00000000 fc404000
a3dacb14
0060: 00000000 fe053f50 00000000 00000000 00000000 00000000 00000000
00000000

Here again, it is jumping to something in the syspage that is not
executable code. Is your reboot callout at 0xfc4044e8?
What is the output from startup -vvv?

If that works OK, it would be useful to see your reboot callout
code to see if there’s anything that might be affected by the
differences between 621 and 630.

Where should I send my reboot callout code?
Directly to you or maybe to support?

I would like to figure out first why you get the crashes shown
above - something doesn’t seem right with the way you set up the
busy-loop callout.

Sunil.

Jacek_Rudnicki · May 25, 2005, 2:30pm

Uzytkownik “Sunil Kittur” <skittur@qnx.com> napisal w wiadomosci
news:d71t11$eqq$1@inn.qnx.com…

Jacek Rudnicki wrote:
With the “busy loop” reboot callout routine
0: b 0b
and the same runtime as below I get:

under QNX 6.2.1

Shutdown[0,0] S/C/F=4/1/1 C/D=fe005de0/fe048500 state(c0)= now lock
[0]PID-TID=1-7? P/T FL=00019001/05020000 “proc/boot/procnto”
[0]ASPACE PID=24579 PF=00000010 “proc/boot/shutdown”
armle context[ff7f5f98]:
0000: fc404000 00000000 fc4040a0 fe0480c0 00000000 fe0480c4 ff7ed008
00000001
0020: 00000000 0000000c fe046448 ff7f5fec ff7f5fdc ff7f5fdc fe01f174
fc4044d8
0040: 00000013
instruction[fc4044d8]:
58 46 40 fc 00 90 28 00 b0 46 40 fc d8 46 40 fc 00 47 40 fc 00 00 00 00
00
00
stack[ff7f5fdc]:
0000: ff7fd550 ff7f5ffc ff7f5ff0 fe031694 fe01f140 ff7eef1c ff7f6000
fe01f5dc
0020: fe031678 ff7f62a8 00000008 e88d000f e24e1004 e14f2000 e1a0300d
e10f0000
0040: e3c0001f e3800013 e129f000 e59f0078 e5900000 e3300000 059f0074
11a0000d
0060: 05900000 02800f43 e9200006 e202201f e3320013 19606000 09206000
e1a0d000

This is attempting to execute something in the syspage that is
not executable code. I’m guessing it’s calling the reboot callout,
but for some reason it is jumping to the wrong location in the
syspage. If you do a startup -vvv to show the syspage contents,
is the reboot callout at 0xfc4044d8?

→ QNX 6.2.1

Here is a part of syspage contents:

Section:callout offset:0x000000a0 size:0x00000048
reboot:fc4048b4 power:fc4048e0
timer_load:fc4048f8 reload:fc404930 value:fc404968
0) display:fc404990 poll:fc4049b4 break:fc4049d8

display:00000000 poll:00000000 break:00000000

with fail at instruction[fc404520]:
a0 46 40 fc 00 90 28 00 f8 46 40 fc 20 47 40 fc 48 47 40 fc 00 00 00 00 00
00

under QNX 6.3

Shutdown[0,0] S/C/F=4/1/1 C/D=fe005f98/fe050ec8 state(c0)= now lock
[0]PID-TID=1-4? P/T FL=00019001/05020000 “proc/boot/procnto”
[0]ASPACE PID=90114 PF=00000000 “bin/shutdown”
armle context[fe05af98]:
0000: fc404000 00000000 fc4040a0 fe050458 00000000 fe05045c fe28b008
00000001
0020: 00000000 0000000d fe04e488 fe05afec fe05afdc fe05afdc fe022d38
fc4044e8
0040: 00000013
instruction[fc4044e8]:
68 46 40 fc 00 90 28 00 c0 46 40 fc e8 46 40 fc 10 47 40 fc 00 00 00 00
00
00
stack[fe05afdc]:
0000: fe054880 fe05affc fe05aff0 fe0363c4 fe022d04 fe28aefc fe05b000
fe0231a0
0020: fe0363a8 fe05b070 00000030 fe05b00d fe05b011 fe05b015 fe05b019
fe05b01d
0040: 00000001 fe05b210 00000010 a3da8b14 00000000 00000000 fc404000
a3dacb14
0060: 00000000 fe053f50 00000000 00000000 00000000 00000000 00000000
00000000

Here again, it is jumping to something in the syspage that is not
executable code. Is your reboot callout at 0xfc4044e8?
What is the output from startup -vvv?

→ QNX 6.3

Section:callout offset:0x000000a0 size:0x00000048
reboot:fc40487c power:fc4048b4
timer_load:fc4048cc reload:fc404904 value:fc40494c
0) display:fc404974 poll:fc404998 break:fc4049bc

display:00000000 poll:00000000 break:00000000

with fail at instruction[fc4044e8]:
68 46 40 fc 00 90 28 00 c0 46 40 fc e8 46 40 fc 10 47 40 fc 00 00 00 00 00
00

In both cases crash instruction is below the base address of callout reboot.

Jacek

If that works OK, it would be useful to see your reboot callout
code to see if there’s anything that might be affected by the
differences between 621 and 630.

Where should I send my reboot callout code?
Directly to you or maybe to support?

I would like to figure out first why you get the crashes shown
above - something doesn’t seem right with the way you set up the
busy-loop callout.

Sunil.

Sunil_Kittur1 · May 25, 2005, 4:13pm

Jacek Rudnicki wrote:

Uzytkownik “Sunil Kittur” <> skittur@qnx.com> > napisal w wiadomosci
news:d71t11$eqq$> 1@inn.qnx.com> …

Jacek Rudnicki wrote:

With the “busy loop” reboot callout routine
0: b 0b
and the same runtime as below I get:

under QNX 6.2.1

Shutdown[0,0] S/C/F=4/1/1 C/D=fe005de0/fe048500 state(c0)= now lock
[0]PID-TID=1-7? P/T FL=00019001/05020000 “proc/boot/procnto”
[0]ASPACE PID=24579 PF=00000010 “proc/boot/shutdown”
armle context[ff7f5f98]:
0000: fc404000 00000000 fc4040a0 fe0480c0 00000000 fe0480c4 ff7ed008
00000001
0020: 00000000 0000000c fe046448 ff7f5fec ff7f5fdc ff7f5fdc fe01f174
fc4044d8
0040: 00000013
instruction[fc4044d8]:
58 46 40 fc 00 90 28 00 b0 46 40 fc d8 46 40 fc 00 47 40 fc 00 00 00 00

00

00
stack[ff7f5fdc]:
0000: ff7fd550 ff7f5ffc ff7f5ff0 fe031694 fe01f140 ff7eef1c ff7f6000
fe01f5dc
0020: fe031678 ff7f62a8 00000008 e88d000f e24e1004 e14f2000 e1a0300d
e10f0000
0040: e3c0001f e3800013 e129f000 e59f0078 e5900000 e3300000 059f0074
11a0000d
0060: 05900000 02800f43 e9200006 e202201f e3320013 19606000 09206000
e1a0d000

This is attempting to execute something in the syspage that is
not executable code. I’m guessing it’s calling the reboot callout,
but for some reason it is jumping to the wrong location in the
syspage. If you do a startup -vvv to show the syspage contents,
is the reboot callout at 0xfc4044d8?

→ QNX 6.2.1

Here is a part of syspage contents:

Section:callout offset:0x000000a0 size:0x00000048
reboot:fc4048b4 power:fc4048e0
timer_load:fc4048f8 reload:fc404930 value:fc404968
0) display:fc404990 poll:fc4049b4 break:fc4049d8

display:00000000 poll:00000000 break:00000000

with fail at instruction[fc404520]:
a0 46 40 fc 00 90 28 00 f8 46 40 fc 20 47 40 fc 48 47 40 fc 00 00 00 00 00
00

I don’t understand why you end up executing code at that address.
The register dump above seems to be consistent with the kernel
code that calls the reboot callout:

r0 contains the address of the syspage = 0xfc404000
r2 contains the address of the syspage callout entry:
0xfc4040a0 = syspage (0xfc404000) + callout offset (0xa0)
From that point, the kernel code just jumps to the pointer stored
at 0xfc4040a0, which startup reported to be 0xfc4048b4.

Can you post the reboot callout code you are using in this case?

I especially don’t understand what is wrong here because you said
your original reboot callout does work fine on 6.2.1.

under QNX 6.3

Shutdown[0,0] S/C/F=4/1/1 C/D=fe005f98/fe050ec8 state(c0)= now lock
[0]PID-TID=1-4? P/T FL=00019001/05020000 “proc/boot/procnto”
[0]ASPACE PID=90114 PF=00000000 “bin/shutdown”
armle context[fe05af98]:
0000: fc404000 00000000 fc4040a0 fe050458 00000000 fe05045c fe28b008
00000001
0020: 00000000 0000000d fe04e488 fe05afec fe05afdc fe05afdc fe022d38
fc4044e8
0040: 00000013
instruction[fc4044e8]:
68 46 40 fc 00 90 28 00 c0 46 40 fc e8 46 40 fc 10 47 40 fc 00 00 00 00

00

00
stack[fe05afdc]:
0000: fe054880 fe05affc fe05aff0 fe0363c4 fe022d04 fe28aefc fe05b000
fe0231a0
0020: fe0363a8 fe05b070 00000030 fe05b00d fe05b011 fe05b015 fe05b019
fe05b01d
0040: 00000001 fe05b210 00000010 a3da8b14 00000000 00000000 fc404000
a3dacb14
0060: 00000000 fe053f50 00000000 00000000 00000000 00000000 00000000
00000000

Here again, it is jumping to something in the syspage that is not
executable code. Is your reboot callout at 0xfc4044e8?
What is the output from startup -vvv?

→ QNX 6.3

Section:callout offset:0x000000a0 size:0x00000048
reboot:fc40487c power:fc4048b4
timer_load:fc4048cc reload:fc404904 value:fc40494c
0) display:fc404974 poll:fc404998 break:fc4049bc

display:00000000 poll:00000000 break:00000000

with fail at instruction[fc4044e8]:
68 46 40 fc 00 90 28 00 c0 46 40 fc e8 46 40 fc 10 47 40 fc 00 00 00 00 00
00

In both cases crash instruction is below the base address of callout reboot.

Yes - the crashing instruction in both cases is 0x394 bytes
before the reboot code. If the reboot code is single instruction
that branches back to itself, I don’t understand how you could
have ended up executing at this other address - I need to see
your reboot callout code to see if there’s anything odd there.

Sunil.

Jacek_Rudnicki · May 30, 2005, 8:36am

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.

Regards,
Jacek

Uzytkownik “Sunil Kittur” <skittur@qnx.com> napisal w wiadomosci
news:d727kq$m5o$1@inn.qnx.com…

Jacek Rudnicki wrote:
Uzytkownik “Sunil Kittur” <> skittur@qnx.com> > napisal w wiadomosci
news:d71t11$eqq$> 1@inn.qnx.com> …

Jacek Rudnicki wrote:

With the “busy loop” reboot callout routine
0: b 0b
and the same runtime as below I get:

under QNX 6.2.1

Shutdown[0,0] S/C/F=4/1/1 C/D=fe005de0/fe048500 state(c0)= now lock
[0]PID-TID=1-7? P/T FL=00019001/05020000 “proc/boot/procnto”
[0]ASPACE PID=24579 PF=00000010 “proc/boot/shutdown”
armle context[ff7f5f98]:
0000: fc404000 00000000 fc4040a0 fe0480c0 00000000 fe0480c4 ff7ed008
00000001
0020: 00000000 0000000c fe046448 ff7f5fec ff7f5fdc ff7f5fdc fe01f174
fc4044d8
0040: 00000013
instruction[fc4044d8]:
58 46 40 fc 00 90 28 00 b0 46 40 fc d8 46 40 fc 00 47 40 fc 00 00 00 00

00

00
stack[ff7f5fdc]:
0000: ff7fd550 ff7f5ffc ff7f5ff0 fe031694 fe01f140 ff7eef1c ff7f6000
fe01f5dc
0020: fe031678 ff7f62a8 00000008 e88d000f e24e1004 e14f2000 e1a0300d
e10f0000
0040: e3c0001f e3800013 e129f000 e59f0078 e5900000 e3300000 059f0074
11a0000d
0060: 05900000 02800f43 e9200006 e202201f e3320013 19606000 09206000
e1a0d000

This is attempting to execute something in the syspage that is
not executable code. I’m guessing it’s calling the reboot callout,
but for some reason it is jumping to the wrong location in the
syspage. If you do a startup -vvv to show the syspage contents,
is the reboot callout at 0xfc4044d8?

→ QNX 6.2.1

Here is a part of syspage contents:

Section:callout offset:0x000000a0 size:0x00000048
reboot:fc4048b4 power:fc4048e0
timer_load:fc4048f8 reload:fc404930 value:fc404968
0) display:fc404990 poll:fc4049b4 break:fc4049d8

display:00000000 poll:00000000 break:00000000

with fail at instruction[fc404520]:
a0 46 40 fc 00 90 28 00 f8 46 40 fc 20 47 40 fc 48 47 40 fc 00 00 00 00
00
00

I don’t understand why you end up executing code at that address.
The register dump above seems to be consistent with the kernel
code that calls the reboot callout:

r0 contains the address of the syspage = 0xfc404000

r2 contains the address of the syspage callout entry:
0xfc4040a0 = syspage (0xfc404000) + callout offset (0xa0)
From that point, the kernel code just jumps to the pointer stored
at 0xfc4040a0, which startup reported to be 0xfc4048b4.

Can you post the reboot callout code you are using in this case?

I especially don’t understand what is wrong here because you said
your original reboot callout does work fine on 6.2.1.

under QNX 6.3

Shutdown[0,0] S/C/F=4/1/1 C/D=fe005f98/fe050ec8 state(c0)= now lock
[0]PID-TID=1-4? P/T FL=00019001/05020000 “proc/boot/procnto”
[0]ASPACE PID=90114 PF=00000000 “bin/shutdown”
armle context[fe05af98]:
0000: fc404000 00000000 fc4040a0 fe050458 00000000 fe05045c fe28b008
00000001
0020: 00000000 0000000d fe04e488 fe05afec fe05afdc fe05afdc fe022d38
fc4044e8
0040: 00000013
instruction[fc4044e8]:
68 46 40 fc 00 90 28 00 c0 46 40 fc e8 46 40 fc 10 47 40 fc 00 00 00 00

00

00
stack[fe05afdc]:
0000: fe054880 fe05affc fe05aff0 fe0363c4 fe022d04 fe28aefc fe05b000
fe0231a0
0020: fe0363a8 fe05b070 00000030 fe05b00d fe05b011 fe05b015 fe05b019
fe05b01d
0040: 00000001 fe05b210 00000010 a3da8b14 00000000 00000000 fc404000
a3dacb14
0060: 00000000 fe053f50 00000000 00000000 00000000 00000000 00000000
00000000

Here again, it is jumping to something in the syspage that is not
executable code. Is your reboot callout at 0xfc4044e8?
What is the output from startup -vvv?

→ QNX 6.3

Section:callout offset:0x000000a0 size:0x00000048
reboot:fc40487c power:fc4048b4
timer_load:fc4048cc reload:fc404904 value:fc40494c
0) display:fc404974 poll:fc404998 break:fc4049bc

display:00000000 poll:00000000 break:00000000

with fail at instruction[fc4044e8]:
68 46 40 fc 00 90 28 00 c0 46 40 fc e8 46 40 fc 10 47 40 fc 00 00 00 00
00
00

In both cases crash instruction is below the base address of callout
reboot.

Yes - the crashing instruction in both cases is 0x394 bytes
before the reboot code. If the reboot code is single instruction
that branches back to itself, I don’t understand how you could
have ended up executing at this other address - I need to see
your reboot callout code to see if there’s anything odd there.

Sunil.

Sunil_Kittur1 · May 31, 2005, 8:51am

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.

Shutdown problem on QNX6.3

pidina a

shutdown -vvvvv

pidina a

shutdown -vvvvv

pidina a

shutdown -vvvvv

pidina a

shutdown -vvvvv

– cburgess@qnx.com \

pidina a

shutdown -vvvvv

html \

cburgess@qnx.com \

pidina a

shutdown -vvvvv

– cburgess@qnx.com \

pidina a

shutdown -vvvvv

html \

cburgess@qnx.com \

cburgess@qnx.com \

pidina a

shutdown -vvvvv

html \

cburgess@qnx.com \

cburgess@qnx.com \

pidina a

shutdown -vvvvv

html \

cburgess@qnx.com \

cburgess@qnx.com \

pidina a

shutdown -vvvvv

You can read the technote at file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump. html \

cburgess@qnx.com \

cburgess@qnx.com \

pidina a

shutdown -vvvvv

You can read the technote at file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump. html \

cburgess@qnx.com \

cburgess@qnx.com \

pidina a

shutdown -vvvvv

pidina a

shutdown -vvvvv

shutdown -vvv

shutdown -vvv

shutdown -vvv

shutdown -vvv

–
cburgess@qnx.com

\

html

\

cburgess@qnx.com

\

–
cburgess@qnx.com

\

html

\

cburgess@qnx.com

\

cburgess@qnx.com

\

html

\

cburgess@qnx.com

\

cburgess@qnx.com

\

html

\

cburgess@qnx.com

\

cburgess@qnx.com

\

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

\

cburgess@qnx.com

\

cburgess@qnx.com

\

You can read the technote at

file:///C:/QNX630/target/qnx6/usr/help/product/neutrino/technotes/proc_dump.

html

\

cburgess@qnx.com

\

cburgess@qnx.com

\