Re: [ros-svn] [ion] 15395: Object Manager Patch. This patch continues the work done in the previous patch and makes the following changes in order to support OB 2.0 (it basically temporarily fixes a highly incorrect implementation so that caller code will be ready to work with the OB 2.0 without change):
18 May
2005
18 May
'05
9:02 p.m.
Hi,
I'm not able to boot reactos after your last four commits.
- Hartmut
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in
remaining
path:"\DeviceClasses\{86E0D1E0-8089-11D0-9CE4-08003E301F73}\##?#ACPI#PNP0501#1#{86E0D1E0-8089-11D0-9CE4-08003E301F73}"!)
KeBugCheckWithTf at ke/catch.c:222
A problem has been detected and ReactOS has been shut down to prevent
damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x80039e70,0x00000000,0x00000004)
*** ntoskrnl.exe - Address 0x80039e70 base at 0x80000000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:80039e70 <ntoskrnl.exe:39e70 (io/device.c:86
(IopInitializeDevice))>
cr2 4 cr3 34000 Proc: 80806364 Pid: 4 <System> Thrd: 80807680 Tid: 0
DS 10 ES 10 FS 30 GS 10
EAX: 00000000 EBX: 000764dc ECX: 80952008
EDX: 809b9e24 EBP: 800eeba0 ESI: 15b62000 ESP: 800eeb14
EDI: 00000000 EFLAGS: 00210296 kESP 800eeb14 kernel stack base 800ed000
Frames:
<ntoskrnl.exe:4b8cf (io/pnpmgr.c:1523 (IopActionInitChildServices))>
<ntoskrnl.exe:4b986 (io/pnpmgr.c:1569 (IopActionInitAllServices))>
<ntoskrnl.exe:4aa6b (io/pnpmgr.c:695 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4aaa1 (io/pnpmgr.c:709 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4aaa1 (io/pnpmgr.c:709 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4aae7 (io/pnpmgr.c:735 (IopTraverseDeviceTree))>
<ntoskrnl.exe:4b9ec (io/pnpmgr.c:1628 (IopInitializePnpServices))>
<800AB56A>
<800A909C>
<ntoskrnl.exe:10544 (ke/main.c:103 (KiSystemStartup))>
<800A77AA>
<ntoskrnl.exe:104b (D:\DOKUME~1\hb\LOKALE~1\Temp/ccO4aaaa.s:51
(_section_alignment__))>
18 May
18 May
9:31 p.m.
New subject: [ros-svn] [ion] 15395: Object Manager Patch. This patch continues the work done in the previous patch and makes the following changes in order to support OB 2.0 (it basically temporarily fixes a highly incorrect implementation so that caller code will be ready to work with the OB 2.0 without change):
Hartmut Birr wrote:
Hi,
I'm not able to boot reactos after your last four commits.
Is the ob stuff causing you the problem?
Let me know if reverting io/driver.c helps.
Best regards,
Alex Ionescu
9:52 p.m.
New subject: [ros-svn] [ion] 15395: Object Manager Patch. This patch continues the work done in the previous patch and makes the following changes in order to support OB 2.0 (it basically temporarily fixes a highly incorrect implementation so th
I tested this patch for Alex today and last night. I have a fairly
vanilla WC, but I build DBG+KDB. I saw no issues under qemu.
On 5/18/05, Hartmut Birr <hartmut.birr(a)gmx.de> wrote:
Hi,
I'm not able to boot reactos after your last four commits.
- Hartmut
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in
remaining
path:"\DeviceClasses\{86E0D1E0-8089-11D0-9CE4-08003E301F73}\##?#ACPI#PNP0501#1#{86E0D1E0-8089-11D0-9CE4-08003E301F73}"!)
KeBugCheckWithTf at ke/catch.c:222
A problem has been detected and ReactOS has been shut down to prevent
damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x80039e70,0x00000000,0x00000004)
*** ntoskrnl.exe - Address 0x80039e70 base at 0x80000000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:80039e70 <ntoskrnl.exe:39e70 (io/device.c:86
(IopInitializeDevice))>
cr2 4 cr3 34000 Proc: 80806364 Pid: 4 <System> Thrd: 80807680 Tid: 0
DS 10 ES 10 FS 30 GS 10
EAX: 00000000 EBX: 000764dc ECX: 80952008
EDX: 809b9e24 EBP: 800eeba0 ESI: 15b62000 ESP: 800eeb14
EDI: 00000000 EFLAGS: 00210296 kESP 800eeb14 kernel stack base 800ed000
Frames:
<ntoskrnl.exe:4b8cf (io/pnpmgr.c:1523 (IopActionInitChildServices))>
<ntoskrnl.exe:4b986 (io/pnpmgr.c:1569 (IopActionInitAllServices))>
<ntoskrnl.exe:4aa6b (io/pnpmgr.c:695 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4aaa1 (io/pnpmgr.c:709 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4aaa1 (io/pnpmgr.c:709 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4aae7 (io/pnpmgr.c:735 (IopTraverseDeviceTree))>
<ntoskrnl.exe:4b9ec (io/pnpmgr.c:1628 (IopInitializePnpServices))>
<800AB56A>
<800A909C>
<ntoskrnl.exe:10544 (ke/main.c:103 (KiSystemStartup))>
<800A77AA>
<ntoskrnl.exe:104b (D:\DOKUME~1\hb\LOKALE~1\Temp/ccO4aaaa.s:51
(_section_alignment__))>
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
--
"<arty> the tree was touched a lot recently"
19 May
19 May
12:23 a.m.
New subject: [ros-svn] [ion] 15395: Object Manager Patch. This patch continues the work done in the previous patch and makes the following changes in order to support OB 2.0 (it basically temporarily fixes a highly incorrect implementation so th
(Alex's mail is down)
Hartmut Birr wrote:
Hi,
I'm not able to boot reactos after your last four commits.
Is the ob stuff causing you the problem?
Let me know if reverting io/driver.c helps.
Best regards,
Alex Ionescu
12:45 a.m.
New subject: [ros-svn] [ion] 15395: Object Manager Patch. This patch continues the work done in the previous patch and makes the following changes in order to support OB 2.0 (it basically temporarily fixes a highly incorrect implementation so th
Well, well. I apologize for not testing Alex's patch under vmware
until this evening. While the very same bootcd works under qemu, I
get this same fault on boot under vmware with 15400:
(io/pnpmgr.c:1575) Service <NULL> is disabled or already initialized
(io/pnpmgr.c:1489) IopActionInitChildServices(806d8f60, 80590c88, 0)
(io/pnpmgr.c:1575) Service <NULL> is disabled or already initialized
(io/pnpmgr.c:1489) IopActionInitChildServices(806d8e68, 80590c88, 0)
(io/pnpmgr.c:1575) Service <NULL> is disabled or already initialized
(io/pnpmgr.c:1489) IopActionInitChildServices(806d8d70, 80590c88, 0)
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in remaining
pa
th: "\DeviceClasses\{86E0D1E0-8089-11D0-9CE4-08003E301F73}\##?#ACPI#PNP0501#1#{8
6E0D1E0-8089-11D0-9CE4-08003E301F73}"!)
(io/pnpmgr.c:1489) IopActionInitChildServices(806d8c78, 80590c88, 0)
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0x4 could not be read: Page not present.
kdb:> bt
Eip:
<ntoskrnl.exe:3df10 (io/device.c:86 (IopInitializeDevice))>
Frames:
<ntoskrnl.exe:505ca (io/pnpmgr.c:1547 (IopActionInitChildServices))>
<ntoskrnl.exe:506b6 (io/pnpmgr.c:1593 (IopActionInitAllServices))>
<ntoskrnl.exe:4ee6f (io/pnpmgr.c:719 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4eea5 (io/pnpmgr.c:733 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4eea5 (io/pnpmgr.c:733 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4ef59 (io/pnpmgr.c:759 (IopTraverseDeviceTree))>
<ntoskrnl.exe:50752 (io/pnpmgr.c:1652 (IopInitializePnpServices))>
<800b859f>
<800b60bc>
<ntoskrnl.exe:14674 (ke/main.c:103 (KiSystemStartup))>
<800b47aa>
<ntoskrnl.exe:104b (/tmp/ccKVWptD.s:51 (NtProcessStartup))>
Couldn't access memory at 0x76498!
kdb:>
On 5/18/05, Hartmut Birr <hartmut.birr(a)gmx.de> wrote:
Hi,
I'm not able to boot reactos after your last four commits.
- Hartmut
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(io/pnpreport.c:84) IoReportResourceForDetection partly implemented
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in
remaining
path:"\DeviceClasses\{86E0D1E0-8089-11D0-9CE4-08003E301F73}\##?#ACPI#PNP0501#1#{86E0D1E0-8089-11D0-9CE4-08003E301F73}"!)
KeBugCheckWithTf at ke/catch.c:222
A problem has been detected and ReactOS has been shut down to prevent
damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x80039e70,0x00000000,0x00000004)
*** ntoskrnl.exe - Address 0x80039e70 base at 0x80000000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:80039e70 <ntoskrnl.exe:39e70 (io/device.c:86
(IopInitializeDevice))>
cr2 4 cr3 34000 Proc: 80806364 Pid: 4 <System> Thrd: 80807680 Tid: 0
DS 10 ES 10 FS 30 GS 10
EAX: 00000000 EBX: 000764dc ECX: 80952008
EDX: 809b9e24 EBP: 800eeba0 ESI: 15b62000 ESP: 800eeb14
EDI: 00000000 EFLAGS: 00210296 kESP 800eeb14 kernel stack base 800ed000
Frames:
<ntoskrnl.exe:4b8cf (io/pnpmgr.c:1523 (IopActionInitChildServices))>
<ntoskrnl.exe:4b986 (io/pnpmgr.c:1569 (IopActionInitAllServices))>
<ntoskrnl.exe:4aa6b (io/pnpmgr.c:695 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4aaa1 (io/pnpmgr.c:709 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4aaa1 (io/pnpmgr.c:709 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4aae7 (io/pnpmgr.c:735 (IopTraverseDeviceTree))>
<ntoskrnl.exe:4b9ec (io/pnpmgr.c:1628 (IopInitializePnpServices))>
<800AB56A>
<800A909C>
<ntoskrnl.exe:10544 (ke/main.c:103 (KiSystemStartup))>
<800A77AA>
<ntoskrnl.exe:104b (D:\DOKUME~1\hb\LOKALE~1\Temp/ccO4aaaa.s:51
(_section_alignment__))>
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
WD
--
"<arty> the tree was touched a lot recently"
12:59 a.m.
New subject: [ros-svn] [ion] 15395: Object Manager Patch. This patch continues the work done in the previous patch and makes the following changes in order to support OB 2.0 (it basically temporarily fixes a highly incorrect implementation so th
Yup, it's the ob patch, I just tried my ReactOS-15386M_ion.iso and it
faults also.
WD
6:14 p.m.
New subject: [ros-svn] [ion] 15395: Object Manager Patch. This patch continues the work done in the previous patch and makes the following changes in order to support OB 2.0 (it basically temporarily fixes a highly incorrect implementation so that caller code will be ready to work with the OB 2.0 without change):
Hi,
withe the current svn tree, I'm able to boot ros.
Thanks.
- Hartmut
Hartmut Birr wrote:
Hi,
I'm not able to boot reactos after your last four commits.
- Hartmut
7064
days inactive
7065
days old
6 comments
3 participants
participants (3)
-
Alex Ionescu -
Hartmut Birr -
WaxDragon