All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Russell King" <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Herve Codina" <herve.codina@bootlin.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Heiner Kallweit" <hkallweit1@gmail.com>,
	"Vladimir Oltean" <vladimir.oltean@nxp.com>,
	"Köry Maincent" <kory.maincent@bootlin.com>,
	"Jesse Brandeburg" <jesse.brandeburg@intel.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Marek Behún" <kabel@kernel.org>,
	"Piergiorgio Beruto" <piergiorgio.beruto@gmail.com>,
	"Oleksij Rempel" <o.rempel@pengutronix.de>,
	"Nicolò Veronese" <nicveronese@gmail.com>,
	"Simon Horman" <horms@kernel.org>,
	mwojtas@chromium.org
Subject: Re: [PATCH net-next v11 01/13] net: phy: Introduce ethernet link topology representation
Date: Wed, 10 Apr 2024 10:16:27 +0200	[thread overview]
Message-ID: <20240410101627.53bfdebf@device-28.home> (raw)
In-Reply-To: <20240409201553.GA4124869@dev-arch.thelio-3990X>

Hello Nathan,

On Tue, 9 Apr 2024 13:15:53 -0700
Nathan Chancellor <nathan@kernel.org> wrote:

> Hi Maxime,
> 
> On Thu, Apr 04, 2024 at 11:29:51AM +0200, Maxime Chevallier wrote:

[...]

> I bisected a crash that I see on one of my test devices to this change
> in -next as commit 6916e461e793 ("net: phy: Introduce ethernet link
> topology representation"). Here is the stack trace passed through
> scripts/decode_stacktrace.sh:

[...]

> [    5.626535] ? phy_link_topo_add_phy (drivers/net/phy/phy_link_topology.c:46) libphy
> [    5.627954] ? _raw_spin_lock (arch/x86/include/asm/atomic.h:115 (discriminator 4) include/linux/atomic/atomic-arch-fallback.h:2170 (discriminator 4) include/linux/atomic/atomic-instrumented.h:1302 (discriminator 4) include/asm-generic/qspinlock.h:111 (discriminator 4) include/linux/spinlock.h:187 (discriminator 4) include/linux/spinlock_api_smp.h:134 (discriminator 4) kernel/locking/spinlock.c:154 (discriminator 4)) 
> [    5.627963] phy_link_topo_add_phy (include/linux/xarray.h:977 drivers/net/phy/phy_link_topology.c:80) libphy
> [    5.629462] phy_attach_direct (drivers/net/phy/phy_device.c:1516) libphy
> [    5.629504] phylink_connect_phy (drivers/net/phy/phylink.c:1983) phylink
> [    5.631030] ax88772_bind (drivers/net/usb/asix_devices.c:710 drivers/net/usb/asix_devices.c:919) asix
> [    5.631049] usbnet_probe (drivers/net/usb/usbnet.c:1745) usbnet

I've run some tests on an arm64 board using an USB to Ethernet adapter
that uses the same driver (It also goes through ax88772_bind() ) but I
don't reproduce the error.

> If there is any additional information I can provide or patches I can
> test, I am more than happy to do so.

The next step for me would be to try on an x86_64 box to get closer to
the config you used, however could you give me the .config that was used
when the bug was triggered ? I'd like to make sure I didn't miss
anything related to some of the parts being build as modules for
example.

Thanks a lot,

Maxime

> Cheers,
> Nathan



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Russell King" <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Herve Codina" <herve.codina@bootlin.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Heiner Kallweit" <hkallweit1@gmail.com>,
	"Vladimir Oltean" <vladimir.oltean@nxp.com>,
	"Köry Maincent" <kory.maincent@bootlin.com>,
	"Jesse Brandeburg" <jesse.brandeburg@intel.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Marek Behún" <kabel@kernel.org>,
	"Piergiorgio Beruto" <piergiorgio.beruto@gmail.com>,
	"Oleksij Rempel" <o.rempel@pengutronix.de>,
	"Nicolò Veronese" <nicveronese@gmail.com>,
	"Simon Horman" <horms@kernel.org>,
	mwojtas@chromium.org
Subject: Re: [PATCH net-next v11 01/13] net: phy: Introduce ethernet link topology representation
Date: Wed, 10 Apr 2024 10:16:27 +0200	[thread overview]
Message-ID: <20240410101627.53bfdebf@device-28.home> (raw)
In-Reply-To: <20240409201553.GA4124869@dev-arch.thelio-3990X>

Hello Nathan,

On Tue, 9 Apr 2024 13:15:53 -0700
Nathan Chancellor <nathan@kernel.org> wrote:

> Hi Maxime,
> 
> On Thu, Apr 04, 2024 at 11:29:51AM +0200, Maxime Chevallier wrote:

[...]

> I bisected a crash that I see on one of my test devices to this change
> in -next as commit 6916e461e793 ("net: phy: Introduce ethernet link
> topology representation"). Here is the stack trace passed through
> scripts/decode_stacktrace.sh:

[...]

> [    5.626535] ? phy_link_topo_add_phy (drivers/net/phy/phy_link_topology.c:46) libphy
> [    5.627954] ? _raw_spin_lock (arch/x86/include/asm/atomic.h:115 (discriminator 4) include/linux/atomic/atomic-arch-fallback.h:2170 (discriminator 4) include/linux/atomic/atomic-instrumented.h:1302 (discriminator 4) include/asm-generic/qspinlock.h:111 (discriminator 4) include/linux/spinlock.h:187 (discriminator 4) include/linux/spinlock_api_smp.h:134 (discriminator 4) kernel/locking/spinlock.c:154 (discriminator 4)) 
> [    5.627963] phy_link_topo_add_phy (include/linux/xarray.h:977 drivers/net/phy/phy_link_topology.c:80) libphy
> [    5.629462] phy_attach_direct (drivers/net/phy/phy_device.c:1516) libphy
> [    5.629504] phylink_connect_phy (drivers/net/phy/phylink.c:1983) phylink
> [    5.631030] ax88772_bind (drivers/net/usb/asix_devices.c:710 drivers/net/usb/asix_devices.c:919) asix
> [    5.631049] usbnet_probe (drivers/net/usb/usbnet.c:1745) usbnet

I've run some tests on an arm64 board using an USB to Ethernet adapter
that uses the same driver (It also goes through ax88772_bind() ) but I
don't reproduce the error.

> If there is any additional information I can provide or patches I can
> test, I am more than happy to do so.

The next step for me would be to try on an x86_64 box to get closer to
the config you used, however could you give me the .config that was used
when the bug was triggered ? I'd like to make sure I didn't miss
anything related to some of the parts being build as modules for
example.

Thanks a lot,

Maxime

> Cheers,
> Nathan



  parent reply	other threads:[~2024-04-10  8:16 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04  9:29 [PATCH net-next v11 00/13] Introduce PHY listing and link_topology tracking Maxime Chevallier
2024-04-04  9:29 ` Maxime Chevallier
2024-04-04  9:29 ` [PATCH net-next v11 01/13] net: phy: Introduce ethernet link topology representation Maxime Chevallier
2024-04-04  9:29   ` Maxime Chevallier
2024-04-06 15:51   ` Andrew Lunn
2024-04-06 15:51     ` Andrew Lunn
2024-04-09 20:15   ` Nathan Chancellor
2024-04-09 20:15     ` Nathan Chancellor
2024-04-10  6:45     ` Maxime Chevallier
2024-04-10  6:45       ` Maxime Chevallier
2024-04-10  8:16     ` Maxime Chevallier [this message]
2024-04-10  8:16       ` Maxime Chevallier
2024-04-10 14:53       ` Nathan Chancellor
2024-04-11  9:25         ` Maxime Chevallier
2024-04-11  9:25           ` Maxime Chevallier
2024-04-04  9:29 ` [PATCH net-next v11 02/13] net: sfp: pass the phy_device when disconnecting an sfp module's PHY Maxime Chevallier
2024-04-04  9:29   ` Maxime Chevallier
2024-04-06 15:51   ` Andrew Lunn
2024-04-06 15:51     ` Andrew Lunn
2024-04-04  9:29 ` [PATCH net-next v11 03/13] net: phy: add helpers to handle sfp phy connect/disconnect Maxime Chevallier
2024-04-04  9:29   ` Maxime Chevallier
2024-04-06 15:52   ` Andrew Lunn
2024-04-06 15:52     ` Andrew Lunn
2024-04-04  9:29 ` [PATCH net-next v11 04/13] net: sfp: Add helper to return the SFP bus name Maxime Chevallier
2024-04-04  9:29   ` Maxime Chevallier
2024-04-04  9:29 ` [PATCH net-next v11 05/13] net: ethtool: Allow passing a phy index for some commands Maxime Chevallier
2024-04-04  9:29   ` Maxime Chevallier
2024-04-04  9:29 ` [PATCH net-next v11 06/13] netlink: specs: add phy-index as a header parameter Maxime Chevallier
2024-04-04  9:29   ` Maxime Chevallier
2024-04-04  9:29 ` [PATCH net-next v11 07/13] net: ethtool: Introduce a command to list PHYs on an interface Maxime Chevallier
2024-04-04  9:29   ` Maxime Chevallier
2024-04-06 15:58   ` Andrew Lunn
2024-04-06 15:58     ` Andrew Lunn
2024-04-04  9:29 ` [PATCH net-next v11 08/13] netlink: specs: add ethnl PHY_GET command set Maxime Chevallier
2024-04-04  9:29   ` Maxime Chevallier
2024-04-06 16:14   ` Andrew Lunn
2024-04-06 16:14     ` Andrew Lunn
2024-04-04  9:29 ` [PATCH net-next v11 09/13] net: ethtool: plca: Target the command to the requested PHY Maxime Chevallier
2024-04-04  9:29   ` Maxime Chevallier
2024-04-06 16:00   ` Andrew Lunn
2024-04-06 16:00     ` Andrew Lunn
2024-04-04  9:30 ` [PATCH net-next v11 10/13] net: ethtool: pse-pd: " Maxime Chevallier
2024-04-04  9:30   ` Maxime Chevallier
2024-04-06 16:00   ` Andrew Lunn
2024-04-06 16:00     ` Andrew Lunn
2024-04-04  9:30 ` [PATCH net-next v11 11/13] net: ethtool: cable-test: " Maxime Chevallier
2024-04-04  9:30   ` Maxime Chevallier
2024-04-06 16:00   ` Andrew Lunn
2024-04-06 16:00     ` Andrew Lunn
2024-04-04  9:30 ` [PATCH net-next v11 12/13] net: ethtool: strset: Allow querying phy stats by index Maxime Chevallier
2024-04-04  9:30   ` Maxime Chevallier
2024-04-06 16:01   ` Andrew Lunn
2024-04-06 16:01     ` Andrew Lunn
2024-04-04  9:30 ` [PATCH net-next v11 13/13] Documentation: networking: document phy_link_topology Maxime Chevallier
2024-04-04  9:30   ` Maxime Chevallier
2024-04-06 16:07   ` Andrew Lunn
2024-04-06 16:07     ` Andrew Lunn
2024-04-06 17:30 ` [PATCH net-next v11 00/13] Introduce PHY listing and link_topology tracking patchwork-bot+netdevbpf
2024-04-06 17:30   ` patchwork-bot+netdevbpf
2024-04-08 14:32   ` Maxime Chevallier
2024-04-08 14:32     ` Maxime Chevallier
2024-04-08 23:50     ` Andrew Lunn
2024-04-08 23:50       ` Andrew Lunn
2024-04-09  7:22       ` Maxime Chevallier
2024-04-09  7:22         ` Maxime Chevallier

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=20240410101627.53bfdebf@device-28.home \
    --to=maxime.chevallier@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=christophe.leroy@csgroup.eu \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=herve.codina@bootlin.com \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=kabel@kernel.org \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mwojtas@chromium.org \
    --cc=nathan@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicveronese@gmail.com \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=piergiorgio.beruto@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vladimir.oltean@nxp.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.