From: Fiona Ebner <f.ebner@proxmox.com>
To: Eneko Lacunza <elacunza@binovo.es>, pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [RFC kernel] revert problematic TSC multiplier commit
Date: Fri, 2 Sep 2022 09:47:45 +0200 [thread overview]
Message-ID: <13967647-13df-0567-0870-3cd7aa461fa6@proxmox.com> (raw)
In-Reply-To: <f7d1ae7c-5b8a-8cf7-8aff-979348b216ca@binovo.es>
Hi,
Am 02.09.22 um 09:22 schrieb Eneko Lacunza:
> Hi Fiona,
>
> Does this patch correspond to kernels linked in this forum thread?
>
> https://forum.proxmox.com/threads/proxmox-7-2-3-ceph-16-2-7-migrating-vms-hangs-them-kernel-panic-on-linux-freeze-on-windows.109645/page-2#post-488479
>
No, there is no public build with the below patch yet.
Did you already test the kernel with the fpu patches that's mentioned in
that forum post?
>
> If so I can test them and see if that helps with bugzilla entry #4073:
> https://bugzilla.proxmox.com/show_bug.cgi?id=4073
>
I don't think theses issues are related, as there, the VM that's been
migrated hangs, and here other VMs on the node were affected.
> Thanks
>
> El 1/9/22 a las 8:25, Fiona Ebner escribió:
>> Am 31.08.22 um 15:28 schrieb Fiona Ebner:
>>> which might be responsible for several issues reported in the
>>> community forum[0][1].
>>>
>>> In my case, loading a VM snapshot that originally was taken on
>>> a CPU from a different vendor often caused problems in other VMs(!).
>>> In particular, it often led to RCU stalls (with similar messages as in
>>> [1]) or slowdowns, and sometimes clock jumps far into the future (like
>>> in [0]). With this revert applied, everything seems to run smoothly
>>> even after loading the "bad" snapshot 10 times.
>>>
>>> [0]https://forum.proxmox.com/threads/112756/
>>> [1]https://forum.proxmox.com/threads/111494/
The fix 11d39e8cc43e1c6737af19ca9372e590061b5ad2 is only for AMD/SVM, so
most likely [1], where people with Intel N5105 are affected, is not
related either. RCU stall messages can happen for different reasons of
course ;)
next prev parent reply other threads:[~2022-09-02 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 13:28 Fiona Ebner
2022-09-01 6:25 ` Fiona Ebner
[not found] ` <f7d1ae7c-5b8a-8cf7-8aff-979348b216ca@binovo.es>
2022-09-02 7:47 ` Fiona Ebner [this message]
[not found] ` <536bbaea-9f39-0b96-e16e-70c04c0852a5@binovo.es>
[not found] ` <1ca8041f-5099-ad72-9c86-ddc86c1aafff@binovo.es>
[not found] ` <c7e45768-c09a-1128-4f5a-5e9f3e0ec06d@binovo.es>
2022-09-14 7:50 ` Fiona Ebner
[not found] ` <4530687c-86ea-e9f6-c932-7f1f702d6647@binovo.es>
[not found] ` <be970183-0eae-9fc8-ad44-f8e90b78b62c@binovo.es>
2022-09-15 8:37 ` Fiona Ebner
[not found] ` <mailman.140.1663148345.354.pve-devel@lists.proxmox.com>
2022-09-15 10:44 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13967647-13df-0567-0870-3cd7aa461fa6@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=elacunza@binovo.es \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox