This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1797406
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu Bionic)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797406
Title:
rpi3b+: ethernet not working
Status in linux package in Ubuntu:
Incomplete
Status in linux-raspi2 package in Ubuntu:
New
Status in linux source package in Bionic:
Incomplete
Status in linux-raspi2 source package in Bionic:
New
Bug description:
Impact:
Since the release of Ubuntu-raspi2_4.15.0-1022.24, the ethernet port
of the RaspberryPi 3B+ has stopped to work: no phy interrupts are
generated when a cable is inserted, so it's like the ethernet port is
always disconnected.
The problem lies in commit 72eff2505735 ("lan78xx: Connect phy
early"), that was backported into Bionic/master (and then percolated
down into Bionic/raspi2):
" Commit 92571a1aae40 ("lan78xx: Connect phy early") moves the PHY
initialisation into lan78xx_probe, but lan78xx_open subsequently calls
lan78xx_reset. As well as forcing a second round of link negotiation,
this reset frequently prevents the phy interrupt from being generated
(even though the link is up), rendering the interface unusable.
Fix this issue by removing the lan78xx_reset call from lan78xx_open.
"
Fix:
Apply the attached patch and recompile
How to test:
Boot a patched kernel and checks if the ethernet port is working
Regression potential:
None, the attached patch is a fix for the aforementioned patch, and
fixes exactly this issue - it's upstream already and was backported
into gregkh's stable branches 4.17+.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797406/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
