Bug 1085726 - ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20131115/dswexec-461)
Summary: ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 19
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-09 08:21 UTC by George R. Goffe
Modified: 2015-02-17 20:08 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 20:08:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
output from dmesg command right after a reboot (85.51 KB, text/plain)
2014-04-09 08:21 UTC, George R. Goffe
no flags Details

Description George R. Goffe 2014-04-09 08:21:34 UTC
Created attachment 884432 [details]
output from dmesg command right after a reboot

Description of problem:

Various error messages from ACPI, see dmsg buffer below

Version-Release number of selected component (if applicable):



How reproducible:

Always

Steps to Reproduce:
1.Just reboot.
2.
3.

Actual results:

These messages.

Expected results:

NO messages.

Additional info:

[   68.814623] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[   68.816144] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[  157.904029] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[  157.904268] ACPI Warning: \_SB_.PCI0.PEG0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)

Comment 1 Josh Boyer 2014-04-09 13:53:49 UTC
This is usually indicative of a BIOS problem.  It seems the ACPI entries that nouveau cases to be probed are broken in the tables.

Is anything actually not working properly, or is the only issue that you see these messages?

Comment 2 George R. Goffe 2014-04-09 19:19:05 UTC
Josh,

Thanks for your response.

I'm not certain that something is not working but the error message does seem to point to some software problem "Argument #4 type mismatch".

I have been seeing these messages for some time.

George...

Comment 3 Fedora End Of Life 2015-01-09 21:17:33 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 20:08:54 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.