Bug 66761

Summary:	ACPI "Firmware Bug" (IGPU, Z01I) causes trouble
Product:	Drivers	Reporter:	David Runge (dave)
Component:	Video(DRI - non Intel)	Assignee:	drivers_video-dri
Status:	NEEDINFO ---
Severity:	high	CC:	77777, szg00000, tianyu.lan
Priority:	P1
Hardware:	x86-64
OS:	Linux
Kernel Version:	3.12.3	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	dmesg output for vanilla Archlinux kernel 3.12.3 dmesg output for Archlinux kernel 3.12.1 -rt patched (+nvidia) dmesg output for Archlinux kernel 3.12.1 -rt patched (+nvidia, !nohz=off) journalctl output for Archlinux kernel 3.8.11-rt8 patched (+nouveau, nohz=off) acpidump for linux-3.12.1-rt4 acpidump for Archlinux linux-3.12.3

Description David Runge 2013-12-07 20:35:54 UTC

Created attachment 117811 [details]
dmesg output for vanilla Archlinux kernel 3.12.3

I'm getting these kernel messages, after boot and they seem to be the root of some trouble with my Dell XPS1340, nvidia/nouveau drivers (respectively the cards in there) and the attempt to do some pro audio work on this machine.


[    0.850175] [Firmware Bug]: ACPI(IGPU) defines _DOD but not _DOS
[    0.940245] [Firmware Bug]: ACPI(Z01I) defines _DOD but not _DOS
...
[    1.053939] ACPI Warning: \_SB_.PCI0.XVR0.Z01I._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20130725/nsarguments-95)
[    1.053968] ACPI Warning: \_SB_.PCI0.XVR0.Z01I._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[    1.053985] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20130725/nsarguments-95)
[    1.054022] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)

The complete dmesg is in attachment.


This is my lspci:
00:00.0 Host bridge: NVIDIA Corporation MCP79 Host Bridge (rev b1)
00:00.1 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.0 ISA bridge: NVIDIA Corporation MCP79 LPC Bridge (rev b2)
00:03.1 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.2 SMBus: NVIDIA Corporation MCP79 SMBus (rev b1)
00:03.3 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.5 Co-processor: NVIDIA Corporation MCP79 Co-processor (rev b1)
00:04.0 USB controller: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:04.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:06.0 USB controller: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:06.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:08.0 Audio device: NVIDIA Corporation MCP79 High Definition Audio (rev b1)
00:09.0 PCI bridge: NVIDIA Corporation MCP79 PCI Bridge (rev b1)
00:0a.0 Ethernet controller: NVIDIA Corporation MCP79 Ethernet (rev b1)
00:0b.0 SATA controller: NVIDIA Corporation MCP79 AHCI Controller (rev b1)
00:0c.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
00:10.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
00:15.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
00:16.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
00:17.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
00:18.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
01:07.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
01:07.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
01:07.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
01:07.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
02:00.0 VGA compatible controller: NVIDIA Corporation G98M [GeForce 9200M GS] (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation C79 [GeForce 9400M G] (rev b1)
06:00.0 Network controller: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01)


That being said: I get harsh lockups when trying to work with pro audio software like JACK & Ardour after a couple of seconds (sometimes minutes) when playing audio (in a very simple setup with pretty high latency, considering it was a realtime patched kernel).

I have been testing several kernel versions with RT patch with nvidia and nouveau and they lockup in a similar way.
http://pastebin.com/m1nahmJG <- like this

Would be most awesome to get some info on those Firmware Bug messages, if, when, where it can be fixed. This system is not usable for audio purposes this way.

I'll test the current mainline 3.13-rc3 in a couple of hours and see how that goes.

Comment 1 David Runge 2013-12-08 10:52:20 UTC

Created attachment 117851 [details]
dmesg output for Archlinux kernel 3.12.1 -rt patched (+nvidia)

The vanilla output from above is with nouveau drivers. Nvidia seems to have even mor of those warning lines though.

[    5.314485] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[    5.314520] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[    5.314579] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[    5.314607] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[    5.314633] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[    5.314659] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[    5.315169] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[    5.315420] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   10.868473] ACPI Warning: \_SB_.PCI0.XVR0.Z01I._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)

Comment 2 David Runge 2013-12-08 11:14:05 UTC

Created attachment 117861 [details]
dmesg output for Archlinux kernel 3.12.1 -rt patched (+nvidia, !nohz=off)

When nohz=off is not set, kernel dies during work with Ardour (for example), but at least lets me grab the dmesg and reboot "gracefully".
With nohz=off the glitches and lockups are much more serious with only the possiblity left to hard kill the laptop.

Comment 3 David Runge 2013-12-08 11:55:10 UTC

Created attachment 117871 [details]
journalctl output for Archlinux kernel 3.8.11-rt8 patched (+nouveau, nohz=off)

This is an older version of the realtime kernel, getting into (most likely) similar trouble.

Comment 4 Lan Tianyu 2013-12-08 13:14:38 UTC

Please provide the output of acpidump.

Comment 5 David Runge 2013-12-08 13:24:22 UTC

Created attachment 117881 [details]
acpidump for linux-3.12.1-rt4

Comment 6 David Runge 2013-12-08 13:29:03 UTC

Created attachment 117891 [details]
acpidump for Archlinux linux-3.12.3

This is the vanilla Achlinux kernel.

Mainline 3.13-rc2/rc3 panic on early boot. Will try to get something out of rc1

Comment 7 Lan Tianyu 2013-12-09 02:42:56 UTC

The warning is caused by gpu driver. Pass different arg type (integer) to _DSM which require package type. So reassign.

Comment 8 David Runge 2013-12-09 10:25:13 UTC

Okay... also these lines?

ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130725/hwxface-571)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130725/hwxface-571)

And all of those saying "[...] can't evaluate _ADR (0x5)", too?

If there is any more info you need from me, please let me know!

Mainline is still not working. Dies the millisecond it tries to use nouveau.

Comment 9 KernelBug 2014-12-17 21:47:59 UTC

Hi,

Not sure if my messages are related, but surfing the internet led me to here, with what appears to be the same types of messages in the logs.

If this seems to have the same relation to this original post, please let me know if you'd like any logs...

My Specs;
Asus G75vw laptop
Slackware 14.1 x86_64
Kernel 3.17.6
Nvidia Geforce GTX660M
nvidia-driver-340.58


$dmesg -t | grep -i 'error\|warn\|exception'  


ACPI Warning: SystemIO range 0x000000000000f000-0x000000000000f01f conflicts with OpRegion 0x000000000000f000-0x000000000000f00f (\SMB0) (20140724/utaddress-258)
ACPI Warning: SystemIO range 0x000000000000f000-0x000000000000f01f conflicts with OpRegion 0x000000000000f000-0x000000000000f00f (\_SB_.PCI0.SBUS.SMBI) (20140724/utaddress-258)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)

Comment 10 KernelBug 2015-01-11 23:28:56 UTC

Don't mean to hijack a bug report, but I'm also getting ACPI Warning messages, and wanted to know, are there kernel modules related to this I can blacklist?

Or anything I can do to fix these?

Also are these releated to smbus?


ACPI Warning: SystemIO range 0x000000000000f000-0x000000000000f01f conflicts with OpRegion 0x000000000000f000-0x000000000000f00f (\SMB0) (20140926/utaddress-258)
ACPI Warning: SystemIO range 0x000000000000f000-0x000000000000f01f conflicts with OpRegion 0x000000000000f000-0x000000000000f00f (\_SB_.PCI0.SBUS.SMBI) (20140926/utaddress-258)



thank you

Comment 11 KernelBug 2015-02-05 04:35:21 UTC

Hi, 

My last post, can someone please tell me if this is something I can blacklist?

thanks

Comment 12 KernelBug 2015-02-10 06:21:23 UTC

I was reently told that OpRegion is something that Linux doesn't use, or something to do with modern harcware not using anymore, bottom line, it's not being used is what I gather...

To be honest I've never seen anyone talk about a solution anywhere for this, until I recently ran across using below, the cmd in your bootloader output, grub/lilo...

acpi_enforce_resources=no

I no longer any SystemIO range conflicts with OpRegion messages! :)

Comment 13 KernelBug 2015-02-10 06:22:36 UTC

Errr typos;

modern harcware/hardware...

I no longer 'see' any SystemIO range conflicts...