klog: HIGH Kernel message: [ 7.944886] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
for _DSM failure, kernel compliant about the mismatch of _DSM method(Device Specific Method)
From ACPI spec,
This optional object is a control method that enables devices to provide device specific control
functions that are consumed by the device driver.
Arguments: (4)
Arg0 – A Buffer containing a UUID
Arg1 – An Integer containing the Revision ID
Arg2 – An Integer containing the Function Index
Arg3 – A Package that contains function-specific arguments
the #4 Arg (i.e Arg3 is defined as a Package) , but seems the graphic driver bright an Buffer to it.
This has often been seen on the graphic driver, since the _DSM is device specific method.
This shouldnot be a problem if the graphic function is fine.
klog: HIGH Kernel message: [ 7.944886] ACPI Warning: \_SB_.PCI0. PEG_.VID_ ._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/ nsarguments- 95)
for _DSM failure, kernel compliant about the mismatch of _DSM method(Device Specific Method)
From ACPI spec,
This optional object is a control method that enables devices to provide device specific control
functions that are consumed by the device driver.
Arguments: (4)
Arg0 – A Buffer containing a UUID
Arg1 – An Integer containing the Revision ID
Arg2 – An Integer containing the Function Index
Arg3 – A Package that contains function-specific arguments
the #4 Arg (i.e Arg3 is defined as a Package) , but seems the graphic driver bright an Buffer to it.
This has often been seen on the graphic driver, since the _DSM is device specific method.
This shouldnot be a problem if the graphic function is fine.