From: Hans de Goede <hdegoede@redhat.com>
To: "Martin Hundebøll" <martin@hundeboll.net>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: ACPI errors on Dell Latitude E5430
Date: Tue, 02 Oct 2012 13:14:41 +0200 [thread overview]
Message-ID: <506ACCA1.6030908@redhat.com> (raw)
In-Reply-To: <506AB25D.7000900@hundeboll.net>
Hi,
On 10/02/2012 11:22 AM, Martin Hundebøll wrote:
> Hi Hans,
>
> On 2012-10-01 20:38, Hans de Goede wrote:
>> 2) Even with a 3.6 which shows the problematic behavior, I can
>> make things work by adding acpi.ec_delay=2000 to the kernel cmdline,
>> the debug traces show that the EC takes it sweet time to respond
>> (sometime close to 2 seconds) but it does eventually respond in all
>> cases I've seen sofar.
>>
>> This also seems to fix a sporadic occurence of:
>> "ACPI: EC: input buffer is not empty aborting transaction"
>> Which I'm seeing with 3.5 / 3.6 in a non debug build.
>>
>> Martin, can you see if adding that helps you with the E5430 problems
>> too ?
>
> As far as I can tell from the attached dmesg, the errors are gone after setting acpi.ec_delay=2000. Thanks a lot!
>
> The only remaining issue is the fan control, which works as expected initially, but then fails to spin down after a few minutes.
Hmm, I'm seeing the same thing, but only when charging my battery, and then indeed
does not spin down completely, but it does step down from vacuum cleaner mode to
something more pleasant after the machine was loaded for a while and returns back
to idle.
Also it spins up to its slowest speed by jut using the charger, so I think it is
just bleeding of heat caused by the charging hardware in this case (for me).
> Is this ACPI related?
That could be the case.
> And if so, please instruct me how to debug further.
I'm afraid I cannot help there, maybe someone else on the list can ...
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-10-02 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 18:38 ACPI errors on Dell Latitude E5430 Hans de Goede
2012-10-02 9:22 ` Martin Hundebøll
2012-10-02 11:14 ` Hans de Goede [this message]
2012-10-03 6:36 ` Martin Hundebøll
2012-10-03 10:43 ` Hans de Goede
2012-10-03 11:48 ` Martin Hundebøll
2012-10-03 12:52 ` Hans de Goede
2012-10-03 16:32 ` Martin Hundebøll
2012-10-08 11:22 ` Hans de Goede
2012-10-03 12:53 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2012-09-21 12:10 Martin Hundebøll
2012-09-21 19:34 ` Matthew Garrett
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=506ACCA1.6030908@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=martin@hundeboll.net \
--cc=mjg59@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).