Re: Kernel hangs while loading udevice.exe
- From: bhoj <vishalbhoj@xxxxxxxxx>
- Date: Tue, 21 Oct 2008 01:43:44 -0700 (PDT)
I tried with disabling the drivers but it still doesn't execute. At
loading udevice.exe it calls oemidle function and keeps printing the
alphabet d. There is no thread i suppose to wake at that point. what
will the kernel be waiting for at that point ?
On Oct 21, 1:41 am, "Michel Verhagen (eMVP)" <mic...@xxxxxxxxxx>
wrote:
What happens if you exclude those user mode device drivers from the
build? Add them one by one again, and see which one is the culprit. Then
add debug messages to your driver and see exactly where it goes wrong.
Good luck,
Michel Verhagen, eMVP
Check out my blog:http://GuruCE.com/blog
GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.
bhoj wrote:
Hi all,
I am trying to port omap 2420 BSP to 2430. I have built the
bootloader. the Kitl connects to the PB and starts giving the debug
msgs. The kernel hangs at udevice.exe . Is it because few drivers
which are for 2420 are getting built along with this modified bsp ?
Here is the log which i get . this is on the serial port without kitl.
Windows CE Kernel for ARM (Thumb Enabled) Built on Sep 6 2006 at
19:11:16
ProcessorType=0b36 Revision=5
OEMAddressTable = 84005ad4
+OEMInit
Cache:
L1Flags: 0x00000000
L1ISetsPerWay: 0x00000100 (256)
L1INumWays: 0x00000004 (4)
L1ILineSize: 0x00000020 (32)
L1ISize: 0x00008000 (32768)
L1DSetsPerWay: 0x00000100 (256)
L1DNumWays: 0x00000004 (4)
L1DLineSize: 0x00000020 (32)
L1DSize: 0x00008000 (32768)
+OALInterruptInit
+OEMInterruptEnable(1, 0x0, 0)
-OALInterruptInit(rc = 1)
Intr Init done
+OALTimerInit(1, 0, 0)
+OALTimerInit(1, 33, 2)
+OALIntrRequestSysIntr(1, 0x85236010, 0x00000004)
+OEMInterruptEnable(16, 0x0, 0)
1011Timer Init done...
OEMInit:initializing FOR FAC,HDQ
Setting up softlog at 0x85ffc000 for 0x800 entries
Booting Windows CE version 6.00 for (ARM)
&pTOC = 85287c1c, pTOC = 8521f4f8, pTOC->ulRamFree = 8528c000,
MemForPT = 00001000
Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 3436, Secondary pages: 0, Filesystem pages
= 134
Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 8528e000, extension: 00002000, length: 00d6c000
NKStartup done, starting up kernel.
Windows CE KernelInit
Reserve VM for kernel XIP DLls, first = c0010000, last = c0b40000
g_pprcNK == 0x85285aa0
Updated eptr->e32_vsize to = 00009000
Initializing Memory Mapped File Support
Scheduling the first thread.
Detecting VFP... VFP Not Found!
LoaderInit: Initialing loader
Updated eptr->e32_vsize to = 00009000
Updated eptr->e32_vsize to = 000a2000
Updated eptr->e32_vsize to = 00022000
Heap Statistics at 0xC018A980
PGPOOL: Reserved 768 pages for Loader pool
PGPOOL: Reserved 256 pages for File pool
OSAXST0: Platform Name =
OSAXST1: >>> Loading Module 'kd.dll' (0x85FDB87C) at address
0xC0010000-0xC0045000 in Process 'NK.EXE' (0x85285AA0)
KD: Starting kernel debugger software probe (KdStub) - KD API version
22
OSAXST1: >>> Loading Module 'NK.EXE' (0x85285AA0) at address
0x84000000-0x84009000 in Process 'NK.EXE' (0x85285AA0)
Message Queue support initialized, g_hMsgQHeap = d0040750
OSAXST1: >>> Loading Module 'filesys.dll' (0x85FB6564) at address
0xC01C0000-0xC0259000 in Process 'NK.EXE' (0x85285AA0)
OSAXST1: >>> Loading Module 'k.fpcrt.dll' (0x85FB66AC) at address
0xC01A0000-0xC01B8000 in Process 'NK.EXE' (0x85285AA0)
OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x85FB67F4) at address
0xC0540000-0xC0585000 in Process 'NK.EXE' (0x85285AA0)
FSDMGR!DllMain: DLL_PROCESS_ATTACH
CertMod.dll not found, using old OEM Trust Model
FileSystem Starting - starting with clean file system
FSDMGR!STOREMGR_Initialize
FSDMGR!InitializeStoreAPI
FSDMGR!MountTable_t::RegisterVolumeName: Registered "StoreMgr" at
index 2FSDMGR!MountTable_t::RegisterVolume: Registered volume at index
2 (Name="StoreMgr", MountFlags=0x1)FSDMGR!InitializeROMFileSystem:
File System=ROM
OSAXST1: >>> Loading Module 'romfsd.dll' (0x85FA0AB0) at address
0xC0260000-0xC0267000 in Process 'NK.EXE' (0x85285AA0)
FSDMGR!MountTable_t::RegisterVolumeName: Registered "ROM" at index
3FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3
(Name="ROM", MountFlags=0x71)Warning: unable to protect OEM reg keys
FSVOL: Opening existing volume
FSVOL: Volume heap already initialized
FSREG: Mounted ROM portion of boot registry
FSVOL: Creating clean virtual volume
FSVOL: Initializing volume heap
FSREG: Mounted RAM portion of boot registry
FS: Creating signal event SYSTEM/DevMgrApiSetReady
FS: Creating signal event SYSTEM/PowerManagerReady
FS: Creating signal event SYSTEM/GweApiSetReady
FS: Creating signal event ReleaseFSD
FSREG: Unable to read value "Start DevMgr" under HKEY_LOCAL_MACHINE
\init\BootVars
FILESYS: Starting boot phase 0.
FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1)
FSDMGR: File security disabled.
FSDMGR!AutoLoadFileSystems: CurrentBootPhase=0, LoadFlags=1
FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System
\StorageManager\AutoLoad, FileSystem_t=ObjectStore
FILESYS: RAM File System FSD_MountDisk registering folder "Object
Store"
FSDMGR!MountTable_t::RegisterVolumeName: Registered "Object Store" at
index 4FSDMGR!MountTable_t::RegisterVolume: Registered volume at index
4 (Name="", MountFlags=0x46)FILESYS: Starting boot phase 1.
FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0)
FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1
FSDMGR!AutoLoadFileSystem: CurrentBootPhase=1, RootKey=System
\StorageManager\AutoLoad, FileSystem_t=Relfsd
OSAXST1: >>> Loading Module 'relfsd.dll' (0x85F81A10) at address
0xC04F0000-0xC04FF000 in Process 'NK.EXE' (0x85285AA0)
FILESYS: Starting device and waiting for boot file system.
OSAXST1: >>> Loading Module 'device.dll' (0x85F7809C) at address
0xC0450000-0xC0455000 in Process 'NK.EXE' (0x85285AA0)
OSAXST1: >>> Loading Module 'devmgr.dll' (0x85F781D4) at address
0xC0460000-0xC0487000 in Process 'NK.EXE' (0x85285AA0)
OSAXST1: >>> Loading Module 'k.ceddk.dll' (0x85F7830C) at address
0xC0620000-0xC062E000 in Process 'NK.EXE' (0x85285AA0)
OSAXST1: >>> Loading Module 'pm.dll' (0x85F78444) at address
0xC04B0000-0xC04D7000 in Process 'NK.EXE' (0x85285AA0)
*** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x400002 ***
Filesys: Loaded device.dll
FILESYS: Waiting for device manager to signal BootPhase1 completion.
FSDMGR!PNPThread: Using PNPUnloadDelay of 4096
FSDMGR!PNPThread: PNPThread starting!
+InitDeviceFileSystems
FSDMGR!MountTable_t::RegisterVolumeName: Registered "$device" at index
5FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 5
(Name="$device", MountFlags=0x1)FSDMGR!
MountTable_t::RegisterVolumeName: Registered "$bus" at index 6FSDMGR!
MountTable_t::RegisterVolume: Registered volume at index 6
(Name="$bus", MountFlags=0x1)-InitDeviceFileSystems: status is 1
Ceddk!CalibrateStallCounter: Enter
Ceddk!CalibrateStallCounter: Could not find stall counter
+OALTimerInit(d)
+OALTimerInit(d)
Ceddk!BeginCalibration: min(328) max(365)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
+OALTimerInit(d)
Ceddk!BeginCalibration: Elapsed is 338
Ceddk!BeginCalibration: Delay is 10
DEVICE!DevloadInit
DEVICE!InitDevices: Root Key is Drivers\BuiltIn.
DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix)
returned 2
DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn
\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'busenum.dll' (0x85F6EAA4) at address
0xC04A0000-0xC04AB000 in Process 'NK.EXE' (0x85285AA0)
DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\SPI
\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'buses.dll' (0x85F638B8) at address
0xC0A10000-0xC0A1E000 in Process 'NK.EXE' (0x85285AA0)
ERROR: SPI_Init: InterruptInitialize failed
DEVICE!LaunchDevice: Init() failed for device 0xd0049690
DEVICE!I_ActivateDeviceEx: couldn't activate: prefix SPI, index 1, dll
buses.dll, context 0xd025e67c
OSAXST1: <<< Unloading Module 'buses.dll' (0x85F638B8) at address
0xC0A10000-0xC0A1E000 in Process 'NK.EXE' (0x85285AA0)
DeviceFolder::LoadDevice(Drivers\BuiltIn\SPI) last 0 TicksDEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\MSFlash
\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'nandflsh.dll' (0x85F638B8) at address
0xC09E0000-0xC09FF000 in Process 'NK.EXE' (0x85285AA0)
Exception 'Data Abort' (4): Thread-Id=00a20002(pth=85f7857c), Proc-
Id=00400002(pprc=85285aa0) 'NK.EXE', VM-active=00400002(pprc=85285aa0)
'NK.EXE'
PC=c09f94cc(nandflsh.dll+0x000194cc) RA=c09f94ac(nandflsh.dll
+0x000194ac) SP=d025e144, BVA=00000000
Exception 'Raised Exception' (-1): Thread-Id=00a20002(pth=85f7857c),
Proc-Id=00400002(pprc=85285aa0) 'NK.EXE', VM-
active=00400002(pprc=85285aa0) 'NK.EXE'
PC=c00f9688(k.coredll.dll+0x00039688) RA=84046b74(kernel.dll
+0x00019b74) SP=d025d90c, BVA=ffffffff
DEVICE!LaunchDevice: exception in Init for device 0xd0049870
DEVICE!LaunchDevice: Init() failed for device 0xd0049870
DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
nandflsh.DLL, context 0xd025e67c
OSAXST1: <<< Unloading Module 'nandflsh.dll' (0x85F638B8) at address
0xC09E0000-0xC09FF000 in Process 'NK.EXE' (0x85285AA0)
DeviceFolder::LoadDevice(Drivers\BuiltIn\MSFlash) last 0 TicksFILESYS:
Waiting for bootable file system to be mounted.
FILESYS: Device started. Boot file system ready.
FSREG: Unable to read value "SystemHiveInitialSize" under
HKEY_LOCAL_MACHINE\init\BootVars
FSVOL: Opening existing volume
FSVOL: Volume heap already initialized
FSREG:
...
read more »
.
- References:
- Kernel hangs while loading udevice.exe
- From: bhoj
- Re: Kernel hangs while loading udevice.exe
- From: Michel Verhagen (eMVP)
- Kernel hangs while loading udevice.exe
- Prev by Date: Re: Can a touchscreen driver be written as a user mode driver?
- Next by Date: Re: Add Drivers to OS desing
- Previous by thread: Re: Kernel hangs while loading udevice.exe
- Next by thread: Kernel hangs while loading udevice.exe
- Index(es):
Relevant Pages
|
Loading
