From: <Parthiban.Veerasooran@microchip.com>
To: <Selvamani.Rajagopal@onsemi.com>
Cc: <andrew@lunn.ch>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <Conor.Dooley@microchip.com>,
<devicetree@vger.kernel.org>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <Pier.Beruto@onsemi.com>
Subject: Re: [PATCH net v5 1/4] net: ethernet: oa_tc6: Interrupt is active low, level triggered.
Date: Tue, 30 Jun 2026 03:24:37 +0000 [thread overview]
Message-ID: <d15eaa01-3312-420f-a34a-d810710e5b12@microchip.com> (raw)
In-Reply-To: <CYYPR02MB98285BD6A2639E0B01AE407183EC2@CYYPR02MB9828.namprd02.prod.outlook.com>
Hi Selvamani,
On 25/06/26 9:01 pm, Selvamani Rajagopal wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Parthiban,
>
> Let me know if you prefer updating the patchset. I certainly prefer adding a NULL check
> In oa_tc6_update_rx_skb function.
Sorry for the delayed response. I see you already shared the patches for
the fixes. Today I will test the below patch series and share the
feedback ASAP.
https://patchwork.kernel.org/project/netdevbpf/patch/20260626-fix-race-condition-and-crash-v2-1-b6c5c10e604f@onsemi.com/
Best regards,
Parthiban V
>
>
>>
>> Root cause seems to be same. When oa_tc6_update_rx_skb function is called, tc6-
>>> rx_skb
>> seems to be NULL, which may mean, controller seems to be not getting start
>>
>> I have a theory. Look at line #933. We have the following comment. I am sure this could
>> be true
>> for the call to oa_tc6_prcs_rx_frame_end at line #926 or oa_tc6_prcs_ongoing_rx_frame
>> at line #950.
>> /* After rx buffer overflow error received, there might be a
>> * possibility of getting an end valid of a previously
>> * incomplete rx frame along with the new rx frame start valid.
>> */
>>
>
next prev parent reply other threads:[~2026-06-30 3:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 21:55 [PATCH net v5 0/4] MAC-PHY interrupt changed to level triggered interrupt Selvamani Rajagopal via B4 Relay
2026-06-11 21:55 ` [PATCH net v5 1/4] net: ethernet: oa_tc6: Interrupt is active low, level triggered Selvamani Rajagopal via B4 Relay
2026-06-16 6:01 ` Parthiban.Veerasooran
2026-06-17 4:54 ` Selvamani Rajagopal
2026-06-18 4:26 ` Parthiban.Veerasooran
2026-06-18 4:26 ` Selvamani Rajagopal
2026-06-22 5:14 ` Selvamani Rajagopal
2026-06-23 5:19 ` Parthiban.Veerasooran
2026-06-23 5:19 ` Parthiban.Veerasooran
2026-06-23 5:48 ` Selvamani Rajagopal
2026-06-25 12:36 ` Parthiban.Veerasooran
2026-06-25 15:21 ` Selvamani Rajagopal
2026-06-25 15:31 ` Selvamani Rajagopal
2026-06-30 3:24 ` Parthiban.Veerasooran [this message]
2026-06-30 4:21 ` Selvamani Rajagopal
2026-06-11 21:55 ` [PATCH net v5 2/4] net: ethernet: oa_tc6: mdiobus->parent initialized with NULL Selvamani Rajagopal via B4 Relay
2026-06-11 21:55 ` [PATCH net v5 3/4] net: ethernet: oa_tc6: Remove FCS size in RX frame Selvamani Rajagopal via B4 Relay
2026-06-11 21:55 ` [PATCH net v5 4/4] dt-bindings: net: updated interrupt type to be active low, level triggered Selvamani Rajagopal via B4 Relay
2026-06-12 8:44 ` Krzysztof Kozlowski
2026-06-15 23:40 ` [PATCH net v5 0/4] MAC-PHY interrupt changed to level triggered interrupt patchwork-bot+netdevbpf
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=d15eaa01-3312-420f-a34a-d810710e5b12@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=Conor.Dooley@microchip.com \
--cc=Pier.Beruto@onsemi.com \
--cc=Selvamani.Rajagopal@onsemi.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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