Oleh Derevenko(deleted)
|
Re: RE: RE: M2 build and 6.3.0 SP3
|
Oleh Derevenko(deleted)
11/28/2007 3:13 PM
post3061
|
Re: RE: RE: M2 build and 6.3.0 SP3
Hi Brian
> The 6.3.2 released in May/June 2006 isn't the same 6.3.2 which was released
> in September 2007. The former was a kernel update and the latter is a
> baseline release, and is the only supported platform for building the M2
> build.
I did not build it myself. I downloaded binaries from your site.
However it does not matter if it is extracted over 6.3.0SP3 or 6.3.2. Today I've unpacked it over 6.3.2 installation
downloaded from the link you provided and it crashes as well.
By the way, the image with Memory Partition libraries does not boot at all. I have to build it without [+keeplinked
module=apm module=partmgr]. You can find my boot image build script in attachment.
> Once you upgrade to Sept 2007 6.3.2, if you're seeing crashes, you can
> either seek help here or submit a support ticket if you have a plan.
No, I do not currently have a support plan. And as far as I understood from conversation with your developers last year
you did not have any means for tracking down crashes like this remotely. :(
Well, maybe I could send you some of my applications if you would agree to run them in your test machine. However with
just few processes running it could not always be easy to reproduce. You may have to restart it several times.
>
> With regards to the causes of kernel crashes, there is a list at the
> following URL:
http://community.qnx.com/sf/wiki/do/viewPage/projects.core_os/wiki/Kernel_Cr
> ashed_Common_Causes
Those all are unlikely. It is a user-mode application and most of those causes are hardware access or driver related.
Memory usage at the time of crash is around 60%.
> We also have a primer on debugging kernel crashes in our technotes, which
> you can find here:
http://www.qnx.com/developers/docs/6.3.2/neutrino/technotes/proc_dump.html
Well, most of the times it only displays Crash[0, 0] at ker_timer 359 or nano_sched 1333. Sometimes it does not display
any message at all. I could see a dump like in that example only once. The "screenshot" ;) for it is in attachment as
well.
|
|
|