with darktable
$ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1: +66.0°C
it8718-isa-0228
Adapter: ISA adapter
in0: +1.47 V (min = +0.00 V, max = +4.08 V)
in1: +1.95 V (min = +0.00 V, max = +4.08 V)
in2: +3.17 V (min = +0.00 V, max = +4.08 V)
+5V: +3.01 V (min = +0.00 V, max = +4.08 V)
in4: +3.10 V (min = +0.00 V, max = +4.08 V)
in5: +3.17 V (min = +0.00 V, max = +4.08 V)
in6: +4.08 V (min = +0.00 V, max = +4.08 V)
in7: +2.94 V (min = +0.00 V, max = +4.08 V)
Vbat: +3.17 V
fan1: 2947 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
temp1: +40.0°C (low = +127.0°C, high = +127.0°C) sensor =
thermistor
temp2: +49.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal
diode
temp3: +51.0°C (low = +127.0°C, high = +127.0°C) sensor =
thermistor
cpu0_vid: +1.050 V
intrusion0: ALARM
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +46.9°C (high = +70.0°C)
(crit = +72.0°C, hyst = +70.0°C)
(shut down darktable:
$ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1: +67.0°C
it8718-isa-0228
Adapter: ISA adapter
in0: +1.28 V (min = +0.00 V, max = +4.08 V)
in1: +1.95 V (min = +0.00 V, max = +4.08 V)
in2: +3.17 V (min = +0.00 V, max = +4.08 V)
+5V: +3.01 V (min = +0.00 V, max = +4.08 V)
in4: +3.10 V (min = +0.00 V, max = +4.08 V)
in5: +3.17 V (min = +0.00 V, max = +4.08 V)
in6: +4.08 V (min = +0.00 V, max = +4.08 V)
in7: +2.50 V (min = +0.00 V, max = +4.08 V)
Vbat: +3.17 V
fan1: 2947 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
temp1: +39.0°C (low = +127.0°C, high = +127.0°C) sensor =
thermistor
temp2: +48.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal
diode
temp3: +51.0°C (low = +127.0°C, high = +127.0°C) sensor =
thermistor
cpu0_vid: +1.050 V
intrusion0: ALARM
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +48.4°C (high = +70.0°C)
(crit = +72.0°C, hyst = +70.0°C)
what makes me wonder is intrusion detection... however from my web search
of it there appears to be no cause for alarm.
I looked at this before and am wondering how to get the AMD CPU readings to
display. My search for a solution yielded no results and was hoping that
someone out there knows of a way.
On Mon, Nov 13, 2017 at 6:32 AM, Romano Giannetti <[email protected]>
wrote:
> On 13/11/17 10:42, Tobias Ellinghaus wrote:
>
>> Am Sonntag, 12. November 2017, 20:11:41 CET schrieb Michael:
>>
>>> Hello ladies and gentleman. Well darktable seems to be causing my system
>>> to
>>> reboot and on a rare occasion to crash. I think it is the video card (it
>>>
>> Did you have a look in your system logs? Maybe the kernel had a chance to
>> put
>> something there before it went south.
>>
>> Tobias
>>
>
> Another thing you can try is to monitor the temperature of the graphic
> card while using DT. In my laptop, out of the box, more than 1 minutes of
> GPU at full power will cause a thermal shutdown. Commented here:
> https://askubuntu.com/a/683883/16395
>
> HTH,
>
> Romano
>
> --
> --
> Romano Giannetti
> http://www.rgtti.com/
>
>
> ____________________________________________________________
> ________________
> darktable user mailing list
> to unsubscribe send a mail to darktable-user+unsubscribe@lis
> ts.darktable.org
>
>
--
:-)~MIKE~(-:
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
