lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALyZvKxcdNWMHEGwgdO=sGTTs9sZYerYXcQEyqFwixKzzz3giA@mail.gmail.com>
Date:	Sat, 7 Jul 2012 15:40:58 +0100
From:	Jason Vas Dias <jason.vas.dias@...il.com>
To:	Andreas Herrmann <herrmann.der.user@...glemail.com>
Cc:	Comrade DOS <suloevdmitry@...il.com>, linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: PROBLEM: Performance drop

I can confirm that the AMD Turion X2 2.2Ghz  HP Compaq 6715b
"business" x86_64 k8 dual-core laptops circa 2007
DO get stuck in 800Khz mode  and cannot switch out of it after booting
the "stable" "v3.4.4" tagged kernel.

I followed the containing post and reverted commit
ff74ae50f01ee67764564815c023c362c87ce18b :

Commit d51cdad33bb5bb370c05129f7c7f3a16a55eff40
Author: root <root@...spc.localdomain>
Date:   Fri Jul 6 18:57:03 2012 +0000

    Revert "ACPI: Evaluate thermal trip points before reading temperature"

    This reverts commit 9bcb8118965ab4631a65ee0726e6518f75cda6c5.

commit ff74ae50f01ee67764564815c023c362c87ce18b
Author: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Date:   Fri Jun 22 11:37:50 2012 -0700

And wow !  what a difference - back to a circa 2007 machine versus  a
circa 1987 machine.

Not too many of us  left around trying to run the latest version of
linux on nearly 5-year-old hardware I guess, but still -
please can you restore correct Linux cpufreq & thermal operation on
old-style AMD k8 CPUs ?
They do seem to depend on the temperature being set BEFORE 1st entry .

Thanks & Regards,
Jason Vas Dias (a Software Engineer) <jason.vas.dias@...il.com>


On Wed, May 30, 2012 at 1:43 PM, Andreas Herrmann
<herrmann.der.user@...glemail.com> wrote:
> On Wed, May 30, 2012 at 03:20:27AM +0700, Comrade DOS wrote:
>> > Unfortunately you have used acpi=debug instead of apic=debug.  So I
>> > can't compare I/O APIC configurations between the different test
>> > scenarios.
>>
>> Sorry me for this mistake.
>
> No problem.
>
> The logs show no difference in IO-APIC pin usage.
> So it's not the old problem ...
>
> Comparing both logs I found following differences:
>
> (Most other stuff seems just to be changed formatting.)
>
> -ACPI: Thermal Zone [TZ1] (67 C)
> +ACPI: Thermal Zone [TZ1] (62 C)
>
> I think what's shown is the temperature value which just differed
> between the boots. But that made me look at acpi/thermal.c where the
> messages came from. The only change between 3.3 and 3.4 is this
> commit:
>
>   commit 9bcb8118965ab4631a65ee0726e6518f75cda6c5
>   Author: Matthew Garrett <mjg@...hat.com>
>   Date:   Wed Feb 1 10:26:54 2012 -0500
>
>     ACPI: Evaluate thermal trip points before reading temperature
>
> I'd suggest to do a test with this patch reverted.  Maybe this change
> to fix issues with one HP Laptop (re-)intruduced the trouble with your
> system.
>
> If reverting the patch helps we have to take a closer look at your
> ACPI tables.  So can you please do a
>
>  # git revert 9bcb8118965ab4631a65ee0726e6518f75cda6c5
>
> on top of v3.4 and rebuid your kernel and rerun your test (with
> apic=debug. This allows easier diff to dmesg output of your previous
> test runs).
>
> In any case it also would be good to have the acpi tables from your
> system. So please also use
> # acpidump >acpidump.3.3    (using the 3.3.x kernel)
> # acpidump >acpidump.3.4    (using the unmodified 3.4 version)
>
> and send all files as attachments to your mail.
>
> This will allow me to look at your thermal zone definitions in the
> working and non-working case.
>
>
> Thanks,
>
> Andreas
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ