From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans de Goede Subject: Re: ACPI errors on Dell Latitude E5430 Date: Mon, 08 Oct 2012 13:22:55 +0200 Message-ID: <5072B78F.6040707@redhat.com> References: <5069E332.9060109@redhat.com> <506AB25D.7000900@hundeboll.net> <506ACCA1.6030908@redhat.com> <506BDCE1.4050007@hundeboll.net> <506C16BF.70100@redhat.com> <506C2629.30902@hundeboll.net> <506C351E.10806@redhat.com> <506C68BB.4030908@hundeboll.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mx1.redhat.com ([209.132.183.28]:46453 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750941Ab2JHLVf (ORCPT ); Mon, 8 Oct 2012 07:21:35 -0400 In-Reply-To: <506C68BB.4030908@hundeboll.net> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: =?UTF-8?B?TWFydGluIEh1bmRlYsO4bGw=?= Cc: linux-acpi , Matthew Garrett Hi, On 10/03/2012 06:32 PM, Martin Hundeb=C3=B8ll wrote: > On 2012-10-03 14:52, Hans de Goede wrote: >> Hi, >> >> On 10/03/2012 01:48 PM, Martin Hundeb=C3=B8ll wrote: >>> On 2012-10-03 12:43, Hans de Goede wrote: >>>> Hi, >>>> >>>> On 10/03/2012 08:36 AM, Martin Hundeb=C3=B8ll wrote: >>>>> On 2012-10-02 13:14, Hans de Goede wrote: >>>>>> Hi, >>>>>> >>>>>> On 10/02/2012 11:22 AM, Martin Hundeb=C3=B8ll 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=3D2000 to the kernel = cmdline, >>>>>>>> the debug traces show that the EC takes it sweet time to respo= nd >>>>>>>> (sometime close to 2 seconds) but it does eventually respond i= n 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 pr= oblems >>>>>>>> too ? >>>>>>> >>>>>>> As far as I can tell from the attached dmesg, the errors are go= ne >>>>>>> after setting acpi.ec_delay=3D2000. Thanks a lot! >>>>>>> >>>>>>> The only remaining issue is the fan control, which works as exp= ected >>>>>>> initially, but then fails to spin down after a few minutes. >>>>>> >>>>>> Hmm, I'm seeing the same thing, but only when charging my batter= y, 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 ca= se >>>>>> (for >>>>>> me). >>>>> >>>>> For the record, my fan keeps spinning also when on battery (as >>>>> reported by i8k/sensors): >>>>> >>>>> i8k-virtual-0 >>>>> Adapter: Virtual device >>>>> Right Fan: 84000 RPM >>>>> CPU: +39.0C >>>>> >>>>> This is not a total show-stopper, but nevertheless quite annoying= when >>>>> the home-office is shared with the bedroom :) >>>> >>>> Ah right, you added acpi_enforce_resources=3Dlax to get i8k to wor= k, >>>> right, hint: >>>> DO NOT DO THAT! >>>> >>>> See: >>>> http://lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkin= ginkernel2.6.31 >>>> >>> >>> Unfortunately, no. I only tried those paramters to see no effect an= d >>> thus removed them again before sending my initial mail. The >>> description in my previous mail was given with only: >>> cat /proc/cmdline >>> BOOT_IMAGE=3D/boot/vmlinuz-linux >>> root=3DUUID=3Def14a89c-443d-4d51-99b8-bff7a90f1015 ro quiet >>> acpi.ec_delay=3D2000 >>> >> >> Hmm, so the i8k driver loads without acpi_enforce_resources=3Dlax, o= k. But >> you do need >> to load it manually right, or does it auto - load ? > > I was in the believe that i8k was of the good, so I loaded it manuall= y, but it did also auto load... > >> Either way could you try without the i8k driver? Blacklisting it if >> necessary ? > > It is now blacklisted/uninstalled and the fan is indeed unhearable! I= will consider the case solved (with the increased timeout), unless som= ething else appears within near future. I'm glad to hear that for you things are solved, but it would be nice t= o make things work out of the box. Can you please send in a bug report about t= he i8k driver causing the fans to spin too fast? Please send it to both the platform-drivers-x86 and the lm-sensors mailing lists: platform-driver-x86@vger.kernel.org and lm-sensors@lm-sensors.org note for the last list you probably need to be subscribed: http://lists.lm-sensors.org/mailman/listinfo/lm-sensors Also please put me in the CC :) On a related note, since I've not heard anything from Dell about this, I'll likely write a patch adding a new dmi based quirk to the ACPI-ec code to make a delay of 2000 the default on both our laptops. Can you do (as root): dmidecode > dmi.log And then send me the generated dmi.log, then I've the necessary info to also enable the quirk for your machine. Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html