View Issue Details

IDProjectCategoryView StatusLast Update
0000846channel: elrepo/el7kmod-e1000epublic2018-05-03 12:31
Reporterstodola Assigned Topperry  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Summary0000846: Failed dependency with kernel 3.10.0-862
DescriptionMy repo verification is failing on kmod-e1000e-3.3.5.10-1.el7_4.elrepo.x86_64 against kernel 3.10.0-862.
Hoping a recompile will take care of it. Also, there is a newer e1000e upstream if anyone cares.
Additional Informationpackage: kmod-e1000e-3.3.5.10-1.el7_4.elrepo.x86_64 from build
  unresolved deps:
     kernel(timecounter_read) = 0:0xc542933a
     kernel(timecounter_init) = 0:0x99840d00
     kernel(timecounter_cyc2time) = 0:0xa8b76a68
     kernel(napi_complete_done) = 0:0x905307be
TagsNo tags attached.
Reported upstream

Activities

pperry

2018-05-02 11:19

administrator   ~0005809

Yes, kmod-e1000e will need rebuilding against the el7.5 kernel.

However, I was looking at the e1000e driver last week, and even though the version number of this kmod driver is newer, the native kernel driver is actually more recent and has support for a greater number of devices. Consequently, we were considering deprecating the elrepo kmod driver in favour of using the kernel driver, unless anyone has a reason for us to continue offering kmod-e1000e.

Have you tried the distro driver? I've been using it with an Intel I219-V device for the last year and it's been very stable for me.

So, is there a compelling reason for us to continue to offer kmod-e1000e over and above using the kernel driver?

stodola

2018-05-02 15:17

reporter   ~0005820

I have been using the kmod-e1000e due to past experiences, mostly with EL5 not keeping up with chipset support. When we moved to EL7, I instinctively continued to use the ELrepo package.

If the native distro driver is doing the job, I don't see a reason to continue offering the package. Out of curiosity, why was the kmod-e1000e offered by ELrepo for EL7 to begin with? Just a continuation from previous point releases (4,5,6)?

I will re-test my hardware using the distro driver and report back.

toracat

2018-05-02 17:07

administrator   ~0005821

Because the version number of our kmod (3.3.5) was newer than the in-kernel one (3.2.6-k), we thought it was worthwhile to offer that version. It is only recent that we realized that the in-kernel driver was actually "newer".

stodola

2018-05-03 10:03

reporter   ~0005822

I have just tested and everything is working well with the distro driver. I see no reason to continue the kmod-e1000e here at this time.

pperry

2018-05-03 12:31

administrator   ~0005826

Thanks.

Closing this bug. I will remove kmod-e1000e from the repository (it will still be available in the archive if required).

Issue History

Date Modified Username Field Change
2018-05-02 09:22 stodola New Issue
2018-05-02 09:22 stodola Status new => assigned
2018-05-02 09:22 stodola Assigned To => toracat
2018-05-02 11:19 pperry Note Added: 0005809
2018-05-02 11:20 pperry Assigned To toracat => pperry
2018-05-02 15:17 stodola Note Added: 0005820
2018-05-02 17:07 toracat Note Added: 0005821
2018-05-03 10:03 stodola Note Added: 0005822
2018-05-03 12:31 pperry Note Added: 0005826
2018-05-03 12:31 pperry Status assigned => resolved
2018-05-03 12:31 pperry Resolution open => fixed