Bug#776431: Fwd: Re: Bug#776431: Rebooting with intel-microcode 3.20150107.1~bpo70+1 causing CPU lockups

2015-01-28 Thread Henrique de Moraes Holschuh
Lost the CC to the bug report... forwarding...

- Original message -
From: Henrique de Moraes Holschuh 
To: Ashish SHUKLA 
Subject: Re: Bug#776431: Rebooting with intel-microcode
3.20150107.1~bpo70+1 causing CPU lockups
Date: Wed, 28 Jan 2015 11:50:45 -0200

Ashish,

> [   20.264878] Hardware name: Dell Inc. PowerEdge R430/0DYFC8, BIOS 1.0.2
> 11/17/2014

> vendor_id   : GenuineIntel
> cpu family  : 6
> model   : 63
> model name  : Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
> stepping: 2
> microcode   : 0x2a

CPUID 0x306f2, hardware stepping R2.

However, this microcode should be 0x2d, that's what is included in the
intel-microcode 20150107.

Because it looks like the microcode was not updated, which would point
to a kernel bug and not a intel-microcode bug. I need to know if this
cpuinfo comes with or without the intel-microcode package installed. 
And if it is installed, I need the contents of /var/log/dmesg, please.

That said, Intel just published release 20150121, which is also a
fast-track emergency update... and it DOWNGRADES that microcode to
release 0x29, which is what was in release 20140913 (the previous Debian
release) AND it is earlier than what you system has in the BIOS.

So here's what you have to do:

1. Remove the intel-microcode package from your system, update the
initramfs and reboot (update-initramfs -u).

2. Ensure that the microcode was not updated by Linux (check the kernel
log, or post the contents of /var/log/dmesg after the reboot to this bug
report).

3. If your microcode is still version 0x2a, contact Dell support for a
beta BIOS update with fixed microcode.

> Let us know if you need anything else.

I'd like to know why that microcode was version 0x2a, please.  And also,
if removing intel-microcode (or downgrading it to version 20140913)
fixes your problem...

Thanks for the report!

-- 
  "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 de Moraes Holschuh 


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



Bug#776431: Rebooting with intel-microcode 3.20150107.1~bpo70+1 causing CPU lockups

2015-01-27 Thread Ashish SHUKLA
Package: intel-microcode
Version: 3.20150107.1~bpo70+1

Hi,

After installing this microcode update and rebooting host (Dell PowerEdge
R430), we get:

--8<---cut here---start->8---
[   20.224624] [ cut here ] 

 
[   20.229882] WARNING: CPU: 0 PID: 1 at 
/build/linux-ax4Uh1/linux-3.16.7-ckt2/kernel/watchdog.c:265 
watchdog_overflow_callback+0x9a/0xc0()  

[   20.243701] Watchdog detected hard LOCKUP on cpu 0   

 
[   20.248931] Modules linked in:   

 
[   20.252809] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G  D   
3.16.0-0.bpo.4-amd64 #1 Debian 3.16.7-ckt2-1~bpo70+1

[   20.264878] Hardware name: Dell Inc. PowerEdge R430/0DYFC8, BIOS 1.0.2 
11/17/2014  
   
[   20.273355]   8171bac8 81541f8f 
88047f406c58
  
[   20.282045]  8106cecc 88046eec0c00  
88047f406d48
  
[   20.290924]   88047f406ef8 8106cfba 
8171baa0
  
[   20.299617] Call Trace:  

 
[   20.302440][] ? dump_stack+0x41/0x51
[   20.309307]  [] ? warn_slowpath_common+0x8c/0xc0
[   20.316306]  [] ? warn_slowpath_fmt+0x4a/0x50
[   20.323014]  [] ? watchdog_overflow_callback+0x9a/0xc0
[   20.330596]  [] ? __perf_event_overflow+0x98/0x230
[   20.337789]  [] ? x86_perf_event_set_period+0xd8/0x150
[   20.345371]  [] ? intel_pmu_handle_irq+0x1f8/0x3d0
[   20.352564]  [] ? perf_event_nmi_handler+0x32/0x60
[   20.359757]  [] ? nmi_handle+0x8d/0x140
[   20.365882]  [] ? 
default_send_IPI_mask_allbutself_phys+0xf0/0xf0
[   20.374553]  [] ? default_do_nmi+0xdd/0x130
[   20.381066]  [] ? do_nmi+0x88/0xc0
[   20.386704]  [] ? end_repeat_nmi+0x1e/0x2e
[   20.393121]  [] ? qi_submit_sync+0x197/0x430
[   20.399732]  [] ? qi_submit_sync+0x197/0x430
[   20.406342]  [] ? qi_submit_sync+0x197/0x430
[   20.412952]  <>  [] ? modify_irte+0xa1/0xf0
[   20.420110]  [] ? intel_ioapic_set_affinity+0x144/0x1e0
[   20.427790]  [] ? setup_ioapic_dest+0x70/0x97
[   20.434489]  [] ? native_smp_cpus_done+0xff/0x108
[   20.441586]  [] ? kernel_init_freeable+0xdc/0x1e7
[   20.448681]  [] ? rest_init+0x80/0x80
[   20.454612]  [] ? kernel_init+0xe/0xf0
[   20.460640]  [] ? ret_from_fork+0x7c/0xb0
[   20.466960]  [] ? rest_init+0x80/0x80
[   20.472890] ---[ end trace a5d8cfb932b02cf3 ]---
--8<---cut here---end--->8---

Kernel: linux-image-3.16.0-0.bpo.4-amd64 3.16.7-ckt2-1~bpo70

Output from "/proc/cpuinfo" from the host with "intel-microcode" package
purged:

--8<---cut here---start->8---
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 63
model name  : Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
stepping: 2
microcode   : 0x2a
cpu MHz : 1200.000
cache size  : 15360 KB
physical id : 0
siblings: 12
core id : 0
cpu cores   : 6
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 15
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt 
pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 
avx2 smep bmi2 erms invpcid
bogomips: 4794.61
clflush size: 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

proce