From Newsgroup: uk.rec.waterways

<div>I've been experiencing stability problems on my main PC for the about a month. The computer would randomly freeze, sometimes after 1-2 days of use (with suspend in between), sometimes after just a few hours. </div><div></div><div>Most of the time, the only options is restarting the computer and the journalctl of the last boot just got cut off with nothing to debug. Starting with kernel 6.x, I can sometimes see some seemingly dangerous CPU lockup right at the end of the lock, right when the computer got frozen.</div><div></div><div></div><div></div><div></div><div></div><div>lockup video download</div><div></div><div>Download: https://t.co/RU8HDBfZwI </div><div></div><div></div><div>When I inspect the syslog if find lots of soft lockups for each CPU with increasing seconds. On one VM all 4 CPU's are locked and on the other only CPU 1-2-3 is locked but the result is the same - no response to keyboard and mouse.</div><div></div><div></div><div> cb831 Since you are experiencing lockups while running VMware Workstation, you should post this in the VMware Workstation forums. Workstation is using a different hypervisor implementation (either VMware's own hypervisor or Hyper-V) than Fusion 12 (macOS hypervisor frameworks).</div><div></div><div></div><div>So you think that the vmware ran CPL0 before when it worked...</div><div></div><div>I have backups - so I can try to find a vmware.log from a month ago.</div><div></div><div></div><div></div><div>Did you notice all the timeouts and failures around VMTools in the log - I guess those could explain the kernel waits in the guest that produces the soft lockups in syslog.</div><div></div><div></div><div>I have been having some of our Windows 10 layered, PVS provisioned, with user layer machines lock up of some users. Typically, director says it is a session prepare failure. The machine becomes unregistered. It still pings but you cannot connect to the machine in any way and must be force restarted. The scenario is always, user has been logged in for a day or more, disconnects in the evening, reconnects in the morning and gets the session prepare failure. I have about 50 of these machines running now with 35 running concurrent user connections. Almost daily I will have one or two lockup and become unregistered like I described.</div><div></div><div></div><div>My question is: What is the best way to go about troubleshooting this issue? When the machines lockup there is no way to go back and review the machines event logs. Are there logs on the PVS server or something that logs the userlayer connection?</div><div></div><div></div><div></div><div></div><div></div><div></div><div>The core dump is expected: QEMU goes into lockup, but we don't emulate lockup correctly (strictly speaking QEMU should just sit there doing nothing like the real hardware does), so we print a register dump and abort(). As I said in my previous comment, your problem is almost certainly that your binary doesn't have a vector table.</div><div></div><div></div><div>The ETR and the ETRs are not very different. The ETRs does NOT have mirror lockup, which is only found on the ETRsi model. I have both the ETRs and the ETRsi. To me, mirror lockup is not so much better that I would take one over the other. I have a 20 x 24 on my wall taken with 400 speed film using the ETRs (which does not have mirror lockup) and people are amazed at the detail.</div><div></div><div></div><div>This thread is consistent with my experiences. I also note that this problem is more frequently triggered by having both Firefox and Steam open at the same time.</div><div></div><div>Given that syslog loses the last few minutes of logging leading into the soft lockup, I expect we're looking at some kind of runaway condition where something is getting stuck in a loop somewhere. My Softlocks are often preceded by CPU/GPU panics, but they are not always.</div><div></div><div></div><div>So, I have not suffered a lockup since upgrading to BIOS to 4011 (with "AGESA 1.0.0.2a + SMU 43.18"), and setting the "Advanced Mode -> Advanced -> AMD CBS -> Power Supply Idle Control" option to "Typical Current Idle".</div><div></div><div> df19127ead</div>
--- Synchronet 3.21d-Linux NewsLink 1.2