All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
	bcm-kernel-feedback-list@broadcom.com,
	linux-rpi-kernel@lists.infradead.org,
	Daniel Wagner <dwagner@suse.de>
Subject: Re: lan78xx and phy_state_machine
Date: Tue, 15 Oct 2019 02:14:59 +0200	[thread overview]
Message-ID: <20191015001459.GI19861@lunn.ch> (raw)
In-Reply-To: <20191014163004.GP25745@shell.armlinux.org.uk>

On Mon, Oct 14, 2019 at 05:30:04PM +0100, Russell King - ARM Linux admin wrote:
> On Mon, Oct 14, 2019 at 04:06:04PM +0200, Daniel Wagner wrote:
> > Hi,
> > 
> > I've trying to boot a RPi 3 Model B+ in 64 bit mode. While I can get
> > my configuratin booting with v5.2.20, the current kernel v5.3.6 hangs
> > when initializing the eth interface.
> > 
> > Is this a know issue? Some configuration issues?
> 
> I don't see any successfully probed ethernet devices in the boot log, so
> I've no idea which of the multitude of ethernet drivers to look at.

Hi Russell

> > [    3.281367] usb 1-1.1.1: new high-speed USB device number 4 using dwc2
> > [    3.652279] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed

This is the Ethernet driver which makes most sense.

> > [    3.663653] libphy: lan78xx-mdiobus: probed

And this fits with a PHY device being probed.

But it does pass a adjust_link callback to phy_connect_direct(). So
this is a bit odd. I don't see anything obviously kicking off the
state machine until the device is opened. And as you said, i don't
think it is even registered yet.

      Andrew

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

  parent reply	other threads:[~2019-10-15 12:47 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 14:06 lan78xx and phy_state_machine Daniel Wagner
2019-10-14 14:32 ` Daniel Wagner
2019-10-14 18:15   ` Stefan Wahren
2019-10-14 19:28     ` Daniel Wagner
2019-10-14 16:30 ` Russell King - ARM Linux admin
2019-10-14 19:25   ` Daniel Wagner
2019-10-14 19:51     ` Stefan Wahren
2019-10-14 19:51       ` Stefan Wahren
2019-10-14 20:20       ` Heiner Kallweit
2019-10-14 20:20         ` Heiner Kallweit
2019-10-14 22:12         ` Russell King - ARM Linux admin
2019-10-14 22:12           ` Russell King - ARM Linux admin
2019-10-15 19:38           ` Heiner Kallweit
2019-10-15 19:38             ` Heiner Kallweit
2019-10-15 22:09             ` Russell King - ARM Linux admin
2019-10-15 22:09               ` Russell King - ARM Linux admin
2019-10-16 15:36               ` Andrew Lunn
2019-10-16 15:36                 ` Andrew Lunn
2019-10-16  5:48             ` Stefan Wahren
2019-10-16  5:48               ` Stefan Wahren
2019-10-15  0:14   ` Andrew Lunn [this message]
2019-10-14 23:53 ` Andrew Lunn
2019-10-15  0:53 ` Andrew Lunn
2019-10-15 17:16   ` Daniel Wagner
2019-10-15 17:16     ` Daniel Wagner
2019-10-16 14:25     ` Daniel Wagner
2019-10-16 14:25       ` Daniel Wagner
2019-10-16 15:51       ` Andrew Lunn
2019-10-16 15:51         ` Andrew Lunn
2019-10-17  6:52         ` Daniel Wagner
2019-10-17  6:52           ` Daniel Wagner
2019-10-17 13:15           ` Andrew Lunn
2019-10-17 13:15             ` Andrew Lunn
2019-10-17 17:05           ` Stefan Wahren
2019-10-17 17:05             ` Stefan Wahren
2019-10-17 17:41             ` Daniel Wagner
2019-10-17 17:41               ` Daniel Wagner
2019-10-17 17:52               ` Stefan Wahren
2019-10-17 17:52                 ` Stefan Wahren
2019-10-17 18:14                 ` Daniel Wagner
2019-10-17 18:14                   ` Daniel Wagner
2019-10-17 18:25                 ` Andrew Lunn
2019-10-17 18:25                   ` Andrew Lunn

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=20191015001459.GI19861@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dwagner@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    /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.