From: Alexander Zeidler <a.zeidler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH kernel 2/2] cherry-pick potential fix for NULL pointer deref with AMD Arcturus GPU during boot
Date: Tue, 16 Jul 2024 11:41:10 +0200 (CEST) [thread overview]
Message-ID: <1887225164.281.1721122870661@webmail.proxmox.com> (raw)
In-Reply-To: <20240710113709.1415909-2-f.ebner@proxmox.com>
> On 10.07.2024 11:37 GMT Fiona Ebner <f.ebner@proxmox.com> wrote:
> The issue was reported in the enterprise support and is handled by
> Alexander Zeidler. It has the following trace [0] and causes an issue
> with the networking down the line, because 'udevadm settle' would time
> out. The customer reported that mainline kernel 6.9.3 booted fine.
> Looking at the new commits, this one stood out, as it heavily modifies
> the arcturus_get_power_limit() function. While not tagged for stable,
> it seems straightforward enough and has a good chance to fix the
> issue.
This commit fixes the problem for the customer after he has booted the
test kernel provided.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-07-16 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 11:37 [pve-devel] [PATCH kernel 1/2] add fix for CIFS client memory leak Fiona Ebner
2024-07-10 11:37 ` [pve-devel] [PATCH kernel 2/2] cherry-pick potential fix for NULL pointer deref with AMD Arcturus GPU during boot Fiona Ebner
2024-07-16 9:41 ` Alexander Zeidler [this message]
2024-07-12 14:54 ` [pve-devel] applied-series: [PATCH kernel 1/2] add fix for CIFS client memory leak 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=1887225164.281.1721122870661@webmail.proxmox.com \
--to=a.zeidler@proxmox.com \
--cc=f.ebner@proxmox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.