retitle 723081 more broken kernels need to be blacklisted (interruptible hangs)
severity 723081 important
thanks

On Mon, 16 Sep 2013, Nick Lewycky wrote:
> Setting up amd64-microcode (2.20131007.1+really20130710.1) ...
> Using per-core interface to update microcode on online processors...
> 
> it hangs, for over an hour before I killed it.

...

> Kernel: Linux 3.5.2 (SMP w/32 CPU cores; PREEMPT)

If you're going to use custom kernels on your box, please base them on the
latest kernel in one of the longterm branches: 3.4 or 3.10 (currently:
3.4.62 or 3.10.12).

Anyway, please look here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716917

It lists a workaround to unwedge the package installation, but you really
need a kernel upgrade. 3.5.2 is so broken it is not funny, you should be
using at least 3.5.7, and that would still be quite buggy.

If you really want to be sure it is your kernel that is broken, try this
(run it as root).  BEWARE, it will hang the shell if your kernel is broken:

   find /sys/devices/system/cpu -noleaf -type f -path 
'/sys/devices/system/cpu/cpu*/microcode/reload' | while read i ; do echo -n 1 
>"$i" || true ; done

It should hang in a broken kernel (interrupt it with ^C, you may need to
press it several times as you have 32 cores...).

Meanwhile, it looks like I will have to add more kernels to the blacklist...
the AMD microcode driver is broken on a lot of kernels, proof that nobody
was using it in the first place. Argh!

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to