Date: Mon, 25 Apr 2011 20:46:41 -0400 From: "Alexandre \"Sunny\" Kovalenko" <bsd.gaijin@gmail.com> To: Bartosz Fabianowski <freebsd@chillt.de> Cc: freebsd-stable@freebsd.org Subject: Re: System extremely slow under light load Message-ID: <1303778801.10649.27.camel@RabbitsDen.RabbitsLawn.verizon.net> In-Reply-To: <4DB60759.1070906@chillt.de> References: <BANLkTi=c3zxYeUqvmsHkyoD6MbXafkK-RA@mail.gmail.com> <4DB5751B.2050903@chillt.de> <BANLkTimdmYUiukrR1F-jZCUD2dOwc5Jncg@mail.gmail.com> <4DB60759.1070906@chillt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2011-04-26 at 01:44 +0200, Bartosz Fabianowski wrote: > > Did you try to set OS override to any of the values, recognized by > > your BIOS, with most interesting being "Windows 2001 SP2", "Windows > > 2006" and "Windows 2009". > > Yes, I tried this a while ago, before messing with the DSDT. I figured > it was unlikely that Dell shipped a DSDT which leads to 0°C readings > under Windows. Alas, no OS override seemed to change anything. The CPU > was running just as hot and the temperature reported by ACPI remained > 0°C. Now that I have tried Linux, I can confirm that there, too, the > temperature is 0°C. The DSDT is completely broken. > > > Additionally, could you, by any chance, replace _TMP method in TZ01 > > with the snippet below and let me know what the result is: > > I am running with that change right now. It seems to have the same > effect as my own fixes: hw.acpi.thermal.tz1.temperature works and > returns a temperature that agrees with dev.cpu.X.temperature. No other > obvious changes. All temperatures are still in the same ranges. There are two things of interest here: * Obviously Dell BIOS writer expected different scoping rules than FreeBSD is applying (DS1 and DS2 are defined in the two different scopes). As you have already pointed out it is unlikely that Dell has produced laptop which will not work correctly in Windows, so, likely Windows scoping rules are also different from FreeBSD ones. You might want to start thread on acpi@ and might get some suggestions from Intel folks who tend to hang out there and/or from people who, unlike me, know something about ACPI in general and FreeBSD ACPI implementation in particular. It is quite possible that scoping is causing some other problems as well, some of which, actually might be applicable to the problem in hand. Alternative approach would be to explicitly name all of the methods/fields in all _ACx, _ALx and fan objects and see whether fans will kick in in time and with the desired intensity and keep temperature at bay. * The main difference between your change and mine is that mine (or, rather, the intent of the original writer) uses two sources and the higher value of the two. I am curious whether the behavior WRT critical shutdown will be the same in both cases. > > - Bartosz -- Alexandre Kovalenko (Олександр Коваленко)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1303778801.10649.27.camel>