You are not logged in.
Hello all,
I recenttly upgraded from a Dual-Core CPU E5200 to a Skylake i5-6600K. This has created a few problems that I am unable to fix.
As per;
VLC seg faults
vim crashing on exit
Multiple programs crashing wSegmentation fault
It seems to be a problem with microcode
I have installed the microcode and added
INITRD ../intel-ucode.img,../initramfs-linux.img
to my syslinux.cfg
"dmesg | grep microcode" gives;
[ 0.279283] microcode: CPU0 sig=0x506e3, pf=0x2, revision=0x2d
[ 0.279290] microcode: CPU1 sig=0x506e3, pf=0x2, revision=0x2d
[ 0.279301] microcode: CPU2 sig=0x506e3, pf=0x2, revision=0x2d
[ 0.279311] microcode: CPU3 sig=0x506e3, pf=0x2, revision=0x2d
[ 0.279352] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
I have added [testing] to pacman.conf and upgraded my kernel to;
Linux tapa 4.2.1-1-ARCH #1 SMP PREEMPT Tue Sep 22 06:57:07 CEST 2015 x86_64 GNU/Linux
I would prefer not to but would a clean Archlinux install likely fix these issues. As the microcode is for Haswell and Broadwell processor families do I need to wait for an update for Skylake?
TIA,
Billy
[Edited the title and removed "Microcode installed." so I could fit [SOLVED] in]
Last edited by Billy_Sykes (2015-09-24 13:31:08)
Offline
Offline
You think you have looked everywhere, tried everything and the solution will take weeks of discusion.
Thanks, recompiled glibc and all is well.
I am guessing that I will have to recompile everytime there is a new glibc released until Intel puts out a microcode for the Skylake architecture?
Have a nice day
I will now. Thank you very much for your help.
Billy
Offline
I am guessing that I will have to recompile everytime there is a new glibc released until Intel puts out a microcode for the Skylake architecture?
Now you've got me, I don't know what will happen when a new version of glibc comes in the official repository. The worst case scenario is that everything is updated besides your custom glibc package and all programs fail to work because they expect newer glibc version. You may want to consult wiki or ask on "pacman" subforum what to do with this time bomb.
As for the final fix, it may be a microcode update, BIOS update or maybe glibc bugfix.
Have a nice day
I will now.
Hopefully. It seems that you are lucky, quite a few users of recent Intel CPUs also visit this second thread
Offline