All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Norbert Jurkeit <norbert.jurkeit@web.de>,
	nic_swsd@realtek.com, Florian Fainelli <f.fainelli@gmail.com>,
	davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, michael.wiktowy@gmail.com,
	jcline@redhat.com, marc.c.dionne@gmail.com
Subject: Re: Issue with RTL8111 NIC after upgrade to kernel 4.19
Date: Wed, 21 Nov 2018 21:20:34 +0100	[thread overview]
Message-ID: <20181121202034.GA10697@lunn.ch> (raw)
In-Reply-To: <38dad61b-bc7f-7038-6d1b-f5c4afe3841c@gmail.com>

> request_module() is supposed to be synchronous, however after some
> reading this may not be 100% guaranteed. Maybe the module init
> function on some systems isn't finished yet when request_module()
> returns. As a result the genphy driver may be used instead of
> the PHY version-specific driver.

Hi Heiner

That would be true for all PHYs i think. We would of noticed this
problem with other systems using other PHY drivers.

	Andrew

  reply	other threads:[~2018-11-21 20:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21 10:51 Issue with RTL8111 NIC after upgrade to kernel 4.19 Norbert Jurkeit
2018-11-21 19:57 ` Heiner Kallweit
2018-11-21 20:20   ` Andrew Lunn [this message]
2018-11-21 20:32     ` Heiner Kallweit
2018-11-21 20:49       ` Heiner Kallweit
2018-11-21 20:52         ` Heiner Kallweit
2018-11-21 21:53           ` Marc Dionne
2018-11-21 22:28             ` Heiner Kallweit
2018-11-21 23:13               ` Marc Dionne
2018-11-22 18:17                 ` Heiner Kallweit
2018-11-22 18:57                   ` Andrew Lunn
2018-11-22 19:48                     ` Heiner Kallweit
2018-11-22 19:29                   ` Marc Dionne
2018-11-22 19:53                     ` Heiner Kallweit

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=20181121202034.GA10697@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=jcline@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.c.dionne@gmail.com \
    --cc=michael.wiktowy@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=norbert.jurkeit@web.de \
    /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.