I don't want to install go-lang, and I want a offline fix.
So I will recreate the ryzen-stabilisator as pure POSIX shell script.
and using the debian msr-tools package (rdmsr/wrmsr)
Ok here is my fix
info(){ printf '%s[INFO]%s %s\n' "$CYAN"...
UPDATE: After changing the 65w adapter with a 90w adapter, the problems are gone, turbo, EIST enabled, everything is working perfectly fine, no crashes, no reboots.
Relax. Take a deep breath. I just recently had this issue. It is easy to fix. But you need a clear mind to not destroy anything.
Like you said, you are not able to run GC, because you have no disk space left. Let us change that.
Get another...
Hi,
I wanted to check whether there is a mirror closer to the Maldives than the Singapore mirror currently being used.
All the CNAMEs appear to resolve to the Singapore CDN:
______________________________
download.proxmox.com. CNAME...
A test-kernel for another regression (in bnxt_en) just got uploaded to:
http://download.proxmox.com/temp/kernel-7.0.14-22_bnxt-test1/
this should contain the current fix mentioned above - if you can - please test booting that kerne (without...
It may also be useful to try with the kernel option: iommu=pt
I have a Ryzen based Proxmox system at home that will consistently crash until this option is used.
What if you pick some other storage for fleecing or disable it completely? I am suspicious that there might be some issue with whatever drives you are using for the "local-lvm" storage. Are they enterprise grade?
Have you checked logs on the...
I tested kernel-7.0.14-22_bnxt-test1, in my case, the problem is gone, there are no issues in the logs regarding the bnxt_en driver, and the network is working.
It did not take long
Crashed immediately, weird !
Turns out, the BIOS does not respect the setting
But then you reboot, and it did not honor the setting, it is BACK TO AUTO !!
Hello,
Thanks for all the replies. I Finally figured out what the error was.
As advised here, I tried running /usr/sbin/upsd -F -DDDDD in foreground with the debug options and found that the problem was related to the interface binding. The...
Hello,
Thanks for all the replies. I Finally figured out what the error was.
As advised here, I tried running /usr/sbin/upsd -F -DDDDD in foreground with the debug options and found that the problem was related to the interface binding. The...
Thank you @shodan for keeping such notes !
It turned out to be quite useful
I confirm this problem still exists in Proxmox 9.2
Here is some useful threads
https://github.com/qrwteyrutiyoup/ryzen-stabilizator...
Hi @mkoeppl
I wanted to disable the softdog to make sure the hardware watchdog was enable.
I was having intermittent hanging on Gen 1 ryzen
Turns out in this weird condition that, hardware watchdog will not reset, even though it is basically...
You are experiencing timeouts between your host(s) and your backup target. these issues stem from one or more of
Source disk bandwidth
network transport
Destination disk bandwidth.
for item 1- you mentioned your host storage is ceph. what is the...
This is exactly why I stopped using veeam agent for linux quite a while ago, they can't keep up with the Proxmox kernel versions.
I have my own custom scripts with fsarchiver that work well with ext4/XFS rootfs and have been tested...
After a long time I have to come back to this post. Sadly even setting the bw to 100MBits, only made the problem seem less frequent. Is there anything else we can try, because this seems like a temporal solution. Where else should our team look...
It is my 20 years of sysadmin and 16 years of Proxmox experience.
I then used Claude to search around this possibility and it found 2 bugs report about it.