Sorry to say but yes it is.

 $ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             AuthenticAMD
CPU family:            16
Model:                 5
Model name:            AMD Athlon(tm) II X4 620 Processor
Stepping:              2
CPU MHz:               1400.000
CPU max MHz:           2600.0000
CPU min MHz:           800.0000
BogoMIPS:              5223.39
Virtualization:        AMD-V
L1d cache:             64K
L1i cache:             64K
L2 cache:              512K
NUMA node0 CPU(s):     0-3
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save

After looking further into this I found something <below>. Do you think I should compile it?
DateFri, 20 Nov 2009 09:15:23 +0100
FromClemens Ladisch <>
Subject[PATCH] k10temp: temperature sensor for AMD Family 10h/11h CPUs
This adds a driver for the internal temperature sensor of AMD Family 10h
and 11h CPUs.

Signed-off-by: Clemens Ladisch <clemens@ladisch.de>
---
Documentation/hwmon/k10temp | 54 +++++++++++++++++
drivers/hwmon/Kconfig | 12 +++
drivers/hwmon/Makefile | 1
drivers/hwmon/k10temp.c | 135 ++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 202 insertions(+)

--- /dev/null
+++ linux-2.6/Documentation/hwmon/k10temp
@@ -0,0 +1,54 @@
+Kernel driver k10temp
+=====================
+
+Supported chips:
+* AMD Family 10h processors:
+ Socket F: Quad-Core/Six-Core/Embedded AMD Opteron
+ Socket AM2+: Phenom II X3/X4
+ Socket AM3: Quad-Core Opteron, Athlon/Phenom II X2/X3/X4, Sempron II
+ mobile: Athlon II, Sempron, Turion II
+
+ Prefix: 'k10temp'
+ Addresses scanned: PCI space
+ Datasheets: see http://developer.amd.com/documentation/guides/
+ #31116: BIOS and Kernel Developer's Guide For AMD Family 10h Processors
+ #41322: Revision Guide for AMD Family 10h Processors
+
+* AMD Family 11h processors:
+ mobile: Athlon (X2), Sempron (X2), Turion X2 (Ultra)
+
+ Prefix: 'k10temp'
+ Addresses scanned: PCI space
+ Datasheets: see http://developer.amd.com/documentation/guides/
+ #41256: BIOS and Kernel Developer's Guide For AMD Family 11h Processors
+ #41788: Revision Guide for AMD Family 11h Processors
+
+Author: Clemens Ladisch <clemens@ladisch.de>
+
+Description
+-----------
+
+This driver permits reading of the internal temperature sensor of AMD
+Family 10h and 11h processors.
+
+All these processors have a sensor, but on older revisions of Family 10h
+processors, the sensor returns inconsistent values (erratum 319). The driver
+refuses to load with these revisions (DR-BA, DR-B2, DR-B3: some Embedded
+Opterons on Socket F; and Quad-Core Opteron, Phenom Triple/Quad-Core, and
+Athon Dual-Core on Socket AM2+). All later revisions (RB-C2, BL-C2, DA-C2,
+RB-C3, HY-D0) work fine; see the list above.
+
+There is one temperature value, available as temp1_input in sysfs. It is
+measured in degrees Celsius with a resolution of 1/8th degree. Please note
+that it is defined as a relative value; to quote the AMD manual:
+
+ Tctl is the processor temperatur control value, used by the platform to
+ control cooling systems. Tctl is a non-physical temperature on an arbitrary
+ scale measured in degrees. It does _not_ represent an actual physical
+ temperature like die or case temperature. Instead, it specifies the
+ processor temperature relative to the point at which the system must supply
+ the maximum cooling for the processor's specified maximum case temperature
+ and maximum thermal power dissipation.
+
+The maximum value for Tctl is usually defined as 70 degrees, so, as a rule of
+thumb, this value should not exceed 60 degrees.
--- linux-2.6/drivers/hwmon/Kconfig
+++ linux-2.6/drivers/hwmon/Kconfig
@@ -222,6 +222,18 @@ config SENSORS_K8TEMP
This driver can also be built as a module. If so, the module
will be called k8temp.

+config SENSORS_K10TEMP
+ tristate "AMD Phenom/Sempron/Turion/Opteron temperature sensor"
+ depends on X86 && PCI
+ help
+ If you say yes here you get support for the temperature
+ sensor inside your CPU. Supported are later revisions of
+ the AMD Family 10h and all revisions of the AMD Family 11h
+ microarchitectures.
+
+ This driver can also be built as a module. If so, the module
+ will be called k10temp.
+
config SENSORS_AMS
tristate "Apple Motion Sensor driver"
depends on PPC_PMAC && !PPC64 && INPUT && ((ADB_PMU && I2C = y) || (ADB_PMU && !I2C) || I2C) && EXPERIMENTAL
--- linux-2.6/drivers/hwmon/Makefile
+++ linux-2.6/drivers/hwmon/Makefile
@@ -53,6 +53,7 @@ obj-$(CONFIG_SENSORS_IBMAEM) += ibmaem.o
obj-$(CONFIG_SENSORS_IBMPEX) += ibmpex.o
obj-$(CONFIG_SENSORS_IT87) += it87.o
obj-$(CONFIG_SENSORS_K8TEMP) += k8temp.o
+obj-$(CONFIG_SENSORS_K10TEMP) += k10temp.o
obj-$(CONFIG_SENSORS_LIS3LV02D) += lis3lv02d.o hp_accel.o
obj-$(CONFIG_SENSORS_LIS3_SPI) += lis3lv02d.o lis3lv02d_spi.o
obj-$(CONFIG_SENSORS_LM63) += lm63.o
--- /dev/null
+++ linux-2.6/drivers/hwmon/k10temp.c
@@ -0,0 +1,135 @@
+/*
+ * k10temp.c - AMD Family 10h/11h CPUs hardware monitoring
+ *
+ * Copyright (c) 2009 Clemens Ladisch <clemens@ladisch.de>
+ *
+ *
+ * This driver is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License; either
+ * version 2 of the License, or (at your option) any later version.
+ *
+ * This driver is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+ * See the GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this driver; if not, see <http://www.gnu.org/licenses/>.
+ */
+
+#include <linux/err.h>
+#include <linux/hwmon.h>
+#include <linux/hwmon-sysfs.h>
+#include <linux/init.h>
+#include <linux/module.h>
+#include <linux/pci.h>
+#include <asm/processor.h>
+
+MODULE_DESCRIPTION("AMD Family 10h/11h CPU core temperature monitor");
+MODULE_AUTHOR("Clemens Ladisch <clemens@ladisch.de>");
+MODULE_LICENSE("GPL");
+
+#define REG_REPORTED_TEMPERATURE 0xa4
+#define CURTMP_TO_MILLIDEGREES(regval) (((regval) >> 21) * 125)
+
+static ssize_t show_temp(struct device *dev,
+ struct device_attribute *attr, char *buf)
+{
+ u32 regval;
+
+ pci_read_config_dword(to_pci_dev(dev),
+ REG_REPORTED_TEMPERATURE, &regval);
+ return sprintf(buf, "%u\n", CURTMP_TO_MILLIDEGREES(regval));
+}
+
+static ssize_t show_name(struct device *dev,
+ struct device_attribute *attr, char *buf)
+{
+ return sprintf(buf, "k10temp\n");
+}
+
+static SENSOR_DEVICE_ATTR(temp1_input, S_IRUGO, show_temp, NULL, 0);
+static DEVICE_ATTR(name, S_IRUGO, show_name, NULL);
+
+static bool __devinit has_erratum_319(void)
+{
+ /*
+ * Erratum 319: The thermal sensor of older Family 10h processors
+ * (B steppings) is unreliable.
+ */
+ return boot_cpu_data.x86 == 0x10 && boot_cpu_data.x86_model <= 2;
+}
+
+static int __devinit k10temp_probe(struct pci_dev *pdev,
+ const struct pci_device_id *id)
+{
+ struct device *hwmon_dev;
+ int err;
+
+ if (has_erratum_319()) {
+ dev_err(&pdev->dev,
+ "unreliable CPU thermal sensor; monitoring disabled\n");
+ err = -ENODEV;
+ goto exit;
+ }
+
+ err = device_create_file(&pdev->dev,
+ &sensor_dev_attr_temp1_input.dev_attr);
+ if (err)
+ goto exit;
+
+ err = device_create_file(&pdev->dev, &dev_attr_name);
+ if (err)
+ goto exit_remove1;
+
+ hwmon_dev = hwmon_device_register(&pdev->dev);
+ if (IS_ERR(hwmon_dev)) {
+ err = PTR_ERR(hwmon_dev);
+ goto exit_remove2;
+ }
+
+ dev_set_drvdata(&pdev->dev, hwmon_dev);
+ return 0;
+
+exit_remove2:
+ device_remove_file(&pdev->dev, &dev_attr_name);
+exit_remove1:
+ device_remove_file(&pdev->dev, &sensor_dev_attr_temp1_input.dev_attr);
+exit:
+ return err;
+}
+
+static void __devexit k10temp_remove(struct pci_dev *pdev)
+{
+ hwmon_device_unregister(dev_get_drvdata(&pdev->dev));
+ device_remove_file(&pdev->dev, &dev_attr_name);
+ device_remove_file(&pdev->dev, &sensor_dev_attr_temp1_input.dev_attr);
+ dev_set_drvdata(&pdev->dev, NULL);
+}
+
+static struct pci_device_id k10temp_id_table[] = {
+ { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_10H_NB_MISC) },
+ { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_11H_NB_MISC) },
+ {}
+};
+MODULE_DEVICE_TABLE(pci, k10temp_id_table);
+
+static struct pci_driver k10temp_driver = {
+ .name = "k10temp",
+ .id_table = k10temp_id_table,
+ .probe = k10temp_probe,
+ .remove = __devexit_p(k10temp_remove),
+};
+
+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)



On Mon, Oct 30, 2017 at 10:44 PM, Brien Dieterle <briend@gmail.com> wrote:
By the way, do you have an AMD cpu?  The sensors output does not seem to include the CPU, and I read it is hard to get them from AMD cpus.  So, your numbers might be a lot higher than what you see there.

On Mon, Oct 30, 2017 at 7:01 PM, Michael <bmike1@gmail.com> wrote:
I'm going to run the gl test and run audio at the same time. That should make it crash sooner and the audio will  also make it not go to sleep.... While i sleep.

On Mon, Oct 30, 2017 at 9:48 PM, Michael <bmike1@gmail.com> wrote:
i'm trying to recreate the crash to make sure I didn't copy and paste the stress command with a blank space in it (which would cause the command to execute).

On Mon, Oct 30, 2017 at 9:29 PM, Michael <bmike1@gmail.com> wrote:
I think glmark2 crashed it just crashed it after about 2 hours



On Mon, Oct 30, 2017 at 9:19 PM, Michael <bmike1@gmail.com> wrote:
final reading:
$ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +53.8°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

editors note: the computer has 2 venting areas with fans. I just took the side panel of and am going to run the computer without it. The new reading since doing that about 3 minutes ago is:

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +72.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +49.5°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +73.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +50.0°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +73.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +49.9°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +72.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +53.0°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +71.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +53.0°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +70.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +52.2°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +70.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.5°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +72.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.0°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +72.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +50.0°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +73.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +50.5°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +72.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +49.5°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

Not bad.... about a 2C drop

Now we crash it!
See you on the other side!

On Mon, Oct 30, 2017 at 8:35 PM, Michael <bmike1@gmail.com> wrote:
'coo' is supposed to read 'cool' as in not shorts temperature

On Mon, Oct 30, 2017 at 8:33 PM, Michael <bmike1@gmail.com> wrote:
I'm just about to take a reading and then run stress again. It is pretty coo, in here so not sure if a fan would do any good.
 $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +74.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.6°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

want me to crash it now?


On Mon, Oct 30, 2017 at 8:30 PM, Brien Dieterle <briend@gmail.com> wrote:
Well, those temperatures are not that hot, but that doesn't mean some cooling wouldn't improve things.
Have you popped the case off and pointed a big fan in there and tried to reproduce the crash yet?

On Mon, Oct 30, 2017 at 5:21 PM, Michael <bmike1@gmail.com> wrote:
Here is around 180 seconds of readings at around 10 second intervals (if it helps):

 $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +74.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.5°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.0°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.0°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.4°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.2°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.0°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.5°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +50.9°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +53.6°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +52.4°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.8°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +74.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.1°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +74.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.0°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +74.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +52.0°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +74.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +50.6°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +74.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.4°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.8°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)

bmike1@MikesBeast ~ $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +75.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.9°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)


On Mon, Oct 30, 2017 at 7:39 PM, Brien Dieterle <briend@gmail.com> wrote:
30 mins is plenty for a test.  Try to get sensors output just before a crash

On Mon, Oct 30, 2017 at 4:25 PM, Michael <bmike1@gmail.com> wrote:
how long do you want me to run glmark2 for? Forever is not feasible!

On Mon, Oct 30, 2017 at 7:22 PM, Michael <bmike1@gmail.com> wrote:
as for the shutoff point everything that had anything to do with cutting power was already diabled

On Mon, Oct 30, 2017 at 7:20 PM, Michael <bmike1@gmail.com> wrote:
 $ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +68.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +45.1°C  (high = +70.0°C)
                       (crit = +72.0°C, hyst = +70.0°C)


On Mon, Oct 30, 2017 at 7:07 PM, Brien Dieterle <briend@gmail.com> wrote:
Well, it might be protecting your computer but if it is too low it will just be annoying.
You still need to run sensors and get those numbers if you haven't yet:


If your machine is legitimately overheating you need to address that with fans and ventilation, etc.

On Mon, Oct 30, 2017 at 3:59 PM, Michael <bmike1@gmail.com> wrote:
if there is a shutoff point you did say disable it?


On Mon, Oct 30, 2017 at 6:56 PM, Brien Dieterle <briend@gmail.com> wrote:
Well, you're on the right track.  Try to isolate whether glmark alone can crash it, or if you need stress as well.   Then try opening up your case and point a fan in there.
Also don't forget to check the BIOS for thermal management events that might be causing the shutdown/reboot.

On Mon, Oct 30, 2017 at 3:52 PM, Michael <bmike1@gmail.com> wrote:
never mind..... I ran glmark around 5 minutes and then stress. that crashed the machine! Not a nice reboot (like what it does with dt) but a power failure outage,

On Mon, Oct 30, 2017 at 6:41 PM, Michael <bmike1@gmail.com> wrote:
and if glmark2 doesn't crash it run stress the same amount of time?

On Mon, Oct 30, 2017 at 6:37 PM, Michael <bmike1@gmail.com> wrote:
how long do I let glmark2's pretty horse rotate?


On Mon, Oct 30, 2017 at 6:36 PM, Michael <bmike1@gmail.com> wrote:
okay
`

On Mon, Oct 30, 2017 at 6:10 PM, Brien Dieterle <briend@gmail.com> wrote:
I'd wait.   If stress alone doesn't crash, run glmark2 by itself.  If glmark2 doesn't crash, run them both at the same time.


On Mon, Oct 30, 2017 at 3:01 PM, Michael <bmike1@gmail.com> wrote:
run this now or after stress completes?
?

On Mon, Oct 30, 2017 at 5:59 PM, Brien Dieterle <briend@gmail.com> wrote:
Well, not yet ;-).   If it doesn't crash, you might need to stress the graphics card as well with one of these tools:

https://www.pcsuggest.com/gpu-benchmarking-and-stress-testing-in-linux/

So maybe kick off both stress and
glmark2 --run-forever

On Mon, Oct 30, 2017 at 2:55 PM, Michael <bmike1@gmail.com> wrote:
if it doesn't crash I'll start hounding the darktable forums.

On Mon, Oct 30, 2017 at 5:45 PM, Michael <bmike1@gmail.com> wrote:
Just started..... lets see what happens

On Mon, Oct 30, 2017 at 5:36 PM, Brien Dieterle <briend@gmail.com> wrote:
Forget darktable for now.  Did you run stress test for more than 10 seconds?

This will run a stress test for 30 minutes:

stress --cpu 8 --io 4 --vm 2  --hdd 2 --timeout 1800s

If you can get it to crash with just this stress program, then it has nothing to do with darktable


On Mon, Oct 30, 2017 at 2:24 PM, Michael <bmike1@gmail.com> wrote:
I have no sensors running and as for it panicing when warm sometimes it panics after I run dt 2 minutes after it had been shut down an hour  and doesn't panic even though dt had run10 minutes.

On Mon, Oct 30, 2017 at 4:31 PM, Brien Dieterle <briend@gmail.com> wrote:
Check your bios settings for hardware monitoring and temperature limits.  You may have it set with a maximum temperature so the machine panics when it's just warm.

Try raising this number or disabling the feature entirely

But first check your sensors by installing a temperature monitoring program

On Oct 30, 2017 1:04 PM, "Michael" <bmike1@gmail.com> wrote:
it is sooo ify! I just ran it for like 10 minutes with no crashes whereas before I had just started the computer and ran dt for 2 minutes and it crashed. Then I restarted and I had a repeat performance of the 2 minute thing.

On Mon, Oct 30, 2017 at 3:38 PM, Michael <bmike1@gmail.com> wrote:
 $ stress --cpu 8 --io 4 --vm 2 --vm-bytes 128M --timeout 10s
stress: info: [7571] dispatching hogs: 8 cpu, 4 io, 2 vm, 0 hdd
stress: info: [7571] successful run completed in 10s

 I don't know what that was suppossed to tell me but there it is.

On Mon, Oct 30, 2017 at 3:36 PM, Michael <bmike1@gmail.com> wrote:
I am experiencing no slowness. It is like the days where you had a power switch on the back of your computer... or it is like a hard reboot.

On Mon, Oct 30, 2017 at 3:33 PM, Stephen Partington <cryptworks@gmail.com> wrote:
OpenCL in darktable mainly impacts rendering. it should have no effect on on system or ram consumption unless you are experiencing slowness during render cycles.

On Mon, Oct 30, 2017 at 12:21 PM, Michael <bmike1@gmail.com> wrote:
You know.... I'm having trouble running darktable. It seems that after I start it it runs a few minutes and then reboots the computer. Probably because I do not have a GPU (I don't think). Then I saw this thread and thought that I'd give that a try. So it seems I can not run chrome and darktable at the same time.
___
'lspci' shows that my graphics card is :
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850]
and 'lspci|grep gpu' returned an empty set
(if I did that correctly)
so I suppose the cheapest way to fix this is to get a gpu.... correct?

On Mon, Oct 30, 2017 at 12:09 PM, Carruth, Rusty <Rusty.Carruth@smartm.com> wrote:

In my experience, it’s almost always Firefox taking all of memory. (Or Chrome, or whatever web browser you’re using).

 

I agree with Mr B, run top or htop and see what’s, well, on top ;-)

 

Rusty

 

 

SMART_HRS_RGB

 

Rusty Carruth | Customer Support | rusty.carruth@smarth.com | http://www.smarth.com

 

      linkedin   twitterSee the new M4cid:image004.jpg@01D348E7.AF930710

 

See us on Storage Search    http://www.storagesearch.com/smart2.html

 

510-624-5391   | Fax: 480-926-5579   | 1325 N. Fiesta Blvd.  Suite 101 Gilbert, Az. 85233

 

From: PLUG-discuss [mailto:plug-discuss-bounces@lists.phxlinux.org] On Behalf Of Michael Butash
Sent: Sunday, October 29, 2017 10:05 AM
To: Main PLUG discussion list
Subject: Re: computer slow

 

If I ever have that, it's usually because of something with a memory leak, or desktop graphic compositing is degrading over time.

 

Before you reboot, see if you can ssh into it from another computer and check htop (or just top all you have), see if something is consuming all your memory or cpu.

 

Desktop compositors are all shite from what I can tell (including windoze), they're all just a varying degree of broken when you push them, or just have a slow (or buggy) video card.  Depending on your desktop environment of choice, try turning down graphics options, or disabling the compositor all together to see if it helps stability.

 

-mb

 

On Sun, Oct 29, 2017 at 3:41 AM, Michael <bmike1@gmail.com> wrote:

I'm almost certain that in my bag of tricks I had instructions on 'resetting' my computer when it started acting weird but I can't find them. Riddle me this: I try to leave the computer on 24/7 (maybe I shouldn't do that) and twice so far I come up to it and it is non-responsive or really slow to respond. Anyone know how to fix this?

 

--

:-)~MIKE~(-:


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

 


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-:

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
A mouse trap, placed on top of your alarm clock, will prevent you from rolling over and going back to sleep after you hit the snooze button.

Stephen


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-:

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-:

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-:

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-:

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:



--
:-)~MIKE~(-:

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
:-)~MIKE~(-: