From: Norbert Jurkeit <norbert.jurkeit@web.de>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Frank Crawford <frank@crawford.emu.id.au>
Subject: Re: [PATCH net] net: phy: replace preliminary fix for PHY driver sometimes not binding to the device
Date: Sat, 29 Dec 2018 17:59:37 +0100 [thread overview]
Message-ID: <6e15bb11-fa63-bd4e-4040-7dd4af878c4e@web.de> (raw)
In-Reply-To: <480f5f57-0193-aafd-1382-46f3f23701cb@gmail.com>
Am 29.12.18 um 16:44 schrieb Heiner Kallweit:
>
> I don't think this patch can have any impact on the issue. Maybe WoL is still active from previous test?
> Manual WoL settings may survive a reboot, you can disable WoL by "ethtool -s <if> wol d".
In theory I agree, but we have seen before that it can not be predicted
or logically explained which kernel build suffers from the issue or does
not. WoL is definitely off. When it was enabled, the LED already turned
on with the BIOS diagnostics screen and not at the end of the boot
process as observed with the patched kernel.
>
> What could be helpful in addition: I provided a patch with some debug output in comment 106
> in the bug ticket (https://bugzilla.redhat.com/show_bug.cgi?id=1650984).
> If you could apply this, trigger a fail scenario, and attach the full dmesg to the bug ticket.
I just tried the Fedora kernel provided in comment 107. Unfortunately
the fault neither shows up with this kernel nor with the stock Fedora
kernel 4.19.12 it is based on. I will further try to find a kernel which
fails to bring up the link AND provides some useful debug information
but can't anticipate if and when.
> Thanks a lot!
You are welcome ;-)
next prev parent reply other threads:[~2018-12-29 16:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 11:21 [PATCH net] net: phy: replace preliminary fix for PHY driver sometimes not binding to the device Heiner Kallweit
2018-12-25 15:17 ` Heiner Kallweit
2018-12-28 21:02 ` David Miller
2018-12-28 21:56 ` Heiner Kallweit
2018-12-29 2:42 ` Florian Fainelli
2018-12-29 2:48 ` Florian Fainelli
2018-12-29 9:45 ` Heiner Kallweit
2018-12-29 11:46 ` Norbert Jurkeit
2018-12-29 11:54 ` Heiner Kallweit
2018-12-29 13:27 ` Norbert Jurkeit
2018-12-29 13:55 ` Heiner Kallweit
2018-12-29 15:31 ` Norbert Jurkeit
2018-12-29 15:44 ` Heiner Kallweit
2018-12-29 16:59 ` Norbert Jurkeit [this message]
2019-01-06 15:45 ` Heiner Kallweit
2019-01-03 20:13 ` Heiner Kallweit
2018-12-29 9:33 ` 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=6e15bb11-fa63-bd4e-4040-7dd4af878c4e@web.de \
--to=norbert.jurkeit@web.de \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=frank@crawford.emu.id.au \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).