netdev - Re: [PATCH net] net: phy: replace preliminary fix for PHY driver sometimes not binding to the device

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] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 29 Dec 2018 17:59:37 +0100
From:   Norbert Jurkeit <norbert.jurkeit@....de>
To:     Heiner Kallweit <hkallweit1@...il.com>
Cc:     Florian Fainelli <f.fainelli@...il.com>,
        Andrew Lunn <andrew@...n.ch>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Frank Crawford <frank@...wford.emu.id.au>
Subject: Re: [PATCH net] net: phy: replace preliminary fix for PHY driver
 sometimes not binding to the device

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 ;-)