0.4.7 Testing

Here you can discuss ReactOS related topics.

Moderator: Moderator Team

Post Reply
Heis Spiter
Developer
Posts: 181
Joined: Sun Sep 03, 2006 11:39 am
Location: Paris, France
Contact:

0.4.7 Testing

Post by Heis Spiter » Tue Oct 31, 2017 9:13 am

We have another release coming up! Please support us in testing for regressions.

https://reactos.org/wiki/Tests_for_0.4.7

Thanks!
Pierre Schweitzer (aka Heis Spiter)
ReactOS kernel developer.
ReactOS systems administrator.

PurpleGurl
Posts: 1534
Joined: Fri Aug 07, 2009 5:11 am
Location: USA

Re: 0.4.7 Testing

Post by PurpleGurl » Thu Nov 16, 2017 4:38 am

Why does it seem like there are many regressions in this RC?

DCH3416
Posts: 2
Joined: Sat Nov 18, 2017 1:06 am

Re: 0.4.7 Testing

Post by DCH3416 » Sat Nov 18, 2017 1:47 am

Installed in VirtualBox on a FreeBSD host, no trouble installing. Installed guest additions, added share directory to begin testing some software. Installed GIMP, installed Visual C++ 2008 Redist. Launched GIMP which started up as expected and then froze after the splash screen. Switched to an explorer window and accidentally pressed the return key which launched vcredist setup application. Choose 'cancel' followed by 'yes' to confirm exiting visual C setup and VM froze entirely. Powered off the VM then powered back on, booted, and the system cannot start. The following is the debug output:

Code: Select all

(../../boot/freeldr/freeldr/arch/i386/i386vid.c:263) err: VESA/DDC installation check failed
(../../ntoskrnl/kd/kdio.c:104) -----------------------------------------------------
(../../ntoskrnl/kd/kdio.c:105) ReactOS 0.4.7-dev (Build 20171029-0.4.7-rc1-4-g68655cc) (Commit 68655cc1e9f395544a97339b3105f586a95fd44d)
(../../ntoskrnl/kd/kdio.c:106) 1 System Processor [511 MB Memory]
(../../ntoskrnl/kd/kdio.c:107) Command Line: DEBUG DEBUGPORT=COM1 BAUDRATE=115200 SOS
(../../ntoskrnl/kd/kdio.c:108) ARC Paths: multi(0)disk(0)rdisk(0)partition(1) \ multi(0)disk(0)rdisk(0)partition(1) \ReactOS\
(../../ntoskrnl/ke/i386/cpu.c:450) Supported CPU features : KF_V86_VIS KF_RDTSC KF_CR4 KF_CMOV KF_GLOBAL_PAGE KF_LARGE_PAGE KF_MTRR KF_CMPXCHG8B KF_MMX KF_WORKING_PTE KF_PAT KF_FXSR KF_FAST_SYSCALL KF_XMMI   KF_XMMI64    
(../../ntoskrnl/ke/i386/cpu.c:722) Prefetch Cache: 64 bytes	L2 Cache: 262144 bytes	L2 Cache Line: 64 bytes	L2 Cache Associativity: 8
(../../hal/halx86/acpi/halacpi.c:782) ACPI Timer at: 4008h (EXT: 256)
(../../hal/halx86/acpi/halacpi.c:890) ACPI 2.0 Detected. Tables: [RSDT] [FACP] 

...

(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\hidusb.sys at F7419000 with d pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\hidclass.sys at F7407000 with 12 pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\hidparse.sys at F73E5000 with 13 pages
(../../drivers/usb/usbhub/pdo.c:850) PDO IRP_MJ_PNP / unknown minor function 0xd
WARNING:  USBHUB_PdoStartDevice at ../../drivers/usb/usbhub/pdo.c:450 is UNIMPLEMENTED!
(../../drivers/usb/usbohci/usb_queue.cpp:667) URB failed with status 0xc0000004
(../../drivers/usb/usbohci/usb_request.cpp:1855) OHCI_TD_CONDITION_STALL detected in TransferDescriptor TransferDescriptor F77063E0
(../../sdk/lib/drivers/libusb/hub_controller.cpp:2191) [USBOHCI] URB_FUNCTION_CLASS_INTERFACE failed with Urb Status 0
(../../drivers/hid/hidusb/hidusb.c:1416) Status c0000001
(../../drivers/usb/usbhub/pdo.c:317) IOCTL_INTERNAL_USB_SUBMIT_URB Function 28 NOT IMPLEMENTED
(../../drivers/usb/usbhub/pdo.c:850) PDO IRP_MJ_PNP / unknown minor function 0x14
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\mouhid.sys at F73FC000 with b pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\cdfs.sys at F73CD000 with 18 pages
(../../base/system/smss/pagefile.c:909) SMSS:PFILE: Volume `\??\D:\' (3) cannot store a paging file
Boot took 13752927618 cycles!
Interrupts: 881 System Calls: 16542 Context Switches: 665
(../../ntoskrnl/config/cmsysini.c:1230) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1230) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1230) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1230) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1230) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1230) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1230) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmcheck.c:25) CmCheckRegistry(0xB0E5A008, 0) is UNIMPLEMENTED!
(../../ntoskrnl/config/cmcheck.c:25) CmCheckRegistry(0xB0E59008, 0) is UNIMPLEMENTED!
(../../ntoskrnl/config/cmcheck.c:25) CmCheckRegistry(0xB0E633E8, 0) is UNIMPLEMENTED!
(../../sdk/lib/cmlib/hiveinit.c:277) Invalid bin at BlockIndex 425, Signature 0x0, Size 0x0

*** Fatal System Error: 0xc0000218
                       (0x00060010,0x00000000,0x00000000,0x00000000)

[7h
Entered debugger on embedded INT3 at 0x0008:0x80945f84.
kdb:> 

DCH3416
Posts: 2
Joined: Sat Nov 18, 2017 1:06 am

Re: 0.4.7 Testing

Post by DCH3416 » Sat Nov 18, 2017 3:49 am

Glancing at that a little closer, I'm pretty sure the hard shutdown fried the registry.

Where is a good place to begin testing a release candidate?

oldman
Posts: 979
Joined: Sun Dec 20, 2009 1:23 pm

Re: 0.4.7 Testing

Post by oldman » Sat Nov 18, 2017 10:14 am

DCH3416 wrote:Installed in VirtualBox on a FreeBSD host, no trouble installing. Installed guest additions, added share directory to begin testing some software. Installed GIMP, installed Visual C++ 2008 Redist. Launched GIMP which started up as expected and then froze after the splash screen. Switched to an explorer window and accidentally pressed the return key which launched vcredist setup application. Choose 'cancel' followed by 'yes' to confirm exiting visual C setup and VM froze entirely. Powered off the VM then powered back on, booted, and the system cannot start. The following is the debug output:
When you see this in the terminal
"Entered debugger on embedded INT3 at 0x0008:0x80945f84.
kdb:>
"
type bt at the prompt, from within the terminal, not within the VM. You will then get more information. And don't forget, that JIRA is the place the place to make bug reports.
DCH3416 wrote:Where is a good place to begin testing a release candidate?
I do not know what you actually mean by this! But if you want to help testing, then look here and find something that as not been tested.
You can keep your Virtual Machines - I test in real hardware!
Please keep the Windows classic (9x/2000) look and feel.
A layman's guide - debugging - bug reporting - compiling - complementary scripts.

Thentair
Posts: 1
Joined: Wed Nov 22, 2017 2:01 pm

Re: 0.4.7 Testing

Post by Thentair » Mon Dec 11, 2017 8:54 pm

thanks a lot for the information. do you have some updates for 0.4.7 testing? thanks. while sitting home searching for pharmacy reviews because of my health issues i thought that i could learn more.
Last edited by Thentair on Tue Jan 23, 2018 6:56 pm, edited 1 time in total.

omegicus
Posts: 1
Joined: Mon Dec 25, 2017 10:00 pm

Re: 0.4.7 Testing

Post by omegicus » Mon Dec 25, 2017 10:05 pm

QEMU 0.14.50
Memory - 512M
LiveCD 0.4.7

Just launched 1 app - game, after some mice clicks got this situation - at first mouse pointer crashes, then all window(s)
Image

hbelusca
Developer
Posts: 954
Joined: Sat Dec 26, 2009 10:36 pm
Location: Zagreb, Croatia

Re: 0.4.7 Testing

Post by hbelusca » Mon Dec 25, 2017 10:15 pm

Thentair wrote:thanks a lot for the information. do you have some updates for 0.4.7 testing? thanks
Who cares about 0.4.7 anymore? The testings had to be done using the release candidates of the 0.4.7, not after it has been released !!
What you can test however are the nightly builds, and see whether they have regressed with respect to the 0.4.7 release.

milon
Posts: 963
Joined: Sat Sep 05, 2009 9:26 pm

Re: 0.4.7 Testing

Post by milon » Thu Dec 28, 2017 6:56 pm

Maybe we should un-sticky this thread then? Or otherwise mark it as obsolete....

Post Reply

Who is online

Users browsing this forum: No registered users and 12 guests