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: Sun, 22 May 2016 09:52:18 +0000 [thread overview]
Message-ID: <bug-104791-2300-fNX7DEmatq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-104791-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=104791
--- Comment #10 from Peter Wu <peter@lekensteyn.nl> ---
(In reply to James from comment #9)
> This patch does stop the infinite loop on my machine.
Cool, can I add your Tested-by: James <...@googlemail.com> to the patch?
> (Although now with or without it nouveau seems to cause delays starting
> GNOME 3, but that's another bug report.)
If it is a second or so, that is likely the card switching on or off. With or
without this patch you can disable the power saving by setting the module
option nouveau.runpm=0 (kernel cmdline) or "options nouveau runpm=0"
(modprobe.conf snippet). Do you still experience a delay after that?
--
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-22 9:52 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
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 [this message]
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-fNX7DEmatq@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