linux-kernel - Re: crashme fault

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070916091754.a2ab62a2.randy.dunlap@oracle.com>
Date:	Sun, 16 Sep 2007 09:17:54 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Andrea Arcangeli <andrea@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: crashme fault

On Sun, 16 Sep 2007 17:53:21 +0200 Andrea Arcangeli wrote:

> On Wed, Sep 12, 2007 at 10:21:51PM -0700, Randy Dunlap wrote:
> > I run almost-daily kernel testing.  I haven't seen 'crashme' cause a
> > kernel fault until today, and now I've seen it twice on 2.6.23-rc6-git2,
> 
> Did the room temperature change in the server room? ;) Those early

I rarely go there, but when I do, it's usually very cool.
But I have no way of tracking the room temp there.

> EM64T P4 core based are fast but they suck a whole lot of power. It
> seems a bitflip in a cpu register. You can use cpufreq to set low
> frequency (they should support it, and they shouldn't use more than
> 100w per core that way) to lower the temp, and see if the problem goes
> away. If it's a software issue it will hopefully be still reproducible
> with ~2ghz instead of 3.4ghz.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/