Re: computer slow

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 wrote: > I'm going to run the gl

Re: computer slow

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 wrote: > i'm trying to recreate the crash to make sure I didn't copy and

Re: computer slow

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 wrote: > I think glmark2 crashed it just crashed it after about 2 hours > > >

Re: computer slow

I think glmark2 crashed it just crashed it after about 2 hours On Mon, Oct 30, 2017 at 9:19 PM, Michael wrote: > final reading: > $ sensors > radeon-pci-0100 > Adapter: PCI adapter > temp1:+75.0°C > > k10temp-pci-00c3 > Adapter: PCI adapter > temp1:+53.8°C

Re: computer slow

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

Re: computer slow

'coo' is supposed to read 'cool' as in not shorts temperature On Mon, Oct 30, 2017 at 8:33 PM, Michael 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 >

Re: computer slow

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)

Re: computer slow

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 wrote: > Here is around 180 seconds

Re: computer slow

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)

Re: computer slow

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 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 wrote: > >> as

Re: computer slow

how long do you want me to run glmark2 for? Forever is not feasible! On Mon, Oct 30, 2017 at 7:22 PM, Michael 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

Re: computer slow

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 wrote: > $ sensors > radeon-pci-0100 > Adapter: PCI adapter > temp1:+68.0°C > > k10temp-pci-00c3 > Adapter: PCI adapter > temp1:

Re: computer slow

$ 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 wrote: > Well, it might

Re: computer slow

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: https://askubuntu.com/questions/15832/how-do-i-get-the-cpu-temperature If your machine is legitimately overheating you need to address

Re: computer slow

if there is a shutoff point you did say disable it? On Mon, Oct 30, 2017 at 6:56 PM, Brien Dieterle 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

Re: computer slow

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,

Re: computer slow

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 wrote: > and if glmark2 doesn't crash it run stress the same amount of

Re: computer slow

well, then run both stress AND glmark2 for like 20 minutes. If that doesn't crash it, look for some other graphical programs like an openGL game. There should be a package to install Nexuiz/Xonotic That'll give you an excuse to play videogames for a bit. If ONLY darktable makes your computer

Re: computer slow

and if glmark2 doesn't crash it run stress the same amount of time? On Mon, Oct 30, 2017 at 6:37 PM, Michael wrote: > how long do I let glmark2's pretty horse rotate? > > > On Mon, Oct 30, 2017 at 6:36 PM, Michael wrote: > >> okay >> ` >> >> On Mon, Oct 30,

Re: computer slow

how long do I let glmark2's pretty horse rotate? On Mon, Oct 30, 2017 at 6:36 PM, Michael wrote: > okay > ` > > On Mon, Oct 30, 2017 at 6:10 PM, Brien Dieterle wrote: > >> I'd wait. If stress alone doesn't crash, run glmark2 by itself. If >> glmark2

Re: computer slow

okay ` On Mon, Oct 30, 2017 at 6:10 PM, Brien Dieterle 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 wrote: > >> run this

Re: computer slow

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 wrote: > run this now or after stress completes? > ? > > On Mon, Oct 30, 2017 at 5:59 PM, Brien Dieterle

Re: computer slow

run this now or after stress completes? ? On Mon, Oct 30, 2017 at 5:59 PM, Brien Dieterle wrote: > Well, not yet ;-). If it doesn't crash, you might need to stress the > graphics card as well with one of these tools: > >

Re: computer slow

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

Re: computer slow

if it doesn't crash I'll start hounding the darktable forums. On Mon, Oct 30, 2017 at 5:45 PM, Michael wrote: > Just started. lets see what happens > > On Mon, Oct 30, 2017 at 5:36 PM, Brien Dieterle wrote: > >> Forget darktable for now. Did you run

Re: computer slow

Just started. lets see what happens On Mon, Oct 30, 2017 at 5:36 PM, Brien Dieterle 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

Re: computer slow

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,

Re: computer slow

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 wrote: > Check your bios settings

Re: computer slow

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

Re: computer slow

That sounds like thermals. do you have the sensors running from the 10 min run vs the 2 min run? On Mon, Oct 30, 2017 at 1:04 PM, Michael 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

Re: computer slow

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 wrote: > $

Re: computer slow

$ 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

Re: computer slow

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 wrote: > OpenCL in darktable mainly impacts rendering. it should have no effect

Re: computer slow

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 wrote: > You know I'm having trouble running darktable. It seems that

Re: computer slow

Sounds more like general overheating apt install stress man stress On Mon, Oct 30, 2017 at 12:21 PM, Michael 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

Re: computer slow

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

RE: computer slow

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 |