Description
Recently bought notebook HP 245 G6, as there is no optical drive, 1st and 2nd stage were performed from Qemu VM using a linux live usb, so ReactOS could be installed at hard disk.
3rd stage (first boot) starts well, showing some new hardware wizards for new devices (mostly ACPI controllers), but when the system loads the multimedia devices, it break the debugger and shows a prompt.
Doing a backtrace the Eip points to HDAudBus.sys (drivers/wdm/audio/hdaudbus/fdo.cpp:674) (HDA_FDOQueryBusRelations)
The line 674 is
672 for (AFGIndex = 0; AFGIndex < Codec->AudioGroupCount; AFGIndex++)
|
673 {
|
*674 DeviceRelations->Objects[DeviceRelations->Count] = Codec->AudioGroups[AFGIndex]->ChildPDO;*
|
675 ObReferenceObject(Codec->AudioGroups[AFGIndex]->ChildPDO);
|
676 DeviceRelations->Count++;
|
677 }
|
Update
I think found the bug
On debug log says:
(drivers/wdm/audio/hdaudbus/fdo.cpp:214) hda Codec 0 Vendor:8094 ... NodeStart 255 NodeCount 255
|
this is key to find the bug, in the file there is a loop 2 lines below:
216 for (NodeId = Response.start; NodeId < Response.start + Response.count; NodeId++) {
|
then there are 2 DPRINTs that repeats a lot of times
(drivers/wdm/audio/hdaudbus/fdo.cpp:222) NodeId 255 GroupType 1
|
(drivers/wdm/audio/hdaudbus/fdo.cpp:238) NodeId ff found ab audio function group!
|
and so on 254 times!
looking after at dmesg, I found that the loop stops at 509 and then breaks the debugger, maybe these are the clues to find the guilty line!
Attachments
Issue Links
- is blocked by
-
CORE-14688 ACPI/PNP Resource Assignment is broken
- Open
- relates to
-
CORE-14153 "Installing devices..." is interrupted by a bluescreen with HDAudBus.sys and STOP errors
- Resolved