From: Jesse Brandeburg <jbrandeburg@cloudflare.com>
To: "Nitka, Grzegorz" <grzegorz.nitka@intel.com>,
Frederick Lawler <fred@cloudflare.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
AndrewLunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"kernel-team@cloudflare.com" <kernel-team@cloudflare.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] ice: General protection fault in ptp_clock_index
Date: Mon, 20 Oct 2025 15:02:11 -0700 [thread overview]
Message-ID: <1f974f16-c46d-4e9b-b0ed-c15b5d5c45cd@cloudflare.com> (raw)
In-Reply-To: <IA1PR11MB6219645389921FD751CA0C8B9227A@IA1PR11MB6219.namprd11.prod.outlook.com>
On 7/31/25 4:01 AM, Nitka, Grzegorz wrote:
>> Hi Intel team, anyone have an idea on this? Looks like maybe removal of
>> device 0 that had originally registered PTP clock isn't handled well?
>>
>
> Hi All,
>
> Thank you for your message. We're looking into this.
> Yes, at first sight it seems to be a race condition hit while removing PF which is PTP
> owner (and responsible for removing PTP clock).
Hi Intel team, any progress on this issue?
BR,
Jesse
prev parent reply other threads:[~2025-10-20 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 20:25 ice: General protection fault in ptp_clock_index Frederick Lawler
2025-07-28 16:18 ` Jesse Brandeburg
2025-07-31 11:01 ` [Intel-wired-lan] " Nitka, Grzegorz
2025-10-20 22:02 ` Jesse Brandeburg [this message]
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=1f974f16-c46d-4e9b-b0ed-c15b5d5c45cd@cloudflare.com \
--to=jbrandeburg@cloudflare.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fred@cloudflare.com \
--cc=grzegorz.nitka@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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