ROS testing on real hardware

Here you can discuss ReactOS related topics.

Moderator: Moderator Team

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

Re: ROS testing on real hardware

Post by oldman » Wed Dec 04, 2013 10:16 am

postby Webunny » 03 Dec 2013 21:30
Bsod with latest build (61208):
It must be your hardware, because I installed 61208 yesterday and it works normally. And I have re-installed it today after trying a new programme yesterday which did not work very well. And it still installs and runs ok. But don't give up, keep testing new revisions.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - with some complementary scripts.
They may help you with a problem, so do have a look at them.

Webunny
Posts: 1201
Joined: Sat Apr 28, 2012 1:30 pm

Re: ROS testing on real hardware

Post by Webunny » Wed Dec 04, 2013 8:46 pm

EmuandCo wrote:Maybe you should photograph the hang with active "Debug to screen" @ boot loader
Sure. Here you go:

Image

Webunny
Posts: 1201
Joined: Sat Apr 28, 2012 1:30 pm

Re: ROS testing on real hardware

Post by Webunny » Thu Dec 05, 2013 12:05 am

oldman wrote:
postby Webunny » 03 Dec 2013 21:30
Bsod with latest build (61208):
It must be your hardware, because I installed 61208 yesterday and it works normally. And I have re-installed it today after trying a new programme yesterday which did not work very well. And it still installs and runs ok. But don't give up, keep testing new revisions.
And so I did. I continued, even though some seem to think it little worth, and with some aid of TheFlash and others, and an adapter I had laying around, I took out the HD of my dedicated ROS machine, and used it as an usb HD to my main one, to search for the debug log. I managed to get this:

Code: Select all

(../../ntoskrnl/kd/kdio.c:243) ---------------------------------------------------------------
(../../ntoskrnl/kd/kdio.c:244) ReactOS 0.4-SVN (Build 20131203-r61208)
(../../ntoskrnl/kd/kdio.c:246) 1 System Processor [767 MB Memory]
(../../ntoskrnl/mm/mminit.c:260)           0x80000000 - 0x81000000	Boot Loaded Image
(../../ntoskrnl/mm/mminit.c:264)           0xB0000000 - 0xB0480000	PFN Database
(../../ntoskrnl/mm/mminit.c:268)           0xB0480000 - 0xB1C50000	ARM3 Non Paged Pool
(../../ntoskrnl/mm/mminit.c:272)           0xB9400000 - 0xBB400000	System View Space
(../../ntoskrnl/mm/mminit.c:276)           0xBB400000 - 0xC0000000	Session Space
(../../ntoskrnl/mm/mminit.c:279)           0xC0000000 - 0xC03FFFFF	Page Tables
(../../ntoskrnl/mm/mminit.c:282)           0xC0300000 - 0xC0300FFF	Page Directories
(../../ntoskrnl/mm/mminit.c:285)           0xC0400000 - 0xC07FFFFF	Hyperspace
(../../ntoskrnl/mm/mminit.c:289)           0xE1000000 - 0xECC00000	ARM3 Paged Pool
(../../ntoskrnl/mm/mminit.c:292)           0xECC00000 - 0xF7BE0000	System PTE Space
(../../ntoskrnl/mm/mminit.c:295)           0xF7BE0000 - 0xFFBE0000	Non Paged Pool Expansion PTE Space
ACPI Compatible Eisa/Isa HAL Detected
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:3186) Firmware mapper is disabled
(../../ntoskrnl/io/pnpmgr/pnpreport.c:353) Reported device: DETECTEDInternal\ACPI_HAL (Root\ACPI_HAL\0)
SAC DriverEntry: Entering.
(../../ntoskrnl/io/iomgr/driver.c:1582) '\Driver\SACDRV' initialization failed, status (0xc0000037)
(../../ntoskrnl/io/iomgr/driver.c:61) Deleting driver object '\Driver\SACDRV'
(../../hal/halx86/legacy/bus/pcibus.c:715) WARNING: PCI Slot Resource Assignment is FOOBAR
(../../ntoskrnl/io/iomgr/iorsrce.c:874) IoReportResourceUsage is halfplemented!
(../../ntoskrnl/io/iomgr/iorsrce.c:874) IoReportResourceUsage is halfplemented!
(../../ntoskrnl/io/iomgr/driver.c:1582) '\Driver\BUSLOGIC' initialization failed, status (0xc00000c0)
(../../ntoskrnl/io/iomgr/driver.c:61) Deleting driver object '\Driver\BUSLOGIC'
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:388) Installed service 'acpi' for critical device '*PNP0C08'
(../../ntoskrnl/io/pnpmgr/pnpinit.c:319) IopOpenRegistryKeyEx() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../drivers/bus/acpi/acpienum.c:69) Detected duplicate device: PNP0C0F 0
(../../drivers/bus/acpi/acpienum.c:69) Detected duplicate device: PNP0C0F 0
(../../drivers/bus/acpi/acpienum.c:69) Detected duplicate device: PNP0C0F 0
(../../drivers/bus/acpi/acpienum.c:69) Detected duplicate device: PNP0C0F 0
(../../drivers/bus/acpi/acpienum.c:69) Detected duplicate device: PNP0C02 0
(../../drivers/bus/acpi/acpienum.c:69) Detected duplicate device: PNP0501 0
(../../drivers/bus/acpi/buspdo.c:692) Using _BBN for bus number
(../../drivers/bus/acpi/buspdo.c:695) Found PCI root hub: 0
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:388) Installed service 'pci' for critical device '*PNP0A03'
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(../../ntoskrnl/io/pnpmgr/pnpinit.c:319) IopOpenRegistryKeyEx() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../drivers/bus/pci/fdo.c:588) Unknown IOCTL 0x9
(../../drivers/bus/pci/fdo.c:588) Unknown IOCTL 0x14
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:388) Installed service 'pci' for critical device 'PCI#CC_0604'
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:388) Installed service 'pci' for critical device 'PCI#CC_0604'
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:388) Installed service 'usbuhci' for critical device 'PCI#CC_0C0300'
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:388) Installed service 'usbuhci' for critical device 'PCI#CC_0C0300'
(../../ntoskrnl/io/pnpmgr/pnpinit.c:319) IopOpenRegistryKeyEx() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../drivers/bus/pci/pdo.c:1288) Enabling command flags for PCI device 0x1 on bus 0x0: None
(../../drivers/bus/pci/fdo.c:588) Unknown IOCTL 0x9
(../../drivers/bus/pci/fdo.c:588) Unknown IOCTL 0x14
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:388) Installed service 'VBE' for critical device 'PCI#CC_0300'
(../../ntoskrnl/mm/ARM3/sysldr.c:3007) ZwOpenFile failed for '\SystemRoot\system32\drivers\vbemp.sys' with status 0xc000003a
(../../ntoskrnl/mm/ARM3/sysldr.c:3007) ZwOpenFile failed for '\SystemRoot\system32\drivers\vbemp.sys' with status 0xc000003a
(../../ntoskrnl/io/pnpmgr/pnpinit.c:319) IopOpenRegistryKeyEx() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../drivers/bus/pci/pdo.c:1288) Enabling command flags for PCI device 0x1e on bus 0x0: None
(../../drivers/bus/pci/fdo.c:588) Unknown IOCTL 0x9
(../../drivers/bus/pci/fdo.c:588) Unknown IOCTL 0x14
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(../../ntoskrnl/io/pnpmgr/pnpinit.c:319) IopOpenRegistryKeyEx() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../lib/drivers/libusb/libusb.cpp:31) USBLIB_AddDevice
(../../drivers/usb/usbuhci/hardware.cpp:168) CUSBHardwareDevice::Initialize
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../drivers/bus/pci/pdo.c:1271) Assigning IRQ 5 to PCI device 0x5f on bus 0x0
(../../drivers/bus/pci/pdo.c:1288) Enabling command flags for PCI device 0x5f on bus 0x0: [Bus master] [I/O space enable] 
(../../drivers/usb/usbuhci/hardware.cpp:254) CUSBHardwareDevice::PnpStart
(../../drivers/usb/usbuhci/hardware.cpp:298) UHCI Base 0000D000 Length ffff0020
(../../drivers/usb/usbuhci/hardware.cpp:606) [USBUHCI] InitializeController
(../../drivers/usb/usbuhci/hardware.cpp:634) [USBUHCI] LEGSUP 53a
(../../drivers/usb/usbuhci/hardware.cpp:639) [USBUHCI] Acquired ownership
(../../drivers/usb/usbuhci/hardware.cpp:642) [USBUHCI] SBRN 10
(../../drivers/usb/usbuhci/hardware.cpp:572) Waiting 10 milliseconds for global reset
(../../drivers/usb/usbuhci/hardware.cpp:733) Index 0 QueueHead F7850000 LinkPhysical 177022 ElementPhysical 1 PhysicalAddress 177000 Request 00000000 NextElementDescriptor 00000000
(../../drivers/usb/usbuhci/hardware.cpp:741) Index 1 QueueHead F7850020 LinkPhysical 177042 ElementPhysical 1 PhysicalAddress 177020 Request 00000000 NextElementDescriptor 00000000
(../../drivers/usb/usbuhci/hardware.cpp:750) Index 2 QueueHead F7850040 LinkPhysical 177062 ElementPhysical 1 PhysicalAddress 177040 Request 00000000 NextElementDescriptor 00000000
(../../drivers/usb/usbuhci/hardware.cpp:758) Index 3 QueueHead F7850060 LinkPhysical 177082 ElementPhysical 1 PhysicalAddress 177060 Request 00000000 NextElementDescriptor 00000000
(../../drivers/usb/usbuhci/hardware.cpp:766) Index 4 QueueHead F7850080 LinkPhysical 1 ElementPhysical 1 PhysicalAddress 177080 Request 00000000 NextElementDescriptor 00000000
(../../drivers/usb/usbuhci/hardware.cpp:833) [USBUHCI] Controller initialized
(../../drivers/usb/usbuhci/hardware.cpp:382) Starting Controller
(../../drivers/usb/usbuhci/hardware.cpp:471) [USBUHCI] USBCMD: 80 USBSTS 20
(../../drivers/usb/usbuhci/hardware.cpp:489) [USBUHCI] Status 0
(../../drivers/usb/usbuhci/hardware.cpp:500) [USBUHCI] USBCMD: 81 USBSTS 0
(../../drivers/usb/usbuhci/hardware.cpp:531) [USBUHCI] Controller Started
(../../drivers/usb/usbuhci/hardware.cpp:532) [USBUHCI] Controller Status 0
(../../drivers/usb/usbuhci/hardware.cpp:533) [USBUHCI] Controller Cmd Status c1
(../../drivers/usb/usbuhci/hardware.cpp:534) [USBUHCI] Controller Interrupt Status d
(../../drivers/usb/usbuhci/hardware.cpp:535) [USBUHCI] Controller Frame 0
(../../drivers/usb/usbuhci/hardware.cpp:536) [USBUHCI] Controller Port Status 0 80
(../../drivers/usb/usbuhci/hardware.cpp:537) [USBUHCI] Controller Port Status 1 80
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(../../lib/drivers/libusb/hub_controller.cpp:3921) CHubController::CreatePDO: DeviceName \Device\USBPDO-0
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:388) Installed service 'usbhub' for critical device 'USB#ROOT_HUB'
(../../ntoskrnl/io/pnpmgr/pnpinit.c:319) IopOpenRegistryKeyEx() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../drivers/usb/usbhub/fdo.c:1631) Status 0, Result 0x00000040
(../../drivers/usb/usbhub/fdo.c:1632) InformationLevel 0
(../../drivers/usb/usbhub/fdo.c:1633) ActualLength 40
(../../drivers/usb/usbhub/fdo.c:1634) PortNumber 0
(../../drivers/usb/usbhub/fdo.c:1635) DeviceDescriptor 20000112
(../../drivers/usb/usbhub/fdo.c:1636) HubAddress 0
(../../drivers/usb/usbhub/fdo.c:1637) NumberofPipes 0
(../../drivers/usb/usbhub/fdo.c:1730) HubDeviceExtension->UsbExtHubInfo.NumberOfPorts 2
(../../drivers/usb/usbuhci/hardware.cpp:1160) [UHCI] SetPortFeature PortId 0 Feature 8
(../../drivers/usb/usbuhci/hardware.cpp:1160) [UHCI] SetPortFeature PortId 1 Feature 8
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(../../ntoskrnl/io/pnpmgr/pnpinit.c:319) IopOpenRegistryKeyEx() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../lib/drivers/libusb/libusb.cpp:31) USBLIB_AddDevice
(../../drivers/usb/usbuhci/hardware.cpp:168) CUSBHardwareDevice::Initialize
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../drivers/bus/pci/pdo.c:1271) Assigning IRQ 11 to PCI device 0x9f on bus 0x0
(../../drivers/bus/pci/pdo.c:1288) Enabling command flags for PCI device 0x9f on bus 0x0: [Bus master] [I/O space enable] 
(../../drivers/usb/usbuhci/hardware.cpp:254) CUSBHardwareDevice::PnpStart
(../../drivers/usb/usbuhci/hardware.cpp:298) UHCI Base 0000D800 Length ffff0020
(../../drivers/usb/usbuhci/hardware.cpp:606) [USBUHCI] InitializeController
(../../drivers/usb/usbuhci/hardware.cpp:634) [USBUHCI] LEGSUP 510
(../../drivers/usb/usbuhci/hardware.cpp:639) [USBUHCI] Acquired ownership
(../../drivers/usb/usbuhci/hardware.cpp:642) [USBUHCI] SBRN 10
(../../drivers/usb/usbuhci/hardware.cpp:572) Waiting 10 milliseconds for global reset
(../../lib/drivers/libusb/hub_controller.cpp:313) [USBUHCI] SCE Request B1C05048 TransferBufferLength 8 Flags 3 MDL 00000000
(../../lib/drivers/libusb/hub_controller.cpp:324) [USBUHCI] Port 0: Status 100, Change 0
(../../lib/drivers/libusb/hub_controller.cpp:324) [USBUHCI] Port 1: Status 100, Change 0
(../../drivers/usb/usbuhci/hardware.cpp:733) Index 0 QueueHead F784C000 LinkPhysical 17b022 ElementPhysical 1 PhysicalAddress 17b000 Request 00000000 NextElementDescriptor 00000000
(../../drivers/usb/usbuhci/hardware.cpp:741) Index 1 QueueHead F784C020 LinkPhysical 17b042 ElementPhysical 1 PhysicalAddress 17b020 Request 00000000 NextElementDescriptor 00000000
(../../drivers/usb/usbuhci/hardware.cpp:750) Index 2 QueueHead F784C040 LinkPhysical 17b062 ElementPhysical 1 PhysicalAddress 17b040 Request 00000000 NextElementDescriptor 00000000
(../../drivers/usb/usbuhci/hardware.cpp:758) Index 3 QueueHead F784C060 LinkPhysical 17b082 ElementPhysical 1 PhysicalAddress 17b060 Request 00000000 NextElementDescriptor 00000000
(../../drivers/usb/usbuhci/hardware.cpp:766) Index 4 QueueHead F784C080 LinkPhysical 1 ElementPhysical 1 PhysicalAddress 17b080 Request 00000000 NextElementDescriptor 00000000
(../../drivers/usb/usbuhci/hardware.cpp:833) [USBUHCI] Controller initialized
(../../drivers/usb/usbuhci/hardware.cpp:382) Starting Controller
(../../drivers/usb/usbuhci/hardware.cpp:471) [USBUHCI] USBCMD: 80 USBSTS 20
(../../drivers/usb/usbuhci/hardware.cpp:489) [USBUHCI] Status 0
(../../drivers/usb/usbuhci/hardware.cpp:500) [USBUHCI] USBCMD: 81 USBSTS 0
(../../drivers/usb/usbuhci/hardware.cpp:531) [USBUHCI] Controller Started
(../../drivers/usb/usbuhci/hardware.cpp:532) [USBUHCI] Controller Status 0
(../../drivers/usb/usbuhci/hardware.cpp:533) [USBUHCI] Controller Cmd Status c1
(../../drivers/usb/usbuhci/hardware.cpp:534) [USBUHCI] Controller Interrupt Status d
(../../drivers/usb/usbuhci/hardware.cpp:535) [USBUHCI] Controller Frame 0
(../../drivers/usb/usbuhci/hardware.cpp:536) [USBUHCI] Controller Port Status 0 80
(../../drivers/usb/usbuhci/hardware.cpp:537) [USBUHCI] Controller Port Status 1 80
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(../../lib/drivers/libusb/hub_controller.cpp:3921) CHubController::CreatePDO: DeviceName \Device\USBPDO-1
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:388) Installed service 'usbhub' for critical device 'USB#ROOT_HUB'
(../../ntoskrnl/io/pnpmgr/pnpinit.c:319) IopOpenRegistryKeyEx() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../drivers/usb/usbhub/fdo.c:1631) Status 0, Result 0x00000040
(../../drivers/usb/usbhub/fdo.c:1632) InformationLevel 0
(../../drivers/usb/usbhub/fdo.c:1633) ActualLength 40
(../../drivers/usb/usbhub/fdo.c:1634) PortNumber 0
(../../drivers/usb/usbhub/fdo.c:1635) DeviceDescriptor 20000112
(../../drivers/usb/usbhub/fdo.c:1636) HubAddress 0
(../../drivers/usb/usbhub/fdo.c:1637) NumberofPipes 0
(../../drivers/usb/usbhub/fdo.c:1730) HubDeviceExtension->UsbExtHubInfo.NumberOfPorts 2
(../../drivers/usb/usbuhci/hardware.cpp:1160) [UHCI] SetPortFeature PortId 0 Feature 8
(../../drivers/usb/usbuhci/hardware.cpp:1160) [UHCI] SetPortFeature PortId 1 Feature 8
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(../../ntoskrnl/mm/ARM3/sysldr.c:3007) ZwOpenFile failed for '\SystemRoot\system32\drivers\vbemp.sys' with status 0xc000003a
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(../../ntoskrnl/mm/ARM3/sysldr.c:3007) ZwOpenFile failed for '\SystemRoot\system32\drivers\vbemp.sys' with status 0xc000003a
(../../lib/drivers/libusb/hub_controller.cpp:313) [USBUHCI] SCE Request B1935BB0 TransferBufferLength 8 Flags 3 MDL 00000000
(../../lib/drivers/libusb/hub_controller.cpp:324) [USBUHCI] Port 0: Status 100, Change 0
(../../lib/drivers/libusb/hub_controller.cpp:324) [USBUHCI] Port 1: Status 100, Change 0
(../../ntoskrnl/io/iomgr/iorsrce.c:725) Failed opening given symbolic link!
(../../ntoskrnl/mm/ARM3/sysldr.c:174) Loading: \SystemRoot\system32\drivers\vbemp.sys at F7843000 with 8 pages
(../../ntoskrnl/mm/ARM3/sysldr.c:174) Loading: \SystemRoot\system32\drivers\videoprt.sys at F782D000 with 16 pages
(../../ntoskrnl/io/pnpmgr/pnpinit.c:319) IopOpenRegistryKeyEx() failed with Status C0000034
(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
Formatted registry key '\Registry\Machine\System\CurrentControlSet\Services\VBE' -> '\Registry\Machine\System\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Services\VBE\Device0'
WARNING:  ExUuidCreate at ../../ntoskrnl/ex/uuid.c:305 is UNIMPLEMENTED!
(../../win32ss/drivers/videoprt/registry.c:307) Failed to open device software key. Status 0xc0000034(../../ntoskrnl/io/iomgr/driver.c:697) ZwOpenKey() failed with Status C0000034
(../../drivers/bus/pci/pdo.c:1271) Assigning IRQ 5 to PCI device 0x0 on bus 0x1
(../../drivers/bus/pci/pdo.c:1288) Enabling command flags for PCI device 0x0 on bus 0x1: [Bus master] [Memory space enable] 
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:848) IRP_MN_QUERY_CAPABILITIES failed with status 0xc00000bb
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:681) IopInitiatePnpIrp() failed (Status 0xc00000bb)
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
Edit:

Seen some recent remarks, I should make it clear once more, apparently.

I don't know how many times I must repeat this:

1)It's a regression only noticeable when HW-testing; it remains UNDETECTED when testing in VM.

2)I CAN NOT get any decent debug-info from the debug screen mode because there IS NOTHING to be shown. I already said it was blank. People keep asking and asking me for that but the ONLY thing I get in that mode is this: http://www.reactos.org/forum/viewtopic. ... 15#p105043

3)I DO NOT have a serial cable (as said many times too), therefore I can not provide debug info that way.

4)After much effort and time, I managed to swap my HD's after I made a debug log mode with tb tracking. When I got the debug log file out of there, I posted (see above). Theflash and others have analysed it: it has NO KD and BT DID NOT work

Thus: it completely freezes, and it's doubtful even a serial cable would help.

In conclusion: the shabby pictures and manual typing of bsods are the ONLY thing that's left, together with my painstakingly narrowing down the build that causes the regression by burning builds two dozen times.

Yes, under those circumstances, I can't provide the coders with an easy-to-digest line-by-line BT. I would say: it's better to have 10% info than 0%. And it's better to know one has a thusfar UNDETECTED regression that has been narrowed down to a specific build and a probably cause, EVEN if one does not have the exact line yet, than to have nothing at all.


And 5) Together with Theflash and some others, I managed to confirm that it is, without any doubt, the driver. (not the kernel, etc.) I removed my card, rebooted ROS, renamed my cmipci.sys, restarted, and everything worked well, this time. I returned it to its original name, restarted, and it borked again. I think we can safely assume, thus, it is, indeed, the driver.

bernarddt
Posts: 91
Joined: Fri Aug 29, 2008 1:57 pm
Location: Pretoria, RSA

Re: ROS testing on real hardware

Post by bernarddt » Thu Dec 05, 2013 8:19 am

Webunny wrote:
EmuandCo wrote:Maybe you should photograph the hang with active "Debug to screen" @ boot loader
Sure. Here you go:

Image
+1! :lol:

PascalDragon
Posts: 123
Joined: Wed Aug 04, 2010 7:34 pm

Re: ROS testing on real hardware

Post by PascalDragon » Thu Dec 05, 2013 8:22 am

Webunny wrote:And 5) Together with Theflash and some others, I managed to confirm that it is, without any doubt, the driver. (not the kernel, etc.) I removed my card, rebooted ROS, renamed my cmipci.sys, restarted, and everything worked well, this time. I returned it to its original name, restarted, and it borked again. I think we can safely assume, thus, it is, indeed, the driver.
It could also be that the driver expects a certain behavior on Windows, but gets a different one on ReactOS (so this would be a bug in the kernel then).

Regards,
Sven
Free Pascal compiler developer

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

Re: ROS testing on real hardware

Post by PurpleGurl » Thu Dec 05, 2013 8:47 am

Too bad there isn't some code that could go between the kernel and the driver to note and observe the behavior and all. It could dump to somewhere. I mean, like the keyboard test that helped debug the keyboard and mouse stuff.

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

Re: ROS testing on real hardware

Post by oldman » Thu Dec 05, 2013 10:26 am

Webunny,
It is really worth getting a serial cable (null modem) if you are going to keep testing in real hardware. There is much more debug info sent out to a log file or serial port, than is displayed to the screen.

The null modem cables are not too expensive, if you go to a small shop. The big boys sell them about three times as much as the small shops, at least here in the uk. I have had one for about two years and it cost about £5.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - with some complementary scripts.
They may help you with a problem, so do have a look at them.

roytam
Posts: 61
Joined: Sat Dec 04, 2004 2:02 pm

Re: ROS testing on real hardware

Post by roytam » Thu Dec 05, 2013 11:34 am

oldman wrote:Webunny,
It is really worth getting a serial cable (null modem) if you are going to keep testing in real hardware. There is much more debug info sent out to a log file or serial port, than is displayed to the screen.

The null modem cables are not too expensive, if you go to a small shop. The big boys sell them about three times as much as the small shops, at least here in the uk. I have had one for about two years and it cost about £5.
actually it may be a bit hard to find, you may want to build your own null modem cable:
http://www.lammertbies.nl/comm/info/RS- ... modem.html
Last edited by roytam on Thu Dec 05, 2013 2:16 pm, edited 1 time in total.

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

Re: ROS testing on real hardware

Post by oldman » Thu Dec 05, 2013 1:45 pm

by Webunny » 04 Dec 2013 22:05
And so I did. I continued, even though some seem to think it little worth, and with some aid of TheFlash and others, and an adapter I had laying around, I took out the HD of my dedicated ROS machine, and used it as an usb HD to my main one, to search for the debug log.
I use a Linux liveCD (puppy) for accessing files on my test machine and for accessing the internet. So wouldn't it be worth getting a liveCD, so in future, if such a situation arises again, you can get at the log file without extracting your hard drive.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - with some complementary scripts.
They may help you with a problem, so do have a look at them.

DOSGuy
Posts: 582
Joined: Wed Sep 14, 2011 5:55 pm
Contact:

Re: ROS testing on real hardware

Post by DOSGuy » Thu Dec 05, 2013 5:32 pm

I bought a null modem cable for $5.99 a few days ago. I wasn't actually looking for one, but when saw it I thought about the possibility of using it for real hardware testing. They're definitely not expensive.
Today entirely the maniac there is no excuse with the article. Get free DOS, Windows and OS/2 games at RGB Classic Games.

bernarddt
Posts: 91
Joined: Fri Aug 29, 2008 1:57 pm
Location: Pretoria, RSA

Re: ROS testing on real hardware

Post by bernarddt » Thu Dec 05, 2013 8:22 pm

oldman wrote: I use a Linux liveCD (puppy) for accessing files on my test machine and for accessing the internet. So wouldn't it be worth getting a liveCD, so in future, if such a situation arises again, you can get at the log file without extracting your hard drive.
What a simple solution! If your hardware is not that old, you can also boot from a Live USB installation. I created one with Ubuntu and it works like a charm. You just need a motherboard + BIOS that support booting from USB Thumb Drive. And Ubuntu has an option of creating a bootable USB drive from it's installation menu! The bonus to USB is if you change settings in Ubuntu then, it is actually saved and loaded next time. Not like a read-only Live CD.

Webunny
Posts: 1201
Joined: Sat Apr 28, 2012 1:30 pm

Re: ROS testing on real hardware

Post by Webunny » Thu Dec 05, 2013 8:31 pm

bernarddt wrote:
oldman wrote: I use a Linux liveCD (puppy) for accessing files on my test machine and for accessing the internet. So wouldn't it be worth getting a liveCD, so in future, if such a situation arises again, you can get at the log file without extracting your hard drive.
What a simple solution! If your hardware is not that old, you can also boot from a Live USB installation. I created one with Ubuntu and it works like a charm. You just need a motherboard + BIOS that support booting from USB Thumb Drive. And Ubuntu has an option of creating a bootable USB drive from it's installation menu! The bonus to USB is if you change settings in Ubuntu then, it is actually saved and loaded next time. Not like a read-only Live CD.
It was suggested in the irc chan too. It's a worthwhile suggestion on itself, and I certainly will think about that, but the problem that now arises is not that I couldn't get the debug file log, but that the log didn't show the real problem (KD/TB didn't work). Using a linux live-cd distribution (I suppose ubuntu would do too? I have some of those) wouldn't solve this issue, thus.

bernarddt
Posts: 91
Joined: Fri Aug 29, 2008 1:57 pm
Location: Pretoria, RSA

Re: ROS testing on real hardware

Post by bernarddt » Thu Dec 05, 2013 8:39 pm

Webunny wrote:It was suggested in the irc chan too. It's a worthwhile suggestion on itself, and I certainly will think about that, but the problem that now arises is not that I couldn't get the debug file log, but that the log didn't show the real problem (KD/TB didn't work). Using a linux live-cd distribution (I suppose ubuntu would do too? I have some of those) wouldn't solve this issue, thus.
Nope, this will not help if the system does not generate a (useful) log file. I don't know anything about debugging ReactOS. So I have no idea if there is a difference between the debug info over a serial cable and normal "boot with debug mode" log files.

I'm also planning to test on real hardware, I have quite a few decommissioned pc's standing in my living room! And I have bundles of hareware stored in my drawers from PC's I have collected and taken apart in the past years. So your findings will probably help me in the future...

Webunny
Posts: 1201
Joined: Sat Apr 28, 2012 1:30 pm

Re: ROS testing on real hardware

Post by Webunny » Thu Dec 05, 2013 10:26 pm

bernarddt wrote:
Webunny wrote:It was suggested in the irc chan too. It's a worthwhile suggestion on itself, and I certainly will think about that, but the problem that now arises is not that I couldn't get the debug file log, but that the log didn't show the real problem (KD/TB didn't work). Using a linux live-cd distribution (I suppose ubuntu would do too? I have some of those) wouldn't solve this issue, thus.
Nope, this will not help if the system does not generate a (useful) log file. I don't know anything about debugging ReactOS. So I have no idea if there is a difference between the debug info over a serial cable and normal "boot with debug mode" log files.

I'm also planning to test on real hardware, I have quite a few decommissioned pc's standing in my living room! And I have bundles of hareware stored in my drawers from PC's I have collected and taken apart in the past years. So your findings will probably help me in the future...
Yes, you do that. There is a lack of real HW testing, imho. Sure, it's far more easier to test things on VM (personally I use Virtualbox and putty), but when push comes to shove, there is nothing better than to test it on real HW, though it's harder work. It's more 'back to basics', I guess. But certainly in regard to drivers this is useful, as my testing has shown. There is no way (and there hasn't) that any VM-testing would have noticed there was this kind of regression, for instance. I suppose the reason is, that VM only emulates some standard 'equipment' virtually, while in reality, certainly with PC's (less with consoles), hardware, and how it works and interacts with software (including OS, and in particular the drivers), greatly diverge. In theory, you could have something that works excellent in VM, but still borks on 80% of all real HW. (in reality, this will be less, but as is shown in my case, it certainly is true that HW reveals things VM-testing don't).

So I think we need more real HW testing, with a variety of machines. That said, I know from my test with the 3.14 build, that only 1 out of four of my PC's managed the run it successfully (the one I'm using now for 3.15 testing). The rest simply did not work on it. If you ever get to it, let me know if your success-rate is higher than 25%; it may give an indication in ROS is slowly getting more compatible with real hardware.

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

Re: ROS testing on real hardware

Post by oldman » Thu Dec 05, 2013 10:43 pm

Post by Webunny » 05 Dec 2013 20:26
let me know if your success-rate is higher than 25%; it may give an indication in ROS is slowly getting more compatible with real hardware.
If you are referring to Ros installing and running, then I have this year been getting something around 95% success rate and possibly 100%! But I only test on one computer.
The issues that I have, are more to do with software that does not install or does not run correctly. The only OS related issue that I can think of, is, that there is a problem with the log in, but that was still being coded.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - with some complementary scripts.
They may help you with a problem, so do have a look at them.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests