| 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
| ||
|
Message-Id: <201312291224.03854.gheskett@wdtv.com> Date: Sun, 29 Dec 2013 12:24:03 -0500 From: Gene Heskett <gheskett@...v.com> To: linux-kernel@...r.kernel.org Subject: [BUG BISECTED] Resend, incorrect subject line Here is the copy/paste of the final git bisect bad report: First, the reason for the bisect: gene@...ote:~/linux-stable$ dmesg | grep -A2 microcode [ 0.518304] microcode: CPU0: patch_level=0x01000065 [ 0.518396] microcode: CPU1: patch_level=0x01000065 [ 0.518498] microcode: CPU2: patch_level=0x01000065 [ 0.518593] microcode: CPU3: patch_level=0x01000065 [ 0.518745] microcode: Microcode Update Driver: v2.00 <tigran@...azian.fsnet.co.uk>, Peter Oruba The output above should have in each cpu case, a second, or final line showing a patch level 0x0100083 in all cases. This failure is on an AMD phenom 9550 equipt machine. I can and have built from the tarball pull, a 3.8.2 which does work correctly. The tarball build of 3.8.3 fails as above, and a tarball build of 3.12.6 still fails. gene@...ote:~/linux-stable$ git bisect bad 908e88f285b909011dc7dbce5abaacf123f2f68d is the first bad commit commit 908e88f285b909011dc7dbce5abaacf123f2f68d Author: Russell King <rmk+kernel@....linux.org.uk> Date: Mon Feb 25 16:09:12 2013 +0000 I'll next do a "git checkout v3.8.2" to double check that it works. Cheers, Gene -- 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