Asus K73TA ACPI Error

Bug #1019417 reported by Bardok
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Hello,

i've got an Asus K73TA under Xubuntu 12.04, 2-3 times per day he turn off with shell terminal. I have to press the power button to continue the extinction and reboot.

I've got ACPI error in syslog :

K73TA kernel: [ 20.496308] ACPI Error: Needed [Integer/String/Buffer], found [Reference] ffff880143ebe168 (20110623/exresop-422)
K73TA kernel: [ 20.496316] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110623/dswexec-460)
K73TA kernel: [ 20.496321] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.AF03] (Node ffff880148640848), AE_AML_OPERAND_TYPE (20110623/psparse-536)
K73TA kernel: [ 20.496331] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.ATIF] (Node ffff8801486405c8), AE_AML_OPERAND_TYPE (20110623/psparse-536)

Is this related ?

I added attachments of log.

Chris.

Revision history for this message
Bardok (bardok) wrote :
Revision history for this message
Bardok (bardok) wrote :

Jun 29 14:28:23 greg-K73TA kernel: [ 21.205604] ACPI Error: Needed [Integer/String/Buffer], found [Reference] ffff880143ce2120 (20110623/exresop-422)
Jun 29 14:28:23 greg-K73TA kernel: [ 21.205613] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110623/dswexec-460)
Jun 29 14:28:23 greg-K73TA kernel: [ 21.205618] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.AF03] (Node ffff880148640848), AE_AML_OPERAND_TYPE (20110623/psparse-536)
Jun 29 14:28:23 greg-K73TA kernel: [ 21.205627] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.ATIF] (Node ffff8801486405c8), AE_AML_OPERAND_TYPE (20110623/psparse-536)

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1019417/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Bardok (bardok) wrote :
Revision history for this message
Bardok (bardok) wrote :
Revision history for this message
Bardok (bardok) wrote :
Revision history for this message
Bardok (bardok) wrote :
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1019417

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc5-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing precise
Revision history for this message
Bardok (bardok) wrote :

Hello,

i've installed the kernel but no boot on this kernel possible.

Bardok

tags: added: kernel-unable-to-test-upstream
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.