* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
@ 2013-08-13 20:27 ` Guenter Roeck
2013-08-13 21:11 ` Dev, Kapil
` (24 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-13 20:27 UTC (permalink / raw)
To: lm-sensors
On Tue, Aug 13, 2013 at 03:05:58PM -0400, Dev, Kapil wrote:
> Hi,
>
> I just changed the motherboard and the processor while the hard-disk is the
> same. I am trying to read the on-die temperature of the AMD A10 5700
> processor. Based on the output of "sensors-detect" command, I
> installed f71882fg
> driver, but the "sensors" command doesn't seem to give me the value of
> core-temperature. IN particular, I am getting following output from sensors
> command:
>
> ----------------------------------------------------------------------------------------------------
> f71869-isa-0e80
> Adapter: ISA adapter
> in0: +1.68 V
> in1: +1.05 V
> in2: +1.21 V
> in3: +1.22 V
> in4: +1.54 V
> in5: +1.19 V
> in6: +1.19 V
> in7: +1.73 V
> in8: +1.65 V
> fan1: 0 RPM ALARM
> fan2: 0 RPM ALARM
> fan3: 0 RPM ALARM
> temp1: +31.0 C (high = +85.0 C, hyst = +81.0 C)
> (crit = +100.0 C, hyst = +96.0 C) sensor = thermistor
> temp2: +30.0 C (high = +85.0 C, hyst = +81.0 C)
> (crit = +100.0 C, hyst = +96.0 C) sensor = thermistor
> temp3: +48.0 C (high = +70.0 C, hyst = +68.0 C)
> (crit = +85.0 C, hyst = +83.0 C) sensor = thermistor
One of those three is probably from the CPU (wild guess would be temp3).
You might be able to find a correlation by putting the system under load
and observing temperature rises.
> ----------------------------------------------------------------------------------------------------
>
> I am wondering if I have to install lm_sensors package all over again.
> Also, I am wondering if "sensors-detect" is up-to-date to detect all
> devices/drivers. I guess the fans' rpm readings are 0 because I am using a
> custom liquid-based cooling system instead of regular fan.
>
If nothing turns it can't measure rpm ...
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
2013-08-13 20:27 ` Guenter Roeck
@ 2013-08-13 21:11 ` Dev, Kapil
2013-08-13 21:51 ` Guenter Roeck
` (23 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Dev, Kapil @ 2013-08-13 21:11 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 3187 bytes --]
Thanks for the response Guenter!
I put the system on load and I noticed their value hardly changes. To my
surprise, I ran a benchmark for 3 minutes and none of temp* values changed
during execution. The highest reported temperature is always 48C.
I was expecting that the internal temperature would have "sensor = thermal
diode" or "sensor = core" as a keyword. I thought "sensor=thermistor" means
the corresponding sensor is on the motherboard and not the internal
die-sensor.
Also, I noticed something that even though I installed and inserted the
driver for f71882fg, when I run "sensor-detect", it still says that "Note:
there is no driver for Fintek F71869FG SUper IO Sensors yet". I thought the
driver name for F71869FG chip is f71882fg (as per
http://lm-sensors.org/wiki/Devices). I installed this driver from here:
http://khali.linux-fr.org/devel/lm-sensors/drivers/f71882fg/ .
I am not worried about the fan-rpm because I intentionally replaced the fan
with a custom heat sink. I mentioned that just so that you ignore those
lines;-).
Thanks,
Kapil
On Tue, Aug 13, 2013 at 4:27 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> On Tue, Aug 13, 2013 at 03:05:58PM -0400, Dev, Kapil wrote:
> > Hi,
> >
> > I just changed the motherboard and the processor while the hard-disk is
> the
> > same. I am trying to read the on-die temperature of the AMD A10 5700
> > processor. Based on the output of "sensors-detect" command, I
> > installed f71882fg
> > driver, but the "sensors" command doesn't seem to give me the value of
> > core-temperature. IN particular, I am getting following output from
> sensors
> > command:
> >
> >
> ----------------------------------------------------------------------------------------------------
> > f71869-isa-0e80
> > Adapter: ISA adapter
> > in0: +1.68 V
> > in1: +1.05 V
> > in2: +1.21 V
> > in3: +1.22 V
> > in4: +1.54 V
> > in5: +1.19 V
> > in6: +1.19 V
> > in7: +1.73 V
> > in8: +1.65 V
> > fan1: 0 RPM ALARM
> > fan2: 0 RPM ALARM
> > fan3: 0 RPM ALARM
> > temp1: +31.0 C (high = +85.0 C, hyst = +81.0 C)
> > (crit = +100.0 C, hyst = +96.0 C) sensor =
> thermistor
> > temp2: +30.0 C (high = +85.0 C, hyst = +81.0 C)
> > (crit = +100.0 C, hyst = +96.0 C) sensor =
> thermistor
> > temp3: +48.0 C (high = +70.0 C, hyst = +68.0 C)
> > (crit = +85.0 C, hyst = +83.0 C) sensor =
> thermistor
>
> One of those three is probably from the CPU (wild guess would be temp3).
> You might be able to find a correlation by putting the system under load
> and observing temperature rises.
>
> >
> ----------------------------------------------------------------------------------------------------
> >
> > I am wondering if I have to install lm_sensors package all over again.
> > Also, I am wondering if "sensors-detect" is up-to-date to detect all
> > devices/drivers. I guess the fans' rpm readings are 0 because I am using
> a
> > custom liquid-based cooling system instead of regular fan.
> >
> If nothing turns it can't measure rpm ...
>
> Guenter
>
[-- Attachment #1.2: Type: text/html, Size: 4181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
2013-08-13 20:27 ` Guenter Roeck
2013-08-13 21:11 ` Dev, Kapil
@ 2013-08-13 21:51 ` Guenter Roeck
2013-08-14 2:41 ` Dev, Kapil
` (22 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-13 21:51 UTC (permalink / raw)
To: lm-sensors
On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
> Thanks for the response Guenter!
>
> I put the system on load and I noticed their value hardly changes. To my
> surprise, I ran a benchmark for 3 minutes and none of temp* values changed
> during execution. The highest reported temperature is always 48C.
>
> I was expecting that the internal temperature would have "sensor = thermal
> diode" or "sensor = core" as a keyword. I thought "sensor=thermistor" means
> the corresponding sensor is on the motherboard and not the internal
> die-sensor.
>
Sure, but who knows if they put a sensor below the CPU for some reason ...
I am not familiar with the A10 CPUs. Are those similar to K10 ?
If so, maybe the k10temp driver works or could be extended to support it.
Can you give it a try ?
If it does not work out of the box, can you send me the output of "lspci -nn" ?
> Also, I noticed something that even though I installed and inserted the
> driver for f71882fg, when I run "sensor-detect", it still says that "Note:
> there is no driver for Fintek F71869FG SUper IO Sensors yet". I thought the
> driver name for F71869FG chip is f71882fg (as per
The most recent version of sensors-detect should support it.
[ Side note: Please don't top-post. ]
Guenter
> http://lm-sensors.org/wiki/Devices). I installed this driver from here:
> http://khali.linux-fr.org/devel/lm-sensors/drivers/f71882fg/ .
>
> I am not worried about the fan-rpm because I intentionally replaced the fan
> with a custom heat sink. I mentioned that just so that you ignore those
> lines;-).
>
>
> Thanks,
> Kapil
>
> On Tue, Aug 13, 2013 at 4:27 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>
> > On Tue, Aug 13, 2013 at 03:05:58PM -0400, Dev, Kapil wrote:
> > > Hi,
> > >
> > > I just changed the motherboard and the processor while the hard-disk is
> > the
> > > same. I am trying to read the on-die temperature of the AMD A10 5700
> > > processor. Based on the output of "sensors-detect" command, I
> > > installed f71882fg
> > > driver, but the "sensors" command doesn't seem to give me the value of
> > > core-temperature. IN particular, I am getting following output from
> > sensors
> > > command:
> > >
> > >
> > ----------------------------------------------------------------------------------------------------
> > > f71869-isa-0e80
> > > Adapter: ISA adapter
> > > in0: +1.68 V
> > > in1: +1.05 V
> > > in2: +1.21 V
> > > in3: +1.22 V
> > > in4: +1.54 V
> > > in5: +1.19 V
> > > in6: +1.19 V
> > > in7: +1.73 V
> > > in8: +1.65 V
> > > fan1: 0 RPM ALARM
> > > fan2: 0 RPM ALARM
> > > fan3: 0 RPM ALARM
> > > temp1: +31.0 C (high = +85.0 C, hyst = +81.0 C)
> > > (crit = +100.0 C, hyst = +96.0 C) sensor > > thermistor
> > > temp2: +30.0 C (high = +85.0 C, hyst = +81.0 C)
> > > (crit = +100.0 C, hyst = +96.0 C) sensor > > thermistor
> > > temp3: +48.0 C (high = +70.0 C, hyst = +68.0 C)
> > > (crit = +85.0 C, hyst = +83.0 C) sensor > > thermistor
> >
> > One of those three is probably from the CPU (wild guess would be temp3).
> > You might be able to find a correlation by putting the system under load
> > and observing temperature rises.
> >
> > >
> > ----------------------------------------------------------------------------------------------------
> > >
> > > I am wondering if I have to install lm_sensors package all over again.
> > > Also, I am wondering if "sensors-detect" is up-to-date to detect all
> > > devices/drivers. I guess the fans' rpm readings are 0 because I am using
> > a
> > > custom liquid-based cooling system instead of regular fan.
> > >
> > If nothing turns it can't measure rpm ...
> >
> > Guenter
> >
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (2 preceding siblings ...)
2013-08-13 21:51 ` Guenter Roeck
@ 2013-08-14 2:41 ` Dev, Kapil
2013-08-14 3:02 ` Guenter Roeck
` (21 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Dev, Kapil @ 2013-08-14 2:41 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 5128 bytes --]
Thanks again Guenter!
On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
> > Thanks for the response Guenter!
> >
> > I put the system on load and I noticed their value hardly changes. To my
> > surprise, I ran a benchmark for 3 minutes and none of temp* values
> changed
> > during execution. The highest reported temperature is always 48C.
> >
> > I was expecting that the internal temperature would have "sensor =
> thermal
> > diode" or "sensor = core" as a keyword. I thought "sensor=thermistor"
> means
> > the corresponding sensor is on the motherboard and not the internal
> > die-sensor.
> >
> Sure, but who knows if they put a sensor below the CPU for some reason ...
>
> I am not familiar with the A10 CPUs. Are those similar to K10 ?
> If so, maybe the k10temp driver works or could be extended to support it.
> Can you give it a try ?
>
> If it does not work out of the box, can you send me the output of "lspci
> -nn" ?
>
>
Kapil: I believe K10 corresponds to A8 seried, and A10 has Bulldozer
architecture (http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html). I
am not sure how different they are though. I tried K10, but it did not work
out of the box. I am looking into k10temp.c driver now. Also,I am attaching
the output of "lspci -nn" command herewith; you might have to open it using
wordpad for proper formatting..
> Also, I noticed something that even though I installed and inserted the
> > driver for f71882fg, when I run "sensor-detect", it still says that
> "Note:
> > there is no driver for Fintek F71869FG SUper IO Sensors yet". I thought
> the
> > driver name for F71869FG chip is f71882fg (as per
>
> The most recent version of sensors-detect should support it.
>
>
Kapil: When I used another sensors-detect (probably a newer one) script, I
no longer see the above warning. It recommended me the following at the end
of sensors-detect: "copy prog/init/lm_sensors.init to
/etc/init.d/lm_sensors". I couldn't find the prog/init directory, but I
copied /etc/sysconfig/lmsensors file in to /etc/init.d directory. But, I
still have to insert the f71882fg.ko driver every time I restart the
computer. I couldn't run "make install successfully, as suggested here:
http://khali.linux-fr.org/devel/lm-sensors/drivers/INSTALL .
[ Side note: Please don't top-post. ]
>
> Guenter
>
> > http://lm-sensors.org/wiki/Devices). I installed this driver from here:
> > http://khali.linux-fr.org/devel/lm-sensors/drivers/f71882fg/ .
> >
> > I am not worried about the fan-rpm because I intentionally replaced the
> fan
> > with a custom heat sink. I mentioned that just so that you ignore those
> > lines;-).
> >
> >
> > Thanks,
> > Kapil
> >
> > On Tue, Aug 13, 2013 at 4:27 PM, Guenter Roeck <linux@roeck-us.net>
> wrote:
> >
> > > On Tue, Aug 13, 2013 at 03:05:58PM -0400, Dev, Kapil wrote:
> > > > Hi,
> > > >
> > > > I just changed the motherboard and the processor while the hard-disk
> is
> > > the
> > > > same. I am trying to read the on-die temperature of the AMD A10 5700
> > > > processor. Based on the output of "sensors-detect" command, I
> > > > installed f71882fg
> > > > driver, but the "sensors" command doesn't seem to give me the value
> of
> > > > core-temperature. IN particular, I am getting following output from
> > > sensors
> > > > command:
> > > >
> > > >
> > >
> ----------------------------------------------------------------------------------------------------
> > > > f71869-isa-0e80
> > > > Adapter: ISA adapter
> > > > in0: +1.68 V
> > > > in1: +1.05 V
> > > > in2: +1.21 V
> > > > in3: +1.22 V
> > > > in4: +1.54 V
> > > > in5: +1.19 V
> > > > in6: +1.19 V
> > > > in7: +1.73 V
> > > > in8: +1.65 V
> > > > fan1: 0 RPM ALARM
> > > > fan2: 0 RPM ALARM
> > > > fan3: 0 RPM ALARM
> > > > temp1: +31.0 C (high = +85.0 C, hyst = +81.0 C)
> > > > (crit = +100.0 C, hyst = +96.0 C) sensor =
> > > thermistor
> > > > temp2: +30.0 C (high = +85.0 C, hyst = +81.0 C)
> > > > (crit = +100.0 C, hyst = +96.0 C) sensor =
> > > thermistor
> > > > temp3: +48.0 C (high = +70.0 C, hyst = +68.0 C)
> > > > (crit = +85.0 C, hyst = +83.0 C) sensor =
> > > thermistor
> > >
> > > One of those three is probably from the CPU (wild guess would be
> temp3).
> > > You might be able to find a correlation by putting the system under
> load
> > > and observing temperature rises.
> > >
> > > >
> > >
> ----------------------------------------------------------------------------------------------------
> > > >
> > > > I am wondering if I have to install lm_sensors package all over
> again.
> > > > Also, I am wondering if "sensors-detect" is up-to-date to detect all
> > > > devices/drivers. I guess the fans' rpm readings are 0 because I am
> using
> > > a
> > > > custom liquid-based cooling system instead of regular fan.
> > > >
> > > If nothing turns it can't measure rpm ...
> > >
> > > Guenter
> > >
>
[-- Attachment #1.2: Type: text/html, Size: 7180 bytes --]
[-- Attachment #2: lspci_output.txt --]
[-- Type: text/plain, Size: 2182 bytes --]
00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1410]
00:00.2 Generic system peripheral [0806]: Advanced Micro Devices [AMD] Device [1022:1419]
00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:9901]
00:01.1 Audio device [0403]: ATI Technologies Inc Device [1002:9902]
00:10.0 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7812] (rev 03)
00:10.1 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7812] (rev 03)
00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] Device [1022:7800] (rev 40)
00:12.0 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7807] (rev 11)
00:12.2 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7808] (rev 11)
00:13.0 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7807] (rev 11)
00:13.2 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7808] (rev 11)
00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] Device [1022:780b] (rev 14)
00:14.1 IDE interface [0101]: Advanced Micro Devices [AMD] Device [1022:780c]
00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] Device [1022:780d] (rev 01)
00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] Device [1022:780e] (rev 11)
00:14.4 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:780f] (rev 40)
00:14.5 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7809] (rev 11)
00:15.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:43a0]
00:15.1 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:43a1]
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1400]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1401]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1402]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1403]
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1404]
00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1405]
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
[-- Attachment #3: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (3 preceding siblings ...)
2013-08-14 2:41 ` Dev, Kapil
@ 2013-08-14 3:02 ` Guenter Roeck
2013-08-14 3:09 ` Dev, Kapil
` (20 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-14 3:02 UTC (permalink / raw)
To: lm-sensors
On 08/13/2013 07:41 PM, Dev, Kapil wrote:
> Thanks again Guenter!
>
>
>
> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net>> wrote:
>
> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
> > Thanks for the response Guenter!
> >
> > I put the system on load and I noticed their value hardly changes. To my
> > surprise, I ran a benchmark for 3 minutes and none of temp* values changed
> > during execution. The highest reported temperature is always 48C.
> >
> > I was expecting that the internal temperature would have "sensor = thermal
> > diode" or "sensor = core" as a keyword. I thought "sensor=thermistor" means
> > the corresponding sensor is on the motherboard and not the internal
> > die-sensor.
> >
> Sure, but who knows if they put a sensor below the CPU for some reason ...
>
> I am not familiar with the A10 CPUs. Are those similar to K10 ?
> If so, maybe the k10temp driver works or could be extended to support it.
> Can you give it a try ?
>
> If it does not work out of the box, can you send me the output of "lspci -nn" ?
>
>
> Kapil: I believe K10 corresponds to A8 seried, and A10 has Bulldozer architecture (http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html). I am not sure how different they are though. I tried K10, but it did not work out of the box. I am looking into k10temp.c driver now. Also,I am attaching the output of "lspci -nn" command herewith; you might have to open it using wordpad for proper formatting..
>
Your lspci output includes
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1403]
which is supported by the latest k10temp driver. Support was added early last year.
What is your kernel version, and can you switch to a more recent version ?
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (4 preceding siblings ...)
2013-08-14 3:02 ` Guenter Roeck
@ 2013-08-14 3:09 ` Dev, Kapil
2013-08-14 4:56 ` Guenter Roeck
` (19 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Dev, Kapil @ 2013-08-14 3:09 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 2272 bytes --]
On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> On 08/13/2013 07:41 PM, Dev, Kapil wrote:
>
>> Thanks again Guenter!
>>
>>
>>
>>
>> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <linux@roeck-us.net<mailto:
>> linux@roeck-us.net>> wrote:
>>
>> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
>> > Thanks for the response Guenter!
>> >
>> > I put the system on load and I noticed their value hardly changes.
>> To my
>> > surprise, I ran a benchmark for 3 minutes and none of temp*
>> values changed
>> > during execution. The highest reported temperature is always 48C.
>> >
>> > I was expecting that the internal temperature would have "sensor =
>> thermal
>> > diode" or "sensor = core" as a keyword. I thought
>> "sensor=thermistor" means
>> > the corresponding sensor is on the motherboard and not the internal
>> > die-sensor.
>> >
>> Sure, but who knows if they put a sensor below the CPU for some
>> reason ...
>>
>> I am not familiar with the A10 CPUs. Are those similar to K10 ?
>> If so, maybe the k10temp driver works or could be extended to support
>> it.
>> Can you give it a try ?
>>
>> If it does not work out of the box, can you send me the output of
>> "lspci -nn" ?
>>
>>
>> Kapil: I believe K10 corresponds to A8 seried, and A10 has Bulldozer
>> architecture (http://www.cpu-world.com/**CPUs/Bulldozer/TYPE-A10-**
>> Series.html<http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>).
>> I am not sure how different they are though. I tried K10, but it did not
>> work out of the box. I am looking into k10temp.c driver now. Also,I am
>> attaching the output of "lspci -nn" command herewith; you might have to
>> open it using wordpad for proper formatting..
>>
>>
> Your lspci output includes
>
> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1403]
>
> which is supported by the latest k10temp driver. Support was added early
> last year.
> What is your kernel version, and can you switch to a more recent version ?
>
Kapil: I have 2.6.39-020639-generic kernel. Is it too old kernel for
k10temp driver to work? Which stable kernel should I upgrade to?
>
> Thanks,
> Guenter
>
>
>
Thanks,
Kapil
[-- Attachment #1.2: Type: text/html, Size: 3162 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (5 preceding siblings ...)
2013-08-14 3:09 ` Dev, Kapil
@ 2013-08-14 4:56 ` Guenter Roeck
2013-08-14 5:17 ` Kapil Dev
` (18 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-14 4:56 UTC (permalink / raw)
To: lm-sensors
On 08/13/2013 08:09 PM, Dev, Kapil wrote:
>
>
> On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net>> wrote:
>
> On 08/13/2013 07:41 PM, Dev, Kapil wrote:
>
> Thanks again Guenter!
>
>
>
>
> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net> <mailto:linux@roeck-us.net <mailto:linux@roeck-us.net>>> wrote:
>
> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
> > Thanks for the response Guenter!
> >
> > I put the system on load and I noticed their value hardly changes. To my
> > surprise, I ran a benchmark for 3 minutes and none of temp* values changed
> > during execution. The highest reported temperature is always 48C.
> >
> > I was expecting that the internal temperature would have "sensor = thermal
> > diode" or "sensor = core" as a keyword. I thought "sensor=thermistor" means
> > the corresponding sensor is on the motherboard and not the internal
> > die-sensor.
> >
> Sure, but who knows if they put a sensor below the CPU for some reason ...
>
> I am not familiar with the A10 CPUs. Are those similar to K10 ?
> If so, maybe the k10temp driver works or could be extended to support it.
> Can you give it a try ?
>
> If it does not work out of the box, can you send me the output of "lspci -nn" ?
>
>
> Kapil: I believe K10 corresponds to A8 seried, and A10 has Bulldozer architecture (http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html <http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>). I am not sure how different they are though. I tried K10, but it did not work out of the box. I am looking into k10temp.c driver now. Also,I am attaching the output of "lspci -nn" command herewith; you might have to open it using wordpad for proper formatting..
>
>
> Your lspci output includes
>
> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1403]
>
> which is supported by the latest k10temp driver. Support was added early last year.
> What is your kernel version, and can you switch to a more recent version ?
>
>
> Kapil: I have 2.6.39-020639-generic kernel. Is it too old kernel for k10temp driver to work? Which stable kernel should I upgrade to?
>
You need 3.4 or later.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (6 preceding siblings ...)
2013-08-14 4:56 ` Guenter Roeck
@ 2013-08-14 5:17 ` Kapil Dev
2013-08-14 5:30 ` Guenter Roeck
` (17 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Kapil Dev @ 2013-08-14 5:17 UTC (permalink / raw)
To: lm-sensors
On Aug 14, 2013, at 12:56 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> On 08/13/2013 08:09 PM, Dev, Kapil wrote:
>>
>>
>> On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net>> wrote:
>>
>> On 08/13/2013 07:41 PM, Dev, Kapil wrote:
>>
>> Thanks again Guenter!
>>
>>
>>
>>
>> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net> <mailto:linux@roeck-us.net <mailto:linux@roeck-us.net>>> wrote:
>>
>> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
>> > Thanks for the response Guenter!
>> >
>> > I put the system on load and I noticed their value hardly changes. To my
>> > surprise, I ran a benchmark for 3 minutes and none of temp* values changed
>> > during execution. The highest reported temperature is always 48C.
>> >
>> > I was expecting that the internal temperature would have "sensor = thermal
>> > diode" or "sensor = core" as a keyword. I thought "sensor=thermistor" means
>> > the corresponding sensor is on the motherboard and not the internal
>> > die-sensor.
>> >
>> Sure, but who knows if they put a sensor below the CPU for some reason ...
>>
>> I am not familiar with the A10 CPUs. Are those similar to K10 ?
>> If so, maybe the k10temp driver works or could be extended to support it.
>> Can you give it a try ?
>>
>> If it does not work out of the box, can you send me the output of "lspci -nn" ?
>>
>>
>> Kapil: I believe K10 corresponds to A8 seried, and A10 has Bulldozer architecture (http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html <http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>). I am not sure how different they are though. I tried K10, but it did not work out of the box. I am looking into k10temp.c driver now. Also,I am attaching the output of "lspci -nn" command herewith; you might have to open it using wordpad for proper formatting..
>>
>>
>> Your lspci output includes
>>
>> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1403]
>>
>> which is supported by the latest k10temp driver. Support was added early last year.
>> What is your kernel version, and can you switch to a more recent version ?
>>
>>
>> Kapil: I have 2.6.39-020639-generic kernel. Is it too old kernel for k10temp driver to work? Which stable kernel should I upgrade to?
>>
>
> You need 3.4 or later.
Kapil: I was trying to avoid updating the kernel because my current kernel is setup for running different type of benchmarks etc. Seems like I can't avoid updating the kernel; I will do it..
Just for my understanding: Currently, when I run "sensors" command, I am getting three values (apparently wrong), temp1-3. So, what do you think is happening that is causing these values wrong? And, how is it going to be fixed by updating the kernel? Although we don't know yet, but, I am hoping that by updating the kernel and loading the k10temp kernel, I would be able to see readings from thermal-diode (core-temperature) along with the current readings from thermal-resistors.
Thanks,
Kapil
>
> Guenter
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (7 preceding siblings ...)
2013-08-14 5:17 ` Kapil Dev
@ 2013-08-14 5:30 ` Guenter Roeck
2013-08-14 5:32 ` Phil Pokorny
` (16 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-14 5:30 UTC (permalink / raw)
To: lm-sensors
On 08/13/2013 10:17 PM, Kapil Dev wrote:
>
> On Aug 14, 2013, at 12:56 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>
>> On 08/13/2013 08:09 PM, Dev, Kapil wrote:
>>>
>>>
>>> On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net>> wrote:
>>>
>>> On 08/13/2013 07:41 PM, Dev, Kapil wrote:
>>>
>>> Thanks again Guenter!
>>>
>>>
>>>
>>>
>>> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net> <mailto:linux@roeck-us.net <mailto:linux@roeck-us.net>>> wrote:
>>>
>>> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
>>> > Thanks for the response Guenter!
>>> >
>>> > I put the system on load and I noticed their value hardly changes. To my
>>> > surprise, I ran a benchmark for 3 minutes and none of temp* values changed
>>> > during execution. The highest reported temperature is always 48C.
>>> >
>>> > I was expecting that the internal temperature would have "sensor = thermal
>>> > diode" or "sensor = core" as a keyword. I thought "sensor=thermistor" means
>>> > the corresponding sensor is on the motherboard and not the internal
>>> > die-sensor.
>>> >
>>> Sure, but who knows if they put a sensor below the CPU for some reason ...
>>>
>>> I am not familiar with the A10 CPUs. Are those similar to K10 ?
>>> If so, maybe the k10temp driver works or could be extended to support it.
>>> Can you give it a try ?
>>>
>>> If it does not work out of the box, can you send me the output of "lspci -nn" ?
>>>
>>>
>>> Kapil: I believe K10 corresponds to A8 seried, and A10 has Bulldozer architecture (http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html <http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>). I am not sure how different they are though. I tried K10, but it did not work out of the box. I am looking into k10temp.c driver now. Also,I am attaching the output of "lspci -nn" command herewith; you might have to open it using wordpad for proper formatting..
>>>
>>>
>>> Your lspci output includes
>>>
>>> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1403]
>>>
>>> which is supported by the latest k10temp driver. Support was added early last year.
>>> What is your kernel version, and can you switch to a more recent version ?
>>>
>>>
>>> Kapil: I have 2.6.39-020639-generic kernel. Is it too old kernel for k10temp driver to work? Which stable kernel should I upgrade to?
>>>
>>
>> You need 3.4 or later.
>
> Kapil: I was trying to avoid updating the kernel because my current kernel is setup for running different type of benchmarks etc. Seems like I can't avoid updating the kernel; I will do it..
>
Alternative would be to back-port the k10temp driver from a later kernel. Then you can keep running the old one.
> Just for my understanding: Currently, when I run "sensors" command, I am getting three values (apparently wrong), temp1-3. So, what do you think is happening that is causing these values wrong? And, how is it going to be fixed by updating the kernel? Although we don't know yet, but, I am hoping that by updating the kernel and loading the k10temp kernel, I would be able to see readings from thermal-diode (core-temperature) along with the current readings from thermal-resistors.
>
Not wrong; those are probably different chassis and/or board temperatures. Does the BIOS report
any matching temperatures ?
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (8 preceding siblings ...)
2013-08-14 5:30 ` Guenter Roeck
@ 2013-08-14 5:32 ` Phil Pokorny
2013-08-14 17:20 ` Dev, Kapil
` (15 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Phil Pokorny @ 2013-08-14 5:32 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 4080 bytes --]
You may be able to compile the k10temp.c driver out of the kernel. I've
had good success with that in the past.
If you have the kernel build environment, it's pretty straightforward. You
just need a couple of files.
Phil P.
On Tue, Aug 13, 2013 at 10:17 PM, Kapil Dev <kapil_dev@brown.edu> wrote:
>
> On Aug 14, 2013, at 12:56 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>
> > On 08/13/2013 08:09 PM, Dev, Kapil wrote:
> >>
> >>
> >> On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <linux@roeck-us.net<mailto:
> linux@roeck-us.net>> wrote:
> >>
> >> On 08/13/2013 07:41 PM, Dev, Kapil wrote:
> >>
> >> Thanks again Guenter!
> >>
> >>
> >>
> >>
> >> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <
> linux@roeck-us.net <mailto:linux@roeck-us.net> <mailto:linux@roeck-us.net<mailto:
> linux@roeck-us.net>>> wrote:
> >>
> >> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
> >> > Thanks for the response Guenter!
> >> >
> >> > I put the system on load and I noticed their value
> hardly changes. To my
> >> > surprise, I ran a benchmark for 3 minutes and none of
> temp* values changed
> >> > during execution. The highest reported temperature is
> always 48C.
> >> >
> >> > I was expecting that the internal temperature would have
> "sensor = thermal
> >> > diode" or "sensor = core" as a keyword. I thought
> "sensor=thermistor" means
> >> > the corresponding sensor is on the motherboard and not
> the internal
> >> > die-sensor.
> >> >
> >> Sure, but who knows if they put a sensor below the CPU for
> some reason ...
> >>
> >> I am not familiar with the A10 CPUs. Are those similar to
> K10 ?
> >> If so, maybe the k10temp driver works or could be extended
> to support it.
> >> Can you give it a try ?
> >>
> >> If it does not work out of the box, can you send me the
> output of "lspci -nn" ?
> >>
> >>
> >> Kapil: I believe K10 corresponds to A8 seried, and A10 has
> Bulldozer architecture (
> http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html <
> http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>). I am not
> sure how different they are though. I tried K10, but it did not work out of
> the box. I am looking into k10temp.c driver now. Also,I am attaching the
> output of "lspci -nn" command herewith; you might have to open it using
> wordpad for proper formatting..
> >>
> >>
> >> Your lspci output includes
> >>
> >> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device
> [1022:1403]
> >>
> >> which is supported by the latest k10temp driver. Support was added
> early last year.
> >> What is your kernel version, and can you switch to a more recent
> version ?
> >>
> >>
> >> Kapil: I have 2.6.39-020639-generic kernel. Is it too old kernel for
> k10temp driver to work? Which stable kernel should I upgrade to?
> >>
> >
> > You need 3.4 or later.
>
> Kapil: I was trying to avoid updating the kernel because my current kernel
> is setup for running different type of benchmarks etc. Seems like I can't
> avoid updating the kernel; I will do it..
>
> Just for my understanding: Currently, when I run "sensors" command, I am
> getting three values (apparently wrong), temp1-3. So, what do you think is
> happening that is causing these values wrong? And, how is it going to be
> fixed by updating the kernel? Although we don't know yet, but, I am hoping
> that by updating the kernel and loading the k10temp kernel, I would be able
> to see readings from thermal-diode (core-temperature) along with the
> current readings from thermal-resistors.
>
> Thanks,
> Kapil
>
> >
> > Guenter
> >
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
--
Philip Pokorny, RHCE
Chief Technical Officer
PENGUIN COMPUTING, Inc
www.penguincomputing.com
[-- Attachment #1.2: Type: text/html, Size: 5851 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (9 preceding siblings ...)
2013-08-14 5:32 ` Phil Pokorny
@ 2013-08-14 17:20 ` Dev, Kapil
2013-08-14 18:29 ` Guenter Roeck
` (14 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Dev, Kapil @ 2013-08-14 17:20 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 4610 bytes --]
On Wed, Aug 14, 2013 at 1:30 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> On 08/13/2013 10:17 PM, Kapil Dev wrote:
>
>>
>> On Aug 14, 2013, at 12:56 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> On 08/13/2013 08:09 PM, Dev, Kapil wrote:
>>>
>>>>
>>>>
>>>> On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <linux@roeck-us.net<mailto:
>>>> linux@roeck-us.net>> wrote:
>>>>
>>>> On 08/13/2013 07:41 PM, Dev, Kapil wrote:
>>>>
>>>> Thanks again Guenter!
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <
>>>> linux@roeck-us.net <mailto:linux@roeck-us.net> <mailto:
>>>> linux@roeck-us.net <mailto:linux@roeck-us.net>>> wrote:
>>>>
>>>> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
>>>> > Thanks for the response Guenter!
>>>> >
>>>> > I put the system on load and I noticed their value
>>>> hardly changes. To my
>>>> > surprise, I ran a benchmark for 3 minutes and none of
>>>> temp* values changed
>>>> > during execution. The highest reported temperature is
>>>> always 48C.
>>>> >
>>>> > I was expecting that the internal temperature would
>>>> have "sensor = thermal
>>>> > diode" or "sensor = core" as a keyword. I thought
>>>> "sensor=thermistor" means
>>>> > the corresponding sensor is on the motherboard and not
>>>> the internal
>>>> > die-sensor.
>>>> >
>>>> Sure, but who knows if they put a sensor below the CPU for
>>>> some reason ...
>>>>
>>>> I am not familiar with the A10 CPUs. Are those similar to
>>>> K10 ?
>>>> If so, maybe the k10temp driver works or could be extended
>>>> to support it.
>>>> Can you give it a try ?
>>>>
>>>> If it does not work out of the box, can you send me the
>>>> output of "lspci -nn" ?
>>>>
>>>>
>>>> Kapil: I believe K10 corresponds to A8 seried, and A10 has
>>>> Bulldozer architecture (http://www.cpu-world.com/__**
>>>> CPUs/Bulldozer/TYPE-A10-__**Series.html<http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html><
>>>> http://www.cpu-world.com/**CPUs/Bulldozer/TYPE-A10-**Series.html<http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>>).
>>>> I am not sure how different they are though. I tried K10, but it did not
>>>> work out of the box. I am looking into k10temp.c driver now. Also,I am
>>>> attaching the output of "lspci -nn" command herewith; you might have to
>>>> open it using wordpad for proper formatting..
>>>>
>>>>
>>>> Your lspci output includes
>>>>
>>>> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device
>>>> [1022:1403]
>>>>
>>>> which is supported by the latest k10temp driver. Support was added
>>>> early last year.
>>>> What is your kernel version, and can you switch to a more recent
>>>> version ?
>>>>
>>>>
>>>> Kapil: I have 2.6.39-020639-generic kernel. Is it too old kernel for
>>>> k10temp driver to work? Which stable kernel should I upgrade to?
>>>>
>>>>
>>> You need 3.4 or later.
>>>
>>
>> Kapil: I was trying to avoid updating the kernel because my current
>> kernel is setup for running different type of benchmarks etc. Seems like I
>> can't avoid updating the kernel; I will do it..
>>
>> Alternative would be to back-port the k10temp driver from a later
> kernel. Then you can keep running the old one.
>
>
Kapil: Not sure how to do that. I am already taking the k10temp driver from
here: http://khali.linux-fr.org/devel/lm-sensors/drivers/k10temp/ and
compiling and using it.
>
> Just for my understanding: Currently, when I run "sensors" command, I am
>> getting three values (apparently wrong), temp1-3. So, what do you think is
>> happening that is causing these values wrong? And, how is it going to be
>> fixed by updating the kernel? Although we don't know yet, but, I am hoping
>> that by updating the kernel and loading the k10temp kernel, I would be able
>> to see readings from thermal-diode (core-temperature) along with the
>> current readings from thermal-resistors.
>>
>> Not wrong; those are probably different chassis and/or board
> temperatures. Does the BIOS report
> any matching temperatures ?
>
> In BIOS, under PC health, I see only one temperature, named CPU Tctl
(control temperature). Its value is in 30s (between 29-36 or so). I believe
this value denotes the distance from a specific maximum temperature (Tmax).
Finding that Tmax would be another challenge; but, I not at that stage yet.
Thanks,
Kapil
> Guenter
>
>
[-- Attachment #1.2: Type: text/html, Size: 6477 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (10 preceding siblings ...)
2013-08-14 17:20 ` Dev, Kapil
@ 2013-08-14 18:29 ` Guenter Roeck
2013-08-14 18:33 ` Guenter Roeck
` (13 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-14 18:29 UTC (permalink / raw)
To: lm-sensors
On Wed, Aug 14, 2013 at 01:20:57PM -0400, Dev, Kapil wrote:
> On Wed, Aug 14, 2013 at 1:30 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>
> > On 08/13/2013 10:17 PM, Kapil Dev wrote:
> >
> >>
> >> On Aug 14, 2013, at 12:56 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> >>
> >> On 08/13/2013 08:09 PM, Dev, Kapil wrote:
> >>>
> >>>>
> >>>>
> >>>> On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <linux@roeck-us.net<mailto:
> >>>> linux@roeck-us.net>> wrote:
> >>>>
> >>>> On 08/13/2013 07:41 PM, Dev, Kapil wrote:
> >>>>
> >>>> Thanks again Guenter!
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <
> >>>> linux@roeck-us.net <mailto:linux@roeck-us.net> <mailto:
> >>>> linux@roeck-us.net <mailto:linux@roeck-us.net>>> wrote:
> >>>>
> >>>> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
> >>>> > Thanks for the response Guenter!
> >>>> >
> >>>> > I put the system on load and I noticed their value
> >>>> hardly changes. To my
> >>>> > surprise, I ran a benchmark for 3 minutes and none of
> >>>> temp* values changed
> >>>> > during execution. The highest reported temperature is
> >>>> always 48C.
> >>>> >
> >>>> > I was expecting that the internal temperature would
> >>>> have "sensor = thermal
> >>>> > diode" or "sensor = core" as a keyword. I thought
> >>>> "sensor=thermistor" means
> >>>> > the corresponding sensor is on the motherboard and not
> >>>> the internal
> >>>> > die-sensor.
> >>>> >
> >>>> Sure, but who knows if they put a sensor below the CPU for
> >>>> some reason ...
> >>>>
> >>>> I am not familiar with the A10 CPUs. Are those similar to
> >>>> K10 ?
> >>>> If so, maybe the k10temp driver works or could be extended
> >>>> to support it.
> >>>> Can you give it a try ?
> >>>>
> >>>> If it does not work out of the box, can you send me the
> >>>> output of "lspci -nn" ?
> >>>>
> >>>>
> >>>> Kapil: I believe K10 corresponds to A8 seried, and A10 has
> >>>> Bulldozer architecture (http://www.cpu-world.com/__**
> >>>> CPUs/Bulldozer/TYPE-A10-__**Series.html<http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html><
> >>>> http://www.cpu-world.com/**CPUs/Bulldozer/TYPE-A10-**Series.html<http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>>).
> >>>> I am not sure how different they are though. I tried K10, but it did not
> >>>> work out of the box. I am looking into k10temp.c driver now. Also,I am
> >>>> attaching the output of "lspci -nn" command herewith; you might have to
> >>>> open it using wordpad for proper formatting..
> >>>>
> >>>>
> >>>> Your lspci output includes
> >>>>
> >>>> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device
> >>>> [1022:1403]
> >>>>
> >>>> which is supported by the latest k10temp driver. Support was added
> >>>> early last year.
> >>>> What is your kernel version, and can you switch to a more recent
> >>>> version ?
> >>>>
> >>>>
> >>>> Kapil: I have 2.6.39-020639-generic kernel. Is it too old kernel for
> >>>> k10temp driver to work? Which stable kernel should I upgrade to?
> >>>>
> >>>>
> >>> You need 3.4 or later.
> >>>
> >>
> >> Kapil: I was trying to avoid updating the kernel because my current
> >> kernel is setup for running different type of benchmarks etc. Seems like I
> >> can't avoid updating the kernel; I will do it..
> >>
> >> Alternative would be to back-port the k10temp driver from a later
> > kernel. Then you can keep running the old one.
> >
> >
> Kapil: Not sure how to do that. I am already taking the k10temp driver from
> here: http://khali.linux-fr.org/devel/lm-sensors/drivers/k10temp/ and
> compiling and using it.
>
That version should already have support for your chip unless I am missing
something. If you already use it, a newer kernel version will not help.
Do you get any kernel log message when you try to load it ?
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (11 preceding siblings ...)
2013-08-14 18:29 ` Guenter Roeck
@ 2013-08-14 18:33 ` Guenter Roeck
2013-08-14 19:06 ` Dev, Kapil
` (12 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-14 18:33 UTC (permalink / raw)
To: lm-sensors
Adding the k10temp driver maintainer to Cc:
Clemens, any idea what we might be missing ?
Thanks,
Guenter
On Wed, Aug 14, 2013 at 11:29:38AM -0700, Guenter Roeck wrote:
> On Wed, Aug 14, 2013 at 01:20:57PM -0400, Dev, Kapil wrote:
> > On Wed, Aug 14, 2013 at 1:30 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > > On 08/13/2013 10:17 PM, Kapil Dev wrote:
> > >
> > >>
> > >> On Aug 14, 2013, at 12:56 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> > >>
> > >> On 08/13/2013 08:09 PM, Dev, Kapil wrote:
> > >>>
> > >>>>
> > >>>>
> > >>>> On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <linux@roeck-us.net<mailto:
> > >>>> linux@roeck-us.net>> wrote:
> > >>>>
> > >>>> On 08/13/2013 07:41 PM, Dev, Kapil wrote:
> > >>>>
> > >>>> Thanks again Guenter!
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <
> > >>>> linux@roeck-us.net <mailto:linux@roeck-us.net> <mailto:
> > >>>> linux@roeck-us.net <mailto:linux@roeck-us.net>>> wrote:
> > >>>>
> > >>>> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
> > >>>> > Thanks for the response Guenter!
> > >>>> >
> > >>>> > I put the system on load and I noticed their value
> > >>>> hardly changes. To my
> > >>>> > surprise, I ran a benchmark for 3 minutes and none of
> > >>>> temp* values changed
> > >>>> > during execution. The highest reported temperature is
> > >>>> always 48C.
> > >>>> >
> > >>>> > I was expecting that the internal temperature would
> > >>>> have "sensor = thermal
> > >>>> > diode" or "sensor = core" as a keyword. I thought
> > >>>> "sensor=thermistor" means
> > >>>> > the corresponding sensor is on the motherboard and not
> > >>>> the internal
> > >>>> > die-sensor.
> > >>>> >
> > >>>> Sure, but who knows if they put a sensor below the CPU for
> > >>>> some reason ...
> > >>>>
> > >>>> I am not familiar with the A10 CPUs. Are those similar to
> > >>>> K10 ?
> > >>>> If so, maybe the k10temp driver works or could be extended
> > >>>> to support it.
> > >>>> Can you give it a try ?
> > >>>>
> > >>>> If it does not work out of the box, can you send me the
> > >>>> output of "lspci -nn" ?
> > >>>>
> > >>>>
> > >>>> Kapil: I believe K10 corresponds to A8 seried, and A10 has
> > >>>> Bulldozer architecture (http://www.cpu-world.com/__**
> > >>>> CPUs/Bulldozer/TYPE-A10-__**Series.html<http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html><
> > >>>> http://www.cpu-world.com/**CPUs/Bulldozer/TYPE-A10-**Series.html<http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>>).
> > >>>> I am not sure how different they are though. I tried K10, but it did not
> > >>>> work out of the box. I am looking into k10temp.c driver now. Also,I am
> > >>>> attaching the output of "lspci -nn" command herewith; you might have to
> > >>>> open it using wordpad for proper formatting..
> > >>>>
> > >>>>
> > >>>> Your lspci output includes
> > >>>>
> > >>>> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device
> > >>>> [1022:1403]
> > >>>>
> > >>>> which is supported by the latest k10temp driver. Support was added
> > >>>> early last year.
> > >>>> What is your kernel version, and can you switch to a more recent
> > >>>> version ?
> > >>>>
> > >>>>
> > >>>> Kapil: I have 2.6.39-020639-generic kernel. Is it too old kernel for
> > >>>> k10temp driver to work? Which stable kernel should I upgrade to?
> > >>>>
> > >>>>
> > >>> You need 3.4 or later.
> > >>>
> > >>
> > >> Kapil: I was trying to avoid updating the kernel because my current
> > >> kernel is setup for running different type of benchmarks etc. Seems like I
> > >> can't avoid updating the kernel; I will do it..
> > >>
> > >> Alternative would be to back-port the k10temp driver from a later
> > > kernel. Then you can keep running the old one.
> > >
> > >
> > Kapil: Not sure how to do that. I am already taking the k10temp driver from
> > here: http://khali.linux-fr.org/devel/lm-sensors/drivers/k10temp/ and
> > compiling and using it.
> >
> That version should already have support for your chip unless I am missing
> something. If you already use it, a newer kernel version will not help.
>
> Do you get any kernel log message when you try to load it ?
>
> Thanks,
> Guenter
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (12 preceding siblings ...)
2013-08-14 18:33 ` Guenter Roeck
@ 2013-08-14 19:06 ` Dev, Kapil
2013-08-14 20:03 ` Guenter Roeck
` (11 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Dev, Kapil @ 2013-08-14 19:06 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 5744 bytes --]
On Wed, Aug 14, 2013 at 2:29 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> On Wed, Aug 14, 2013 at 01:20:57PM -0400, Dev, Kapil wrote:
> > On Wed, Aug 14, 2013 at 1:30 AM, Guenter Roeck <linux@roeck-us.net>
> wrote:
> >
> > > On 08/13/2013 10:17 PM, Kapil Dev wrote:
> > >
> > >>
> > >> On Aug 14, 2013, at 12:56 AM, Guenter Roeck <linux@roeck-us.net>
> wrote:
> > >>
> > >> On 08/13/2013 08:09 PM, Dev, Kapil wrote:
> > >>>
> > >>>>
> > >>>>
> > >>>> On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <linux@roeck-us.net
> <mailto:
> > >>>> linux@roeck-us.net>> wrote:
> > >>>>
> > >>>> On 08/13/2013 07:41 PM, Dev, Kapil wrote:
> > >>>>
> > >>>> Thanks again Guenter!
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <
> > >>>> linux@roeck-us.net <mailto:linux@roeck-us.net> <mailto:
> > >>>> linux@roeck-us.net <mailto:linux@roeck-us.net>>> wrote:
> > >>>>
> > >>>> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil
> wrote:
> > >>>> > Thanks for the response Guenter!
> > >>>> >
> > >>>> > I put the system on load and I noticed their value
> > >>>> hardly changes. To my
> > >>>> > surprise, I ran a benchmark for 3 minutes and none
> of
> > >>>> temp* values changed
> > >>>> > during execution. The highest reported temperature
> is
> > >>>> always 48C.
> > >>>> >
> > >>>> > I was expecting that the internal temperature would
> > >>>> have "sensor = thermal
> > >>>> > diode" or "sensor = core" as a keyword. I thought
> > >>>> "sensor=thermistor" means
> > >>>> > the corresponding sensor is on the motherboard and
> not
> > >>>> the internal
> > >>>> > die-sensor.
> > >>>> >
> > >>>> Sure, but who knows if they put a sensor below the CPU
> for
> > >>>> some reason ...
> > >>>>
> > >>>> I am not familiar with the A10 CPUs. Are those similar
> to
> > >>>> K10 ?
> > >>>> If so, maybe the k10temp driver works or could be
> extended
> > >>>> to support it.
> > >>>> Can you give it a try ?
> > >>>>
> > >>>> If it does not work out of the box, can you send me the
> > >>>> output of "lspci -nn" ?
> > >>>>
> > >>>>
> > >>>> Kapil: I believe K10 corresponds to A8 seried, and A10 has
> > >>>> Bulldozer architecture (http://www.cpu-world.com/__**
> > >>>> CPUs/Bulldozer/TYPE-A10-__**Series.html<
> http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html><
> > >>>> http://www.cpu-world.com/**CPUs/Bulldozer/TYPE-A10-**Series.html<
> http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>>).
> > >>>> I am not sure how different they are though. I tried K10, but it
> did not
> > >>>> work out of the box. I am looking into k10temp.c driver now. Also,I
> am
> > >>>> attaching the output of "lspci -nn" command herewith; you might
> have to
> > >>>> open it using wordpad for proper formatting..
> > >>>>
> > >>>>
> > >>>> Your lspci output includes
> > >>>>
> > >>>> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device
> > >>>> [1022:1403]
> > >>>>
> > >>>> which is supported by the latest k10temp driver. Support was
> added
> > >>>> early last year.
> > >>>> What is your kernel version, and can you switch to a more recent
> > >>>> version ?
> > >>>>
> > >>>>
> > >>>> Kapil: I have 2.6.39-020639-generic kernel. Is it too old kernel for
> > >>>> k10temp driver to work? Which stable kernel should I upgrade to?
> > >>>>
> > >>>>
> > >>> You need 3.4 or later.
> > >>>
> > >>
> > >> Kapil: I was trying to avoid updating the kernel because my current
> > >> kernel is setup for running different type of benchmarks etc. Seems
> like I
> > >> can't avoid updating the kernel; I will do it..
> > >>
> > >> Alternative would be to back-port the k10temp driver from a later
> > > kernel. Then you can keep running the old one.
> > >
> > >
> > Kapil: Not sure how to do that. I am already taking the k10temp driver
> from
> > here: http://khali.linux-fr.org/devel/lm-sensors/drivers/k10temp/ and
> > compiling and using it.
> >
> That version should already have support for your chip unless I am missing
> something. If you already use it, a newer kernel version will not help.
>
> Do you get any kernel log message when you try to load it ?
>
Kapil: When I insert the module using: sudo insmod k10temp.ko, I don't get
any message on terminal. However, when I compile ktemp10.c file using make,
I get following warnings; I am not sure if they are acceptable.
----------------------------------------------------------------------------
make[1]: Entering directory `/usr/src/linux-headers-2.6.39-020639-generic'
CC [M] /home/amd_a10/k10temp_driver/k10temp.o
/home//amd_a10/k10temp_driver/k10temp.c:232: warning: data definition has
no type or storage class
/home//amd_a10/k10temp_driver/k10temp.c:232: warning: type defaults to
‘int’ in declaration of ‘module_pci_driver’
/home//amd_a10/k10temp_driver/k10temp.c:232: warning: parameter names
(without types) in function declaration
/home//amd_a10/k10temp_driver/k10temp.c:225: warning: ‘k10temp_driver’
defined but not used
Building modules, stage 2.
MODPOST 1 modules
CC /home/amd_a10/k10temp_driver/k10temp.mod.o
LD [M] /home/amd_a10/k10temp_driver/k10temp.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.39-020639-generic'
I am also attaching the output of "dmesg" command herewith for your
reference.
Thanks,
Kapil
>
> Thanks,
> Guenter
>
[-- Attachment #1.2: Type: text/html, Size: 8971 bytes --]
[-- Attachment #2: dmesg_output.TXT --]
[-- Type: text/plain, Size: 49783 bytes --]
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.39-020639-generic (root@zinc) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #201105190911 SMP Thu May 19 09:14:05 UTC 2011
[ 0.000000] Command line: root=UUID=0ce88e3c-aac7-4516-9912-773de2bf44a9 ro quiet splash crashkernel=384M-2G:64M@16M,2G-:128M@16M
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000005bb8c000 (usable)
[ 0.000000] BIOS-e820: 000000005bb8c000 - 000000005be67000 (reserved)
[ 0.000000] BIOS-e820: 000000005be67000 - 000000005c22b000 (usable)
[ 0.000000] BIOS-e820: 000000005c22b000 - 000000005c6d3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000005c6d3000 - 000000005d90f000 (reserved)
[ 0.000000] BIOS-e820: 000000005d90f000 - 000000005d910000 (usable)
[ 0.000000] BIOS-e820: 000000005d910000 - 000000005db16000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000005db16000 - 000000005dc6e000 (usable)
[ 0.000000] BIOS-e820: 000000005dc6e000 - 000000005e432000 (reserved)
[ 0.000000] BIOS-e820: 000000005e432000 - 000000005e470000 (usable)
[ 0.000000] BIOS-e820: 000000005e470000 - 000000005e7f1000 (reserved)
[ 0.000000] BIOS-e820: 000000005e7f1000 - 000000005e800000 (usable)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec10000 - 00000000fec11000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed00000 - 00000000fed01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed80000 - 00000000fed90000 (reserved)
[ 0.000000] BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI 2.7 present.
[ 0.000000] DMI: ECS A75F2-A2/A75F2-A2, BIOS 4.6.5 05/08/2013
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0x5e800 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF write-through
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-E7FFF uncachable
[ 0.000000] E8000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000000 mask FFFF80000000 write-back
[ 0.000000] 1 base 00005E800000 mask FFFFFF800000 uncachable
[ 0.000000] 2 base 00005F000000 mask FFFFFF000000 uncachable
[ 0.000000] 3 base 000060000000 mask FFFFE0000000 uncachable
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] found SMP MP-table at [ffff8800000fd910] fd910
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] Base memory trampoline at [ffff88000009a000] 9a000 size 20480
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] init_memory_mapping: 0000000000000000-000000005e800000
[ 0.000000] 0000000000 - 0040000000 page 1G
[ 0.000000] 0040000000 - 005e800000 page 2M
[ 0.000000] kernel direct mapping tables up to 5e800000 @ 5e7fe000-5e800000
[ 0.000000] RAMDISK: 3762d000 - 37ff0000
[ 0.000000] crashkernel reservation failed - memory is in use.
[ 0.000000] ACPI: RSDP 00000000000f0490 00024 (v02 ALASKA)
[ 0.000000] ACPI: XSDT 000000005c2bb078 0006C (v01 ALASKA A M I 01072009 AMI 00010013)
[ 0.000000] ACPI: FACP 000000005c2c4448 0010C (v05 ALASKA A M I 01072009 AMI 00010013)
[ 0.000000] ACPI Warning: FADT (revision 5) is longer than ACPI 2.0 version, truncating length 268 to 244 (20110316/tbfadt-288)
[ 0.000000] ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20110316/tbfadt-560)
[ 0.000000] ACPI: DSDT 000000005c2bb178 092CD (v02 ALASKA A M I 00000000 INTL 20051117)
[ 0.000000] ACPI: FACS 000000005c6c8080 00040
[ 0.000000] ACPI: APIC 000000005c2c4558 00072 (v03 ALASKA A M I 01072009 AMI 00010013)
[ 0.000000] ACPI: FPDT 000000005c2c45d0 00044 (v01 ALASKA A M I 01072009 AMI 00010013)
[ 0.000000] ACPI: MCFG 000000005c2c4618 0003C (v01 ALASKA A M I 01072009 MSFT 00010013)
[ 0.000000] ACPI: HPET 000000005c2c4658 00038 (v01 ALASKA A M I 01072009 AMI 00000005)
[ 0.000000] ACPI: IVRS 000000005c2c4690 00070 (v02 AMD ANNAPURN 00000001 AMD 00000000)
[ 0.000000] ACPI: SSDT 000000005c2c4700 006B2 (v01 AMD ANNAPURN 00000001 AMD 00000001)
[ 0.000000] ACPI: SSDT 000000005c2c4db8 004B7 (v02 AMD ANNAPURN 00000001 MSFT 04000000)
[ 0.000000] ACPI: CRAT 000000005c2c5270 001A8 (v01 AMD ANNAPURN 00000001 AMD 00000001)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at 0000000000000000-000000005e800000
[ 0.000000] NUMA: Using 63 for the hash shift.
[ 0.000000] Initmem setup node 0 0000000000000000-000000005e800000
[ 0.000000] NODE_DATA [000000005e7f9000 - 000000005e7fdfff]
[ 0.000000] [ffffea0000000000-ffffea00015fffff] PMD -> [ffff880059a00000-ffff88005affffff] on node 0
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal empty
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[7] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x0005bb8c
[ 0.000000] 0: 0x0005be67 -> 0x0005c22b
[ 0.000000] 0: 0x0005d90f -> 0x0005d910
[ 0.000000] 0: 0x0005db16 -> 0x0005dc6e
[ 0.000000] 0: 0x0005e432 -> 0x0005e470
[ 0.000000] 0: 0x0005e7f1 -> 0x0005e800
[ 0.000000] On node 0 totalpages: 376965
[ 0.000000] DMA zone: 56 pages used for memmap
[ 0.000000] DMA zone: 5 pages reserved
[ 0.000000] DMA zone: 3922 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 5236 pages used for memmap
[ 0.000000] DMA32 zone: 367746 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x11] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x14] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x15] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x03] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 3, version 33, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x10228210 base: 0xfed00000
[ 0.000000] SMP: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
[ 0.000000] PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
[ 0.000000] PM: Registered nosave memory: 000000005bb8c000 - 000000005be67000
[ 0.000000] PM: Registered nosave memory: 000000005c22b000 - 000000005c6d3000
[ 0.000000] PM: Registered nosave memory: 000000005c6d3000 - 000000005d90f000
[ 0.000000] PM: Registered nosave memory: 000000005d910000 - 000000005db16000
[ 0.000000] PM: Registered nosave memory: 000000005dc6e000 - 000000005e432000
[ 0.000000] PM: Registered nosave memory: 000000005e470000 - 000000005e7f1000
[ 0.000000] Allocating PCI resources starting at 5e800000 (gap: 5e800000:a0400000)
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88005c000000 s85056 r8192 d21440 u524288
[ 0.000000] pcpu-alloc: s85056 r8192 d21440 u524288 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 371668
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line: root=UUID=0ce88e3c-aac7-4516-9912-773de2bf44a9 ro quiet splash crashkernel=384M-2G:64M@16M,2G-:128M@16M
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] xsave/xrstor: enabled xstate_bv 0x7, cntxt size 0x340
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 1461300k/1548288k available (6019k kernel code, 40428k absent, 46560k reserved, 4946k data, 1068k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] RCU-based detection of stalled CPUs is disabled.
[ 0.000000] NR_IRQS:16640 nr_irqs:712 16
[ 0.000000] Extended CMOS year: 2000
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] allocated 12582912 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] hpet clockevent registered
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 3400.287 MHz processor.
[ 0.000003] Calibrating delay loop (skipped), value calculated using timer frequency.. 6800.57 BogoMIPS (lpj=34002870)
[ 0.000006] pid_max: default: 32768 minimum: 301
[ 0.000026] Security Framework initialized
[ 0.000039] AppArmor: AppArmor initialized
[ 0.000236] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.000841] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.001100] Mount-cache hash table entries: 256
[ 0.001204] Initializing cgroup subsys ns
[ 0.001207] ns_cgroup deprecated: consider using the 'clone_children' flag without the ns_cgroup.
[ 0.001209] Initializing cgroup subsys cpuacct
[ 0.001212] Initializing cgroup subsys memory
[ 0.001219] Initializing cgroup subsys devices
[ 0.001221] Initializing cgroup subsys freezer
[ 0.001222] Initializing cgroup subsys net_cls
[ 0.001224] Initializing cgroup subsys blkio
[ 0.001230] Initializing cgroup subsys perf_event
[ 0.001253] tseg: 005e800000
[ 0.001254] CPU: Physical Processor ID: 0
[ 0.001255] CPU: Processor Core ID: 0
[ 0.001257] mce: CPU supports 7 MCE banks
[ 0.011574] ACPI: Core revision 20110316
[ 0.020016] ftrace: allocating 28675 entries in 113 pages
[ 0.030062] Setting APIC routing to flat
[ 0.030330] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.134579] CPU0: AMD A10-5700 APU with Radeon(tm) HD Graphics stepping 01
[ 0.140000] Performance Events: AMD Family 15h PMU driver.
[ 0.140000] ... version: 0
[ 0.140000] ... bit width: 48
[ 0.140000] ... generic registers: 6
[ 0.140000] ... value mask: 0000ffffffffffff
[ 0.140000] ... max period: 00007fffffffffff
[ 0.140000] ... fixed-purpose events: 0
[ 0.140000] ... event mask: 000000000000003f
[ 0.140000] Booting Node 0, Processors #1
[ 0.140000] smpboot cpu 1: start_ip = 9a000
[ 0.300013] Brought up 2 CPUs
[ 0.300017] Total of 2 processors activated (13600.99 BogoMIPS).
[ 0.300365] devtmpfs: initialized
[ 0.300365] PM: Registering ACPI NVS region at 5c22b000 (4882432 bytes)
[ 0.300365] PM: Registering ACPI NVS region at 5d910000 (2121728 bytes)
[ 0.300862] print_constraints: dummy:
[ 0.300881] Time: 10:16:09 Date: 08/14/13
[ 0.300909] NET: Registered protocol family 16
[ 0.301056] Extended Config Space enabled on 0 nodes
[ 0.301075] ACPI: bus type pci registered
[ 0.301120] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 0.301123] PCI: not using MMCONFIG
[ 0.301125] PCI: Using configuration type 1 for base access
[ 0.301126] PCI: Using configuration type 1 for extended access
[ 0.301693] bio: create slab <bio-0> at 0
[ 0.301693] ACPI: EC: Look up EC in DSDT
[ 0.302602] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.306328] ACPI: Interpreter enabled
[ 0.306331] ACPI: (supports S0 S3 S4 S5)
[ 0.306362] ACPI: Using IOAPIC for interrupt routing
[ 0.306382] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 0.306419] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[ 0.550162] ACPI: No dock devices found.
[ 0.550166] HEST: Table not found.
[ 0.550169] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.550494] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.550786] pci_root PNP0A03:00: host bridge window [io 0x0000-0x03af]
[ 0.550788] pci_root PNP0A03:00: host bridge window [io 0x03e0-0x0cf7]
[ 0.550790] pci_root PNP0A03:00: host bridge window [io 0x03b0-0x03df]
[ 0.550792] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff]
[ 0.550795] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff]
[ 0.550797] pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff]
[ 0.550799] pci_root PNP0A03:00: host bridge window [mem 0x7f000000-0xffffffff]
[ 0.550810] pci 0000:00:00.0: [1022:1410] type 0 class 0x000600
[ 0.550840] pci 0000:00:00.2: [1022:1419] type 0 class 0x000806
[ 0.550889] pci 0000:00:01.0: [1002:9901] type 0 class 0x000300
[ 0.550897] pci 0000:00:01.0: reg 10: [mem 0xc0000000-0xcfffffff pref]
[ 0.550902] pci 0000:00:01.0: reg 14: [io 0xf000-0xf0ff]
[ 0.550907] pci 0000:00:01.0: reg 18: [mem 0xfef00000-0xfef3ffff]
[ 0.550932] pci 0000:00:01.0: supports D1 D2
[ 0.550944] pci 0000:00:01.1: [1002:9902] type 0 class 0x000403
[ 0.550951] pci 0000:00:01.1: reg 10: [mem 0xfef44000-0xfef47fff]
[ 0.550982] pci 0000:00:01.1: supports D1 D2
[ 0.551023] pci 0000:00:10.0: [1022:7812] type 0 class 0x000c03
[ 0.551041] pci 0000:00:10.0: reg 10: [mem 0xfef4a000-0xfef4bfff 64bit]
[ 0.551112] pci 0000:00:10.0: PME# supported from D0 D3hot D3cold
[ 0.551116] pci 0000:00:10.0: PME# disabled
[ 0.551150] pci 0000:00:10.1: [1022:7812] type 0 class 0x000c03
[ 0.551167] pci 0000:00:10.1: reg 10: [mem 0xfef48000-0xfef49fff 64bit]
[ 0.551239] pci 0000:00:10.1: PME# supported from D0 D3hot D3cold
[ 0.551242] pci 0000:00:10.1: PME# disabled
[ 0.551273] pci 0000:00:11.0: [1022:7800] type 0 class 0x000101
[ 0.551287] pci 0000:00:11.0: reg 10: [io 0xf190-0xf197]
[ 0.551295] pci 0000:00:11.0: reg 14: [io 0xf180-0xf183]
[ 0.551303] pci 0000:00:11.0: reg 18: [io 0xf170-0xf177]
[ 0.551311] pci 0000:00:11.0: reg 1c: [io 0xf160-0xf163]
[ 0.551319] pci 0000:00:11.0: reg 20: [io 0xf150-0xf15f]
[ 0.551327] pci 0000:00:11.0: reg 24: [mem 0xfef51000-0xfef517ff]
[ 0.551344] pci 0000:00:11.0: set SATA to AHCI mode
[ 0.551367] pci 0000:00:12.0: [1022:7807] type 0 class 0x000c03
[ 0.551378] pci 0000:00:12.0: reg 10: [mem 0xfef50000-0xfef50fff]
[ 0.551435] pci 0000:00:12.2: [1022:7808] type 0 class 0x000c03
[ 0.551451] pci 0000:00:12.2: reg 10: [mem 0xfef4f000-0xfef4f0ff]
[ 0.551508] pci 0000:00:12.2: supports D1 D2
[ 0.551510] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
[ 0.551513] pci 0000:00:12.2: PME# disabled
[ 0.551533] pci 0000:00:13.0: [1022:7807] type 0 class 0x000c03
[ 0.551544] pci 0000:00:13.0: reg 10: [mem 0xfef4e000-0xfef4efff]
[ 0.551601] pci 0000:00:13.2: [1022:7808] type 0 class 0x000c03
[ 0.551617] pci 0000:00:13.2: reg 10: [mem 0xfef4d000-0xfef4d0ff]
[ 0.551674] pci 0000:00:13.2: supports D1 D2
[ 0.551675] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
[ 0.551679] pci 0000:00:13.2: PME# disabled
[ 0.551696] pci 0000:00:14.0: [1022:780b] type 0 class 0x000c05
[ 0.551753] pci 0000:00:14.1: [1022:780c] type 0 class 0x000101
[ 0.551765] pci 0000:00:14.1: reg 10: [io 0xf140-0xf147]
[ 0.551773] pci 0000:00:14.1: reg 14: [io 0xf130-0xf133]
[ 0.551781] pci 0000:00:14.1: reg 18: [io 0xf120-0xf127]
[ 0.551789] pci 0000:00:14.1: reg 1c: [io 0xf110-0xf113]
[ 0.551797] pci 0000:00:14.1: reg 20: [io 0xf100-0xf10f]
[ 0.551826] pci 0000:00:14.2: [1022:780d] type 0 class 0x000403
[ 0.551844] pci 0000:00:14.2: reg 10: [mem 0xfef40000-0xfef43fff 64bit]
[ 0.551891] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
[ 0.551895] pci 0000:00:14.2: PME# disabled
[ 0.551905] pci 0000:00:14.3: [1022:780e] type 0 class 0x000601
[ 0.551966] pci 0000:00:14.4: [1022:780f] type 1 class 0x000604
[ 0.551999] pci 0000:00:14.5: [1022:7809] type 0 class 0x000c03
[ 0.552010] pci 0000:00:14.5: reg 10: [mem 0xfef4c000-0xfef4cfff]
[ 0.552068] pci 0000:00:15.0: [1022:43a0] type 1 class 0x000604
[ 0.552113] pci 0000:00:15.0: supports D1 D2
[ 0.552134] pci 0000:00:15.1: [1022:43a1] type 1 class 0x000604
[ 0.552179] pci 0000:00:15.1: supports D1 D2
[ 0.552203] pci 0000:00:18.0: [1022:1400] type 0 class 0x000600
[ 0.552218] pci 0000:00:18.1: [1022:1401] type 0 class 0x000600
[ 0.552233] pci 0000:00:18.2: [1022:1402] type 0 class 0x000600
[ 0.552248] pci 0000:00:18.3: [1022:1403] type 0 class 0x000600
[ 0.552265] pci 0000:00:18.4: [1022:1404] type 0 class 0x000600
[ 0.552279] pci 0000:00:18.5: [1022:1405] type 0 class 0x000600
[ 0.552350] pci 0000:00:14.4: PCI bridge to [bus 01-01] (subtractive decode)
[ 0.552355] pci 0000:00:14.4: bridge window [io 0xf000-0x0000] (disabled)
[ 0.552359] pci 0000:00:14.4: bridge window [mem 0xfff00000-0x000fffff] (disabled)
[ 0.552363] pci 0000:00:14.4: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 0.552365] pci 0000:00:14.4: bridge window [io 0x0000-0x03af] (subtractive decode)
[ 0.552367] pci 0000:00:14.4: bridge window [io 0x03e0-0x0cf7] (subtractive decode)
[ 0.552370] pci 0000:00:14.4: bridge window [io 0x03b0-0x03df] (subtractive decode)
[ 0.552372] pci 0000:00:14.4: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 0.552374] pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 0.552376] pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
[ 0.552378] pci 0000:00:14.4: bridge window [mem 0x7f000000-0xffffffff] (subtractive decode)
[ 0.552419] pci 0000:00:15.0: PCI bridge to [bus 02-02]
[ 0.552424] pci 0000:00:15.0: bridge window [io 0xfff000-0x0000] (disabled)
[ 0.552428] pci 0000:00:15.0: bridge window [mem 0xfff00000-0x000fffff] (disabled)
[ 0.552433] pci 0000:00:15.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 0.552490] pci 0000:03:00.0: [10ec:8168] type 0 class 0x000200
[ 0.552506] pci 0000:03:00.0: reg 10: [io 0xe000-0xe0ff]
[ 0.552534] pci 0000:03:00.0: reg 18: [mem 0xd0004000-0xd0004fff 64bit pref]
[ 0.552551] pci 0000:03:00.0: reg 20: [mem 0xd0000000-0xd0003fff 64bit pref]
[ 0.552601] pci 0000:03:00.0: supports D1 D2
[ 0.552603] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.552607] pci 0000:03:00.0: PME# disabled
[ 0.570053] pci 0000:00:15.1: PCI bridge to [bus 03-03]
[ 0.570061] pci 0000:00:15.1: bridge window [io 0xe000-0xefff]
[ 0.570065] pci 0000:00:15.1: bridge window [mem 0xfff00000-0x000fffff] (disabled)
[ 0.570071] pci 0000:00:15.1: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
[ 0.570092] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.570347] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PE20._PRT]
[ 0.570379] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PE21._PRT]
[ 0.570440] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0PC._PRT]
[ 0.570613] pci0000:00: Requesting ACPI _OSC control (0x1d)
[ 0.570786] pci0000:00: ACPI _OSC control (0x1d) granted
[ 0.576882] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 14 15)
[ 0.576944] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 14 15)
[ 0.577008] ACPI: PCI Interrupt Link [LNKC] (IRQs 4 5 7 10 *11 14 15)
[ 0.577072] ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 6 7 10 11 14 15)
[ 0.577121] ACPI: PCI Interrupt Link [LNKE] (IRQs 4 5 7 10 11 14 15) *0
[ 0.577159] ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 7 10 11 14 15) *0
[ 0.577196] ACPI: PCI Interrupt Link [LNKG] (IRQs 4 5 7 10 11 14 15) *0
[ 0.577233] ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 7 10 11 14 15) *0
[ 0.577330] vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.577340] vgaarb: loaded
[ 0.577498] SCSI subsystem initialized
[ 0.577515] libata version 3.00 loaded.
[ 0.577515] usbcore: registered new interface driver usbfs
[ 0.577515] usbcore: registered new interface driver hub
[ 0.577515] usbcore: registered new device driver usb
[ 0.577515] wmi: Mapper loaded
[ 0.577515] PCI: Using ACPI for IRQ routing
[ 0.577515] PCI: pci_cache_line_size set to 64 bytes
[ 0.577515] reserve RAM buffer: 000000000009fc00 - 000000000009ffff
[ 0.577515] reserve RAM buffer: 000000005bb8c000 - 000000005bffffff
[ 0.577515] reserve RAM buffer: 000000005c22b000 - 000000005fffffff
[ 0.577515] reserve RAM buffer: 000000005d910000 - 000000005fffffff
[ 0.577515] reserve RAM buffer: 000000005dc6e000 - 000000005fffffff
[ 0.577515] reserve RAM buffer: 000000005e470000 - 000000005fffffff
[ 0.577515] reserve RAM buffer: 000000005e800000 - 000000005fffffff
[ 0.577515] NetLabel: Initializing
[ 0.577515] NetLabel: domain hash size = 128
[ 0.577515] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.577515] NetLabel: unlabeled traffic allowed by default
[ 0.577515] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.577515] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
[ 0.580013] Switching to clocksource hpet
[ 0.585273] AppArmor: AppArmor Filesystem Enabled
[ 0.585298] pnp: PnP ACPI init
[ 0.585314] ACPI: bus type pnp registered
[ 0.585507] pnp 00:00: [bus 00-ff]
[ 0.585509] pnp 00:00: [io 0x0cf8-0x0cff]
[ 0.585511] pnp 00:00: [io 0x0000-0x03af window]
[ 0.585513] pnp 00:00: [io 0x03e0-0x0cf7 window]
[ 0.585515] pnp 00:00: [io 0x03b0-0x03df window]
[ 0.585516] pnp 00:00: [io 0x0d00-0xffff window]
[ 0.585518] pnp 00:00: [mem 0x000a0000-0x000bffff window]
[ 0.585520] pnp 00:00: [mem 0x000c0000-0x000dffff window]
[ 0.585522] pnp 00:00: [mem 0x7f000000-0xffffffff window]
[ 0.585524] pnp 00:00: [mem 0x00000000 window]
[ 0.585569] pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
[ 0.585602] pnp 00:01: [mem 0xe0000000-0xefffffff]
[ 0.585643] system 00:01: [mem 0xe0000000-0xefffffff] has been reserved
[ 0.585646] system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.585699] pnp 00:02: [mem 0x5f000000-0x7effffff]
[ 0.585731] system 00:02: [mem 0x5f000000-0x7effffff] could not be reserved
[ 0.585734] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.585787] pnp 00:03: [mem 0xfeb80000-0xfebfffff]
[ 0.585818] system 00:03: [mem 0xfeb80000-0xfebfffff] has been reserved
[ 0.585821] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.586062] pnp 00:04: [io 0x0010-0x001f]
[ 0.586064] pnp 00:04: [io 0x0022-0x003f]
[ 0.586065] pnp 00:04: [io 0x0063]
[ 0.586067] pnp 00:04: [io 0x0065]
[ 0.586070] pnp 00:04: [io 0x0067-0x006f]
[ 0.586072] pnp 00:04: [io 0x0072-0x007f]
[ 0.586073] pnp 00:04: [io 0x0080]
[ 0.586075] pnp 00:04: [io 0x0084-0x0086]
[ 0.586076] pnp 00:04: [io 0x0088]
[ 0.586077] pnp 00:04: [io 0x008c-0x008e]
[ 0.586079] pnp 00:04: [io 0x0090-0x009f]
[ 0.586080] pnp 00:04: [io 0x00a2-0x00bf]
[ 0.586082] pnp 00:04: [io 0x00b1]
[ 0.586083] pnp 00:04: [io 0x00e0-0x00ef]
[ 0.586084] pnp 00:04: [io 0x04d0-0x04d1]
[ 0.586086] pnp 00:04: [io 0x040b]
[ 0.586087] pnp 00:04: [io 0x04d6]
[ 0.586088] pnp 00:04: [io 0x0c00-0x0c01]
[ 0.586090] pnp 00:04: [io 0x0c14]
[ 0.586091] pnp 00:04: [io 0x0c50-0x0c51]
[ 0.586093] pnp 00:04: [io 0x0c52]
[ 0.586094] pnp 00:04: [io 0x0c6c]
[ 0.586095] pnp 00:04: [io 0x0c6f]
[ 0.586097] pnp 00:04: [io 0x0cd0-0x0cd1]
[ 0.586098] pnp 00:04: [io 0x0cd2-0x0cd3]
[ 0.586099] pnp 00:04: [io 0x0cd4-0x0cd5]
[ 0.586101] pnp 00:04: [io 0x0cd6-0x0cd7]
[ 0.586102] pnp 00:04: [io 0x0cd8-0x0cdf]
[ 0.586104] pnp 00:04: [io 0x0800-0x089f]
[ 0.586105] pnp 00:04: [io 0x0000-0xffffffffffffffff disabled]
[ 0.586107] pnp 00:04: [io 0x0000-0x000f]
[ 0.586109] pnp 00:04: [io 0x0b20-0x0b3f]
[ 0.586110] pnp 00:04: [io 0x0900-0x090f]
[ 0.586111] pnp 00:04: [io 0x0910-0x091f]
[ 0.586113] pnp 00:04: [io 0xfe00-0xfefe]
[ 0.586114] pnp 00:04: [io 0x0060-0x005f disabled]
[ 0.586116] pnp 00:04: [io 0x0064-0x0063 disabled]
[ 0.586118] pnp 00:04: [mem 0xfec00000-0xfec00fff]
[ 0.586119] pnp 00:04: [mem 0xfee00000-0xfee00fff]
[ 0.586121] pnp 00:04: [mem 0xfed80000-0xfed8ffff]
[ 0.586123] pnp 00:04: [mem 0xfed61000-0xfed70fff]
[ 0.586124] pnp 00:04: [mem 0xfec10000-0xfec10fff]
[ 0.586126] pnp 00:04: [mem 0xfed00000-0xfed00fff]
[ 0.586127] pnp 00:04: [mem 0xff000000-0xffffffff]
[ 0.586285] system 00:04: [io 0x04d0-0x04d1] has been reserved
[ 0.586287] system 00:04: [io 0x040b] has been reserved
[ 0.586290] system 00:04: [io 0x04d6] has been reserved
[ 0.586292] system 00:04: [io 0x0c00-0x0c01] has been reserved
[ 0.586294] system 00:04: [io 0x0c14] has been reserved
[ 0.586296] system 00:04: [io 0x0c50-0x0c51] has been reserved
[ 0.586298] system 00:04: [io 0x0c52] has been reserved
[ 0.586300] system 00:04: [io 0x0c6c] has been reserved
[ 0.586302] system 00:04: [io 0x0c6f] has been reserved
[ 0.586304] system 00:04: [io 0x0cd0-0x0cd1] has been reserved
[ 0.586307] system 00:04: [io 0x0cd2-0x0cd3] has been reserved
[ 0.586309] system 00:04: [io 0x0cd4-0x0cd5] has been reserved
[ 0.586311] system 00:04: [io 0x0cd6-0x0cd7] has been reserved
[ 0.586313] system 00:04: [io 0x0cd8-0x0cdf] has been reserved
[ 0.586315] system 00:04: [io 0x0800-0x089f] has been reserved
[ 0.586318] system 00:04: [io 0x0b20-0x0b3f] has been reserved
[ 0.586323] system 00:04: [io 0x0900-0x090f] has been reserved
[ 0.586325] system 00:04: [io 0x0910-0x091f] has been reserved
[ 0.586327] system 00:04: [io 0xfe00-0xfefe] has been reserved
[ 0.586331] system 00:04: [mem 0xfec00000-0xfec00fff] could not be reserved
[ 0.586334] system 00:04: [mem 0xfee00000-0xfee00fff] has been reserved
[ 0.586336] system 00:04: [mem 0xfed80000-0xfed8ffff] has been reserved
[ 0.586339] system 00:04: [mem 0xfed61000-0xfed70fff] has been reserved
[ 0.586341] system 00:04: [mem 0xfec10000-0xfec10fff] has been reserved
[ 0.586344] system 00:04: [mem 0xfed00000-0xfed00fff] has been reserved
[ 0.586347] system 00:04: [mem 0xff000000-0xffffffff] has been reserved
[ 0.586350] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.586447] pnp 00:05: [io 0x0000-0xffffffffffffffff disabled]
[ 0.586449] pnp 00:05: [io 0x0a00-0x0a1f]
[ 0.586453] pnp 00:05: [io 0x0e80-0x0e8f]
[ 0.586487] system 00:05: [io 0x0a00-0x0a1f] has been reserved
[ 0.586490] system 00:05: [io 0x0e80-0x0e8f] has been reserved
[ 0.586492] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.586744] pnp 00:06: [io 0x03f8-0x03ff]
[ 0.586755] pnp 00:06: [irq 4]
[ 0.586756] pnp 00:06: [dma 0 disabled]
[ 0.586799] pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
[ 0.587101] pnp 00:07: [io 0x0378-0x037f]
[ 0.587105] pnp 00:07: [irq 5]
[ 0.587107] pnp 00:07: [dma 3]
[ 0.587216] pnp 00:07: Plug and Play ACPI device, IDs PNP0400 (active)
[ 0.587260] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.587279] pnp 00:09: [dma 4]
[ 0.587280] pnp 00:09: [io 0x0000-0x000f]
[ 0.587282] pnp 00:09: [io 0x0081-0x0083]
[ 0.587284] pnp 00:09: [io 0x0087]
[ 0.587285] pnp 00:09: [io 0x0089-0x008b]
[ 0.587286] pnp 00:09: [io 0x008f]
[ 0.587288] pnp 00:09: [io 0x00c0-0x00df]
[ 0.587310] pnp 00:09: Plug and Play ACPI device, IDs PNP0200 (active)
[ 0.587319] pnp 00:0a: [io 0x0070-0x0071]
[ 0.587323] pnp 00:0a: [irq 8]
[ 0.587344] pnp 00:0a: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.587351] pnp 00:0b: [io 0x0061]
[ 0.587372] pnp 00:0b: Plug and Play ACPI device, IDs PNP0800 (active)
[ 0.587397] pnp 00:0c: [io 0x0010-0x001f]
[ 0.587398] pnp 00:0c: [io 0x0022-0x003f]
[ 0.587400] pnp 00:0c: [io 0x0044-0x005f]
[ 0.587402] pnp 00:0c: [io 0x0062-0x0063]
[ 0.587403] pnp 00:0c: [io 0x0065-0x006f]
[ 0.587405] pnp 00:0c: [io 0x0072-0x007f]
[ 0.587406] pnp 00:0c: [io 0x0080]
[ 0.587409] pnp 00:0c: [io 0x0084-0x0086]
[ 0.587411] pnp 00:0c: [io 0x0088]
[ 0.587412] pnp 00:0c: [io 0x008c-0x008e]
[ 0.587413] pnp 00:0c: [io 0x0090-0x009f]
[ 0.587415] pnp 00:0c: [io 0x00a2-0x00bf]
[ 0.587416] pnp 00:0c: [io 0x00e0-0x00ef]
[ 0.587418] pnp 00:0c: [io 0x04d0-0x04d1]
[ 0.587471] system 00:0c: [io 0x04d0-0x04d1] has been reserved
[ 0.587474] system 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.587481] pnp 00:0d: [io 0x00f0-0x00ff]
[ 0.587486] pnp 00:0d: [irq 13]
[ 0.587507] pnp 00:0d: Plug and Play ACPI device, IDs PNP0c04 (active)
[ 0.587681] pnp 00:0e: [mem 0xfed00000-0xfed003ff]
[ 0.587711] pnp 00:0e: Plug and Play ACPI device, IDs PNP0103 (active)
[ 0.587718] pnp: PnP ACPI: found 15 devices
[ 0.587720] ACPI: ACPI bus type pnp unregistered
[ 0.589872] Switched to NOHz mode on CPU #0
[ 0.589964] Switched to NOHz mode on CPU #1
[ 0.593416] pci 0000:00:14.4: PCI bridge to [bus 01-01]
[ 0.593418] pci 0000:00:14.4: bridge window [io disabled]
[ 0.593422] pci 0000:00:14.4: bridge window [mem disabled]
[ 0.593425] pci 0000:00:14.4: bridge window [mem pref disabled]
[ 0.593431] pci 0000:00:15.0: PCI bridge to [bus 02-02]
[ 0.593432] pci 0000:00:15.0: bridge window [io disabled]
[ 0.593436] pci 0000:00:15.0: bridge window [mem disabled]
[ 0.593439] pci 0000:00:15.0: bridge window [mem pref disabled]
[ 0.593444] pci 0000:00:15.1: PCI bridge to [bus 03-03]
[ 0.593446] pci 0000:00:15.1: bridge window [io 0xe000-0xefff]
[ 0.593450] pci 0000:00:15.1: bridge window [mem disabled]
[ 0.593454] pci 0000:00:15.1: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
[ 0.593473] pci 0000:00:15.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.593477] pci 0000:00:15.0: setting latency timer to 64
[ 0.593482] pci 0000:00:15.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.593486] pci 0000:00:15.1: setting latency timer to 64
[ 0.593489] pci_bus 0000:00: resource 4 [io 0x0000-0x03af]
[ 0.593491] pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7]
[ 0.593493] pci_bus 0000:00: resource 6 [io 0x03b0-0x03df]
[ 0.593495] pci_bus 0000:00: resource 7 [io 0x0d00-0xffff]
[ 0.593497] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
[ 0.593499] pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff]
[ 0.593501] pci_bus 0000:00: resource 10 [mem 0x7f000000-0xffffffff]
[ 0.593503] pci_bus 0000:01: resource 4 [io 0x0000-0x03af]
[ 0.593505] pci_bus 0000:01: resource 5 [io 0x03e0-0x0cf7]
[ 0.593506] pci_bus 0000:01: resource 6 [io 0x03b0-0x03df]
[ 0.593508] pci_bus 0000:01: resource 7 [io 0x0d00-0xffff]
[ 0.593510] pci_bus 0000:01: resource 8 [mem 0x000a0000-0x000bffff]
[ 0.593512] pci_bus 0000:01: resource 9 [mem 0x000c0000-0x000dffff]
[ 0.593514] pci_bus 0000:01: resource 10 [mem 0x7f000000-0xffffffff]
[ 0.593516] pci_bus 0000:03: resource 0 [io 0xe000-0xefff]
[ 0.593518] pci_bus 0000:03: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref]
[ 0.593552] NET: Registered protocol family 2
[ 0.593662] IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.594330] TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
[ 0.595390] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.595629] TCP: Hash tables configured (established 262144 bind 65536)
[ 0.595631] TCP reno registered
[ 0.595638] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[ 0.595651] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[ 0.595736] NET: Registered protocol family 1
[ 0.595751] pci 0000:00:01.0: Boot video device
[ 0.680127] PCI: CLS 64 bytes, default 64
[ 0.680172] Trying to unpack rootfs image as initramfs...
[ 0.839291] Freeing initrd memory: 9996k freed
[ 0.845158] pci 0000:00:00.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.845325] pci 0000:00:00.2: irq 40 for MSI/MSI-X
[ 0.845347] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40
[ 0.857021] AMD-Vi: Lazy IO/TLB flushing enabled
[ 0.857456] audit: initializing netlink socket (disabled)
[ 0.857468] type=2000 audit(1376475369.850:1): initialized
[ 0.874859] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.876535] VFS: Disk quotas dquot_6.5.2
[ 0.876582] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.877122] fuse init (API version 7.16)
[ 0.877194] msgmni has been set to 2873
[ 0.877411] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 0.877438] io scheduler noop registered
[ 0.877440] io scheduler deadline registered
[ 0.877476] io scheduler cfq registered (default)
[ 0.877567] pcieport 0000:00:15.0: setting latency timer to 64
[ 0.877611] pcieport 0000:00:15.0: irq 41 for MSI/MSI-X
[ 0.877666] pcieport 0000:00:15.1: setting latency timer to 64
[ 0.877702] pcieport 0000:00:15.1: irq 42 for MSI/MSI-X
[ 0.877774] pcieport 0000:00:15.0: Signaling PME through PCIe PME interrupt
[ 0.877778] pcie_pme 0000:00:15.0:pcie01: service driver pcie_pme loaded
[ 0.877792] pcieport 0000:00:15.1: Signaling PME through PCIe PME interrupt
[ 0.877794] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
[ 0.877797] pcie_pme 0000:00:15.1:pcie01: service driver pcie_pme loaded
[ 0.877810] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.877828] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.877923] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
[ 0.877929] ACPI: Power Button [PWRB]
[ 0.877961] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 0.877964] ACPI: Power Button [PWRF]
[ 0.878140] ACPI: acpi_idle registered with cpuidle
[ 1.020544] ERST: Table is not found!
[ 1.020615] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 1.041149] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 1.063219] 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 1.063431] Linux agpgart interface v0.103
[ 1.064239] brd: module loaded
[ 1.064615] loop: module loaded
[ 1.064783] pata_acpi 0000:00:14.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 1.064812] pata_acpi 0000:00:14.1: PCI INT B disabled
[ 1.065039] Fixed MDIO Bus: probed
[ 1.065061] PPP generic driver version 2.4.2
[ 1.065086] tun: Universal TUN/TAP device driver, 1.6
[ 1.065087] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 1.065147] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.065157] ehci_hcd 0000:00:12.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 1.065167] ehci_hcd 0000:00:12.2: EHCI Host Controller
[ 1.065192] ehci_hcd 0000:00:12.2: new USB bus registered, assigned bus number 1
[ 1.070120] ehci_hcd 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[ 1.070155] QUIRK: Enable AMD PLL fix
[ 1.070165] ehci_hcd 0000:00:12.2: debug port 1
[ 1.070188] ehci_hcd 0000:00:12.2: irq 17, io mem 0xfef4f000
[ 1.090106] ehci_hcd 0000:00:12.2: USB 2.0 started, EHCI 1.00
[ 1.090242] hub 1-0:1.0: USB hub found
[ 1.090246] hub 1-0:1.0: 5 ports detected
[ 1.090315] ehci_hcd 0000:00:13.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 1.090331] ehci_hcd 0000:00:13.2: EHCI Host Controller
[ 1.090366] ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 2
[ 1.090398] ehci_hcd 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[ 1.090421] ehci_hcd 0000:00:13.2: debug port 1
[ 1.090435] ehci_hcd 0000:00:13.2: irq 17, io mem 0xfef4d000
[ 1.110106] ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00
[ 1.110251] hub 2-0:1.0: USB hub found
[ 1.110255] hub 2-0:1.0: 5 ports detected
[ 1.110324] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.110350] ohci_hcd 0000:00:12.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 1.110367] ohci_hcd 0000:00:12.0: OHCI Host Controller
[ 1.110397] ohci_hcd 0000:00:12.0: new USB bus registered, assigned bus number 3
[ 1.120149] ohci_hcd 0000:00:12.0: irq 18, io mem 0xfef50000
[ 1.184249] hub 3-0:1.0: USB hub found
[ 1.184257] hub 3-0:1.0: 5 ports detected
[ 1.184325] ohci_hcd 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 1.184341] ohci_hcd 0000:00:13.0: OHCI Host Controller
[ 1.184370] ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 4
[ 1.184414] ohci_hcd 0000:00:13.0: irq 18, io mem 0xfef4e000
[ 1.244267] hub 4-0:1.0: USB hub found
[ 1.244274] hub 4-0:1.0: 5 ports detected
[ 1.244344] ohci_hcd 0000:00:14.5: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 1.244360] ohci_hcd 0000:00:14.5: OHCI Host Controller
[ 1.244395] ohci_hcd 0000:00:14.5: new USB bus registered, assigned bus number 5
[ 1.250143] ohci_hcd 0000:00:14.5: irq 18, io mem 0xfef4c000
[ 1.314291] hub 5-0:1.0: USB hub found
[ 1.314300] hub 5-0:1.0: 2 ports detected
[ 1.314382] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.314473] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 1.314815] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.314822] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.314929] mousedev: PS/2 mouse device common for all mice
[ 1.315035] rtc_cmos 00:0a: RTC can wake from S4
[ 1.330231] rtc_cmos 00:0a: rtc core: registered rtc_cmos as rtc0
[ 1.330255] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 1.330363] device-mapper: uevent: version 1.0.3
[ 1.330432] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com
[ 1.330499] device-mapper: multipath: version 1.3.0 loaded
[ 1.330502] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 1.330598] cpuidle: using governor ladder
[ 1.330652] cpuidle: using governor menu
[ 1.330654] EFI Variables Facility v0.08 2004-May-17
[ 1.330921] TCP cubic registered
[ 1.331022] NET: Registered protocol family 10
[ 1.331562] NET: Registered protocol family 17
[ 1.331576] Registering the dns_resolver key type
[ 1.331595] powernow-k8: Found 1 AMD A10-5700 APU with Radeon(tm) HD Graphics (2 cpu cores) (version 2.20.00)
[ 1.331606] powernow-k8: Core Performance Boosting: on.
[ 1.331669] powernow-k8: 0 : pstate 0 (3400 MHz)
[ 1.331671] powernow-k8: 1 : pstate 1 (3000 MHz)
[ 1.331672] powernow-k8: 2 : pstate 2 (2600 MHz)
[ 1.331673] powernow-k8: 3 : pstate 3 (2300 MHz)
[ 1.331675] powernow-k8: 4 : pstate 4 (1900 MHz)
[ 1.331676] powernow-k8: 5 : pstate 5 (1400 MHz)
[ 1.331860] PM: Hibernation image not present or could not be loaded.
[ 1.331870] registered taskstats version 1
[ 1.332180] Magic number: 9:841:274
[ 1.332199] tty tty11: hash matches
[ 1.332237] rtc_cmos 00:0a: setting system clock to 2013-08-14 10:16:10 UTC (1376475370)
[ 1.332240] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 1.332241] EDD information not available.
[ 1.334778] Freeing unused kernel memory: 1068k freed
[ 1.335008] Write protecting the kernel read-only data: 10240k
[ 1.335569] Freeing unused kernel memory: 104k freed
[ 1.341170] Freeing unused kernel memory: 1364k freed
[ 1.440286] udevd (155): /proc/155/oom_adj is deprecated, please use /proc/155/oom_score_adj instead.
[ 1.508992] ahci 0000:00:11.0: version 3.0
[ 1.509015] ahci 0000:00:11.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 1.509087] ahci 0000:00:11.0: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x2 impl SATA mode
[ 1.509092] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
[ 1.661823] scsi0 : ahci
[ 1.666162] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.666189] r8169 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 1.666237] r8169 0000:03:00.0: setting latency timer to 64
[ 1.666246] r8169 0000:03:00.0: (unregistered net_device): unknown MAC, using family default
[ 1.666321] r8169 0000:03:00.0: irq 43 for MSI/MSI-X
[ 1.666430] r8169 0000:03:00.0: eth0: Features changed: 0x00004980 -> 0x00004180
[ 1.667028] r8169 0000:03:00.0: eth0: RTL8168b/8111b at 0xffffc90000320000, 74:27:ea:45:94:62, XID 0c900800 IRQ 43
[ 1.667131] scsi1 : ahci
[ 1.667339] ata1: DUMMY
[ 1.667342] ata2: SATA max UDMA/133 abar m2048@0xfef51000 port 0xfef51180 irq 19
[ 1.667425] pata_atiixp 0000:00:14.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 1.672020] scsi2 : pata_atiixp
[ 1.680053] scsi3 : pata_atiixp
[ 1.680918] ata3: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf100 irq 14
[ 1.680923] ata4: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf108 irq 15
[ 1.740070] usb 4-1: new full speed USB device number 2 using ohci_hcd
[ 1.850023] Refined TSC clocksource calibration: 3400.254 MHz.
[ 1.850029] Switching to clocksource tsc
[ 2.040195] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:13.0/usb4/4-1/4-1:1.0/input/input2
[ 2.040371] generic-usb 0003:046D:C52E.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:13.0-1/input0
[ 2.044500] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:13.0/usb4/4-1/4-1:1.1/input/input3
[ 2.044926] generic-usb 0003:046D:C52E.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:13.0-1/input1
[ 2.045045] usbcore: registered new interface driver usbhid
[ 2.045048] usbhid: USB HID core driver
[ 2.220113] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2.221125] ata2.00: ATA-8: WDC WD2500AAJS-75B4A0, 01.03A01, max UDMA/133
[ 2.221128] ata2.00: 488281250 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 2.222153] ata2.00: configured for UDMA/133
[ 2.222259] scsi 1:0:0:0: Direct-Access ATA WDC WD2500AAJS-7 01.0 PQ: 0 ANSI: 5
[ 2.222414] sd 1:0:0:0: Attached scsi generic sg0 type 0
[ 2.222505] sd 1:0:0:0: [sda] 488281250 512-byte logical blocks: (250 GB/232 GiB)
[ 2.222554] sd 1:0:0:0: [sda] Write Protect is off
[ 2.222557] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.222590] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.222758] sda: detected capacity change from 0 to 250000000000
[ 2.257930] sda: sda1 sda2 < sda5 >
[ 2.258205] sd 1:0:0:0: [sda] Attached SCSI disk
[ 2.426123] PM: Starting manual resume from disk
[ 2.426126] PM: Hibernation image partition 8:5 present
[ 2.426127] PM: Looking for hibernation image.
[ 2.426259] PM: Image not found (code -22)
[ 2.426261] PM: Hibernation image not present or could not be loaded.
[ 2.456436] EXT3-fs: barriers not enabled
[ 2.477803] kjournald starting. Commit interval 5 seconds
[ 2.477889] EXT3-fs (sda1): mounted filesystem with ordered data mode
[ 7.051633] udev: starting version 141
[ 7.150909] udev: renamed network interface eth0 to eth16
[ 7.156177] xhci_hcd 0000:00:10.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 7.156199] xhci_hcd 0000:00:10.0: setting latency timer to 64
[ 7.156203] xhci_hcd 0000:00:10.0: xHCI Host Controller
[ 7.156315] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 6
[ 7.180396] xhci_hcd 0000:00:10.0: irq 18, io mem 0xfef4a000
[ 7.180460] xhci_hcd 0000:00:10.0: irq 44 for MSI/MSI-X
[ 7.180465] xhci_hcd 0000:00:10.0: irq 45 for MSI/MSI-X
[ 7.180470] xhci_hcd 0000:00:10.0: irq 46 for MSI/MSI-X
[ 7.180652] xHCI xhci_add_endpoint called for root hub
[ 7.180654] xHCI xhci_check_bandwidth called for root hub
[ 7.180681] hub 6-0:1.0: USB hub found
[ 7.180689] hub 6-0:1.0: 2 ports detected
[ 7.180752] xhci_hcd 0000:00:10.0: xHCI Host Controller
[ 7.180799] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 7
[ 7.220266] xHCI xhci_add_endpoint called for root hub
[ 7.220269] xHCI xhci_check_bandwidth called for root hub
[ 7.220309] hub 7-0:1.0: USB hub found
[ 7.220317] hub 7-0:1.0: 2 ports detected
[ 7.220395] xhci_hcd 0000:00:10.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 7.220417] xhci_hcd 0000:00:10.1: setting latency timer to 64
[ 7.220421] xhci_hcd 0000:00:10.1: xHCI Host Controller
[ 7.220461] xhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 8
[ 7.227552] input: PC Speaker as /devices/platform/pcspkr/input/input4
[ 7.240523] xhci_hcd 0000:00:10.1: irq 17, io mem 0xfef48000
[ 7.240587] xhci_hcd 0000:00:10.1: irq 47 for MSI/MSI-X
[ 7.240593] xhci_hcd 0000:00:10.1: irq 48 for MSI/MSI-X
[ 7.240597] xhci_hcd 0000:00:10.1: irq 49 for MSI/MSI-X
[ 7.240798] xHCI xhci_add_endpoint called for root hub
[ 7.240800] xHCI xhci_check_bandwidth called for root hub
[ 7.240827] hub 8-0:1.0: USB hub found
[ 7.240835] hub 8-0:1.0: 2 ports detected
[ 7.240905] xhci_hcd 0000:00:10.1: xHCI Host Controller
[ 7.240945] xhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 9
[ 7.280452] xHCI xhci_add_endpoint called for root hub
[ 7.280455] xHCI xhci_check_bandwidth called for root hub
[ 7.280483] hub 9-0:1.0: USB hub found
[ 7.280491] hub 9-0:1.0: 2 ports detected
[ 7.280718] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[ 7.308351] parport_pc 00:07: reported by Plug and Play ACPI
[ 7.308397] parport0: PC-style at 0x378, irq 5 [PCSPP]
[ 7.422549] ppdev: user-space parallel port driver
[ 7.689373] HDA Intel 0000:00:01.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18
[ 7.689426] HDA Intel 0000:00:01.1: irq 50 for MSI/MSI-X
[ 7.689448] HDA Intel 0000:00:01.1: setting latency timer to 64
[ 8.245900] HDMI: no space for converter 8
[ 8.245946] HDMI: no space for converter 10
[ 8.245993] HDMI: no space for converter 12
[ 8.246482] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 8.511546] lp0: using parport0 (interrupt-driven).
[ 8.741185] Adding 5952044k swap on /dev/sda5. Priority:-1 extents:1 across:5952044k
[ 12.718834] EXT3-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
[ 12.719061] EXT3-fs (sda1): using internal journal
[ 14.061788] ipmi message handler version 39.2
[ 14.089815] EINJ: Table is not found!
[ 14.119064] GHES: HEST is not enabled!
[ 15.863529] Bluetooth: Core ver 2.16
[ 15.863553] NET: Registered protocol family 31
[ 15.863555] Bluetooth: HCI device and connection manager initialized
[ 15.863559] Bluetooth: HCI socket layer initialized
[ 15.863560] Bluetooth: L2CAP socket layer initialized
[ 15.864319] Bluetooth: SCO socket layer initialized
[ 15.868955] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 15.868959] Bluetooth: BNEP filters: protocol multicast
[ 15.878329] Bridge firewalling registered
[ 16.243393] Bluetooth: RFCOMM TTY layer initialized
[ 16.243406] Bluetooth: RFCOMM socket layer initialized
[ 16.243411] Bluetooth: RFCOMM ver 1.11
[ 22.020599] r8169 0000:03:00.0: eth16: link down
[ 22.021124] ADDRCONF(NETDEV_UP): eth16: link is not ready
[ 177.688549] hda-intel: Invalid position buffer, using LPIB read method instead.
[ 177.721782] hda-intel: Invalid position buffer, using LPIB read method instead.
[ 246.061579] f71882fg: Found f71869 chip at 0xe80, revision 17
[ 246.061838] f71882fg f71882fg.3712: Auto pwm controlled by raw digital data, disabling pwm auto_point sysfs attributes
[ 246.061849] f71882fg f71882fg.3712: Fan: 1 is in duty-cycle mode
[ 246.061856] f71882fg f71882fg.3712: Fan: 2 is in duty-cycle mode
[ 246.061863] f71882fg f71882fg.3712: Fan: 3 is in duty-cycle mode
[ 4889.245312] No module found in object
[ 4901.007955] No module found in object
[-- Attachment #3: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (13 preceding siblings ...)
2013-08-14 19:06 ` Dev, Kapil
@ 2013-08-14 20:03 ` Guenter Roeck
2013-08-14 20:45 ` Dev, Kapil
` (10 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-14 20:03 UTC (permalink / raw)
To: lm-sensors
T24gV2VkLCBBdWcgMTQsIDIwMTMgYXQgMDM6MDY6MzVQTSAtMDQwMCwgRGV2LCBLYXBpbCB3cm90
ZToKPiBPbiBXZWQsIEF1ZyAxNCwgMjAxMyBhdCAyOjI5IFBNLCBHdWVudGVyIFJvZWNrIDxsaW51
eEByb2Vjay11cy5uZXQ+IHdyb3RlOgo+IAo+ID4gT24gV2VkLCBBdWcgMTQsIDIwMTMgYXQgMDE6
MjA6NTdQTSAtMDQwMCwgRGV2LCBLYXBpbCB3cm90ZToKPiA+ID4gT24gV2VkLCBBdWcgMTQsIDIw
MTMgYXQgMTozMCBBTSwgR3VlbnRlciBSb2VjayA8bGludXhAcm9lY2stdXMubmV0Pgo+ID4gd3Jv
dGU6Cj4gPiA+Cj4gPiA+ID4gT24gMDgvMTMvMjAxMyAxMDoxNyBQTSwgS2FwaWwgRGV2IHdyb3Rl
Ogo+ID4gPiA+Cj4gPiA+ID4+Cj4gPiA+ID4+IE9uIEF1ZyAxNCwgMjAxMywgYXQgMTI6NTYgQU0s
IEd1ZW50ZXIgUm9lY2sgPGxpbnV4QHJvZWNrLXVzLm5ldD4KPiA+IHdyb3RlOgo+ID4gPiA+Pgo+
ID4gPiA+PiAgT24gMDgvMTMvMjAxMyAwODowOSBQTSwgRGV2LCBLYXBpbCB3cm90ZToKPiA+ID4g
Pj4+Cj4gPiA+ID4+Pj4KPiA+ID4gPj4+Pgo+ID4gPiA+Pj4+IE9uIFR1ZSwgQXVnIDEzLCAyMDEz
IGF0IDExOjAyIFBNLCBHdWVudGVyIFJvZWNrIDxsaW51eEByb2Vjay11cy5uZXQKPiA+IDxtYWls
dG86Cj4gPiA+ID4+Pj4gbGludXhAcm9lY2stdXMubmV0Pj4gd3JvdGU6Cj4gPiA+ID4+Pj4KPiA+
ID4gPj4+PiAgICAgT24gMDgvMTMvMjAxMyAwNzo0MSBQTSwgRGV2LCBLYXBpbCB3cm90ZToKPiA+
ID4gPj4+Pgo+ID4gPiA+Pj4+ICAgICAgICAgVGhhbmtzIGFnYWluIEd1ZW50ZXIhCj4gPiA+ID4+
Pj4KPiA+ID4gPj4+Pgo+ID4gPiA+Pj4+Cj4gPiA+ID4+Pj4KPiA+ID4gPj4+PiAgICAgICAgIE9u
IFR1ZSwgQXVnIDEzLCAyMDEzIGF0IDU6NTEgUE0sIEd1ZW50ZXIgUm9lY2sgPAo+ID4gPiA+Pj4+
IGxpbnV4QHJvZWNrLXVzLm5ldCA8bWFpbHRvOmxpbnV4QHJvZWNrLXVzLm5ldD4gPG1haWx0bzoK
PiA+ID4gPj4+PiBsaW51eEByb2Vjay11cy5uZXQgPG1haWx0bzpsaW51eEByb2Vjay11cy5uZXQ+
Pj4gd3JvdGU6Cj4gPiA+ID4+Pj4KPiA+ID4gPj4+PiAgICAgICAgICAgICAgT24gVHVlLCBBdWcg
MTMsIDIwMTMgYXQgMDU6MTE6MzFQTSAtMDQwMCwgRGV2LCBLYXBpbAo+ID4gd3JvdGU6Cj4gPiA+
ID4+Pj4gICAgICAgICAgICAgICA+IFRoYW5rcyBmb3IgdGhlIHJlc3BvbnNlIEd1ZW50ZXIhCj4g
PiA+ID4+Pj4gICAgICAgICAgICAgICA+Cj4gPiA+ID4+Pj4gICAgICAgICAgICAgICA+IEkgcHV0
IHRoZSBzeXN0ZW0gb24gbG9hZCBhbmQgSSBub3RpY2VkIHRoZWlyIHZhbHVlCj4gPiA+ID4+Pj4g
aGFyZGx5IGNoYW5nZXMuIFRvIG15Cj4gPiA+ID4+Pj4gICAgICAgICAgICAgICA+IHN1cnByaXNl
LCBJIHJhbiBhIGJlbmNobWFyayBmb3IgMyBtaW51dGVzIGFuZCBub25lCj4gPiBvZgo+ID4gPiA+
Pj4+IHRlbXAqICB2YWx1ZXMgY2hhbmdlZAo+ID4gPiA+Pj4+ICAgICAgICAgICAgICAgPiBkdXJp
bmcgZXhlY3V0aW9uLiBUaGUgaGlnaGVzdCByZXBvcnRlZCB0ZW1wZXJhdHVyZQo+ID4gaXMKPiA+
ID4gPj4+PiBhbHdheXMgNDhDLgo+ID4gPiA+Pj4+ICAgICAgICAgICAgICAgPgo+ID4gPiA+Pj4+
ICAgICAgICAgICAgICAgPiBJIHdhcyBleHBlY3RpbmcgdGhhdCB0aGUgaW50ZXJuYWwgdGVtcGVy
YXR1cmUgd291bGQKPiA+ID4gPj4+PiBoYXZlICJzZW5zb3IgPSB0aGVybWFsCj4gPiA+ID4+Pj4g
ICAgICAgICAgICAgICA+IGRpb2RlIiBvciAic2Vuc29yID0gY29yZSIgYXMgYSBrZXl3b3JkLiBJ
IHRob3VnaHQKPiA+ID4gPj4+PiAic2Vuc29yPXRoZXJtaXN0b3IiIG1lYW5zCj4gPiA+ID4+Pj4g
ICAgICAgICAgICAgICA+IHRoZSBjb3JyZXNwb25kaW5nIHNlbnNvciBpcyBvbiB0aGUgbW90aGVy
Ym9hcmQgYW5kCj4gPiBub3QKPiA+ID4gPj4+PiB0aGUgaW50ZXJuYWwKPiA+ID4gPj4+PiAgICAg
ICAgICAgICAgID4gZGllLXNlbnNvci4KPiA+ID4gPj4+PiAgICAgICAgICAgICAgID4KPiA+ID4g
Pj4+PiAgICAgICAgICAgICAgU3VyZSwgYnV0IHdobyBrbm93cyBpZiB0aGV5IHB1dCBhIHNlbnNv
ciBiZWxvdyB0aGUgQ1BVCj4gPiBmb3IKPiA+ID4gPj4+PiBzb21lIHJlYXNvbiAuLi4KPiA+ID4g
Pj4+Pgo+ID4gPiA+Pj4+ICAgICAgICAgICAgICBJIGFtIG5vdCBmYW1pbGlhciB3aXRoIHRoZSBB
MTAgQ1BVcy4gQXJlIHRob3NlIHNpbWlsYXIKPiA+IHRvCj4gPiA+ID4+Pj4gSzEwID8KPiA+ID4g
Pj4+PiAgICAgICAgICAgICAgSWYgc28sIG1heWJlIHRoZSBrMTB0ZW1wIGRyaXZlciB3b3JrcyBv
ciBjb3VsZCBiZQo+ID4gZXh0ZW5kZWQKPiA+ID4gPj4+PiB0byBzdXBwb3J0IGl0Lgo+ID4gPiA+
Pj4+ICAgICAgICAgICAgICBDYW4geW91IGdpdmUgaXQgYSB0cnkgPwo+ID4gPiA+Pj4+Cj4gPiA+
ID4+Pj4gICAgICAgICAgICAgIElmIGl0IGRvZXMgbm90IHdvcmsgb3V0IG9mIHRoZSBib3gsIGNh
biB5b3Ugc2VuZCBtZSB0aGUKPiA+ID4gPj4+PiBvdXRwdXQgb2YgImxzcGNpIC1ubiIgPwo+ID4g
PiA+Pj4+Cj4gPiA+ID4+Pj4KPiA+ID4gPj4+PiAgICAgICAgIEthcGlsOiBJIGJlbGlldmUgSzEw
IGNvcnJlc3BvbmRzIHRvIEE4IHNlcmllZCwgYW5kIEExMCBoYXMKPiA+ID4gPj4+PiBCdWxsZG96
ZXIgYXJjaGl0ZWN0dXJlIChodHRwOi8vd3d3LmNwdS13b3JsZC5jb20vX18qKgo+ID4gPiA+Pj4+
IENQVXMvQnVsbGRvemVyL1RZUEUtQTEwLV9fKipTZXJpZXMuaHRtbDwKPiA+IGh0dHA6Ly93d3cu
Y3B1LXdvcmxkLmNvbS9fX0NQVXMvQnVsbGRvemVyL1RZUEUtQTEwLV9fU2VyaWVzLmh0bWw+PAo+
ID4gPiA+Pj4+IGh0dHA6Ly93d3cuY3B1LXdvcmxkLmNvbS8qKkNQVXMvQnVsbGRvemVyL1RZUEUt
QTEwLSoqU2VyaWVzLmh0bWw8Cj4gPiBodHRwOi8vd3d3LmNwdS13b3JsZC5jb20vQ1BVcy9CdWxs
ZG96ZXIvVFlQRS1BMTAtU2VyaWVzLmh0bWw+PikuCj4gPiA+ID4+Pj4gSSBhbSBub3Qgc3VyZSBo
b3cgZGlmZmVyZW50IHRoZXkgYXJlIHRob3VnaC4gSSB0cmllZCBLMTAsIGJ1dCBpdAo+ID4gZGlk
IG5vdAo+ID4gPiA+Pj4+IHdvcmsgb3V0IG9mIHRoZSBib3guIEkgYW0gbG9va2luZyBpbnRvIGsx
MHRlbXAuYyBkcml2ZXIgbm93LiBBbHNvLEkKPiA+IGFtCj4gPiA+ID4+Pj4gYXR0YWNoaW5nIHRo
ZSBvdXRwdXQgb2YgImxzcGNpIC1ubiIgY29tbWFuZCBoZXJld2l0aDsgeW91IG1pZ2h0Cj4gPiBo
YXZlIHRvCj4gPiA+ID4+Pj4gb3BlbiBpdCB1c2luZyB3b3JkcGFkIGZvciBwcm9wZXIgZm9ybWF0
dGluZy4uCj4gPiA+ID4+Pj4KPiA+ID4gPj4+Pgo+ID4gPiA+Pj4+ICAgICBZb3VyIGxzcGNpIG91
dHB1dCBpbmNsdWRlcwo+ID4gPiA+Pj4+Cj4gPiA+ID4+Pj4gICAgIDAwOjE4LjMgSG9zdCBicmlk
Z2UgWzA2MDBdOiBBZHZhbmNlZCBNaWNybyBEZXZpY2VzIFtBTURdIERldmljZQo+ID4gPiA+Pj4+
IFsxMDIyOjE0MDNdCj4gPiA+ID4+Pj4KPiA+ID4gPj4+PiAgICAgd2hpY2ggaXMgc3VwcG9ydGVk
IGJ5IHRoZSBsYXRlc3QgazEwdGVtcCBkcml2ZXIuIFN1cHBvcnQgd2FzCj4gPiBhZGRlZAo+ID4g
PiA+Pj4+IGVhcmx5IGxhc3QgeWVhci4KPiA+ID4gPj4+PiAgICAgV2hhdCBpcyB5b3VyIGtlcm5l
bCB2ZXJzaW9uLCBhbmQgY2FuIHlvdSBzd2l0Y2ggdG8gYSBtb3JlIHJlY2VudAo+ID4gPiA+Pj4+
IHZlcnNpb24gPwo+ID4gPiA+Pj4+Cj4gPiA+ID4+Pj4KPiA+ID4gPj4+PiBLYXBpbDogSSBoYXZl
IDIuNi4zOS0wMjA2MzktZ2VuZXJpYyBrZXJuZWwuIElzIGl0IHRvbyBvbGQga2VybmVsIGZvcgo+
ID4gPiA+Pj4+IGsxMHRlbXAgZHJpdmVyIHRvIHdvcms/IFdoaWNoIHN0YWJsZSBrZXJuZWwgc2hv
dWxkIEkgdXBncmFkZSB0bz8KPiA+ID4gPj4+Pgo+ID4gPiA+Pj4+Cj4gPiA+ID4+PiBZb3UgbmVl
ZCAzLjQgb3IgbGF0ZXIuCj4gPiA+ID4+Pgo+ID4gPiA+Pgo+ID4gPiA+PiBLYXBpbDogSSB3YXMg
dHJ5aW5nIHRvIGF2b2lkIHVwZGF0aW5nIHRoZSBrZXJuZWwgYmVjYXVzZSBteSBjdXJyZW50Cj4g
PiA+ID4+IGtlcm5lbCBpcyBzZXR1cCBmb3IgcnVubmluZyBkaWZmZXJlbnQgdHlwZSBvZiBiZW5j
aG1hcmtzIGV0Yy4gU2VlbXMKPiA+IGxpa2UgSQo+ID4gPiA+PiBjYW4ndCBhdm9pZCB1cGRhdGlu
ZyB0aGUga2VybmVsOyBJIHdpbGwgZG8gaXQuLgo+ID4gPiA+Pgo+ID4gPiA+PiAgQWx0ZXJuYXRp
dmUgd291bGQgYmUgdG8gYmFjay1wb3J0IHRoZSBrMTB0ZW1wIGRyaXZlciBmcm9tIGEgbGF0ZXIK
PiA+ID4gPiBrZXJuZWwuIFRoZW4geW91IGNhbiBrZWVwIHJ1bm5pbmcgdGhlIG9sZCBvbmUuCj4g
PiA+ID4KPiA+ID4gPgo+ID4gPiBLYXBpbDogTm90IHN1cmUgaG93IHRvIGRvIHRoYXQuIEkgYW0g
YWxyZWFkeSB0YWtpbmcgdGhlIGsxMHRlbXAgZHJpdmVyCj4gPiBmcm9tCj4gPiA+IGhlcmU6IGh0
dHA6Ly9raGFsaS5saW51eC1mci5vcmcvZGV2ZWwvbG0tc2Vuc29ycy9kcml2ZXJzL2sxMHRlbXAv
IGFuZAo+ID4gPiBjb21waWxpbmcgYW5kIHVzaW5nIGl0Lgo+ID4gPgo+ID4gVGhhdCB2ZXJzaW9u
IHNob3VsZCBhbHJlYWR5IGhhdmUgc3VwcG9ydCBmb3IgeW91ciBjaGlwIHVubGVzcyBJIGFtIG1p
c3NpbmcKPiA+IHNvbWV0aGluZy4gSWYgeW91IGFscmVhZHkgdXNlIGl0LCBhIG5ld2VyIGtlcm5l
bCB2ZXJzaW9uIHdpbGwgbm90IGhlbHAuCj4gPgo+ID4gRG8geW91IGdldCBhbnkga2VybmVsIGxv
ZyBtZXNzYWdlIHdoZW4geW91IHRyeSB0byBsb2FkIGl0ID8KPiA+Cj4gCj4gS2FwaWw6IFdoZW4g
SSBpbnNlcnQgdGhlIG1vZHVsZSB1c2luZzogc3VkbyBpbnNtb2QgazEwdGVtcC5rbywgSSBkb24n
dCBnZXQKPiBhbnkgbWVzc2FnZSBvbiB0ZXJtaW5hbC4gSG93ZXZlciwgd2hlbiBJIGNvbXBpbGUg
a3RlbXAxMC5jIGZpbGUgdXNpbmcgbWFrZSwKPiBJIGdldCBmb2xsb3dpbmcgd2FybmluZ3M7IEkg
YW0gbm90IHN1cmUgaWYgdGhleSBhcmUgYWNjZXB0YWJsZS4KPiAtLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
Cj4gbWFrZVsxXTogRW50ZXJpbmcgZGlyZWN0b3J5IGAvdXNyL3NyYy9saW51eC1oZWFkZXJzLTIu
Ni4zOS0wMjA2MzktZ2VuZXJpYycKPiAgIENDIFtNXSAgL2hvbWUvYW1kX2ExMC9rMTB0ZW1wX2Ry
aXZlci9rMTB0ZW1wLm8KPiAvaG9tZS8vYW1kX2ExMC9rMTB0ZW1wX2RyaXZlci9rMTB0ZW1wLmM6
MjMyOiB3YXJuaW5nOiBkYXRhIGRlZmluaXRpb24gaGFzCj4gbm8gdHlwZSBvciBzdG9yYWdlIGNs
YXNzCj4gL2hvbWUvL2FtZF9hMTAvazEwdGVtcF9kcml2ZXIvazEwdGVtcC5jOjIzMjogd2Fybmlu
ZzogdHlwZSBkZWZhdWx0cyB0bwo+IOKAmGludOKAmSBpbiBkZWNsYXJhdGlvbiBvZiDigJhtb2R1
bGVfcGNpX2RyaXZlcuKAmQo+IC9ob21lLy9hbWRfYTEwL2sxMHRlbXBfZHJpdmVyL2sxMHRlbXAu
YzoyMzI6IHdhcm5pbmc6IHBhcmFtZXRlciBuYW1lcwo+ICh3aXRob3V0IHR5cGVzKSBpbiBmdW5j
dGlvbiBkZWNsYXJhdGlvbgo+IC9ob21lLy9hbWRfYTEwL2sxMHRlbXBfZHJpdmVyL2sxMHRlbXAu
YzoyMjU6IHdhcm5pbmc6IOKAmGsxMHRlbXBfZHJpdmVy4oCZCj4gZGVmaW5lZCBidXQgbm90IHVz
ZWQKPiAgIEJ1aWxkaW5nIG1vZHVsZXMsIHN0YWdlIDIuCj4gICBNT0RQT1NUIDEgbW9kdWxlcwo+
ICAgQ0MgICAgICAvaG9tZS9hbWRfYTEwL2sxMHRlbXBfZHJpdmVyL2sxMHRlbXAubW9kLm8KPiAg
IExEIFtNXSAgL2hvbWUvYW1kX2ExMC9rMTB0ZW1wX2RyaXZlci9rMTB0ZW1wLmtvCj4gbWFrZVsx
XTogTGVhdmluZyBkaXJlY3RvcnkgYC91c3Ivc3JjL2xpbnV4LWhlYWRlcnMtMi42LjM5LTAyMDYz
OS1nZW5lcmljJwo+IApUaGVyZSBpcyBubyBkZWZpbml0aW9uIGZvciBtb2R1bGVfcGNpX2RyaXZl
ciBpbiB5b3VyIGtlcm5lbCwKdGh1cyB0aGUgaW5pdGlhbGl6YXRpb24gY29kZSB3b24ndCBydW4g
YW5kIHRoZSBkcml2ZXIgd2lsbApub3QgcmVhbGx5IGJlIGRvaW5nIGFueXRoaW5nLgoKWW91IHdp
bGwgaGF2ZSB0byByZXBsYWNlCgptb2R1bGVfcGNpX2RyaXZlcihrMTB0ZW1wX2RyaXZlcik7Cgp3
aXRoIAoKc3RhdGljIGludCBfX2luaXQgazEwdGVtcF9pbml0KHZvaWQpCnsKCXJldHVybiBwY2lf
cmVnaXN0ZXJfZHJpdmVyKCZrMTB0ZW1wX2RyaXZlcik7Cn0KCnN0YXRpYyB2b2lkIF9fZXhpdCBr
MTB0ZW1wX2V4aXQodm9pZCkKewoJcGNpX3VucmVnaXN0ZXJfZHJpdmVyKCZrMTB0ZW1wX2RyaXZl
cik7Cn0KCm1vZHVsZV9pbml0KGsxMHRlbXBfaW5pdCkKbW9kdWxlX2V4aXQoazEwdGVtcF9leGl0
KQoKR3VlbnRlcgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fCmxtLXNlbnNvcnMgbWFpbGluZyBsaXN0CmxtLXNlbnNvcnNAbG0tc2Vuc29ycy5vcmcKaHR0
cDovL2xpc3RzLmxtLXNlbnNvcnMub3JnL21haWxtYW4vbGlzdGluZm8vbG0tc2Vuc29ycw=
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (14 preceding siblings ...)
2013-08-14 20:03 ` Guenter Roeck
@ 2013-08-14 20:45 ` Dev, Kapil
2013-08-14 22:39 ` Guenter Roeck
` (9 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Dev, Kapil @ 2013-08-14 20:45 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 8303 bytes --]
On Wed, Aug 14, 2013 at 4:03 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> On Wed, Aug 14, 2013 at 03:06:35PM -0400, Dev, Kapil wrote:
> > On Wed, Aug 14, 2013 at 2:29 PM, Guenter Roeck <linux@roeck-us.net>
> wrote:
> >
> > > On Wed, Aug 14, 2013 at 01:20:57PM -0400, Dev, Kapil wrote:
> > > > On Wed, Aug 14, 2013 at 1:30 AM, Guenter Roeck <linux@roeck-us.net>
> > > wrote:
> > > >
> > > > > On 08/13/2013 10:17 PM, Kapil Dev wrote:
> > > > >
> > > > >>
> > > > >> On Aug 14, 2013, at 12:56 AM, Guenter Roeck <linux@roeck-us.net>
> > > wrote:
> > > > >>
> > > > >> On 08/13/2013 08:09 PM, Dev, Kapil wrote:
> > > > >>>
> > > > >>>>
> > > > >>>>
> > > > >>>> On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <
> linux@roeck-us.net
> > > <mailto:
> > > > >>>> linux@roeck-us.net>> wrote:
> > > > >>>>
> > > > >>>> On 08/13/2013 07:41 PM, Dev, Kapil wrote:
> > > > >>>>
> > > > >>>> Thanks again Guenter!
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <
> > > > >>>> linux@roeck-us.net <mailto:linux@roeck-us.net> <mailto:
> > > > >>>> linux@roeck-us.net <mailto:linux@roeck-us.net>>> wrote:
> > > > >>>>
> > > > >>>> On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev,
> Kapil
> > > wrote:
> > > > >>>> > Thanks for the response Guenter!
> > > > >>>> >
> > > > >>>> > I put the system on load and I noticed their
> value
> > > > >>>> hardly changes. To my
> > > > >>>> > surprise, I ran a benchmark for 3 minutes and
> none
> > > of
> > > > >>>> temp* values changed
> > > > >>>> > during execution. The highest reported
> temperature
> > > is
> > > > >>>> always 48C.
> > > > >>>> >
> > > > >>>> > I was expecting that the internal temperature
> would
> > > > >>>> have "sensor = thermal
> > > > >>>> > diode" or "sensor = core" as a keyword. I
> thought
> > > > >>>> "sensor=thermistor" means
> > > > >>>> > the corresponding sensor is on the motherboard
> and
> > > not
> > > > >>>> the internal
> > > > >>>> > die-sensor.
> > > > >>>> >
> > > > >>>> Sure, but who knows if they put a sensor below the
> CPU
> > > for
> > > > >>>> some reason ...
> > > > >>>>
> > > > >>>> I am not familiar with the A10 CPUs. Are those
> similar
> > > to
> > > > >>>> K10 ?
> > > > >>>> If so, maybe the k10temp driver works or could be
> > > extended
> > > > >>>> to support it.
> > > > >>>> Can you give it a try ?
> > > > >>>>
> > > > >>>> If it does not work out of the box, can you send
> me the
> > > > >>>> output of "lspci -nn" ?
> > > > >>>>
> > > > >>>>
> > > > >>>> Kapil: I believe K10 corresponds to A8 seried, and A10
> has
> > > > >>>> Bulldozer architecture (http://www.cpu-world.com/__**
> > > > >>>> CPUs/Bulldozer/TYPE-A10-__**Series.html<
> > > http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html><
> > > > >>>>
> http://www.cpu-world.com/**CPUs/Bulldozer/TYPE-A10-**Series.html<
> > > http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>>).
> > > > >>>> I am not sure how different they are though. I tried K10, but it
> > > did not
> > > > >>>> work out of the box. I am looking into k10temp.c driver now.
> Also,I
> > > am
> > > > >>>> attaching the output of "lspci -nn" command herewith; you might
> > > have to
> > > > >>>> open it using wordpad for proper formatting..
> > > > >>>>
> > > > >>>>
> > > > >>>> Your lspci output includes
> > > > >>>>
> > > > >>>> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD]
> Device
> > > > >>>> [1022:1403]
> > > > >>>>
> > > > >>>> which is supported by the latest k10temp driver. Support was
> > > added
> > > > >>>> early last year.
> > > > >>>> What is your kernel version, and can you switch to a more
> recent
> > > > >>>> version ?
> > > > >>>>
> > > > >>>>
> > > > >>>> Kapil: I have 2.6.39-020639-generic kernel. Is it too old
> kernel for
> > > > >>>> k10temp driver to work? Which stable kernel should I upgrade to?
> > > > >>>>
> > > > >>>>
> > > > >>> You need 3.4 or later.
> > > > >>>
> > > > >>
> > > > >> Kapil: I was trying to avoid updating the kernel because my
> current
> > > > >> kernel is setup for running different type of benchmarks etc.
> Seems
> > > like I
> > > > >> can't avoid updating the kernel; I will do it..
> > > > >>
> > > > >> Alternative would be to back-port the k10temp driver from a later
> > > > > kernel. Then you can keep running the old one.
> > > > >
> > > > >
> > > > Kapil: Not sure how to do that. I am already taking the k10temp
> driver
> > > from
> > > > here: http://khali.linux-fr.org/devel/lm-sensors/drivers/k10temp/and
> > > > compiling and using it.
> > > >
> > > That version should already have support for your chip unless I am
> missing
> > > something. If you already use it, a newer kernel version will not help.
> > >
> > > Do you get any kernel log message when you try to load it ?
> > >
> >
> > Kapil: When I insert the module using: sudo insmod k10temp.ko, I don't
> get
> > any message on terminal. However, when I compile ktemp10.c file using
> make,
> > I get following warnings; I am not sure if they are acceptable.
> >
> ----------------------------------------------------------------------------
> > make[1]: Entering directory
> `/usr/src/linux-headers-2.6.39-020639-generic'
> > CC [M] /home/amd_a10/k10temp_driver/k10temp.o
> > /home//amd_a10/k10temp_driver/k10temp.c:232: warning: data definition has
> > no type or storage class
> > /home//amd_a10/k10temp_driver/k10temp.c:232: warning: type defaults to
> > ‘int’ in declaration of ‘module_pci_driver’
> > /home//amd_a10/k10temp_driver/k10temp.c:232: warning: parameter names
> > (without types) in function declaration
> > /home//amd_a10/k10temp_driver/k10temp.c:225: warning: ‘k10temp_driver’
> > defined but not used
> > Building modules, stage 2.
> > MODPOST 1 modules
> > CC /home/amd_a10/k10temp_driver/k10temp.mod.o
> > LD [M] /home/amd_a10/k10temp_driver/k10temp.ko
> > make[1]: Leaving directory `/usr/src/linux-headers-2.6.39-020639-generic'
> >
> There is no definition for module_pci_driver in your kernel,
> thus the initialization code won't run and the driver will
> not really be doing anything.
>
> You will have to replace
>
> module_pci_driver(k10temp_driver);
>
> with
>
> static int __init k10temp_init(void)
> {
> return pci_register_driver(&k10temp_driver);
> }
>
> static void __exit k10temp_exit(void)
> {
> pci_unregister_driver(&k10temp_driver);
> }
>
> module_init(k10temp_init)
> module_exit(k10temp_exit)
>
>
Kapil: After making above changes, I think it seems to work now. Now I am
getting following output from sensors:
f71869-isa-0e80
Adapter: ISA adapter
in0: +1.69 V
in1: +0.90 V
in2: +1.21 V
in3: +1.22 V
in4: +1.49 V
in5: +1.22 V
in6: +1.19 V
in7: +1.73 V
in8: +1.66 V
fan1: 2177 RPM
fan2: 0 RPM ALARM
fan3: 0 RPM ALARM
temp1: +24.0 C (high = +85.0 C, hyst = +81.0 C)
(crit = +100.0 C, hyst = +96.0 C) sensor = thermistor
temp2: +32.0 C (high = +85.0 C, hyst = +81.0 C)
(crit = +100.0 C, hyst = +96.0 C) sensor = thermistor
temp3: +48.0 C (high = +70.0 C, hyst = +68.0 C)
(crit = +85.0 C, hyst = +83.0 C) sensor = thermistor
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +4.5 C (high = +70.0 C, crit = +70.0 C)
I believe temp1 from PCI adapter denotes the core-temperature? But, it is
definitely off by 20-30C; its hard to believe that the temperature would be
4.5C under fan based cooling system. I ran a SPEC hmmer benchmark and
plotted the temperature over time. temp1 seems to change now. I am
attaching the plots herewith.
Please let me know if there is a way to calibrate the core-temperature.
Thanks a lot for your help!
Guenter
>
>
[-- Attachment #1.2: Type: text/html, Size: 12462 bytes --]
[-- Attachment #2: testTempSensor.pdf --]
[-- Type: application/pdf, Size: 4538 bytes --]
[-- Attachment #3: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (15 preceding siblings ...)
2013-08-14 20:45 ` Dev, Kapil
@ 2013-08-14 22:39 ` Guenter Roeck
2013-08-15 4:16 ` Dev, Kapil
` (8 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-14 22:39 UTC (permalink / raw)
To: lm-sensors
On Wed, Aug 14, 2013 at 04:45:43PM -0400, Dev, Kapil wrote:
[ ... ]
> Kapil: After making above changes, I think it seems to work now. Now I am
> getting following output from sensors:
> f71869-isa-0e80
> Adapter: ISA adapter
> in0: +1.69 V
> in1: +0.90 V
> in2: +1.21 V
> in3: +1.22 V
> in4: +1.49 V
> in5: +1.22 V
> in6: +1.19 V
> in7: +1.73 V
> in8: +1.66 V
> fan1: 2177 RPM
> fan2: 0 RPM ALARM
> fan3: 0 RPM ALARM
> temp1: +24.0 C (high = +85.0 C, hyst = +81.0 C)
> (crit = +100.0 C, hyst = +96.0 C) sensor = thermistor
> temp2: +32.0 C (high = +85.0 C, hyst = +81.0 C)
> (crit = +100.0 C, hyst = +96.0 C) sensor = thermistor
> temp3: +48.0 C (high = +70.0 C, hyst = +68.0 C)
> (crit = +85.0 C, hyst = +83.0 C) sensor = thermistor
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1: +4.5 C (high = +70.0 C, crit = +70.0 C)
>
> I believe temp1 from PCI adapter denotes the core-temperature? But, it is
Correct.
> definitely off by 20-30C; its hard to believe that the temperature would be
> 4.5C under fan based cooling system. I ran a SPEC hmmer benchmark and
> plotted the temperature over time. temp1 seems to change now. I am
> attaching the plots herewith.
>
Yes, that is pretty common with AMD chips.
> Please let me know if there is a way to calibrate the core-temperature.
>
Yes, you'll have to do it in /etc/sensors3.conf. Basically you'll have to
figure out what you think the real temperature is and add it to the raw
temperature provided by the driver.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (16 preceding siblings ...)
2013-08-14 22:39 ` Guenter Roeck
@ 2013-08-15 4:16 ` Dev, Kapil
2013-08-15 4:29 ` Guenter Roeck
` (7 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Dev, Kapil @ 2013-08-15 4:16 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 4460 bytes --]
Hi,
Sorry for the verbose email. I am trying to read the temperature value as
accurately as possible, that's why.
It is evident that there are some computations happening internally before
these values are reported. Here is what I have to say about the 4.5C
reported value.
I am using A10 5700 APU amd processor. It has bulldozer architecure (
http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html). Bulldozer
architecture corresponds to 15h micro-architecture family (
http://en.wikipedia.org/wiki/List_of_AMD_CPU_microarchitectures). So, I
looked at the official manual of 15h family
http://support.amd.com/us/Processor_TechDocs/42301_15h_Mod_00h-0Fh_BKDG.pdf).
And, I found the following:
Page 219 and 393 (figure-14) of the document mention that bits 31:21 (11
bits) of the register D18F3xA4 denote the current temperature of the die as
reported by temperature calculation circuit (TCC). The maximum value that
could be represented by 11 bits is 2048 (2047, but ignore this for now) and
they want to translate that to 256. So, I think the magic number 125 is
obtained by computing 256/2048*1000. Line number 66-68 in k10temp.c (as
downloaded from the drivers' link) use 125 as the factor to compute the
value to be reported. I guess the factor of 1000 would be taken care
somewhere else inside the kernel.
It also means that the lowest resolution of reading the temperature is
0.125C, which might mean that we could get a sub-degree resolution in
temperature reading?
I got a little confused about the way temperature-computation is explained
on page 393. The interpretation of D18F3xA4[31:21] seems to be different
based on the D18F3xA4[17:16] bits. Something similar, but not exactly the
same thing, is implemented in k10temp.c in lines 85-90. The value
(D18F3xA4[18:16]) is multiplied by 500 and then 52000 is added to it.
While, on page 393, I see <(CurTmp[10:2]*0.5)-49>. In line 89 of k10temp.c,
the hysteresis is computed as (D18F3xA4[27:24])*500, i.e. four bits are
used. While on page 393, three bits (equivalent to 0.125*8 = 1C) is used as
hysteresis. Am I understanding things correctly here?
Also, if I want to apply any further correction to the reported raw values,
I guess I just need to put following piece of code in /etc/sensors3.conf
file:
-------------------------------------------------------------
chip "k10temp-*"
compute temp1 (@+correction),(@-correction)
-------------------------------------------------------------
This should add correction to the temp1 value under PCI adapter alone and
not to the temp1 value under ISA adapter?
Thanks,
Kapil
On Wed, Aug 14, 2013 at 6:39 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> On Wed, Aug 14, 2013 at 04:45:43PM -0400, Dev, Kapil wrote:
>
> [ ... ]
>
> > Kapil: After making above changes, I think it seems to work now. Now I am
> > getting following output from sensors:
> > f71869-isa-0e80
> > Adapter: ISA adapter
> > in0: +1.69 V
> > in1: +0.90 V
> > in2: +1.21 V
> > in3: +1.22 V
> > in4: +1.49 V
> > in5: +1.22 V
> > in6: +1.19 V
> > in7: +1.73 V
> > in8: +1.66 V
> > fan1: 2177 RPM
> > fan2: 0 RPM ALARM
> > fan3: 0 RPM ALARM
> > temp1: +24.0 C (high = +85.0 C, hyst = +81.0 C)
> > (crit = +100.0 C, hyst = +96.0 C) sensor =
> thermistor
> > temp2: +32.0 C (high = +85.0 C, hyst = +81.0 C)
> > (crit = +100.0 C, hyst = +96.0 C) sensor =
> thermistor
> > temp3: +48.0 C (high = +70.0 C, hyst = +68.0 C)
> > (crit = +85.0 C, hyst = +83.0 C) sensor =
> thermistor
> >
> > k10temp-pci-00c3
> > Adapter: PCI adapter
> > temp1: +4.5 C (high = +70.0 C, crit = +70.0 C)
> >
> > I believe temp1 from PCI adapter denotes the core-temperature? But, it is
>
> Correct.
>
> > definitely off by 20-30C; its hard to believe that the temperature would
> be
> > 4.5C under fan based cooling system. I ran a SPEC hmmer benchmark and
> > plotted the temperature over time. temp1 seems to change now. I am
> > attaching the plots herewith.
> >
> Yes, that is pretty common with AMD chips.
>
> > Please let me know if there is a way to calibrate the core-temperature.
> >
> Yes, you'll have to do it in /etc/sensors3.conf. Basically you'll have to
> figure out what you think the real temperature is and add it to the raw
> temperature provided by the driver.
>
> Guenter
>
[-- Attachment #1.2: Type: text/html, Size: 5724 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (17 preceding siblings ...)
2013-08-15 4:16 ` Dev, Kapil
@ 2013-08-15 4:29 ` Guenter Roeck
2013-08-15 4:32 ` Dev, Kapil
` (6 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-15 4:29 UTC (permalink / raw)
To: lm-sensors
On 08/14/2013 09:16 PM, Dev, Kapil wrote:
> Hi,
>
> Sorry for the verbose email. I am trying to read the temperature value as accurately as possible, that's why.
>
> It is evident that there are some computations happening internally before these values are reported. Here is what I have to say about the 4.5C reported value.
>
> I am using A10 5700 APU amd processor. It has bulldozer architecure (http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html). Bulldozer architecture corresponds to 15h micro-architecture family (http://en.wikipedia.org/wiki/List_of_AMD_CPU_microarchitectures). So, I looked at the official manual of 15h family http://support.amd.com/us/Processor_TechDocs/42301_15h_Mod_00h-0Fh_BKDG.pdf). And, I found the following:
>
> Page 219 and 393 (figure-14) of the document mention that bits 31:21 (11 bits) of the register D18F3xA4 denote the current temperature of the die as reported by temperature calculation circuit (TCC). The maximum value that could be represented by 11 bits is 2048 (2047, but ignore this for now) and they want to translate that to 256. So, I think the magic number 125 is obtained by computing 256/2048*1000. Line number 66-68 in k10temp.c (as downloaded from the drivers' link) use 125 as the factor to compute the value to be reported. I guess the factor of 1000 would be taken care somewhere else inside the kernel.
>
The kernel reports the temperature to userland in milli-degrees Celsius.
> It also means that the lowest resolution of reading the temperature is 0.125C, which might mean that we could get a sub-degree resolution in temperature reading?
>
... which also answers this question.
> I got a little confused about the way temperature-computation is explained on page 393. The interpretation of D18F3xA4[31:21] seems to be different based on the D18F3xA4[17:16] bits. Something similar, but not exactly the same thing, is implemented in k10temp.c in lines 85-90. The value (D18F3xA4[18:16]) is multiplied by 500 and then 52000 is added to it. While, on page 393, I see <(CurTmp[10:2]*0.5)-49>. In line 89 of k10temp.c, the hysteresis is computed as (D18F3xA4[27:24])*500, i.e. four bits are used. While on page 393, three bits (equivalent to 0.125*8 = 1C) is used as hysteresis. Am I understanding things correctly here?
>
The 0.5 -> 500 is due to the conversion to milli-degrees.
Adding Clemens to the thread - maybe he can help with the rest. I am not really an expert on AMD CPUs.
> Also, if I want to apply any further correction to the reported raw values, I guess I just need to put following piece of code in /etc/sensors3.conf file:
>
> -------------------------------------------------------------
> chip "k10temp-*"
> compute temp1 (@+correction),(@-correction)
> -------------------------------------------------------------
>
> This should add correction to the temp1 value under PCI adapter alone and not to the temp1 value under ISA adapter?
>
Yes, something like that.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (18 preceding siblings ...)
2013-08-15 4:29 ` Guenter Roeck
@ 2013-08-15 4:32 ` Dev, Kapil
2013-08-15 5:30 ` Guenter Roeck
` (5 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Dev, Kapil @ 2013-08-15 4:32 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 3596 bytes --]
On Thu, Aug 15, 2013 at 12:29 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> On 08/14/2013 09:16 PM, Dev, Kapil wrote:
>
>> Hi,
>>
>> Sorry for the verbose email. I am trying to read the temperature value as
>> accurately as possible, that's why.
>>
>> It is evident that there are some computations happening internally
>> before these values are reported. Here is what I have to say about the 4.5C
>> reported value.
>>
>> I am using A10 5700 APU amd processor. It has bulldozer architecure (
>> http://www.cpu-world.com/**CPUs/Bulldozer/TYPE-A10-**Series.html<http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>).
>> Bulldozer architecture corresponds to 15h micro-architecture family (
>> http://en.wikipedia.org/wiki/**List_of_AMD_CPU_**microarchitectures<http://en.wikipedia.org/wiki/List_of_AMD_CPU_microarchitectures>).
>> So, I looked at the official manual of 15h family
>> http://support.amd.com/us/**Processor_TechDocs/42301_15h_**
>> Mod_00h-0Fh_BKDG.pdf<http://support.amd.com/us/Processor_TechDocs/42301_15h_Mod_00h-0Fh_BKDG.pdf>).
>> And, I found the following:
>>
>> Page 219 and 393 (figure-14) of the document mention that bits 31:21 (11
>> bits) of the register D18F3xA4 denote the current temperature of the die as
>> reported by temperature calculation circuit (TCC). The maximum value that
>> could be represented by 11 bits is 2048 (2047, but ignore this for now) and
>> they want to translate that to 256. So, I think the magic number 125 is
>> obtained by computing 256/2048*1000. Line number 66-68 in k10temp.c (as
>> downloaded from the drivers' link) use 125 as the factor to compute the
>> value to be reported. I guess the factor of 1000 would be taken care
>> somewhere else inside the kernel.
>>
>> The kernel reports the temperature to userland in milli-degrees Celsius.
>
>
> It also means that the lowest resolution of reading the temperature is
>> 0.125C, which might mean that we could get a sub-degree resolution in
>> temperature reading?
>>
>> ... which also answers this question.
Thanks! Does it mean that I can change the k10temp.c to read milli-degree
C. I have always seen integer readings.
>
>
> I got a little confused about the way temperature-computation is
>> explained on page 393. The interpretation of D18F3xA4[31:21] seems to be
>> different based on the D18F3xA4[17:16] bits. Something similar, but not
>> exactly the same thing, is implemented in k10temp.c in lines 85-90. The
>> value (D18F3xA4[18:16]) is multiplied by 500 and then 52000 is added to it.
>> While, on page 393, I see <(CurTmp[10:2]*0.5)-49>. In line 89 of k10temp.c,
>> the hysteresis is computed as (D18F3xA4[27:24])*500, i.e. four bits are
>> used. While on page 393, three bits (equivalent to 0.125*8 = 1C) is used as
>> hysteresis. Am I understanding things correctly here?
>>
>> The 0.5 -> 500 is due to the conversion to milli-degrees.
> Adding Clemens to the thread - maybe he can help with the rest. I am not
> really an expert on AMD CPUs.
>
>
> Also, if I want to apply any further correction to the reported raw
>> values, I guess I just need to put following piece of code in
>> /etc/sensors3.conf file:
>>
>> ------------------------------**------------------------------**-
>> chip "k10temp-*"
>> compute temp1 (@+correction),(@-correction)
>> ------------------------------**------------------------------**-
>>
>> This should add correction to the temp1 value under PCI adapter alone and
>> not to the temp1 value under ISA adapter?
>>
>> Yes, something like that.
Thanks for everything!
Regards,
Kapil
>
> Guenter
>
>
[-- Attachment #1.2: Type: text/html, Size: 4955 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (19 preceding siblings ...)
2013-08-15 4:32 ` Dev, Kapil
@ 2013-08-15 5:30 ` Guenter Roeck
2013-08-15 7:55 ` Clemens Ladisch
` (4 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Guenter Roeck @ 2013-08-15 5:30 UTC (permalink / raw)
To: lm-sensors
On 08/14/2013 09:32 PM, Dev, Kapil wrote:
>
>
> On Thu, Aug 15, 2013 at 12:29 AM, Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net>> wrote:
>
> On 08/14/2013 09:16 PM, Dev, Kapil wrote:
>
> Hi,
>
> Sorry for the verbose email. I am trying to read the temperature value as accurately as possible, that's why.
>
> It is evident that there are some computations happening internally before these values are reported. Here is what I have to say about the 4.5C reported value.
>
> I am using A10 5700 APU amd processor. It has bulldozer architecure (http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html <http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>). Bulldozer architecture corresponds to 15h micro-architecture family (http://en.wikipedia.org/wiki/__List_of_AMD_CPU___microarchitectures <http://en.wikipedia.org/wiki/List_of_AMD_CPU_microarchitectures>). So, I looked at the official manual of 15h family http://support.amd.com/us/__Processor_TechDocs/42301_15h___Mod_00h-0Fh_BKDG.pdf <http://support.amd.com/us/Processor_TechDocs/42301_15h_Mod_00h-0Fh_BKDG.pdf>). And, I found the following:
>
> Page 219 and 393 (figure-14) of the document mention that bits 31:21 (11 bits) of the register D18F3xA4 denote the current temperature of the die as reported by temperature calculation circuit (TCC). The maximum value that could be represented by 11 bits is 2048 (2047, but ignore this for now) and they want to translate that to 256. So, I think the magic number 125 is obtained by computing 256/2048*1000. Line number 66-68 in k10temp.c (as downloaded from the drivers' link) use 125 as the factor to compute the value to be reported. I guess the factor of 1000 would be taken care somewhere else inside the kernel.
>
> The kernel reports the temperature to userland in milli-degrees Celsius.
>
>
> It also means that the lowest resolution of reading the temperature is 0.125C, which might mean that we could get a sub-degree resolution in temperature reading?
>
> ... which also answers this question.
>
>
> Thanks! Does it mean that I can change the k10temp.c to read milli-degree C. I have always seen integer readings.
>
No. The value in the sysfs attribute file is already reported in milli-degrees C;
this is what the driver prints. The sensors command converts it into degrees C.
If the sensors command reports 4.5 degrees C, the sysfs attribute value is 4500.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (20 preceding siblings ...)
2013-08-15 5:30 ` Guenter Roeck
@ 2013-08-15 7:55 ` Clemens Ladisch
2013-08-16 3:48 ` Dev, Kapil
` (3 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Clemens Ladisch @ 2013-08-15 7:55 UTC (permalink / raw)
To: lm-sensors
> On 08/14/2013 09:16 PM, Dev, Kapil wrote:
>> I got a little confused about the way temperature-computation is
>> explained on page 393. The interpretation of D18F3xA4[31:21] seems to
>> be different based on the D18F3xA4[17:16] bits.
These two bits should always be 00; Linux never tries to write the
temperature value.
>> Something similar, but not exactly the same thing, is implemented in
>> k10temp.c in lines 85-90. The value (D18F3xA4[18:16])
No, this value is D18F3x64[22:16].
>> is multiplied by 500 and then 52000 is added to it. While, on page
>> 393, I see <(CurTmp[10:2]*0.5)-49>.
On page 382, I see <(HtcTmpLmt*0.5)+52>.
Regards,
Clemens
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (21 preceding siblings ...)
2013-08-15 7:55 ` Clemens Ladisch
@ 2013-08-16 3:48 ` Dev, Kapil
2013-08-16 7:03 ` Clemens Ladisch
` (2 subsequent siblings)
25 siblings, 0 replies; 27+ messages in thread
From: Dev, Kapil @ 2013-08-16 3:48 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 2447 bytes --]
Thanks Clemens!
On Thu, Aug 15, 2013 at 3:55 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
> > On 08/14/2013 09:16 PM, Dev, Kapil wrote:
> >> I got a little confused about the way temperature-computation is
> >> explained on page 393. The interpretation of D18F3xA4[31:21] seems to
> >> be different based on the D18F3xA4[17:16] bits.
>
> These two bits should always be 00; Linux never tries to write the
> temperature value.
>
I see. It means that D18F3xA4[31:21] always denotes the Tctl temperature
(control temperature). Where, Tctl <= Tmeasured <= Tctl+TmpMaxDiffUp. The
value of TmpMaxDiffUp is between 0 and 9C depending on the value of two
bits, D18F3xA4[6:5]. Should I check the value of these two bits, or did you
already figure that out? So, line 68 is really what I should worry about:
return sprintf(buf, "%u\n", (regval >> 21) * 125);
I installed ubuntu 12.04.02 LTS on another hard-disk and installed
lm-sensors on that. I did not install the driver from
http://khali.linux-fr.org/devel/lm-sensors/drivers/k10temp/k10temp.c manually,
because it was already installed in the kernel. I noticed, that the
reported temperature was very erratic, changing anywhere between 3 C and
30C, even when there was no workload running on the cpu.
>> Something similar, but not exactly the same thing, is implemented in
> >> k10temp.c in lines 85-90. The value (D18F3xA4[18:16])
>
> No, this value is D18F3x64[22:16].
>
Sorry, it was a typo from my side. If I understand it correctly, the
implementation is such that it reports following values:
1) Highest temperature = 70; due to "return sprintf(buf, "%d\n", 70 * 1000
in c-code);"
2) Critical temperature = mostly 70; due to D18F3x64[22:16]*0.5+52 (value =
((regval >> 16) & 0x7f) * 500 + 52000; in c-code), which kind of means
that D18F3x64[22:16]
is mostly fixed to 36?
3) Hysteresis value: From D18F3x64[22:16]*0.5+52 -
D18F3x64[22:16]*0.5 (value
-= ((regval >> 24) & 0xf) * 500; in c-code). Is the value of D18F3x64[22:16]
fixed or it changes based on some condition?
>
> >> is multiplied by 500 and then 52000 is added to it. While, on page
> >> 393, I see <(CurTmp[10:2]*0.5)-49>.
>
> On page 382, I see <(HtcTmpLmt*0.5)+52>.
>
>
Again, thanks a lot! As I said, I am trying to compute the temperature
values as accurately as possible because my project involves calibrating
the die-temperature values against other measurements
Regards,
Kapil
>
> Regards,
> Clemens
>
[-- Attachment #1.2: Type: text/html, Size: 3860 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (22 preceding siblings ...)
2013-08-16 3:48 ` Dev, Kapil
@ 2013-08-16 7:03 ` Clemens Ladisch
2013-08-16 8:57 ` Kapil Dev
2013-08-16 9:27 ` Clemens Ladisch
25 siblings, 0 replies; 27+ messages in thread
From: Clemens Ladisch @ 2013-08-16 7:03 UTC (permalink / raw)
To: lm-sensors
Dev, Kapil wrote:
> On Thu, Aug 15, 2013 at 3:55 AM, Clemens Ladisch wrote:
>> On 08/14/2013 09:16 PM, Dev, Kapil wrote:
>>> I got a little confused about the way temperature-computation is
>>> explained on page 393. The interpretation of D18F3xA4[31:21] seems to
>>> be different based on the D18F3xA4[17:16] bits.
>>
>> These two bits should always be 00; Linux never tries to write the
>> temperature value.
>
> I see. It means that D18F3xA4[31:21] always denotes the Tctl
> temperature (control temperature). Where, Tctl <= Tmeasured <> Tctl+TmpMaxDiffUp.
All four fields in bits 0..12 can make the shown temperature value
slightly out of date. This is intentional to smooth out the
measurements.
> The value of TmpMaxDiffUp is between 0 and 9C
No, it is between 0 and 9.
> depending on the value of two bits, D18F3xA4[6:5]. Should I check the
> value of these two bits
Over time, the average value should be accurate.
> I noticed, that the reported temperature was very erratic, changing
> anywhere between 3 C and 30C,
No, between 3 and 30.
> even when there was no workload running on the cpu.
When the CPU is mostly idle, even small wakeups for interrupts will
result in rather large relative changes in power consumption and,
therefore, power dissipation.
> If I understand it correctly, the implementation is such that it
> reports following values:
> 1) Highest temperature = 70
This is not the highest possible value; temp1_max is the highest value
during normal operation. On AMD CPUs, this is the point at which the
CPU fan should run at 100 % (of TDP).
> 2) Critical temperature = mostly 70; [...] which kind of means that
> D18F3x64[22:16] is mostly fixed to 36?
This register has whatever value the BIOS has written into it.
> 3) Hysteresis value: [...] Is the value of D18F3x64[22:16] fixed or
> it changes based on some condition?
It changes when the BIOS (or somebody else) writes to it.
> I am trying to compute the temperature values as accurately as
> possible because my project involves calibrating the die-temperature
> values against other measurements
Did you read section 2.11.1? It says:
| Tctl does not represent a temperature which could be measured on the
| die or the case of the processor. Instead, it specifies the processor
| temperature relative to the maximum operating temperature
The maximum operating temperature is defined as 70, but does not
correspond to a known absolute temperature.
This temperature sensor is designed to control the CPU fan; it is _not_
intended to result in a value that can be shown to the user in a way
that makes much sense.
Regards,
Clemens
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (23 preceding siblings ...)
2013-08-16 7:03 ` Clemens Ladisch
@ 2013-08-16 8:57 ` Kapil Dev
2013-08-16 9:27 ` Clemens Ladisch
25 siblings, 0 replies; 27+ messages in thread
From: Kapil Dev @ 2013-08-16 8:57 UTC (permalink / raw)
To: lm-sensors
On Aug 16, 2013, at 3:03 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
Thanks Clemens!
Seems like, there is big gap in my understanding.
> Dev, Kapil wrote:
>> On Thu, Aug 15, 2013 at 3:55 AM, Clemens Ladisch wrote:
>>> On 08/14/2013 09:16 PM, Dev, Kapil wrote:
>>>> I got a little confused about the way temperature-computation is
>>>> explained on page 393. The interpretation of D18F3xA4[31:21] seems to
>>>> be different based on the D18F3xA4[17:16] bits.
>>>
>>> These two bits should always be 00; Linux never tries to write the
>>> temperature value.
>>
>> I see. It means that D18F3xA4[31:21] always denotes the Tctl
>> temperature (control temperature). Where, Tctl <= Tmeasured <>> Tctl+TmpMaxDiffUp.
>
> All four fields in bits 0..12 can make the shown temperature value
> slightly out of date. This is intentional to smooth out the
> measurements.
>
>> The value of TmpMaxDiffUp is between 0 and 9C
>
> No, it is between 0 and 9.
>
>> depending on the value of two bits, D18F3xA4[6:5]. Should I check the
>> value of these two bits
>
> Over time, the average value should be accurate.
>
>> I noticed, that the reported temperature was very erratic, changing
>> anywhere between 3 C and 30C,
>
> No, between 3 and 30.
>
>> even when there was no workload running on the cpu.
>
> When the CPU is mostly idle, even small wakeups for interrupts will
> result in rather large relative changes in power consumption and,
> therefore, power dissipation.
>
>> If I understand it correctly, the implementation is such that it
>> reports following values:
>> 1) Highest temperature = 70
>
> This is not the highest possible value; temp1_max is the highest value
> during normal operation. On AMD CPUs, this is the point at which the
> CPU fan should run at 100 % (of TDP).
>
>> 2) Critical temperature = mostly 70; [...] which kind of means that
>> D18F3x64[22:16] is mostly fixed to 36?
>
> This register has whatever value the BIOS has written into it.
>
>> 3) Hysteresis value: [...] Is the value of D18F3x64[22:16] fixed or
>> it changes based on some condition?
>
> It changes when the BIOS (or somebody else) writes to it.
>
>> I am trying to compute the temperature values as accurately as
>> possible because my project involves calibrating the die-temperature
>> values against other measurements
>
> Did you read section 2.11.1? It says:
> | Tctl does not represent a temperature which could be measured on the
> | die or the case of the processor. Instead, it specifies the processor
> | temperature relative to the maximum operating temperature
>
> The maximum operating temperature is defined as 70, but does not
> correspond to a known absolute temperature.
>
> This temperature sensor is designed to control the CPU fan; it is _not_
> intended to result in a value that can be shown to the user in a way
> that makes much sense.
>
Yes, I read it and I understood it in a way that Tctl is changed dynamically to track Tmeasured. Although, the scale of Tctl is weird, but I still thought these final values were still in degree C. I think that you are saying that the units of final reported values are not deg-C. I will read the document again, more carefully this time.
I had following understanding:
Based on page 220, fig-14, max operating T and Tctl_max are the same. Also, the temperature of the part is [Tctl_max - Tctl] below the max operating T, which is the same as Tctl_max. So, it kind of means that Tctl itself is the temperature of the part (without the slew-rate control). Thats why I assumed that TmpMaxDiffUp was between 0C and 9C because I assumed that Tctl had units of degree C. I thought that when they say the temperature of the part or measured temperature, they mean the die-tmperature coming through temperature calculation circuit (TCC). But, it seems like thats the wrong understanding.
Little bit detail of what I intend to do:
I have a high-end IR camera which I use to take real-time high resolution image of the processor. Unfortunately, I need to calibrate the camera itself against true temperature. I need two temperature-points at which the temperature reported by the sensor is correct; using those two points, I might be able to calibrate the camera in the entire range and could potentially figure out the discrepancy in reported temperature at every other temperature reading. I am not sure if I am clear; if not, please let me know.
Also, I have come to know that these sensors are more accurate at higher temperature; but, this information is not sufficient enough. I am looking for those temperature values at which the reported value is the same as the absolute temperature of the die. I thought this value is 70C for AMD processor. If those values are high, I could achieve them by controlling the cooling of the processor. In my experiments, I remove the fan and use liquid cooling with controlled fluid-temperature.
Regards,
Kapil
>
> Regards,
> Clemens
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread* Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
` (24 preceding siblings ...)
2013-08-16 8:57 ` Kapil Dev
@ 2013-08-16 9:27 ` Clemens Ladisch
25 siblings, 0 replies; 27+ messages in thread
From: Clemens Ladisch @ 2013-08-16 9:27 UTC (permalink / raw)
To: lm-sensors
Kapil Dev wrote:
> I think that you are saying that the units of final reported values
> are not deg-C.
Indeed they are not. The final reported values do not have any unit.
The only known facts about the scale of these temperate values are:
1) Higher values corresponds to higher temperatures; and
2) at a value of 70, a fan designed for TDP must run at 100 %.
> I need to calibrate the camera itself against true temperature.
This is not possible with the CPU sensor.
Regards,
Clemens
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 27+ messages in thread