Re: Filesys failed to initialize registry dirty, trying clean...

Tell us a bit more about your system, and show us your config.bib and OEMAddresstable. Also, try to create a kernel with RAM based registry and RAM/ROM filesystem first. That's the easier configuration and makes testing your memory config more clear.


Michel Verhagen, eMVP
Embedded Fusion
www.embeddedfusion.com
mverhagen at embeddedfusion dot com

Benson Wang wrote:
Hi All:

I am trying to porting our system from 64MB SDRAM to 128MB SDRAM.
I had changed config.bib & oemaddrtab_cfg.inc to 128MB.

When OS boots, it show below message and then lock ...

Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:21:58
ProcessorType=0920 Revision=0
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 8c219e04
DCache: 8 sets, 64 ways, 32 line size, 16384 size
ICache: 8 sets, 64 ways, 32 line size, 16384 size
+OALIntrInit: Set SYSINTR_WLAN as IRQ_EINT8 .

Error Reporting Memory Reserved, dump size = 00020000
Booting Windows CE version 5.00 for (ARM)
&pTOC = 8c20ac1c, pTOC = 8d08f030, pTOC->ulRamFree = 8d629000, MemForPT = 00000000

Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 27055, Secondary pages: 0, Filesystem pages = 13527

Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 8d62a000, extension: 00007000, length: 069af000
Sp=ffffc7cc
ARMInit done.
Windows CE KernelInit
Updated eptr->e32_vsize to = 000a9000
Scheduling the first thread.
0x93fdf024: KernelInit2: pCurThread=93fdf024 hCurThread=13fdf266 hCurProc=13fdf002, KernelInit = 8c228034
0x93fdf024: Detecting VFP...0x93fdf024: VFP Not Found!
0x93fdf024: first = 01e60000, last = 02000000, SharedDllBase = 031f0000
0x93fdf024: OEMIoControl: Unsupported Code 0x10100b4 - device 0x0101 func 45
0x93fc5000: CertMod.dll not found, using old OEM Trust Model
0x93fc5000: FileSystem Starting - starting with clean file system
0x93fc5000: +SMDK2410_OALIoCtlHalInitRTC(...)
0x93fc5000: +SMDK2410_OEMSetRealTime(2003/1/1 12:0:0.000)
0x93fc5000: -SMDK2410_OALIoCtlHalInitRTC(rc = 1)
0x93fc5000: FS: initializing ROM/RAM file system
0x93fc5000: SC_CreateAPIHandle: pvData == NULL
0x93fc5000: FS: Registering file system ROM, index 2, flags 0x00000031
0x93fc5000: FS: Mount complete (ROM, index 2, flags 0x00000031)
0x93fc5000: OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
0x93fc5000: Failed CheckFile 4
0x93fc5000: Filesys failed to initialize registry dirty, trying clean...
0x93fc5000: OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
0x93fc5000: InitSharedHeap: 4a000000 10000 c
0x93fc5000: InitSharedHeap: return 4a000060
0x93fc5000: FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars
0x93fc5000: FSREG: Logging in default user.
0x93fc5000: FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars
0x93fc5000: SetCurrentUser: Logging out (nobody), logging in default
0x93fc5000: FS: Using default path "\profiles\"
0x93fc5000: BuildPath: profiles
0x93fc5000: BuildPath: profiles\default
0x93fc5000: SetCurrentUser: User hives not supported -- using same registry for all users
0x93fc5000: FS: Using default path "Windows\"
0x93fc5000: OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
0x93fc5000: OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
0x93fc5000: FS: Using default path "Windows\"
0x93fc5000: FSREG: Unable to read value "DBFlags" under HKEY_LOCAL_MACHINE\init\BootVars
0x93fc5000: INITOBJ: Syntax error at initobj.dat:72, ignoring line
0x93fc5000: INITOBJ: Error: "root" not first statement in initobj.dat, not processing initobj.dat
0x93fc5000: Initializing Database
0x93fc5000: ERROR: c:\macallan\private\winceos\coreos\filesys\dbase\initdb.c line 667: 0x93fc5000: Illegal spec on line 207
0x93fc5000: Filesystem initialized!
0x93fc5000: FILESYS: Waiting for kernel to be ready to launch apps
0x93fcaa40: InitMUI: DISABLED (-1039860968)
0x93fc5000: FS: HKLM\System\Events not available, no signal events created.
0x93fc5000: FILESYS: Launching apps
0x93fc5000: ERROR: c:\macallan\private\winceos\coreos\filesys\main\fsmain.c line 4101: 0x93fc5000: Unable to locate init key for starting apps!
0x93fc5000: FILESYS: Done launching apps
0x93fc5000: This device has booted 2 times !!!

Please help me to find what is wrong with this?

--
.

Relevant Pages

  • Re: Filesys failed to initialize registry dirty, trying clean...
    ... And my OS design has already added RAM based registry and RAM/ROM filesystem. ... try to create a kernel with RAM based registry and RAM/ROM filesystem first. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Filesys failed to initialize registry dirty, trying clean...
    ... And my OS design has already added RAM based registry and RAM/ROM filesystem. ... try to create a kernel with RAM based registry ...
    (microsoft.public.windowsce.platbuilder)
  • Re: [00/41] Large Blocksize Support V7 (adds memmap support)
    ... kernel and already must have fallbacks.... ... I don't agree with using higher order pages to fix SLUB vs SLAB performance ... as well as something the filesystem people recommend to get good coverage ...
    (Linux-Kernel)
  • kernel BUG at mm/slab.c:610
    ... I'm experimenting this kernel panic on 3 different ... I don't think this is related to buggy hardware ... Filesystem "hda1": Disabling barriers, not supported by the ... # ACPI Support ...
    (Linux-Kernel)
  • Re: [RFC][PATCH] VFS: update documentation (take #2)
    ... > filesystem interface to userspace programs. ... > abstraction within the kernel which allows different filesystem ... > a pointer to the dentry and a set of file operation member functions. ... called when the VFS needs to get filesystem statistics. ...
    (Linux-Kernel)
Loading