Linux Fixes Hosts Randomly Rebooting During Virtualization With Ryzen 7000/8000 CPUs

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • jenav
    replied
    Great news! I've been hitting this bug frequently on a Ryzen 7600.

    Leave a comment:


  • caligula
    replied
    Originally posted by fafreeman View Post
    i hate ryzen fanboys so much its unreal. i'm not even an intel fanboy and even use a amd gpu but for as long as i can remember amd cpu fanboys have been the absolute worst. almost like they have rabies
    At least many models of Ryzen series have been very competitive products. Before Ryzen AMD had only shit hardware. Intel has f*cked the asses of their buyers several times without using lube. Two whole generations of recent chips are flawed and will eventually break down. Lots of unimpressive products. Totally f*cked up energy consumption for some generations of i7 CPUs. Also most of the 3rd to 7th generation models were totally unimpressive in terms of performance. 2600/2700k was good, the next good model was 8700k. Most users were also affected by SPECTRE/MELTDOWN. So much performance lost due to incompetence.

    Leave a comment:


  • intelfx
    replied
    Originally posted by Forge View Post
    Do you have any idea what you are talking about
    Lol, no, he doesn’t.

    Judging by this guy’s recent comments across various topics, I’m practically convinced he is on some sort of a “trolling by cluelessness” contest.

    Leave a comment:


  • Paradigm Shifter
    replied
    Cyrix forever...?
    Originally posted by fafreeman View Post
    i hate ryzen fanboys so much its unreal. i'm not even an intel fanboy and even use a amd gpu but for as long as i can remember amd cpu fanboys have been the absolute worst. almost like they have rabies
    Just like Intel. Fanboys are fanboys. Insufferable no matter whose flag they wave.

    Leave a comment:


  • fafreeman
    replied
    i hate ryzen fanboys so much its unreal. i'm not even an intel fanboy and even use a amd gpu but for as long as i can remember amd cpu fanboys have been the absolute worst. almost like they have rabies

    Leave a comment:


  • pWe00Iri3e7Z9lHOX2Qx
    replied
    Not this issue, but my 7900X3D desktop still hard crashes on resume from sleep frequently on 6.11.x. I've been running OpenSUSE Slowroll with their 6.6.x LTS kernel to have something stable. I'll try again once 6.12 makes it into a snapshot.

    Leave a comment:


  • intelfx
    replied
    Originally posted by sophisticles View Post

    Anyone that even thinks about running a VM within a VM deserves to have his system shutdown!!!
    You should run for the word-twisting and mental gymnastics contest. Easy podium for you there, mate.

    Leave a comment:


  • intelfx
    replied
    Originally posted by theriddick View Post
    I think I've experienced this a few times and was like WTF... thought I was experiencing some sort of PSU fault!

    I've got the VM flags enabled in bios and don't use a VM currently but have experienced this even when a guest vm isn't running so perhaps it happens when support is enabled even if unused as well?
    No, it doesn't and you haven't. Unless you're using not just VMs but nested VMs, whatever you are affected by is not this problem.

    Leave a comment:


  • Forge
    replied
    Originally posted by Espionage724 View Post

    So, AMD being cheap and leaving vendors to be indirectly incompetent, along with end-users having the results after paying for all the hardware involved? I'm still not seeing a chain of confidence

    What is newer hardware doing re-using old hardware and cutting out a feature on the old hardware? And why would someone buy that?
    Do you have any idea what you are talking about? What “old hardware”? Ryzen 7000/8000 and EPYC 4000 are all contemporary and run on the exact same silicon.

    Leave a comment:


  • sophisticles
    replied
    Originally posted by intelfx View Post
    This issue is about nested virtualization, i.e. VMSAVE/VMLOAD in the guest. You won't ever experience this issue unless you really go out of your way (and get unlucky with the BIOS/ucode).
    Anyone that even thinks about running a VM within a VM deserves to have his system shutdown!!!

    Leave a comment:

Working...
X