Any idea why Proc has crashed here? It happened 3 times in a row at
boot time. How does one interpret such a dump?
Version 4.25L Feb 15 2001 Technical support …
Proc fault 1, ldt 100 sys/Proc32; fault e+2
cs:eip=5:1004e ss:esp=d:f7c0fb0 efl=12246 ds=d es=d fs=0 gs=0
eax/1b5e0 ebx/100 ecx 3822 edx/0 esi/1b490 edi/2 ebp/f7c0fb4
Stack (d:f7c0fb0)
00000000 0f7c0fe8 00000000 0000595d 0000001b 00003822 0f7c0fd0 0000580e
00003820 0000000d 00000610 00003820 0000000d 000001d2 00000001 00005945
0000595d 0f7c0925 00000678 00005988 00000000 00000000 1000717f ff406380
000007ff ff00b380 b00000ff 0000b300 0000ffff 00cfb300 01cec010 00c0b30b
Process Entry (addr 6050)
00000000 00000001 00000000 00000001 00000000 00000000 30020207 00001e1e
00005838 0100000d 00006108 ffffffff 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000501 000d0005 00007118 00000000 00000001
0000000c 00000000 0000004a 0000c140 00000000 00000000 00010090 00000000
00000000 00000000 00000000 ffff0001 00000000 00000000 00000000
Thanks in advance
William Morris
wrm@innovation-tk.com
I think only QSSL can interpret these dumps.
But the obvious question is what have you changed. If it happens during the
boot process did you just change your boot image? Can you go back you your
old boot image? (That’s what I use .altboot for.)
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net
“William Morris” <wrm@innovation-tk.com> wrote in message
news:9qop9v$o3h$2@inn.qnx.com…
Any idea why Proc has crashed here? It happened 3 times in a row at
boot time. How does one interpret such a dump?
Version 4.25L Feb 15 2001 Technical support …
Proc fault 1, ldt 100 sys/Proc32; fault e+2
cs:eip=5:1004e ss:esp=d:f7c0fb0 efl=12246 ds=d es=d fs=0 gs=0
eax/1b5e0 ebx/100 ecx 3822 edx/0 esi/1b490 edi/2 ebp/f7c0fb4
Stack (d:f7c0fb0)
00000000 0f7c0fe8 00000000 0000595d 0000001b 00003822 0f7c0fd0 0000580e
00003820 0000000d 00000610 00003820 0000000d 000001d2 00000001 00005945
0000595d 0f7c0925 00000678 00005988 00000000 00000000 1000717f ff406380
000007ff ff00b380 b00000ff 0000b300 0000ffff 00cfb300 01cec010 00c0b30b
Process Entry (addr 6050)
00000000 00000001 00000000 00000001 00000000 00000000 30020207 00001e1e
00005838 0100000d 00006108 ffffffff 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000501 000d0005 00007118 00000000 00000001
0000000c 00000000 0000004a 0000c140 00000000 00000000 00010090 00000000
00000000 00000000 00000000 ffff0001 00000000 00000000 00000000
Thanks in advance
William Morris
wrm@innovation-tk.com
“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
I think only QSSL can interpret these dumps.
But the obvious question is what have you changed. If it happens during the
boot process did you just change your boot image? Can you go back you your
old boot image? (That’s what I use .altboot for.)
We didn’t change anything. Honest!
There was just this sequence of reboots which failed, followed by
success. My feeling is that the h/w is broken but I get little
sympathy - (“those s/w engineers, always blaming the h/w instead of
finding the problems in their own code”).
Regards
William Morris
wrm@innovation-tk.com
“William Morris” <wrm@innovation-tk.com> wrote
But the obvious question is what have you changed. If it happens during
the
boot process did you just change your boot image? Can you go back you
your
old boot image? (That’s what I use .altboot for.)
We didn’t change anything. Honest!
There was just this sequence of reboots which failed, followed by
success. My feeling is that the h/w is broken but I get little
sympathy - (“those s/w engineers, always blaming the h/w instead of
finding the problems in their own code”).
OK. My personal feeling is, wether the problem was sofware or hardware,
when a problem fixes itself, it’s just hiding from you. I.E. It’s probibly
still broken.
If you think it’s HW, giggle cables, cards, etc, until you get it fail
again. Then you’ll know what device it is.
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net
Also if you happen to have spare parts around, try swapping them
and see if the problem re-occurs. Try easy stuff first, i.e. RAM.
Erick.
“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
“William Morris” <> wrm@innovation-tk.com> > wrote
But the obvious question is what have you changed. If it happens during
the
boot process did you just change your boot image? Can you go back you
your
old boot image? (That’s what I use .altboot for.)
We didn’t change anything. Honest!
There was just this sequence of reboots which failed, followed by
success. My feeling is that the h/w is broken but I get little
sympathy - (“those s/w engineers, always blaming the h/w instead of
finding the problems in their own code”).
OK. My personal feeling is, wether the problem was sofware or hardware,
when a problem fixes itself, it’s just hiding from you. I.E. It’s probibly
still broken.
If you think it’s HW, giggle cables, cards, etc, until you get it fail
again. Then you’ll know what device it is.
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net