Conversation

Notices

1. Embed this notice
   Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Tuesday, 23-Jul-2024 21:08:57 JST Ryan Castellucci :nonbinary_flag:

   • Tulip ?️‍⚧️

   @domi It really doesn't help that the logged errors are inscrutable. I reseated the RAM, maybe that will help.

   • Embed this notice
     Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Tuesday, 23-Jul-2024 22:52:17 JST Ryan Castellucci :nonbinary_flag:

     in reply to

     • Tulip ?️‍⚧️
     • Chuck Fry

     @SVChucko @domi It's an Intel Atom CPU with ECC DDR3 on a server motherboard. I don't think I could overclock it even if I wanted to. Not under volted either.

   • Embed this notice
     Chuck Fry (svchucko@sfba.social)'s status on Tuesday, 23-Jul-2024 22:52:18 JST Chuck Fry

     in reply to

     • Tulip ?️‍⚧️

     @ryanc @domi What about stress-ng? My experience with memtest86 is that it's not very sensitive to the kinds of RAM issues you might encounter in overclocking. stress-ng and even Prime95 are better at exercising the whole memory subsystem.

   • Embed this notice
     Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Tuesday, 23-Jul-2024 23:06:44 JST Ryan Castellucci :nonbinary_flag:

     in reply to

     • Tulip ?️‍⚧️
     • Chuck Fry

     @SVChucko @domi The other issue is that standard burn in tools aren't likely to be ECC-aware. :-(