P.S. I should also mention that the 60 degree throttling doesn't change no
matter what I do. I set every BIOS setting to max performance and turned
off power saving, set all the settings in Windows and Lenovo power manager
to max, etc. and it still happens.
On Sun, May 21, 2017 at 1:36 AM, neil k <host.cr...@gmail.com> wrote:
> I put Windows 10 back on the machine and installed the Lenovo power
> manager and Thinkvantage suite. I converted video and used HWinfo to
> monitor the processor. I couldn't get it to go over 60C / 2GHz in Windows
> either after closing the lid on battery power. I attached some screenshots
> of the stats. It says "thermal throttling" when the lid is closed and
> stays maxed out at 60. In the other screenshot it says "power limit
> exceeded" which I think is what it must be doing on Balanced / Battery save
> to stay at 80C instead of mid 90s for max performance.
>
> I also ran acpi_listen and noticed something else. The very first time I
> trigger HKEY event 0x6032 after powering on the system, 4 lines show up
> that appear to have something to do with the processor (see acpi
> attachment.) If I boot up the laptop with the lid closed, it won't start
> thermal throttling until after I trigger the event for the first time. So
> that makes me think the throttling is 1. caused by the firmware and 2.
> definitely related to this event somehow.
>
> Considering that 60 degrees is nowhere near the critical temperature, and
> the fact that I can bypass the throttling by closing the lid on A/C then
> unplugging, booting up with the lid closed, etc. It seems to me like this
> is either a bug in the firmware or a poorly implemented "feature." Is that
> what it seems like to you too? If there was something dangerous about
> exceeding 60 degrees with the lid closed, I'd expect it to throttle to that
> temperature regardless of whether it's plugged in at the time the lid is
> closed...
>
> Is there anything else I can do on Windows to help investigate what the
> lid helper event means? I have it dual booting now, so I can test things
> in Windows or Linux.
>
> Thanks again for your help so far!
>
> Neil
>
> On Sun, May 14, 2017 at 7:16 PM, Henrique de Moraes Holschuh <
> h...@hmh.eng.br> wrote:
>
>> On Sun, 14 May 2017, neil k wrote:
>> > Thanks for the response Henrique. I do have the laptop setup not to
>> > suspend when I close the lid.
>>
>> Ok.
>>
>> > So 60C / ~2.0GHz sounds right to you if I have it set to "balanced" for
>> > battery power, as opposed to the 80C / ~2.9GHz when I run on battery
>> with
>> > the lid open? I do have a couple options available through the power
>>
>> Well, to know what it should be doing, you really need to run it under
>> Windows *with* the Lenovo drivers ("thinkvantage suite") loaded.
>>
>> But, since it was cooking itself with the lid closed, and now it is not
>> cooking itself anymore, I'd say it is at least *safer* to keep it set to
>> "balanced" for now.
>>
>> > I haven't noticed anything weird with the fan controls. But I can be
>>
>> Ok.
>>
>> > so I'll give that a try and see if anything changes. In any case,
>> > whatever's in control of this appears to be blowing off my settings in
>> the
>> > BIOS, because the clock speeds and temps don't seem to change even if I
>> set
>> > everything to Max Performance.
>>
>> Hmm, check if you have "thermald" running. If you do, try without it
>> (but keep a close look at temperatures the entire time!). If you don't,
>> try installing it.
>>
>> thermald is prone to do very idiotic things on Xeon processors, but for
>> laptops with mobile processors, it is often a good way to work around
>> misbehavior.
>>
>> > If I wanted to change the code of thinkpad-acpi.c to "handle" this
>> event,
>> > should I treat it the same way as the normal lid open/close events in
>> the
>> > hotkey_notify_usrevent section? Is this something that could be put in
>> the
>> > code for later versions?
>>
>> LID events are actually handled by the acpi "lid" driver, which is sane
>> on 4.9, but currently insanely broken on 4.11 (and maybe 4.10) -- the
>> breakage is in the process of being reverted.
>>
>> Lenovo woudln't add a *new* "LID changed" helper event (like the one you
>> reported) if its drivers did not have to handle it *differently* from
>> what is already in there. I think we actually need to know what happens
>> in Windows to correctly handle this one.
>>
>> --
>> Henrique Holschuh
>>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
ibm-acpi-devel mailing list
ibm-acpi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
