Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Boot falilure: (2 Items)
   
Boot falilure  
Hi everyone,

I'm having an weird problem in the boot process of QNX 6.3.0 SP3 on a AMD Geode LX800 board.
Every 10 out of 1000 (1%) of the boots fail.
It fails just after starting the OS image created with the build below.
The screen output looks like:

QNX 6.3.0 SP3"

---> Starting PCI Services
Can't locate PNP bios (No errors)
---> Starting Console Manager
Unable to start "devc-con" (8)
Unable to access "/dev/con1" (2)
Unable to access "/dev/con1" (2)
---> Starting EIDE Driver
Unable to start "mount" (8)
---> Starting /etc/system/sysinit

and it hangs here. This happens in 1% of the boots.

Does anyone have an idea of what could cause this? We have experienced this behaviour in 2 boards.

Regards,

Leonel


Build file used to create the image:

[virtual=x86,bios +compress] boot = { 
	# Reserve 64k of video memory to handle multiple video cards 
	startup-bios 
	# PATH is the *safe* path for executables (confstr(_CS_PATH...)) 
	# LD_LIBRARY_PATH is the *safe* path for libraries (confstr(_CS_LIBPATH)) 
	# i.e. This is the path searched for libs in setuid/setgid executables. 
	PATH=/proc/boot:/bin:/usr/bin:/opt/bin:/sbin:/usr/sbin:/opt/sbin LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll:/opt
/lib procnto
} 

[+script] startup-script = {
    display_msg "  "
    display_msg "QNX 6.3.0 SP3"
    display_msg "  "

    procmgr_symlink ../../proc/boot/libc.so.2 /usr/lib/ldqnx.so.2

    display_msg "---> Starting PCI Services"
    seedres
    pci-bios &
    waitfor /dev/pci

    display_msg "---> Starting Console Manager"
    devc-con -n2
    waitfor /dev/con1
    reopen /dev/con1
    
    display_msg "---> Starting EIDE Driver"
    devb-eide blk noatime auto=partition dos exe=all cam quiet

    # Mount one QNX 4 filesystem as /, and another as /home.
    # Also, mount a DOS partition and the CD drive.

    waitfor /dev/hd0
    mount /dev/hd0t79 /

#	display_msg "---> Starting Pipe, Slogger & Queue Services"
#	slogger
#	pipe
#	mqueue

    display_msg "---> Starting /etc/system/sysinit"
    ksh -c /etc/system/sysinit
}

libc.so
libcam.so
io-blk.so
cam-disk.so
fs-qnx4.so

[data=c]
seedres
pci-bios
devb-eide
ksh
devc-con
mount


Re: Boot falilure  
It's weird indeed, because when it cannot start devc-con, it means something is pretty wrong with the boot image, 
because devc-con is in there.

Either the boot image was not correctly loaded from the boot media.

Or the boot image is corrupt in RAM. 

What is your boot media? Maybe it's a CF card not behaving correctly. CF cards generally are tricky because they have 
built-in, undocumented controllers.

Maybe your RAM is faulty, but I guess you didn't use the same RAM on both of the boards?

Maybe it's a BIOS issue - the boot loader uses BIOS calls to load the boot image. Is there a BIOS update available ? 
It's worth a try.

Furthermore, have you tried QNX Neutrino 6.4? 


- Malte