From: Soeren Sonnenburg <kernel@nn7.de>
To: Rudolf Marek <r.marek@assembler.cz>
Cc: lkml <linux-kernel@vger.kernel.org>,
LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH] hwmon/coretemp: Fix a broken error path -
Date: Thu, 21 Jun 2007 21:55:16 +0000 [thread overview]
Message-ID: <1182462916.5118.3.camel@localhost> (raw)
In-Reply-To: <467AE640.9090409@assembler.cz>
On Thu, 2007-06-21 at 22:57 +0200, Rudolf Marek wrote:
> 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?
great! it works:
sensors excerpt :
coretemp-isa-0000
Adapter: ISA adapter
temp1: +62°C (high = +100°C)
coretemp-isa-0001
Adapter: ISA adapter
temp1: +64°C (high = +100°C)
> 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.
how do I find that out ? I mean sensors seem to work but how do I know
which CPUID+version I have ?
> 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
$ cat /proc/cpuinfo | grep stepping
stepping : 8
stepping : 8
Thank you *very* much!
Soeren
--
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Soeren Sonnenburg <kernel@nn7.de>
To: Rudolf Marek <r.marek@assembler.cz>
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 23:55:16 +0200 [thread overview]
Message-ID: <1182462916.5118.3.camel@localhost> (raw)
In-Reply-To: <467AE640.9090409@assembler.cz>
On Thu, 2007-06-21 at 22:57 +0200, Rudolf Marek wrote:
> 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?
great! it works:
sensors excerpt :
coretemp-isa-0000
Adapter: ISA adapter
temp1: +62°C (high = +100°C)
coretemp-isa-0001
Adapter: ISA adapter
temp1: +64°C (high = +100°C)
> 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.
how do I find that out ? I mean sensors seem to work but how do I know
which CPUID+version I have ?
> 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
$ cat /proc/cpuinfo | grep stepping
stepping : 8
stepping : 8
Thank you *very* much!
Soeren
--
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
next prev parent reply other threads:[~2007-06-21 21:55 UTC|newest]
Thread overview: 15+ 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 ` [lm-sensors] [PATCH] hwmon/coretemp: Fix a broken error path - Rudolf Marek
2007-06-21 20:57 ` [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix Rudolf Marek
2007-06-21 21:55 ` Soeren Sonnenburg [this message]
2007-06-21 21:55 ` Soeren Sonnenburg
2007-06-25 13:57 ` [lm-sensors] [PATCH] hwmon/coretemp: Fix a broken error path - Soeren Sonnenburg
2007-06-25 13:57 ` [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix Soeren Sonnenburg
2007-06-25 18:20 ` [lm-sensors] [PATCH] hwmon/coretemp: Fix a broken error path - Rudolf Marek
2007-06-25 18:20 ` [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix Rudolf Marek
2007-06-25 19:35 ` [lm-sensors] [PATCH] hwmon/coretemp: Fix a broken error path Soeren Sonnenburg
2007-06-25 19:35 ` [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix 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=1182462916.5118.3.camel@localhost \
--to=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=r.marek@assembler.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.