Hi!
In v4.15-rc2+, network manager can not see my ethernet card, and
manual attempts to ifconfig it up did not really help, either.
Card is:
02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
Controller
Dmesg says:
dmesg | grep eth
[ 0.648931] e1000e 0000:02:00.0 eth0: (PCI Express:2.5GT/s:Width
x1) 00:16:d3:25:19:04
[ 0.648934] e1000e 0000:02:00.0 eth0: Intel(R) PRO/1000 Network
Connection
[ 0.649012] e1000e 0000:02:00.0 eth0: MAC: 2, PHY: 2, PBA No:
005302-003
[ 0.706510] usbcore: registered new interface driver cdc_ether
[ 6.557022] e1000e 0000:02:00.0 eth1: renamed from eth0
[ 6.577554] systemd-udevd[2363]: renamed network interface eth0 to
eth1
Any ideas?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On 10.12.2017 09:39, Pavel Machek wrote:
> Hi!
Hi,
> In v4.15-rc2+, network manager can not see my ethernet card, and
> manual attempts to ifconfig it up did not really help, either.
>
> Card is:
>
> 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
> Controller
>
> Dmesg says:
>
> dmesg | grep eth
> [ 0.648931] e1000e 0000:02:00.0 eth0: (PCI Express:2.5GT/s:Width
> x1) 00:16:d3:25:19:04
> [ 0.648934] e1000e 0000:02:00.0 eth0: Intel(R) PRO/1000 Network
> Connection
> [ 0.649012] e1000e 0000:02:00.0 eth0: MAC: 2, PHY: 2, PBA No:
> 005302-003
> [ 0.706510] usbcore: registered new interface driver cdc_ether
> [ 6.557022] e1000e 0000:02:00.0 eth1: renamed from eth0
> [ 6.577554] systemd-udevd[2363]: renamed network interface eth0 to
> eth1
>
> Any ideas ?
Yes , 19110cfbb34d4af0cdfe14cd243f3b09dc95b013 broke it.
See:
https://bugzilla.kernel.org/show_bug.cgi?id=198047
Fix there :
https://marc.info/?l=linux-kernel&m=151272209903675&w=2
Regards,
Gabriel C
Hi!
> >In v4.15-rc2+, network manager can not see my ethernet card, and
> >manual attempts to ifconfig it up did not really help, either.
> >
> >Card is:
> >
> >02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
> >Controller
....
> >Any ideas ?
>
> Yes , 19110cfbb34d4af0cdfe14cd243f3b09dc95b013 broke it.
>
> See:
> https://bugzilla.kernel.org/show_bug.cgi?id=198047
>
> Fix there :
> https://marc.info/?l=linux-kernel&m=151272209903675&w=2
I don't see the patch in latest mainline. Not having ethernet
is... somehow annoying. What is going on there?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
From: Pavel Machek <[email protected]>
Date: Fri, 15 Dec 2017 10:28:49 +0100
> Hi!
>
>> >In v4.15-rc2+, network manager can not see my ethernet card, and
>> >manual attempts to ifconfig it up did not really help, either.
>> >
>> >Card is:
>> >
>> >02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
>> >Controller
> ....
>> >Any ideas ?
>>
>> Yes , 19110cfbb34d4af0cdfe14cd243f3b09dc95b013 broke it.
>>
>> See:
>> https://bugzilla.kernel.org/show_bug.cgi?id=198047
>>
>> Fix there :
>> https://marc.info/?l=linux-kernel&m=151272209903675&w=2
>
> I don't see the patch in latest mainline. Not having ethernet
> is... somehow annoying. What is going on there?
Generally speaking, e1000 maintainence has been handled very poorly over
the past few years, I have to say.
Fixes take forever to propagate even when someone other than the
maintainer provides a working and tested fix, just like this case.
Jeff, please take e1000 maintainence seriously and get these critical
bug fixes propagated.
Thank you.
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Gabriel C
> Sent: Sunday, December 10, 2017 4:44 AM
> To: Pavel Machek <[email protected]>; kernel list <[email protected]>
> Cc: Kirsher, Jeffrey T <[email protected]>; intel-wired-
> [email protected]; [email protected]
> Subject: Re: v4.15-rc2 on thinkpad x60: ethernet stopped working
>
> On 10.12.2017 09:39, Pavel Machek wrote:
> > Hi!
>
> Hi,
>
> > In v4.15-rc2+, network manager can not see my ethernet card, and
> > manual attempts to ifconfig it up did not really help, either.
> >
> > Card is:
> >
> > 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
> > Controller
> >
> > Dmesg says:
> >
> > dmesg | grep eth
> > [ 0.648931] e1000e 0000:02:00.0 eth0: (PCI Express:2.5GT/s:Width
> > x1) 00:16:d3:25:19:04
> > [ 0.648934] e1000e 0000:02:00.0 eth0: Intel(R) PRO/1000 Network
> > Connection
> > [ 0.649012] e1000e 0000:02:00.0 eth0: MAC: 2, PHY: 2, PBA No:
> > 005302-003
> > [ 0.706510] usbcore: registered new interface driver cdc_ether
> > [ 6.557022] e1000e 0000:02:00.0 eth1: renamed from eth0
> > [ 6.577554] systemd-udevd[2363]: renamed network interface eth0 to
> > eth1
> >
> > Any ideas ?
>
> Yes , 19110cfbb34d4af0cdfe14cd243f3b09dc95b013 broke it.
>
> See:
> https://bugzilla.kernel.org/show_bug.cgi?id=198047
>
> Fix there :
> https://marc.info/?l=linux-kernel&m=151272209903675&w=2
>
> Regards,
>
> Gabriel C
Hi,
Digging into this, the problem is complicated. The original bug assumed behavior of the .check_for_link call, which is universally not implemented.
I think the correct fix is to revert 19110cfbb34d ("e1000e: Separate signaling for link check/link up", 2017-10-10) and find a more proper solution.
I don't think any other code which uses check_for_link expects the interface to return in the way this patch attempted.
Thanks,
Jake
> -----Original Message-----
> From: Intel-wired-lan [mailto:[email protected]] On Behalf Of
> Keller, Jacob E
> Sent: Friday, December 15, 2017 9:29 AM
> To: Gabriel C <[email protected]>; Pavel Machek <[email protected]>; kernel list
> <[email protected]>
> Cc: [email protected]; [email protected]
> Subject: Re: [Intel-wired-lan] v4.15-rc2 on thinkpad x60: ethernet stopped
> working
>
> > -----Original Message-----
> > From: [email protected] [mailto:netdev-
> [email protected]]
> > On Behalf Of Gabriel C
> > Sent: Sunday, December 10, 2017 4:44 AM
> > To: Pavel Machek <[email protected]>; kernel list <[email protected]>
> > Cc: Kirsher, Jeffrey T <[email protected]>; intel-wired-
> > [email protected]; [email protected]
> > Subject: Re: v4.15-rc2 on thinkpad x60: ethernet stopped working
> >
> > On 10.12.2017 09:39, Pavel Machek wrote:
> > > Hi!
> >
> > Hi,
> >
> > > In v4.15-rc2+, network manager can not see my ethernet card, and
> > > manual attempts to ifconfig it up did not really help, either.
> > >
> > > Card is:
> > >
> > > 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
> > > Controller
> > >
> > > Dmesg says:
> > >
> > > dmesg | grep eth
> > > [ 0.648931] e1000e 0000:02:00.0 eth0: (PCI Express:2.5GT/s:Width
> > > x1) 00:16:d3:25:19:04
> > > [ 0.648934] e1000e 0000:02:00.0 eth0: Intel(R) PRO/1000 Network
> > > Connection
> > > [ 0.649012] e1000e 0000:02:00.0 eth0: MAC: 2, PHY: 2, PBA No:
> > > 005302-003
> > > [ 0.706510] usbcore: registered new interface driver cdc_ether
> > > [ 6.557022] e1000e 0000:02:00.0 eth1: renamed from eth0
> > > [ 6.577554] systemd-udevd[2363]: renamed network interface eth0 to
> > > eth1
> > >
> > > Any ideas ?
> >
> > Yes , 19110cfbb34d4af0cdfe14cd243f3b09dc95b013 broke it.
> >
> > See:
> > https://bugzilla.kernel.org/show_bug.cgi?id=198047
> >
> > Fix there :
> > https://marc.info/?l=linux-kernel&m=151272209903675&w=2
> >
> > Regards,
> >
> > Gabriel C
>
> Hi,
>
> Digging into this, the problem is complicated. The original bug assumed behavior
> of the .check_for_link call, which is universally not implemented.
>
> I think the correct fix is to revert 19110cfbb34d ("e1000e: Separate signaling for
> link check/link up", 2017-10-10) and find a more proper solution.
>
> I don't think any other code which uses check_for_link expects the interface to
> return in the way this patch attempted.
>
> Thanks,
> Jake
>
Alternatively, we can go a step farther and make sure every implementation of .check_for_link follows the modified interface.
Thanks,
Jake
Hi!
> > > > Any ideas ?
> > >
> > > Yes , 19110cfbb34d4af0cdfe14cd243f3b09dc95b013 broke it.
> > >
> > > See:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=198047
> > >
> > > Fix there :
> > > https://marc.info/?l=linux-kernel&m=151272209903675&w=2
> > >
> > > Regards,
> > >
> > > Gabriel C
> >
> > Hi,
> >
> > Digging into this, the problem is complicated. The original bug assumed behavior
> > of the .check_for_link call, which is universally not implemented.
> >
> > I think the correct fix is to revert 19110cfbb34d ("e1000e: Separate signaling for
> > link check/link up", 2017-10-10) and find a more proper solution.
> >
> > I don't think any other code which uses check_for_link expects the interface to
> > return in the way this patch attempted.
> Alternatively, we can go a step farther and make sure every implementation of .check_for_link follows the modified interface.
>
We are at -rc3 now. Reverting 19110cfbb34d seems like good solution at
the moment.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Hi!
> >> >In v4.15-rc2+, network manager can not see my ethernet card, and
> >> >manual attempts to ifconfig it up did not really help, either.
> >> >
> >> >Card is:
> >> >
> >> >02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
> >> >Controller
> > ....
> >> >Any ideas ?
> >>
> >> Yes , 19110cfbb34d4af0cdfe14cd243f3b09dc95b013 broke it.
> >>
> >> See:
> >> https://bugzilla.kernel.org/show_bug.cgi?id=198047
> >>
> >> Fix there :
> >> https://marc.info/?l=linux-kernel&m=151272209903675&w=2
> >
> > I don't see the patch in latest mainline. Not having ethernet
> > is... somehow annoying. What is going on there?
>
> Generally speaking, e1000 maintainence has been handled very poorly over
> the past few years, I have to say.
>
> Fixes take forever to propagate even when someone other than the
> maintainer provides a working and tested fix, just like this case.
>
> Jeff, please take e1000 maintainence seriously and get these critical
> bug fixes propagated.
No response AFAICT. I guess I should test reverting
19110cfbb34d4af0cdfe14cd243f3b09dc95b013, then ask you for revert?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Dear Pavel,
On 12/10/17 09:39, Pavel Machek wrote:
> In v4.15-rc2+, network manager can not see my ethernet card, and
> manual attempts to ifconfig it up did not really help, either.
>
> Card is:
>
> 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit
> Ethernet Controller
>
> Dmesg says:
>
> dmesg | grep eth
> [ 0.648931] e1000e 0000:02:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:16:d3:25:19:04
> [ 0.648934] e1000e 0000:02:00.0 eth0: Intel(R) PRO/1000 Network Connection
> [ 0.649012] e1000e 0000:02:00.0 eth0: MAC: 2, PHY: 2, PBA No: 005302-003
> [ 0.706510] usbcore: registered new interface driver cdc_ether
> [ 6.557022] e1000e 0000:02:00.0 eth1: renamed from eth0
> [ 6.577554] systemd-udevd[2363]: renamed network interface eth0 to eth1
>
> Any ideas?
I am sorry for jumping in on this so late.
Since using a Lenovo X60t more ofter since a year or so, I experience
the issue, that the link doesn?t come up during that period occasionally
[1]. I haven?t tried the latest patches yet, but it might be unrelated.
Did you test, that removing and loading the e1000e module fixes the issue?
Additionally, I was asked privately to test the out of tree driver, but
haven?t had time yet.
> You might give the out-of-tree driver a try, you can download it here
> https://downloadcenter.intel.com/download/26549/Intel-Network-Adapter-Driver-for-PCIe-Intel-Gigabit-Ethernet-Network-Connections-Under-Linux-?product=19297
> It's version is 3.3.5, dated 8/2016
Kind regards,
Paul
[1]
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20170410/008590.html