> -------- Ursprüngliche Nachricht --------
> Von: David Christensen <dpchr...@holgerdanske.com>
> An: debian-user@lists.debian.org
> Betreff: Re: Weird behaviour on System under high load
> Datum: Sun, 21 May 2023 14:22:22 -0700
>
> On 5/21/23 06:31, Christian wrote:
> > David Christensen Sun, 21 May 2023 03:11:43 -0700
>
> >>> David Christensen Sat, 20 May 2023 18:00:48 -0700
>
> > > Please use inline posting style and proper indentation.
> >
> > Phew... will be quite hard to read. But here you go.
>
>
> It is not hard when you delete the portions that you are not
> responding to.
>
>
> > > > > Have you cleaned the system interior, filters, fans,
> heatsinks,
> > > > > ducts,
> > > > > etc., recently?
>
> > As written in OP, the system is new. Only PSU is used. So it is
> clean
>
>
> Okay.
>
>
> > What is a thermal solution?
>
>
> Heat sinks, heat pipes, water blocks, radiators, fans, ducts, etc..
>
It is quite simple
- Noctua NH-L9a-AM4 for CPU
- Chassis 12cm fan
- PSU Integrated fans
>
> > > What stresstest are you using?
> > >
> > stress running in s-tui
>
>
> Do you mean "in situ"?
>
> https://www.merriam-webster.com/dictionary/in%20situ
>
No, it is the package and command "s-tui" and "stress"
s-tui gives you an overview on power usage, fan control, temps, core
frequencies and core utilization on the console
stress is just producing load on selected # of cpus, it can be
integrated in s-tui.
> I prefer a tool that I can control. That is why I wrote the
> previously
> attached Perl script. It is public domain; you and everyone are free
> to
> use, modify, distribute, etc., as you see fit.
>
>
> > > > > Have you tested the power supply recently?
>
> > It was working before without issues, so not explicitly tested.
>
> > I am not building regularly, so would need to borrow such equipment
> > somewhere
>
>
> Understand that an ATX PSU has multiple stages that produce +12 VDC,
> +5
> VDC, +5 VDC standby, +3.3 VDC, and -12 VDC ("rails"). It is common
> for
> one or more rails to fail and the others to continue working.
> Computers
> exhibit "weird behaviour" when this happens.
>
>
> Just spend the US$20.
>
>
> > > > > Have you tested the memory recently?
>
> > > Did you do multi-threaded/ stress tests?
> > >
> > Yes, stress is running multiple threads. Only on 2 threads it was
> > stable so far. However it takes longer for the errors to come up
> when
> > using less threads. might be that I did not test long enough.
>
>
> I use Memtest86+ 5.01 on a bootable USB stick. In the
> "Configuration"
> menu, I can choose "Core Selection". It appears the default is
> "Parallel (all)". Other choices include "Round Robin" and
> "Sequential".
> Memtest 5.01 also displays the CPU temperature. Running it an
> Intel
> Core i7-2600S with matching factory heat sink and fan for 30+
> minutes,
> the current CPU temperature is 50 C. This leads me to believe that
> the
> memory is loaded to 100%, but the CPU is less (perhaps 60%?).
>
> https://memtest.org/
>
>
> I recommend that you run Memtest86+ in parallel mode for at least one
> pass. I have seen computers go for 20+ hours before encountering a
> memory error.
>
>
> > > Did you see the problems when running Debian stable OOTB, before
> > > adding
> > > anything?
>
> > I would need to do this with a liveUSB, to have it run OOTB
>
>
> Okay. Put my Perl script on your liveUSB. Also put some tool for
> monitoring CPU temperature, such as sensors(1).
Will have time again in a few days and check.
>
>
> David
>
>
