Test run failed due to exceeding the maximum number of restarts, Problem
started with unexpected crash:

Running Wine Test, Module: pdh, Test: pdh
Assertion 'KiTimerTableListHead[Index].Time.QuadPart <=
Timer->DueTime.QuadPart' failed at ../../ntoskrnl/ke/dpc.c line 252

Entered debugger on embedded INT3 at 0x0008:0x809257d2.
kdb:> bt
Eip:
<NTOSKRNL.EXE:1257d3 (../../lib/rtl/i386/debug_asm.S:35
(_DbgBreakPoint@0))>
Frames:
<NTOSKRNL.EXE:82a22 (../../ntoskrnl/ke/dpc.c:251
(KiTimerExpiration@16))>
<NTOSKRNL.EXE:82c20 (../../ntoskrnl/ke/dpc.c:576 (@KiRetireDpcList@4))>
<NTOSKRNL.EXE:10a2fa (../../ntoskrnl/ke/i386/ctxswitch.S:78
(KiRetireDpcListInDpcStack))>
<HAL.DLL:a71b (../../hal/halx86/up/pic.c:1323
(@HalpDispatchInterrupt2ndEntry@4))>
<HAL.DLL:a684 (../../hal/halx86/up/pic.c:1243
(HalEndSystemInterrupt@8))>
<NTOSKRNL.EXE:89dbf
(../../ntoskrnl/include/internal/arch/../i386/ke.h:829
(@KeUpdateSystemTime@12))>
<HAL.DLL:9b6b (../../hal/halx86/generic/timer.c:172
(@HalpClockInterruptHandler@4))>
<HAL.DLL:9f52 (../../hal/halx86/generic/trap.S:0 (_HalpClockInterrupt))>
<rosautotest.exe:67cb>
<rosautotest.exe:703d>

The subsequent reboots have been asserting at startup:

Boot took 33308394332 cycles!
Interrupts: 1838 System Calls: 15454 Context Switches: 1688
(../../ntoskrnl/se/semgr.c:646) HACK: Should deny access for caller:
granted 0x90003, desired 0x190003 (generic mapping B12893B0).
(../../base/services/eventlog/eventlog.c:296) RegQueryValueEx failed:
126
(../../base/services/eventlog/eventlog.c:393) Failed to load Wine
(../../base/services/wlansvc/wlansvc.c:145) wlansvc: main() started
(../../base/services/wlansvc/wlansvc.c:96) ServiceMain() called
(../../base/services/wlansvc/wlansvc.c:130) ServiceMain() done
(../../base/system/services/rpcserver.c:1716)
RNotifyBootConfigStatus(00000000 1) called
Assertion 'CellBlock < RegistryHive->Storage[CellType].Length' failed at
../../lib/cmlib/hivecell.c line 32

Entered debugger on embedded INT3 at 0x0008:0x809257d2.
kdb:> bt
Eip:
<NTOSKRNL.EXE:1257d3 (../../lib/rtl/i386/debug_asm.S:35
(_DbgBreakPoint@0))>
Frames:
<NTOSKRNL.EXE:124087 (../../lib/cmlib/hivecell.c:32
(HvpGetCellHeader@8))>
<NTOSKRNL.EXE:124119 (../../lib/cmlib/hivecell.c:74 (HvGetCell@8))>
<NTOSKRNL.EXE:125318 (../../lib/cmlib/cminit.c:97
(CmpPrepareIndexOfKeys@8))>
<NTOSKRNL.EXE:125407 (../../lib/cmlib/cminit.c:124 (CmpPrepareKey@8))>
<NTOSKRNL.EXE:125435 (../../lib/cmlib/cminit.c:135 (CmPrepareHive@4))>
<NTOSKRNL.EXE:12528e (../../lib/cmlib/hiveinit.c:506 (HvInitialize@52))>
<NTOSKRNL.EXE:1dca5 (../../ntoskrnl/config/cminit.c:177
(CmpInitializeHive@40))>
<NTOSKRNL.EXE:26132 (../../ntoskrnl/config/cmsysini.c:287
(CmpInitHiveFromFile@20))>
<NTOSKRNL.EXE:2060d (../../ntoskrnl/config/cmlazy.c:259
(CmpCmdHiveOpen@20))>
<NTOSKRNL.EXE:1548d (../../ntoskrnl/config/cmapi.c:1713 (CmLoadKey@16))>
<NTOSKRNL.EXE:2928e (../../ntoskrnl/config/ntapi.c:843
(NtLoadKeyEx@16))>
<NTOSKRNL.EXE:29356 (../../ntoskrnl/config/ntapi.c:791 (NtLoadKey@8))>
<NTOSKRNL.EXE:110fb2 (../../ntoskrnl/ke/i386/traphdlr.c:1629
(@KiFastCallEntryHandler@8))>
<NTOSKRNL.EXE:10eba1 (../../ntoskrnl/ke/i386/trap.s:150
(_KiFastCallEntry))>
<ntdll.dll:b009>
<userenv.dll:62a4>
<winlogon.exe:2317>
<winlogon.exe:3023>
<user32.dll:4bb39>
<user32.dll:4c188>--- Press q to abort, any other key to continue ---

<user32.dll:4d37b>
<winlogon.exe:4b00>

----- Original message -----
From: build...@reactos.org
To: cae...@myopera.com
Subject: buildbot failure in ReactOS on Windows_AMD64_1 VBox-Test
Date: Thu, 13 Sep 2012 01:14:24 +0000

The Buildbot has finished a build on builder Windows_AMD64_1 VBox-Test
while building ReactOS.
Full details are available at:
 http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/6579

Buildbot URL: http://build.reactos.org/

Buildslave for this Build: Windows_AMD64_2

Build Reason: Triggerable(Windows_AMD64_1 VBox-Test Trigger)
Build Source Stamp: 57288
Blamelist: mnordell

BUILD FAILED: failed test

sincerely,
 -The Buildbot



-- 
With best regards
Caemyr

_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Reply via email to