From: Hey M. <Matthew.Hey@NBNZ.CO.NZ> - 2002-09-04 21:09:29
|
Is it missing a Retries++ in the for loop by any chance???? -----Original Message----- From: Royce Mitchell III [mailto:ro...@ev...] Sent: Thursday, 5 September 2002 8:48 a.m. To: rea...@li... Subject: Re[5]: [ros-kernel] Finally have good stack trace on crash I'm experiencing... Eric, I put in the following code where you suggested. The OS is locking up before it gets to the page fault. I don't have the screen capture, but will get it to you as soon as I get a chance. > if (DeviceStatus & IDE_SR_BUSY) > { > /* Wait for BUSY to drop */ > for (Retries = 0; Retries < IDE_MAX_BUSY_RETRIES; Retries) > { > DeviceStatus = IDEReadStatus(CommandPortBase); > if (!(DeviceStatus & IDE_SR_BUSY)) > { > break; > } > ScsiPortStallExecution(10); > } > if (Retries >= IDE_MAX_BUSY_RETRIES) > { > DPRINT1("Drive is BUSY for too long\n"); > /* FIXME: handle timeout */ > } > } ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ reactos-kernel mailing list rea...@li... https://lists.sourceforge.net/lists/listinfo/reactos-kernel This communication is confidential and may contain privileged material. If you are not the intended recipient you must not use, disclose, copy or retain it. If you have received it in error please immediately notify me by return email and delete the emails. Thank you. |
From: Eric K. <ek...@rz...> - 2002-09-04 21:30:26
|
"Hey Matthew" <Matthew.Hey@NBNZ.CO.NZ> wrote: > Is it missing a Retries++ in the for loop by any chance???? Yes, that's a bug. I just checked-in a fixed version. Eric |
From: Royce M. I. <ro...@ev...> - 2002-09-05 00:16:40
|
Yay!!! disk.sys is finally able to load with no page fault. However, ReactOS is now locking up on me a little further down the line. Here's my screen dump: ---------------------------------------------------------------------- Initializing system32\drivers\disk.sys... DriverBase for system32\drivers\disk.sys: dcbf4000 Initializing system32\drivers\vfatfs.sys... DriverBase for system32\drivers\vfatfs.sys: dcbfb000 Initializing system32\ntoskrnl\ntoskrnl.sym... Initializing hal\halx86\hal.sym... Initializing drivers\storage\scsiport\scsiport.sym... Initializing drivers\storage\atapi\atapi.sym... Initializing drivers\storage\class2\class2.sym... Initializing drivers\storage\disk\disk.sym... Initializing drivers\fs\vfat\vfatfs.sym... Loading Cdrom... (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) Loading Fs_Rec... (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) Loading Beep... (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) Loading Null... (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) Loading Keyboard... (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) Loading Blue... (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) Loading Vga... (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) Loading Msfs... (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) Loading Npfs... (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) Loading Ndis... (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) ---------------------------------------------------------------------- Here's the command in the BAT file I use to launch ReactOS: ---------------------------------------------------------------------- c: cd\reactos loadros system32\ntoskrnl.exe system32\hal.dll /DEBUGPORT=SCREEN bootsym.lst ---------------------------------------------------------------------- Here's the contents of bootsym.lst ---------------------------------------------------------------------- system32\drivers\scsiport.sys system32\drivers\atapi.sys system32\drivers\class2.sys system32\drivers\disk.sys system32\drivers\vfatfs.sys system32\config\system.hiv system32\ntoskrnl\ntoskrnl.sym hal\halx86\hal.sym drivers\storage\scsiport\scsiport.sym drivers\storage\atapi\atapi.sym drivers\storage\class2\class2.sym drivers\storage\disk\disk.sym drivers\fs\vfat\vfatfs.sym * ---------------------------------------------------------------------- |
From: Royce M. I. <ro...@ev...> - 2002-09-05 00:57:58
|
I'm trying to piece together how drivers are loaded... RMI> (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) c000003a is STATUS_OBJECT_PATH_NOT_FOUND RMI> Loading Cdrom... This appears to be coming from ldr/loader.c:333 which is: DPRINT("Loading Module %wZ...\n", Filename); I guess that InitializeObjectAttributes() is looking up HKLM/SYSTEM/ControlSet001/Services/Cdrom. Here's my (default) entry from system.hiv [\Registry\Machine\SYSTEM\ControlSet001\Services\Cdrom] "ErrorControl"=dword:00000000 "Group"="SCSI Class" "ImagePath"=expand:"system32\drivers\cdrom.sys" "Start"=dword:00000001 "Type"=dword:00000001 There is a cdrom.sys in the location that ImagePath is pointing to. |
From: Steven E. <ste...@ya...> - 2002-09-05 01:04:29
|
Something may be going on with your fat32 partition as it is not finding any of the drivers once vfat is loaded. --- Royce Mitchell III <ro...@ev...> wrote: > > Yay!!! disk.sys is finally able to load with no page fault. > > However, ReactOS is now locking up on me a little further down the > line. Here's my screen dump: > > ---------------------------------------------------------------------- > Initializing system32\drivers\disk.sys... > DriverBase for system32\drivers\disk.sys: dcbf4000 > > Initializing system32\drivers\vfatfs.sys... > DriverBase for system32\drivers\vfatfs.sys: dcbfb000 > > Initializing system32\ntoskrnl\ntoskrnl.sym... > > Initializing hal\halx86\hal.sym... > > Initializing drivers\storage\scsiport\scsiport.sym... > > Initializing drivers\storage\atapi\atapi.sym... > > Initializing drivers\storage\class2\class2.sym... > > Initializing drivers\storage\disk\disk.sym... > > Initializing drivers\fs\vfat\vfatfs.sym... > > Loading Cdrom... > (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) > > Loading Fs_Rec... > (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) > > Loading Beep... > (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) > > Loading Null... > (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) > > Loading Keyboard... > (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) > > Loading Blue... > (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) > > Loading Vga... > (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) > > Loading Msfs... > (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) > > Loading Npfs... > (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) > > Loading Ndis... > (io/drivers.c:210) LdrLoadModule() failed (Status c000003a) > ---------------------------------------------------------------------- > > Here's the command in the BAT file I use to launch ReactOS: > > ---------------------------------------------------------------------- > c: > cd\reactos > loadros system32\ntoskrnl.exe system32\hal.dll /DEBUGPORT=SCREEN bootsym.lst > ---------------------------------------------------------------------- > > Here's the contents of bootsym.lst > > ---------------------------------------------------------------------- > system32\drivers\scsiport.sys > system32\drivers\atapi.sys > system32\drivers\class2.sys > system32\drivers\disk.sys > system32\drivers\vfatfs.sys > system32\config\system.hiv > system32\ntoskrnl\ntoskrnl.sym > hal\halx86\hal.sym > drivers\storage\scsiport\scsiport.sym > drivers\storage\atapi\atapi.sym > drivers\storage\class2\class2.sym > drivers\storage\disk\disk.sym > drivers\fs\vfat\vfatfs.sym > * > ---------------------------------------------------------------------- > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com |
From: Royce M. I. <ro...@ev...> - 2002-09-05 05:16:30
|
SE> Something may be going on with your fat32 partition as it is not finding any of the drivers once SE> vfat is loaded. Yeah, I gots Linux on here too, not that I ever use it :) First partition is Linux Boot, 2nd is Linux Root, 3rd is FAT32, 4th is extended partition for Linux swap. Here's FDISK specifics... Display Partition Information Current fixed disk drive: 1 Partition Status Type Volume Label Mbytes System Usage 1 Non-DOS 47 % 2 Non-DOS 2698 9% C: 3 A PRI DOS 25627 FAT32 90% 4 EXT DOS 251 1% Total disk space is 28624 Mbytes (1 Mbyte = 1048576 bytes) The Extended DOS Partition contains Logical DOS Drives. Do you want to display the logical drive information (Y/N)......?[Y] Press Esc to return to FDISK Options Display Logical DOS Drive Information No logical drives defined Total Extended DOS Partition size is 251 Mbytes (1 MByte = 1048576 bytes) Press Esc to continue |
From: Eric K. <ek...@rz...> - 2002-09-05 13:38:54
|
"Royce Mitchell III" <ro...@ev...> wrote: > Yeah, I gots Linux on here too, not that I ever use it :) > > First partition is Linux Boot, 2nd is Linux Root, 3rd is FAT32, 4th is > extended partition for Linux swap. > [...] > Partition Status Type Volume Label Mbytes System Usage > 1 Non-DOS 47 % > 2 Non-DOS 2698 9% > C: 3 A PRI DOS 25627 FAT32 90% > 4 EXT DOS 251 1% > This 'strange' layout might cause your boot problems. Please enable the DPRINT() macro in ntoskrnl/io/xhaldrv.c line 754. This will display the partition table of your harddisk. Btw, Linux fdisk provides much more information about partition tables, especially in expert-mode. Eric |
From: Royce M. I. <ro...@ev...> - 2002-09-06 01:21:25
|
Here are the results, reformatted for easier readability. Oddly enough this seems to conflict with the report from FDISK :( 0: nr: 1 boot: 1 type: c start: 7e00 count: 641b18800 1: nr: 0 boot: 0 type: 83 start: 641b20600 count: 2f10c00 2: nr: 0 boot: 0 type: 83 start: 644a31200 count: a8a6b000 3: nr: 0 boot: 0 type: f start: 0 count: fb04000 4: nr: 0 boot: 0 type: 82 start: 6ed4a4000 count: fafc200 5: nr: 0 boot: 0 type: 0 start: 0 count: 0 6: nr: 0 boot: 0 type: 0 start: 0 count: 0 7: nr: 0 boot: 0 type: 0 start: 0 count: 0 |