lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <151585637e9ada09bbc2bd2e3ab85c4d491bcc5e.camel@microchip.com>
Date: Mon, 21 Apr 2025 04:17:23 +0000
From: <Thangaraj.S@...rochip.com>
To: <andrew@...n.ch>
CC: <andrew+netdev@...n.ch>, <linux-usb@...r.kernel.org>,
	<davem@...emloft.net>, <Rengarajan.S@...rochip.com>,
	<kernel-list@...pberrypi.com>, <fiona.klute@....de>,
	<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>, <kuba@...nel.org>,
	<edumazet@...gle.com>, <pabeni@...hat.com>, <UNGLinuxDriver@...rochip.com>
Subject: Re: [PATCH net v2] net: phy: microchip: force IRQ polling mode for
 lan88xx

On Thu, 2025-04-17 at 20:11 +0200, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
> 
> On Thu, Apr 17, 2025 at 02:17:20PM +0000, Thangaraj.S@...rochip.com
> wrote:
> > Hi Flona,
> > We haven't observed this issue with our LAN7801 + LAN88xx setup
> > during
> > testing in our setups. Issue reported  specifically in RPI and
> > NVidea
> > with which we have not tested recently. Additionally, community
> > discussions suggest that this issue may have been introduced due to
> > driver updates in the LAN78xx. There's no hardware errata
> > indicating
> > any problems with the interrupts in LAN88xx.
> > 
> > If the issue lies in the interrupt handling within the LAN78xx,
> > it's
> > likely that similar problems could arise with other PHYs that
> > support
> > interrupt handling. This need to be debugged and addressed from
> > LAN78xx
> > driver rather than removing interrupt support in LAN88xx.
> 
> Hi Thangaraj
> 
> It is an easily available platform. Maybe you can get one and try to
> debug it?
> 
> This is a self contained simple fix. From a pragmatic standpoint, it
> solves an issue which is bothering people. If you do find and fix an
> issue in the LAN78xx this change can be easily reverted. So i'm
> learning towards merging it.
> 
>         Andrew

Hi Andrew,
Sure, I will debug this issue from my end. Agree we can merge this fix
for now, and revert once this is fixed in LAN78xx.

Thanks,
Thangaraj Samynathan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ