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
| ||
|
Date: Thu, 27 Sep 2012 22:05:38 +0200 From: Jan Kara <jack@...e.cz> To: Alexander Holler <holler@...oftware.de> Cc: Jan Kara <jack@...e.cz>, Dan Carpenter <dan.carpenter@...cle.com>, linux-kernel@...r.kernel.org Subject: Re: kernel BUG at fs/buffer.c:3205 (stable 3.5.3) On Thu 27-09-12 20:01:00, Alexander Holler wrote: > [ 111.087356] EXT4-fs (sdc1): mounted filesystem with ordered data > mode. Opts: (null) > [ 672.868948] CPU4: Core temperature above threshold, cpu clock > throttled (total events = 1) > [ 672.868949] CPU0: Core temperature above threshold, cpu clock > throttled (total events = 1) > [ 672.869970] CPU0: Core temperature/speed normal > [ 672.869971] CPU4: Core temperature/speed normal > [ 688.285419] CPU6: Core temperature above threshold, cpu clock > throttled (total events = 1) > [ 688.285421] CPU2: Core temperature above threshold, cpu clock > throttled (total events = 1) > [ 688.286442] CPU2: Core temperature/speed normal > [ 688.286443] CPU6: Core temperature/speed normal > [ 698.822614] CPU3: Core temperature above threshold, cpu clock > throttled (total events = 1) > [ 698.822615] CPU7: Core temperature above threshold, cpu clock > throttled (total events = 1) > [ 698.824674] CPU3: Core temperature/speed normal > [ 698.824675] CPU7: Core temperature/speed normal > [ 706.979633] CPU1: Core temperature above threshold, cpu clock > throttled (total events = 1) > [ 706.979635] CPU5: Core temperature above threshold, cpu clock > throttled (total events = 1) > [ 706.980648] CPU1: Core temperature/speed normal > [ 706.980649] CPU5: Core temperature/speed normal > [ 899.540485] [Hardware Error]: Machine check events logged This last message usually means hardware really has an issue. You can use mcelog tool to find out what problems did the hardware report. Honza -- Jan Kara <jack@...e.cz> SUSE Labs, CR -- 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