Contribute
Register

DSDT/ACPI warnings in kernel log (Sierra)

Status
Not open for further replies.
athei

athei

Joined
Nov 13, 2012
Messages
90
Motherboard
Asrock Z390 Phantom Gaming 6
CPU
i9-9900K
Graphics
RX 5700 XT
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
I was inspecting the kernel logs because I was testing the new AppleALC kext with sierra. While this was going fine I found these bad boys in my kernel log:
Code: 
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)

(20140828/nsarguments-a9)

ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)

(20140828/nsarguments-a9)

ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)

(20140828/nsarguments-a9)

ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)

(20140828/nsarguments-a9)

While everything graphic related works there must be some misconfiguration with my DSDT I guess have the Gigabyte Z77-DS3H and a Nvidia GTX 660Ti. I applied the appropriate patch from the Pjalm-Gigabyte Repo and the GFX-Discrete Patch from the Pjalm-Graphics Repo. I attached my patched DSDT. Maybe someone can help because the warning sounds very descriptive.

I deactivated my embedded Intel graphics in the bios.
 

Attachments

  • dsdt.dsl
    380.1 KB · Views: 270
As the warning says your DSDT is using buffer data type where the OSPM acpi driver is expecting package data type in method DSM for device PEGP.GFX0
 
Try without calling not needed DTGP method should get rid of this error:

Method (_DSM, 4, NotSerialized)
{
If (LEqual (Arg2, Zero))
{
Return (Buffer (One)
{
0x03
})
}

Return (Package ()
{
"AAPL,slot-name",
"Slot-1",
"name",
"Display Controller",
"@0,connector-type",
Buffer (0x04)
{
0x00, 0x08, 0x00, 0x00
},

"@1,connector-type",
Buffer (0x04)
{
0x00, 0x08, 0x00, 0x00
},

"@2,connector-type",
Buffer (0x04)
{
0x00, 0x08, 0x00, 0x00
},

"@3,connector-type",
Buffer (0x04)
{
0x00, 0x08, 0x00, 0x00
},

"hda-gfx",
Buffer (0x0A)
{
"onboard-2"
}
}
}
 
I made the changes but get the same message (I guess):
Code: 
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)
(20140828/nsarguments-a9)
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)
(20140828/nsarguments-a9)
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)
(20140828/nsarguments-a9)
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)
(20140828/nsarguments-a9)
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)
(20140828/nsarguments-a9)

I uploaded the modified dsdt.
 

Attachments

  • DSDT.aml
    40.1 KB · Views: 247
athei said:
I made the changes but get the same message (I guess):
Code: 
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)
(20140828/nsarguments-a9)
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)
(20140828/nsarguments-a9)
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)
(20140828/nsarguments-a9)
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)
(20140828/nsarguments-a9)
ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: ACPI Warning: \134_SB_.PCI0.PEGP.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140828/nsarguments-a9)
(20140828/nsarguments-a9)

I uploaded the modified dsdt.
Click to expand...

The problem is likely in an SSDT.
 
Okay when I did the changes suggested here my mouse does not work after boot (is invisible) so I reverted them. As long as everything works I guess it's okay. Just wondering because I could not find any GFX0 or PCI in SSDT.
 
athei said:
Okay when I did the changes suggested here my mouse does not work after boot (is invisible) so I reverted them. As long as everything works I guess it's okay. Just wondering because I could not find any GFX0 or PCI in SSDT.
Click to expand...

You should search all your OEM SSDTs for calls to _DSM, then analyze the code there.
 
Hi can you tell me how to find kernel log in Sierra, I also saw some ACPI warning while in verbose mode, but i cant quiet see it cause it went away too fast. i checked system.log but i didn't see anything related to ACPI nor kernel in there, so can you tell me how did you find it?
 
No problem ACPI error without:

Code: 
into device label SAT0 set_label begin SATA end;
into_all all code_regex SAT0 replaceall_matched begin SATA end;
into device label SAT1 remove_entry;
into_all scope label _SB.PCI0.SAT0.PRT0 set_label begin _SB.PCI0.SATA.PRT0 end;
into_all scope label _SB.PCI0.SAT0.PRT1 set_label begin _SB.PCI0.SATA.PRT1 end;
into_all scope label _SB.PCI0.SAT0.PRT2 set_label begin _SB.PCI0.SATA.PRT2 end;
into_all scope label _SB.PCI0.SAT0.PRT3 set_label begin _SB.PCI0.SATA.PRT3 end;
into method label _DSM parent_label SATA remove_entry;
into device label SATA insert begin
Method (_DSM, 4, NotSerialized)\n
{\n
    Store (Package (0x0A) {\n
        "AAPL,slot-name", "Built In",\n
        "name", "Intel AHCI Controller",\n
        "model", Buffer (0x2D) {"Intel 9 Series Chipset Family SATA Controller"},\n
        "device_type", Buffer (0x0F) {"AHCI Controller"},\n
        "device-id", Buffer (0x04) {0x02,0x1E,0x00,0x00}\n
    }, Local0)\n
    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
    Return (Local0)\n
}
end;
 
iMac 14.2
GA-Z97-HD3 |  i7 4790 |  Graphics Card
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top