linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rudolf Marek <r.marek@assembler.cz>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix
Date: Thu, 21 Jun 2007 22:57:36 +0200	[thread overview]
Message-ID: <467AE640.9090409@assembler.cz> (raw)
In-Reply-To: <1182335403.21563.99.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

Hello Soeren,

Sorry for the delay.

I'm ccing all lists maybe some other people are interested. There is known 
errata AE18 which prevents coretemp from working correctly on some mobile Core 
processors (family 6 model e). My driver refuses to load and now thanks to 
soeren will not crash ;) However what to do when no microcode update (no new 
BIOS) is available?

Soeren pointed at some T60, T60p BIOS update and luckily, there is a easy way 
how to extract the microcode update and even convert it into the .txt format as 
microcode update utility (http://www.urbanmyth.org/microcode/) expects.
Attached scripts generates the mcode.txt file which may be used by the update 
utility. Please can you give a try?

It seems that there is microcode update for CPUID 06E8 version 0x39 just as my 
driver is checking. So if your CPUID is 06e8 too you should get the coretemp 
driver working.

If so I will post a patch and document the script in documentation directory (or 
at least some general instructions how to do that)

Please tell me your stepping:
cat /proc/cpuinfo  | grep stepping

Thanks,

Rudolf



[-- Attachment #2: gen_mcode.txt --]
[-- Type: text/plain, Size: 313 bytes --]

#!/bin/bash

#get the BIOS http://www-307.ibm.com/pc/support/site.wss/MIGR-63024.html
wget ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/79uj20us.exe
cabextract -F "*PAT" 79uj20us.exe
 ls -1 *PAT | while read line; do echo "/* Microcode from $line */" ;  hexdump -e  ' 4/4 "0x%08X, " "\n"'  $line ;done >mcode.txt

  parent reply	other threads:[~2007-06-21 20:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 20:43 git-current: latest coretemp changes break s2ram Soeren Sonnenburg
2007-06-16 21:17 ` [PATCH] hwmon/coretemp: Fix a broken error path Jean Delvare
2007-06-17  9:16   ` Soeren Sonnenburg
2007-06-17 17:56     ` Rudolf Marek
     [not found]       ` <1182335403.21563.99.camel@localhost>
2007-06-21 20:57         ` Rudolf Marek [this message]
2007-06-21 21:55           ` [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix Soeren Sonnenburg
2007-06-25 13:57           ` Soeren Sonnenburg
2007-06-25 18:20             ` Rudolf Marek
2007-06-25 19:35               ` Soeren Sonnenburg
2007-06-18  7:17     ` [PATCH] hwmon/coretemp: Fix a broken error path Jean Delvare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=467AE640.9090409@assembler.cz \
    --to=r.marek@assembler.cz \
    --cc=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).