Revision 20911 Boot Problems

[James Tabor]

Hi all,

WaxDragon gets this,
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(./lib/advapi32/service/scm.c:2035) dwBufSize: 0
(subsys/system/services/rpcserver.c:1759) ScmrStartServiceW() called
(ntoskrnl/ke/i386/v86m.c:678) V86GPF unhandled (was cf)
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0xf000e739 could not be written: Page not present.
kdb:> bt
Eip:
<ntoskrnl.exe:65a69 (ntoskrnl/ke/i386/v86m.c:383 (KeV86GPF))>
Frames:
<ntoskrnl.exe:65d92 (ntoskrnl/ke/i386/v86m.c:791 (KeV86Exception))>
<ntoskrnl.exe:62a1f (ntoskrnl/ke/i386/exp.c:514 (KiTrapHandler))>
<ntoskrnl.exe:64cb1 (ntoskrnl/ke/i386/trap.s:151 (KiTrapProlog2))>
<00000c33>
kdb:>


I get this,
(lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv'
  (Status c0000135)
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'midimap.dr
v' (Status c0000135)
(./subsys/win32k/ntuser/class.c:137) Failed to lookup class atom (ClassName 'SHE
LLDLL_DefView')!
(ntoskrnl/ke/i386/v86m.c:678) V86GPF unhandled (was ec)
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0xdeadbeef could not be written: Page not present.
kdb:> bt
Eip:
<ntoskrnl.exe:65aa9 (ntoskrnl/ke/i386/v86m.c:383 (KeV86GPF))>
Frames:
<ntoskrnl.exe:65dd2 (ntoskrnl/ke/i386/v86m.c:791 (KeV86Exception))>
<ntoskrnl.exe:62a5f (ntoskrnl/ke/i386/exp.c:514 (KiTrapHandler))>
<ntoskrnl.exe:64cf1 (ntoskrnl/ke/i386/trap.s:151 (KiTrapProlog2))>
<00003443>
<00000000>
kdb:>

Second reboot it worked after booting linux than reboot warm, third reboot by power on
reset,
(ntoskrnl/ke/i386/v86m.c:678) V86GPF unhandled (was ee)
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0xdeadbeef could not be written: Page not present.
kdb:> bt
Eip:
<ntoskrnl.exe:65aa9 (ntoskrnl/ke/i386/v86m.c:383 (KeV86GPF))>
Frames:
<ntoskrnl.exe:65dd2 (ntoskrnl/ke/i386/v86m.c:791 (KeV86Exception))>
<ntoskrnl.exe:62a5f (ntoskrnl/ke/i386/exp.c:514 (KiTrapHandler))>
<ntoskrnl.exe:64cf1 (ntoskrnl/ke/i386/trap.s:151 (KiTrapProlog2))>
<00002eee>
<00000000>
kdb:>

I can repeat this over and over with real hardware,
Thanks,
James

[WaxDragon]

I actually get this under qemu:

(./ntoskrnl/ke/main.c:291)
---------------------------------------------------------------
(./ntoskrnl/ke/main.c:292) ReactOS 0.3-SVN (Build 20060116-r20911)
Used memory 262144Kb
(./ntoskrnl/mm/mminit.c:387) Kernel Stack Limits. InitTop =
0x800ca000, Init = 0x800c7000
(./ntoskrnl/mm/mm.c:283) No current process
(./ntoskrnl/io/driver.c:1295) Driver 'buslogic.sys' load failed,
status (c0000001)
(drivers/input/i8042prt/registry.c:197) Can't read registry: c0000034
(drivers/input/i8042prt/registry.c:203) Manually set defaults
(./ntoskrnl/io/disk.c:630) RDiskCount 2
(./ntoskrnl/io/disk.c:665) ZwCreateKey failed for
\Registry\Machine\SYSTEM\MountedDevices, status=c0000034
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0x00000000 could not be read: Page not present.
kdb:> bt
Eip:
<7c907b29>
Frames:
kdb:>

*Unless* I disable kqemu, then I get the V86GPF like vmware does.  I
also get the same error on my real hardware.  Alex suggested had a
dirty tree, and even though I clean before each update, I went back
over my tree with 'svn st --no-ignore' and cleaned everything.  This
still happens.

Alex claimed that he was able to boot in qemu and vmware, so I'm
suspecting this is a compiler problem.

Jim Tabor and I are both using mingw 3.4.2 and binutils 2.15.94, which
is the same versions as the RosBE 0.1.

Anyone *not* seeing this problem?

WD
--
<Alex_Ionescu> it's like saying let's rename Ke to Kernel because
people think it's Ketchup

[TwoTailedFox]

I'm seeing a BSOD in Ntoskrl on Real Hardware
(KMODE_EXCEPTION_NOT_HANDLED), on boot after 1st Stage Setup, and
that's using 20911, compiled with GCC 3.4.5, and Binutils 2.16.91.

I'll have a crack on VMWare 5.5 with this revision, and see what I get.

On 1/16/06, WaxDragon <waxdragon(a)gmail.com> wrote:
>   I actually get this under qemu:
>
>  (./ntoskrnl/ke/main.c:291)
>  ---------------------------------------------------------------
>  (./ntoskrnl/ke/main.c:292) ReactOS 0.3-SVN (Build 20060116-r20911)
>  Used memory 262144Kb
>  (./ntoskrnl/mm/mminit.c:387) Kernel Stack Limits. InitTop =
>  0x800ca000, Init = 0x800c7000
>  (./ntoskrnl/mm/mm.c:283) No current process
>  (./ntoskrnl/io/driver.c:1295) Driver 'buslogic.sys' load failed,
>  status (c0000001)
>  (drivers/input/i8042prt/registry.c:197) Can't read registry: c0000034
>  (drivers/input/i8042prt/registry.c:203) Manually set defaults
>  (./ntoskrnl/io/disk.c:630) RDiskCount 2
>  (./ntoskrnl/io/disk.c:665) ZwCreateKey failed for
>  \Registry\Machine\SYSTEM\MountedDevices, status=c0000034
>  Entered debugger on last-chance exception number 14 (Page Fault)
>  Memory at 0x00000000 could not be read: Page not present.
>  kdb:> bt
>  Eip:
>  <7c907b29>
>  Frames:
>  kdb:>
>
>  *Unless* I disable kqemu, then I get the V86GPF like vmware does.  I
>  also get the same error on my real hardware.  Alex suggested had a
>  dirty tree, and even though I clean before each update, I went back
>  over my tree with 'svn st --no-ignore' and cleaned everything.  This
>  still happens.
>
>  Alex claimed that he was able to boot in qemu and vmware, so I'm
>  suspecting this is a compiler problem.
>
>  Jim Tabor and I are both using mingw 3.4.2 and binutils 2.15.94, which
>  is the same versions as the RosBE 0.1.
>
>  Anyone *not* seeing this problem?
>
>  WD
>  --
>  <Alex_Ionescu> it's like saying let's rename Ke to Kernel because
>  people think it's Ketchup
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  

--
"I had a handle on life, but then it broke"