linux-kernel - Re: Machine Check Exception and cpufreq

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] [day] [month] [year] [list]

Message-ID: <AANLkTiktv4+OeJW0yHBAeDtoHf4bvyx_W61AeZNozHzU@mail.gmail.com>
Date:	Wed, 23 Mar 2011 20:48:48 +0100
From:	Giorgio <mywing81@...il.com>
To:	Borislav Petkov <bp@...64.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux@...do.de" <linux@...do.de>,
	"dougthompson@...ssion.com" <dougthompson@...ssion.com>,
	"mchehab@...hat.com" <mchehab@...hat.com>
Subject: Re: Machine Check Exception and cpufreq

2011/3/23 Borislav Petkov <bp@...64.org>:
> On Wed, Mar 23, 2011 at 03:02:01PM -0400, Giorgio wrote:
>> 2011/3/22 Giorgio <mywing81@...il.com>:
>> > 2011/3/22 Borislav Petkov <bp@...64.org>:
>> >> this is very interesting. Question: is it possible to retest with
>> >> a newer kernel from upstream (say 2.6.38) to see whether the issue
>> >> persists? I'd like to rule out the possibility that powernow-k8 is
>> >> not causing any trouble which has been fixed in newer kernels in the
>> >> meantime.
>> >>
>> >> Thanks.
>> >
>> > Hello Borislav,
>> >
>> > thanks for your quick reply. Yes, I only tested it with the stock
>> > 2.6.32 kernel shipped with Ubuntu 10.04, but I will download the
>> > latest stable kernel from kernel.org (2.6.38) and test again. I'll
>> > come back to you in the following days. Regards,
>>
>> Borislav,
>>
>> I tested again with 2.6.38 kernel: the system was stressed for several
>> hours with various activities (compiling, copying data back and forth
>> from two hard drives, encoding/decoding video streams, etc) but I was
>> not able to reproduce the problem, so I guess it has been fixed.
>> If you're interested here's the info I collected with 2.6.38:
>>
>> http://mywing.altervista.org/tmp/info-2.6.38.log
>
> Great. It's either fixed or latest powernow-k8 changes timings so as not
> to trigger it anymore, because your issue looks like the chipset could
> by doing something fishy with CRC during Pstate transitions.
>
> If it happens again, try whether upgrading your BIOS solves it (although
> I'm pretty sceptical about getting newer BIOS for such an old board :-) ).

I am fairly sure I am using the latest BIOS available, and yes, I
admit this is quite an old board! :) Thank you again for looking at my
report.

Giorgio Vazzana
--
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/