Search results

  1. C

    Just got a subscription license ... WTH?

    It won't complain, but if you ever need to use those support tickets you purchased you would find it invalidated if you are only licensing some of the nodes in the cluster. Assuming you are OK purchasing support you cannot use the other benefit of it is the enterprise repository which has...
  2. C

    kernel: pcieport 0000:c0:03.1: PME: Spurious native interrupt!

    Have you tried setting pcie_aspm=off in your kernel command line? That's still working for me
  3. C

    Proxmox 7: pcieport 0000:00:01.0: PME: Spurious native interrupt!

    Check my reply over here for a workaround: https://forum.proxmox.com/threads/kernel-pcieport-0000-c0-03-1-pme-spurious-native-interrupt.101338/post-479912
  4. C

    kernel: pcieport 0000:c0:03.1: PME: Spurious native interrupt!

    It's been a while and this is still an issue. In the mean time I've also discovered that disabling PCIe power management in /etc/kernel/cmdline (pcie_aspm=off) also stops this log spam, with the benefit of not needing manual intervention each boot.
  5. C

    [SOLVED] Mellanox ConnectX-5 EN - 100G running at 40G

    Just a note that both intel_idle and intel_pstate modules are only active on Intel CPUs (as per the names) so those commands won't do anything on your EPYC server. 'processor.max_cstate=2' might be what you want.
  6. C

    kernel: pcieport 0000:c0:03.1: PME: Spurious native interrupt!

    The usecs parameters specify how many microseconds after at least 1 packet is received/transmitted before generating an interrupt. In my case the default is 3. You can check yours by running ethtool -c <interface> and reading the output on a fresh boot before you disable it.
  7. C

    kernel: pcieport 0000:c0:03.1: PME: Spurious native interrupt!

    As this is the first thread on the issue with a staff reply I thought I'd add the following: It appears that it's 'fixed' not just by disabling interrupt coalescing but rather toggling it; it can safely be turned back on again after disabling. Also as noticed by 'ajeffco' in another thread on...
  8. C

    Proxmox VE Licensing & Features

    None of the features are disabled or limited, there are two major differences, support and the enterprise repository. Support should be self explainitory, should you have an issue without at least a "basic" subscription your only avenue for help is community settings such as this forum. The...
  9. C

    Kernel Update

    apt install pve-headers-5.11 pve-kernel-5.11
  10. C

    Proxmox Backup Server 1.0 (stable)

    Seems a bit steep to be honest, as a (standard) subscriber to proxmox on 3 nodes I was intending on subscribing to pbs but as it stands I'll take my chances with the no subscription option.
  11. C

    "PME: Spurious native interrupt!" Kernel Meldungen

    I haven't had any issue since turning off interrupt coalescing. The expected side effect of doing this is slight cpu usage increase as there will be more interrupts. In my environment this is immeasurably small.
  12. C

    "PME: Spurious native interrupt!" Kernel Meldungen

    Hi, I have the same issue atm with the 82599ES driver on proxmox. I've found that if you disable interrupt coalescing on the affected cards then the errors stop happening. sudo ethtool -C <iface> rx-usecs 0

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!