Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Linux>
  3. Kernel
Re: [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix
r.marek at assembler
Jun 21, 2007, 1:57 PM
Post #1 of 5 (265 views)
Permalink
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

Attached Files:

Re: [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix [ In reply to ]
kernel at nn7
Jun 21, 2007, 2:55 PM
Post #2 of 5 (252 views)
Permalink
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix [ In reply to ]
kernel at nn7
Jun 25, 2007, 6:57 AM
Post #3 of 5 (239 views)
Permalink
On Thu, 2007-06-21 at 22:57 +0200, Rudolf Marek wrote:
> Hello Soeren,
[...]
> 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?

Hi Rudolf,

just one more update:

When I put my machine into s2ram and make it resume, one of the coretemp
sensors gets lost. Ahh and I am already rmmod coretemp / loading
microcode after resume / insmod coretemp...

Any idea's on that ?

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix [ In reply to ]
r.marek at assembler
Jun 25, 2007, 11:20 AM
Post #4 of 5 (244 views)
Permalink
> Hi Rudolf,
>
> just one more update:
>
> When I put my machine into s2ram and make it resume, one of the coretemp
> sensors gets lost. Ahh and I am already rmmod coretemp / loading
> microcode after resume / insmod coretemp...

Hello, If I understand correctly you unload the driver before suspend. Resume,
update microcode, load the driver correct?

Please can you check dmesg if for example one core complains about bad microcode
version?

Thanks,
Rudolf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] hwmon/coretemp: Fix a broken error path - microcode update fix [ In reply to ]
kernel at nn7
Jun 25, 2007, 12:35 PM
Post #5 of 5 (238 views)
Permalink
On Mon, 2007-06-25 at 20:20 +0200, Rudolf Marek wrote:
> > Hi Rudolf,
> >
> > just one more update:
> >
> > When I put my machine into s2ram and make it resume, one of the coretemp
> > sensors gets lost. Ahh and I am already rmmod coretemp / loading
> > microcode after resume / insmod coretemp...
>
> Hello, If I understand correctly you unload the driver before suspend. Resume,
> update microcode, load the driver correct?

no I did not unload the driver but rmmod it after resume before I load
the microcode.

> Please can you check dmesg if for example one core complains about bad microcode
> version?

indeed core1 still complains. and I just now loaded the new microcode
( rmmod of coretemp before and insmod after) and voila coretemp displays
both cpu's again. So I guess the microcode reloading is done to soon
after resume...

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal