[ros-bugs] [Bug 4354] Videoprt ASSERT at 3rd stage startup when installing Voodoo 3 drivers
ReactOS.Bugzilla at www.reactos.org
ReactOS.Bugzilla at www.reactos.org
Fri Jun 5 11:01:59 CEST 2009
http://www.reactos.org/bugzilla/show_bug.cgi?id=4354
--- Comment #3 from Haos <olaf_siejka at o2.pl> 2009-05-20 23:43:25 CET ---
Same problem on 3DLabs Oxygen GVX1, using GPU`s own drivers. Tested on 41022.
Debug output is identical:
(drivers\video\videoprt\dispatch.c:363) InterfaceType 5 BusNumber List 0 Device
BusNumber 1 Version 1 Revision 1
Assertion 'FullList->InterfaceType == PCIBus && FullList->BusNumber ==
DeviceExtension->SystemIoBusNumber && 1 ==
FullList->PartialResourceList.Version && 1 ==
FullList->PartialResourceList.Revision' failed at
drivers\video\videoprt\dispatch.c line 370
[7hEntered debugger on embedded INT3 at 0x0008:0x808c23a6.
kdb:> bt
Eip:
<NTOSKRNL.EXE:c23a7 (lib\rtl\i386\debug_asm.S:33 (DbgBreakPoint at 0))>
Frames:
<VIDEOPRT.SYS:2058 (drivers/video/videoprt/dispatch.c:371
(IntVideoPortPnPStartDevice at 8))>
<VIDEOPRT.SYS:213f (drivers/video/videoprt/dispatch.c:456
(IntVideoPortDispatchPnp at 8))>
<NTOSKRNL.EXE:567bd (ntoskrnl/io/iomgr/irp.c:1137 (@IofCallDriver at 8))>
<NTOSKRNL.EXE:5b562 (ntoskrnl/io/pnpmgr/pnpmgr.c:534 (IopInitiatePnpIrp))>
<NTOSKRNL.EXE:5b01b (ntoskrnl/include/internal/ke_x.h:98 (IopStartDevice))>
<NTOSKRNL.EXE:5c9cd (ntoskrnl/io/pnpmgr/pnpmgr.c:2055
(IopActionInitChildServices))>
<NTOSKRNL.EXE:5b5b7 (ntoskrnl/io/pnpmgr/pnpmgr.c:562
(IopTraverseDeviceTreeNode))>
<NTOSKRNL.EXE:5b5cc (ntoskrnl/io/pnpmgr/pnpmgr.c:576
(IopTraverseDeviceTreeNode))>
<NTOSKRNL.EXE:5b5ed (ntoskrnl/io/pnpmgr/pnpmgr.c:600 (IopTraverseDeviceTree))>
<NTOSKRNL.EXE:5ca8d (ntoskrnl/io/pnpmgr/pnpmgr.c:2112
(IopInitializePnpServices))>
<NTOSKRNL.EXE:5c7d2 (ntoskrnl/io/pnpmgr/pnpmgr.c:1810 (IopEnumerateDevice))>
<NTOSKRNL.EXE:5b06a (ntoskrnl/io/pnpmgr/pnpmgr.c:205 (IopStartDevice))>
<NTOSKRNL.EXE:5c9cd (ntoskrnl/io/pnpmgr/pnpmgr.c:2055
(IopActionInitChildServices))>
<NTOSKRNL.EXE:5b5b7 (ntoskrnl/io/pnpmgr/pnpmgr.c:562
(IopTraverseDeviceTreeNode))>
<NTOSKRNL.EXE:5b5cc (ntoskrnl/io/pnpmgr/pnpmgr.c:576
(IopTraverseDeviceTreeNode))>
<NTOSKRNL.EXE:5b5ed (ntoskrnl/io/pnpmgr/pnpmgr.c:600 (IopTraverseDeviceTree))>
<NTOSKRNL.EXE:5ca8d (ntoskrnl/io/pnpmgr/pnpmgr.c:2112
(IopInitializePnpServices))>
<NTOSKRNL.EXE:5c7d2 (ntoskrnl/io/pnpmgr/pnpmgr.c:1810 (IopEnumerateDevice))>
<NTOSKRNL.EXE:5b06a (ntoskrnl/io/pnpmgr/pnpmgr.c:205 (IopStartDevice))>
<NTOSKRNL.EXE:5c9cd (ntoskrnl/io/pnpmgr/pnpmgr.c:2055
(IopActionInitChildServices))>
<NTOSKRNL.EXE:5b5b7 (ntoskrnl/io/pnpmgr/pnpmgr.c:562
(IopTraverseDeviceTreeNode))>--- Press q to abort, any other key to continue
---
<NTOSKRNL.EXE:5b5cc (ntoskrnl/io/pnpmgr/pnpmgr.c:576
(IopTraverseDeviceTreeNode))>
<NTOSKRNL.EXE:5b5ed (ntoskrnl/io/pnpmgr/pnpmgr.c:600 (IopTraverseDeviceTree))>
<NTOSKRNL.EXE:5ca8d (ntoskrnl/io/pnpmgr/pnpmgr.c:2112
(IopInitializePnpServices))>
<NTOSKRNL.EXE:5c7d2 (ntoskrnl/io/pnpmgr/pnpmgr.c:1810 (IopEnumerateDevice))>
<NTOSKRNL.EXE:daff4 (ntoskrnl/io/iomgr/iomgr.c:517 (IoInitSystem at 4))>
<NTOSKRNL.EXE:369d6 (ntoskrnl/ex/init.c:1711 (Phase1InitializationDiscard at 4))>
<NTOSKRNL.EXE:376f7 (ntoskrnl/ex/init.c:1921 (Phase1Initialization at 4))>
<NTOSKRNL.EXE:b00d6 (ntoskrnl/ps/thread.c:159 (PspSystemThreadStartup at 8))>
<NTOSKRNL.EXE:ba1a2 (ntoskrnl\ke\i386\ctxswitch.S:306 (KiThreadStartup at 156))>
kdb:>
--- Comment #4 from Haos <olaf_siejka at o2.pl> 2009-05-31 23:06:01 CET ---
Same error with S3 Trio64V+.
--- Comment #5 from usurp <spetreolle at yahoo.fr> 2009-06-04 17:01:32 CET ---
Please retest with rev 41285 (videoprt debug enabled)
--- Comment #6 from Haos <olaf_siejka at o2.pl> 2009-06-05 11:01:59 CET ---
Created an attachment (id=4035)
--> (http://www.reactos.org/bugzilla/attachment.cgi?id=4035)
Log with videoprt debug
I separated the ASSERT into 4 independent ones. The effect is in attached log.
Crash happening at the end is related to 3dLabs Oxygene GPU, and it occurs when
any window is displayed (exactly while drawing title) - a separate bug though,
not related anyhow with this one.
--
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the Ros-bugs
mailing list