>>> On 06.07.10 at 22:54, 0bo0 <[email protected]> wrote:
> all sorts of 'new' info in logs when looking closer ... again, seeming
> no ill effects to this.  fwiw, this box's CPU is:
> 
>     AMD Phenom(tm) II X4 920 Processor
> 
> anything to worry about?
> 
> 
> 
> [   10.580576] platform microcode: firmware: requesting
> amd-ucode/microcode_amd.bin

I'm having difficulty figuring out what RPM (if any) this file comes
from - could you please provide this information?

Also, is the native kernel happily using this file?

Jan

> [   10.590598] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [   10.590928] sd 2:0:0:0: Attached scsi generic sg1 type 0
> [   10.591276] scsi 6:0:0:0: Attached scsi generic sg2 type 5
> [   10.602757] IT8712 SuperIO detected.
> [   10.603353] parport_pc 00:07: reported by Plug and Play ACPI
> [   10.603489] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
> [   10.606649] Serial: 8250/16550 driver, 8 ports, IRQ sharing
> disabled
> [   10.623230] floppy0: Unable to grab DMA2 for the floppy driver
> [   10.639898] FDC 0 is a post-1991 82077
> [   10.751544] microcode: Microcode Update Driver: v2.00-xen
> <[email protected]>, Peter Oruba
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info:
> patch_id=0x1000086
> (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch
> file magic
> (XEN) [2010-07-06 20:46:44] PCI add device 00:18.3
> [   10.963847] k10temp 0000:00:18.3: unreliable CPU thermal sensor;
> monitoring disabled
> [   10.988935] input: Power Button as
> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0



--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to