hybrid-graphics-linux team mailing list archive

[johnny <durango8113@xxxxxxxxxxxx>]

Hi All 

I have been inserting debug calls in the dsdt.dsl for _DSM calls 
and related calls and arguments .

This has helped diagnose new calls and modified calls during boot and 
when injecting via acpiexec or custom aml injection.
The debug statement is used a few times in the standard dsdt.

Some of the results are interesting but concerning as i had fixed 
the DSDT to correct an error found with a reserved compiler name which
is a name T_0 within the DSM method .

Some Results below and if you have any suggestions please comment ,# note some of the debug statements are mine for tracking the scope areas.

acpi_call: Calling \_SB.PCI0.GFX0._DSM

localhost kernel: [ACPI Debug]  String [0x1B] "In_SB_GFX0_SCOPE_METHOD_DSM"
localhost kernel: ACPI Error (psargs-0359): [T_0_] Namespace lookup failure, AE_NOT_FOUND

localhost kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.GFX0._DSM] (Node ffff880137a442e0), AE_NOT_FOUND

localhost kernel: acpi_call: ATPX method call failed: AE_NOT_FOUND


localhost kernel: acpi_call: Calling \_SB.PCI0.LPCB.EC0._Q11

localhost kernel: [ACPI Debug]  String [0x19] "In Root ADVG for GFX_PRST"

localhost kernel: [ACPI Debug]  String [0x10] "In_SB_GFX0_ADVD_"

localhost kernel: [ACPI Debug]  String [0x10] "In_SB_GFX0_NATK_"

localhost kernel: [ACPI Debug]  String [0x19] "In Root NATK for GFX_PRST"

localhost kernel: [ACPI Debug]  String [0x2B] "In Root Scope FHKS if Q11 ADVG & T_0 Failed"

Cheers 

JD