Re: IXP42X NOR FileSystem Problem !!! wince5
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Thu, 8 Nov 2007 10:20:25 -0700
I don't know if you can and I don't know if it would help, even if you can.
As I said, investigate the source of some of those messages and strings and
***SEE WHAT YOU FIND***.
Paul T.
"sampeper" <sampeper@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A5E61F0E-6CD3-4CD6-8FA3-B77C4B9D74AD@xxxxxxxxxxxxxxxx
how can i preallocate extra space for system.hv and user.hv on the hard
disk?
i have just one partetion(hard disk)!
thanks
sam
"Paul G. Tobey [eMVP]" wrote:
I don't have the CE6 source code in front of me, but it looks like a
search
in the code for "Skipping trim of volume" might tell you something. It
seems like the registry might not be valid, possibly because there were
registry changes to be written when you rebooted, but because the disk
was
full, that could not be done or something. There's also a reference to
"SystemHiveInitialSize" that I don't recognize. If you could preallocate
space for the system and user hives when before the disk filled up, it
seems
like you might avoid the problem I'm postulating above...
Paul T.
"sampeper" <sampeper@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F53079B7-64FF-448D-8B5B-BF564FD879CC@xxxxxxxxxxxxxxxx
Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 8202b000, extension: 00004000, length: 01fcd000
NKStartup done, starting up kernel.
Windows CE KernelInit
Reserve VM for kernel XIP DLls, first = c0010000, last = c11c0000
g_pprcNK == 0x82022aa0
Updated eptr->e32_vsize to = 00042000
Initializing Memory Mapped File Support
Scheduling the first thread.
Detecting VFP... VFP Not Found!
LoaderInit: Initialing loader
Updated eptr->e32_vsize to = 00042000
Updated eptr->e32_vsize to = 000a2000
Updated eptr->e32_vsize to = 0003c000
-199843: RT_Init_RealTime() entered
OEMIoControl: Unsupported IOCTL code: 0x'1010148'
PGPOOL: Reserved 768 pages for Loader pool
PGPOOL: Reserved 256 pages for File pool
+OEMIoControl: IOCTL_HAL_GET_DEVICE_INFO
+OEMIoControl: IOCTL_HAL_GET_DEVICE_INFO
OSAXST0: Platform Name = Undefined
+OEMIoControl: IOCTL_HAL_GET_DEVICE_INFO
OSAXST1: >>> Loading Module 'kd.dll' (0x83FD7938) at address
0xC0010000-0xC0045000 in Process 'NK.EXE' (0x82022AA0)
KD: Starting kernel debugger software probe (KdStub) - KD API version
22
OSAXST1: >>> Loading Module 'NK.EXE' (0x82022AA0) at address
0x8028D000-0x802CF000 in Process 'NK.EXE' (0x82022AA0)
OEMIoControl: IOCTL_HAL_POSTINIT called
Message Queue support initialized, g_hMsgQHeap = d0040770
OSAXST1: >>> Loading Module 'filesys.dll' (0x83FB38EC) at address
0xC01E0000-0xC0279000 in Process 'NK.EXE' (0x82022AA0)
OSAXST1: >>> Loading Module 'k.fpcrt.dll' (0x83FB3A34) at address
0xC01C0000-0xC01D8000 in Process 'NK.EXE' (0x82022AA0)
OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x83FB3B7C) at address
0xC0610000-0xC0655000 in Process 'NK.EXE' (0x82022AA0)
FSDMGR!DllMain: DLL_PROCESS_ATTACH
CertMod.dll not found, using old OEM Trust Model
FileSystem Starting - starting with clean file system
+OEMIoControl: IOCTL_HAL_INIT_RTC
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' (0x83F9CDF8) at address
0xC0280000-0xC0287000 in Process 'NK.EXE' (0x82022AA0)
FSDMGR!MountTable_t::RegisterVolumeName: Registered "ROM" at index
3FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3
(Name="ROM", MountFlags=0x71)OEMIoControl: IOCTL_HAL_GETREGSECUREKEYS
not
supported
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
OEMIoControl: IOCTL_HAL_INITREGISTRY
PCIReg(key: , device: 0/0/0)
FS: Creating signal event SYSTEM/DevMgrApiSetReady
FS: Creating signal event SYSTEM/PowerManagerReady
FS: Creating signal event SYSTEM/GweApiSetReady
FILESYS: Starting boot phase 0.
FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1)
FSDMGR: File security disabled.
FSDMGR!AutoFSDMGR!PNPThread: Using PNPUnloadDelay of 4096
FSDMGR!PNPThread: PNPThread starting!
LoadFileSystems: 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=0x44)FILESYS: Starting boot phase 1.
FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0)
FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1
FILESYS: Starting device and waiting for boot file system.
OSAXST1: >>> Loading Module 'device.dll' (0x83F73000) at address
0xC04C0000-0xC04C5000 in Process 'NK.EXE' (0x82022AA0)
OSAXST1: >>> Loading Module 'devmgr.dll' (0x83F73138) at address
0xC04D0000-0xC04F7000 in Process 'NK.EXE' (0x82022AA0)
OSAXST1: >>> Loading Module 'k.ceddk.dll' (0x83F73270) at address
0xC0DF0000-0xC0DFF000 in Process 'NK.EXE' (0x82022AA0)
OSAXST1: >>> Loading Module 'pm.dll' (0x83F733B8) at address
0xC0520000-0xC0547000 in Process 'NK.EXE' (0x82022AA0)
*** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x400002 ***
Filesys: Loaded device.dll
FILESYS: Waiting for device manager to signal BootPhase1 completion.
+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
Ceddk!BeginCalibration: min(101) max(112)
Ceddk!BeginCalibration: Elapsed is 109
Ceddk!BeginCalibration: Delay is 9
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' (0x83F697D4) at address
0xC0510000-0xC051B000 in Process 'NK.EXE' (0x82022AA0)
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\StrataFMD\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'ixp4xx_stratad.dll' (0x83F5E5A4) at
address
0xC0FF0000-0xC100E000 in Process 'NK.EXE' (0x82022AA0)
: FMD_Init lpActiveReg:D024E67C , pRegIn:0, pRegOut: 0
FMD_Init: Warning, IsPairedFlash not specified in registry. Using
value
of 0.
INFO: FMD_Init: Flash Address=0xb5100000 Length=0x500000.
FLASHDRV.DLL:BuildupMappingInfo() - Enter.
DeviceFolder::LoadDevice(Drivers\BuiltIn\StrataFMD) last 132
TicksDEVICE!RegReadActivationValues RegOpenKeyEx(Notify) returned 2.
DEVICE!I_ActivateDeviceEx: can't find all required activation values in
'Notify'
FSDMGR!MountStore: Attaching new storage device
"DSK1:"FSDMGR!StoreDisk_t::OpenDisk(0xD004BDD0) DeviceInfo
Class(0x00000001)
Flags(0x00000015) Type(0x00000002) Profile(MSFlash)
FMD_OEMIoControl: unrecognized IOCTL (0x71c24).
FSDMGR!DumpRegKey: Dumping registry for key
System\StorageManager\Profiles
AutoMount = 00000001
AutoPart = 00000000
AutoFormat = 00000000
MountFFILESYS: Waiting for bootable file system to be mounted.
lags = 00000000
DefaultFileSystem =
PartitionDriverName = MSPART
Folder = Mounted Volume
ActivityEvent = PowerManager/ActivityTimer/SystemActivity
FSDMGR!DumpRegKey: Dumping registry for key MSFlash
Name = MSFLASH for STRATAFLASH
DefaultFileSystem = FATFS
Folder = Hard Disk
PartitionDriverName = MSPART
AutoMount = 00000001
AutoPart = 00000001
AutoFormat = 00000001
MountAsBootable = 00000001
OSAXST1: >>> Loading Module 'mspart.dll' (0x83F5EF50) at address
0xC0660000-0xC066F000 in Process 'NK.EXE' (0x82022AA0)
FSDMGR!LoadPartitionDriver: Loading partition driver mspart.dll
hModule=83F5EF50
FSDMGR!StoreDisk_t::MountStore: Opened the store "DSK1:"
hStore=0xD004C9F0
FSDMGR!StoreDisk_t::MountStore: Geometry: NumSec=1178 BytesPerSec=4096
FreeSec=0 BiggestCreatable=0
Partition Part00 NumSectors=1176
MSPART!PD_OpenPartition: dwStoreId=D004C9F0, PartName=Part00
FSDMGR!StoreDisk_t::LoadPartition: mounting partition "Part00" on store
"DSK1:"FSDMGR!ParitionDisk::LoadPartition: Partition Type 0x01 -->
"FATFS"
FSDMGR!ParitionDisk::MountPartition: "FATFS" --> exfat.dll
OSAXST1: >>> Loading Module 'exfat.dll' (0x83F4B138) at address
0xC0560000-0xC059B000 in Process 'NK.EXE' (0x82022AA0)
FSD_MountDisk: Mounting volume for hDsk=D004CA90
FATFS!ReadRegistryValues: Registry flags = 0x3d003e
FATFS!ReadRegistryValues: Force write through enabled
FATFS!ReadRegistryValues: Automatic formatting enabled
FATFS!ReadRegistryValues: Transact data enabled
FATFS!ReadRegistryValues: Security Support disabled
OSAXST1: >>> Loading Module 'diskcache.dll' (0x83F4BC30) at address
0xC05A0000-0xC05AA000 in Process 'NK.EXE' (0x82022AA0)
CreateCache: Successful. Cache Size: 4 KB, Start: 1, End: 1,
CreateFlags:
0.
CreateCache: Successful. Cache Size: 8 KB, Start: 3, End: 1175,
CreateFlags: 0.
FSDMGR!MountTable_t::RegisterVolumeName: Registered "Hard Disk" at
index
7FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 7
(Name="Hard Disk", MountFlags=0x2)FATFS!RegisterVolume: Mounted volume
HVOL=0x01200003 at "Hard Disk"
FATFS!MountVolume: Successfully mounted regular FAT12 volume.
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: Mounted ROM portion of system hive
FILESYS: Loading system hive from Hard Disk\Documents and
Settings\system.hv.
OEM: IOCTL_HAL_GET_HIVE_CLEAN_FLAG!
OEMIoControl: Returning Success
ERROR: C:\ymzki\private\winceos\COREOS\filesys\heap\.\volume.c line
1428:
FSVolTrimFile: Invalid volume: Hard Disk\Documents and
Settings\system.hv.
ERROR: C:\ymzki\private\winceos\COREOS\filesys\heap\.\volume.c line
565:
FSVOL: Aborting init on non-volume
FSREG: Mounting clean system hive
BuildPath: Hard Disk
BuildPath: Hard Disk\Documents and Settings
FSVOL: Opening existing volume
FSVOL: Creating new volume (size=28672 bytes)
FATFS!FAT_DeviceIoControl returned LRESULT 0x57
FSVOL: Initializing volume heap
FSREG: Taking down boot registry. Any open keys will be invalid.
FILESYS: Registry in place.
OEM: IOCTL_HAL_GET_HIVE_CLEAN_FLAG!
OEMIoControl: Returning Success
FSREG: Unable to read value "RegistryFlags" under
HKEY_LOCAL_MACHINE\init\BootVars
FSVOL: Using system database volume "Hard Disk\Documents and
Settings\default.vol"
BuildPath: Hard Disk
BuildPath: Hard Disk\Documents and Settings
OEM: IOCTL_HAL_GET_HIVE_CLEAN_FLAG!
OEMIoControl: Returning Success
FSVOL: Creating new volume (size=28672 bytes)
FATFS!FAT_DeviceIoControl returned LRESULT 0x57
FSVOL: Initializing volume heap
FSREG: Unable to read value "RequireCertMod" under
HKEY_LOCAL_MACHINE\init\BootVars
FSREG: Unable to read value "NoDefaultUser" under
HKEY_LOCAL_MACHINE\init\BootVars
FSREG: Logging in default user.
FSREG: Unable to read value "DefaultUser" under
HKEY_LOCAL_MACHINE\init\BootVars
SetCurrentUser: Logging out (nobody), logging in default
FSREG: Mounting ROM portion of user hive
FSVOL: Opening existing volume
FSVOL: Volume heap already initialized
Mounting user hive from Hard Disk\Documents and
Settings\default\user.hv
ERROR: C:\ymzki\private\winceos\COREOS\filesys\heap\.\volume.c line
1437:
FSVolTrimFile: Skipping trim of volume Hard Disk\Documents and
Settings\default\user.hv.
FSVOL: Opening existing volume
FATFS!FAT_DeviceIoControl returned LRESULT 0x57
FSVOL: Volume heap already initialized
FileSys: DEBUGCHK failed in file
C:\ymzki\private\winceos\COREOS\filesys\heap\.\heap.c at line 1580
KdTrap: JIT debugging requested, waiting for OEM selection
KdTrap: JIT debugging accepted
+KITLRegisterDfltClient, service:2
Exception 'Data Abort' (4): Thread-Id=005d0002(pth=83f9c000),
Proc-Id=00400002(pprc=82022aa0) 'NK.EXE',
VM-active=00400002(pprc=82022aa0)
'NK.EXE'
PC=802e4cec(kitl.dll+0x00014cec) RA=802dc3f0(kitl.dll+0x0000c3f0)
SP=d00be9e8, BVA=00000010
Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1 time(s).
This
OK if KdStub stumbling on its own BP.
KdTrap: Exception in debugger, Addr=0x802E4CEC - attempting to
recover
RtlDispatchException: returning failure. Flags=0
KPSLExceptionHandler: flags=1 ControlPc=c020fd4c
RtlDispatchException: returning failure. Flags=1
NK Kernel: DEBUGCHK failed in file
C:\yzkiqfe\private\winceos\COREOS\nk\kernel\nknormal\..\exdsptch.c at
line
333
Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1 time(s).
This
OK if KdStub stumbling on its own BP.
KdTrap: Exception in debugger, Addr=
*** hang here****
"Paul G. Tobey [eMVP]" wrote:
Seems like building a DEBUG build and capturing the debug messages to
see
where it's failing would be the first step...
Paul T.
"sampeper" <u38902@uwe> wrote in message news:7ae83e195f6a8@xxxxxx
i used Strata nor flash from intel (16 MB)
9 MB for OS image and the rest for Hard Disk(4MB) and Eboot.
i have this Problem:
1. i making the Hard Disk full with any data ---->no free space more
on
hard
disk
2. restart my Device
----->Device does't boot more!!!
kernel hang after trying to loading the System.hv and
.
- References:
- IXP42X NOR FileSystem Problem !!! wince5
- From: sampeper
- Re: IXP42X NOR FileSystem Problem !!! wince5
- From: Paul G. Tobey [eMVP]
- Re: IXP42X NOR FileSystem Problem !!! wince5
- From: sampeper
- Re: IXP42X NOR FileSystem Problem !!! wince5
- From: Paul G. Tobey [eMVP]
- Re: IXP42X NOR FileSystem Problem !!! wince5
- From: sampeper
- IXP42X NOR FileSystem Problem !!! wince5
- Prev by Date: Re: IXP42X NOR FileSystem Problem !!! wince5
- Next by Date: Force Libraries to generate .lib
- Previous by thread: Re: IXP42X NOR FileSystem Problem !!! wince5
- Next by thread: Infamous DHCP was unable to obtain an IP address issue.
- Index(es):
Relevant Pages
|
