Jump to content

Darqfallen

Members
  • Content Count

    167
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Darqfallen

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. New motherboard will be installed this weekend. I will start a new thread if there are any issues. Cheers.
  2. Here is the raw syslog from the time I updated to just after the crash. syslog.zip
  3. Crashed again, Kernel panic. By chance was at the console when it happened. dirge-diagnostics-20191115-0246.zip
  4. Removed the old ram and installed 64 gigs of new ram. Re-updated to 6.8.0-RC5. If this fails as well then it's a new motherboard.
  5. That was done, memory was shifted into different channels and retested. Perhaps I will look for some new memory and see, though DDR3-1600 or 1866 ECC ram is expensive.
  6. Then why would there be no problem in 5.7.0?
  7. Changed Status to Open Changed Priority to Urgent
  8. What's also interesting is what is picked up by the IPMI 1306 11/04/2019 21:21:18 Unknown BIOS POST Progress Progress - Asserted 1305 11/04/2019 21:19:01 Unknown BIOS POST Progress Progress - Asserted 1304 11/04/2019 21:18:52 Unknown BIOS POST Progress Progress - Asserted 1303 11/04/2019 21:18:52 Unknown BIOS POST Progress Progress - Asserted 1302 11/04/2019 21:18:45 Unknown BIOS POST Progress Progress - Asserted 1301 11/04/2019 21:18:38 Unknown BIOS POST Progress Progress - Asserted 1300 11/04/2019 21:18:31 Unknown BIOS POST Progress Progress - Asserted 1299 11/04/2019 21:17:15 Unknown BIOS POST Progress Progress - Asserted 1298 11/04/2019 21:17:11 Unknown BIOS POST Progress Progress - Asserted 1297 11/04/2019 21:17:02 Unknown BIOS POST Progress Progress - Asserted 1296 11/04/2019 21:17:02 Unknown BIOS POST Progress Progress - Asserted 1295 11/04/2019 21:17:02 Unknown BIOS POST Progress Progress - Asserted 1294 11/04/2019 21:17:01 Unknown BIOS POST Progress Progress - Asserted 1293 11/04/2019 21:16:51 Unknown BIOS POST Progress Progress - Asserted 1292 11/04/2019 21:16:49 Unknown BIOS POST Progress Progress - Asserted 1291 10/25/2030 22:31:12 Unknown Progress - Asserted - Asserted 1290 11/26/2031 15:22:24 Unknown OS Critical Stop Progress - Asserted - Asserted - Asserted 1289 05/14/2023 08:49:52 Unknown [undefined] Progress - Asserted - Asserted - Asserted - Asserted 1288 09/09/2028 04:57:20 Unknown [undefined] Progress - Asserted - Asserted - Asserted - Asserted - Asserted 1287 04/03/1987 11:36:16 Unknown OS Critical Stop Progress - Asserted - Asserted - Asserted - Asserted - Asserted - Asserted 1286 12/30/2025 09:38:56 Unknown [undefined] Progress - Asserted - Asserted - Asserted - Asserted - Asserted - Asserted - Asserted 1285 11/04/2019 21:16:16 Unknown OS Critical Stop Run-Time Stop - Asserted Perhaps is some update in the microcode that causes my cpus to not play nice with the ram. Ive also included the syslog that is logging to the USB drive. The server crashed again as I was writing this so I've downgraded back to 6.7.0 syslog.zip
  9. Updated to RC5 to see if there's any difference. Lasted ~23 hours before a crash and reboot. Diag at tached. dirge-diagnostics-20191105-0429.zip
  10. So something in the kernel patch in 6.7.2 and 6.8.0-RC1 is causing my hardware to start throwing memory errors. And a memtest will not show bad memory due to it being ecc memory. How do you fully test ECC ram?
  11. Why wouldn’t it show up in a memtest then?
  12. But it doesn’t happen in 6.7.0. So I’m thinking it’s a software issue.
  13. Ran a memtest for 8 hours. No errors.
  14. I'm sorry but I didn't realize that the diagnostics didn't use the whole syslog. I posted above my diag of when it was crashing. Attached is my whole syslog including the crashing.syslog.zip I'm not sure what else to do, if I leave the server running on anything > 6.7.0 then it crashes and reboots every 1-4 hours.