Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16164 - [microcode_ctl] doesn't work with kernel 2.6.31

Attached to Project: Arch Linux
Opened by none (foxdie) - Sunday, 13 September 2009, 01:42 GMT
Last edited by Thomas Bächler (brain0) - Wednesday, 21 October 2009, 22:56 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Package "extra/microcode_ctl" doesn't work with kernel 2.6.31 from testing repository. When the daemon starts, it says that "/etc/rc.d/microcode: /dev/cpu/microcode not a character device". I'm using 64 bit version of Archlinux and I cannot test if this affects also to the i686 version.

Additional info:
* package version(s)
* config and/or log files etc.

- testing/kernel26 2.6.31-1
- extra/microcode_ctl 1.17.20090330-2

Steps to reproduce:

Start the daemon of that version of microcode_ctl with kernel 2.6.31 from testing repository.
This task depends upon

Closed by  Thomas Bächler (brain0)
Wednesday, 21 October 2009, 22:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in the new extra/microcode_ctl package
Comment by Thomas Bächler (brain0) - Monday, 21 September 2009, 22:58 GMT
Works for me, what happens if you run "modprobe microcode" and "microcode_ctl -u" manually?
Comment by none (foxdie) - Monday, 21 September 2009, 23:19 GMT
Solved. I had to put microcode in rc.conf. This wasn't necessary for kernel versions < 2.6.31 and, when this was failing (in 2.6.31), if I ran "lsmod", I could see microcode in the output. Any explanation? Should I request closure?
Comment by Thomas Bächler (brain0) - Monday, 21 September 2009, 23:52 GMT
Yet another timing problem. The rc script loads microcode, but it calls microcode_ctl too soon after, apparently.
Comment by none (foxdie) - Tuesday, 22 September 2009, 10:23 GMT
Ok, thanks for the explanation. I'm going to close this.
Comment by Thomas Bächler (brain0) - Tuesday, 22 September 2009, 10:40 GMT
Actually, we should fix that :)

I'm thinking about a solution, let's see what I can come up with.
Comment by Jonathan Liu (net147) - Wednesday, 21 October 2009, 13:34 GMT
Just to clarify in case anyone is having this issue, the fix is to add microcode to the MODULES array in /etc/rc.conf.
Comment by Thomas Bächler (brain0) - Wednesday, 21 October 2009, 13:39 GMT
Can you test another fix? Remove microcode from the MODULES array, and after "modprobe microcode" in /etc/rc.d/microcode, add "/sbin/udevadm settle --exit-if-exists=/dev/microcode". That should also fix it.
Comment by Thomas Bächler (brain0) - Wednesday, 21 October 2009, 13:40 GMT
Oops, it should be /dev/cpu/microcode instead of /dev/microcode.

Loading...