From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104791] ACPI errors on Lenovo C50-30 (AE_AML_INFINITE_LOOP, argument type mismatch)
Date: Sat, 14 May 2016 16:54:49 +0000 [thread overview]
Message-ID: <bug-104791-2300-GxwgWz4u8k@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-104791-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=104791
Peter Wu <peter@lekensteyn.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |peter@lekensteyn.nl
--- Comment #6 from Peter Wu <peter@lekensteyn.nl> ---
The problem is that nouveau_switcheroo_optimus_dsm() unconditionally calls
function 0x1B ("NOUVEAU_DSM_OPTIMUS_FLAGS") without checking that this function
is actually supported. Lenovo's firmware decides to run into an infinite loop
in this case instead of returning an error code.
Proposed patch:
https://lkml.kernel.org/r/1463244575-3515-1-git-send-email-peter@lekensteyn.nl
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-05-14 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-104791-2300@https.bugzilla.kernel.org/>
2015-10-22 6:39 ` [Bug 104791] ACPI errors on Lenovo C50-30 (AE_AML_INFINITE_LOOP, argument type mismatch) bugzilla-daemon
2016-05-14 16:54 ` bugzilla-daemon [this message]
2016-05-20 19:13 ` bugzilla-daemon
2016-05-20 20:14 ` bugzilla-daemon
2016-05-22 7:08 ` bugzilla-daemon
2016-05-22 9:52 ` bugzilla-daemon
2016-05-22 13:02 ` bugzilla-daemon
2020-06-10 23:20 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-104791-2300-GxwgWz4u8k@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox