Summary: | sys-apps/microcode-ctl-1.15: "Bad data in microcode data file" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paul Taylor <birder> |
Component: | [OLD] Core system | Assignee: | Daniel Drake (RETIRED) <dsd> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | casta, help, iyosifov, kernel, zeekec |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://www2.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=bd8e39f9e4c0960541c8c69e1f7cb321574d7c90 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | backport to 2.6.18 |
Description
Paul Taylor
2006-11-09 21:35:04 UTC
I confirm this problem on 3 differents machines. Reverting to 1.14 or using the http://urbanmyth.org/microcode/ucode/intel-ia32microcode-10May2006.txt.bz2 microcode.dat file solved the problem. http://urbanmyth.org/microcode/ucode/intel-ia32microcode-07Sep2006.txt.bz2 included in 1.15 seems to be buggy... I found this kernel patch is supposed to fix the problem: http://linux.bkbits.net:8080/linux-2.6/gnupatch@451a9864jKk9Jk5CliEBE9pB86swnw It works here on a newer kernel 2.6.19-rc4. not a bug in userspace (In reply to comment #4) > not a bug in userspace > Sorry, but if this version need a 2.6.19_rc kernel version, there is a missing dependancy. And ~x86 gentoo-sources does not provide a sufficient version to run ~x86 microcode-ctl (we can think that 2 different ~x86 packages of the tree should be in line). So my position is : you should at least mask it untill ~x86 has an official kernel that have the patch that correct this problem, and probably better add a dependency asking for a minimal kernel version. But this is only my opinion :) Regards, Guillaume Castagnino: there's one major flaw with dependancies on kernels. Namely they exist to require that the kernel sources is of a sufficent version for a task. It says absolutely nothing about the kernel that is actually running. Agreed - a bug in non-userspace is still a bug. feel free to waste the kernel team's time then ... the bug will just stagnant anyways until 2.6.19 hits portage, but whatever If the problem is to be fixed by the simple patch pointed by Paul Taylor* why wait for 2.6.19 ? * http://linux.bkbits.net:8080/linux-2.6/gnupatch%40451a9864jKk9Jk5CliEBE9pB86swnw nothing is stopping you from applying it to your own kernel Mike, this seems like a legitimate kernel bug to me, but I don't have much knowledge in this area. If you apply that patch to 2.6.18, can anyone confirm that both microcode-ctl-1.15 and microcode-ctl-1.16 work fine with 2.6.18? The patch per se does not seem to apply cleanly to 2.6.18. I tried bringing only /arch/i386/kernel/microcode.c up to date with 2.6.19-rc5, the resulting kernel built ok but crashed with a backtrace on boot. I am no kernel programmer so it is very possible that I just messed up the patching. Created attachment 102154 [details, diff]
backport to 2.6.18
please run the above tests with this patch
microcode-ctl-1.14 works always fine with this patch applied, and microcode-ctl-1.15 also works fine. This patch seems to be OK Thanks ! Thanks for the speedy testing Just performed the same test on hardened-sources-2.6.18 patched with this patch : same result, it's all fine with both version. Thanks (In reply to comment #13) > Created an attachment (id=102154) [edit] > backport to 2.6.18 > > please run the above tests with this patch > I've applied the patch, the resulting kernel builds, boots and works fine. Microcode updates ( with both 1.15 and 1.14) appear to work: home ~ # microcode_ctl -u microcode_ctl: writing microcode (length: 265216) microcode_ctl: microcode successfuly written to /dev/cpu/microcode home ~ # However: home ~ # dmesg | grep -i microcode IA-32 Microcode Update Driver: v1.14a <tigran@veritas.com> home ~ # I fail to see any confirmation message in the kernel log. Is this normal ? *** Bug 155659 has been marked as a duplicate of this bug. *** Fixed in gentoo-sources-2.6.18-r3 (genpatches-2.6.18-4) |