View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000809 | channel: elrepo/el7 | kmod-e1000e | public | 2017-12-29 10:34 | 2018-02-06 01:17 |
| Reporter | rsantos | Assigned To | toracat | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0000809: Version 3.3.5.10-1.el7_4 does not load on latest 7.4 CentOS kernel | ||||
| Description | After updating to the latest kernel version X on CentOS 7.4, the kernel will not load the module present on kmod-e1000e-3.3.5.10-1.el7_4.elrepo.x86_64.rpm. It exits with the following error: Request for unknown module key 'The ELRepo Project (http://elrepo.org): ELRepo.org Secure Boot Key: f365ad3481a7b20e3427b61b2a26635b83fe427b' err -11 e1000e: Unknown symbol ptp_clock_index (err 0) e1000e: Unknown symbol ptp_clock_register (err 0) e1000e: Unknown symbol ptp_clock_unregister (err 0) I have managed to recompile the same SRPM on the newer kernel, and only adjusted the kernel path and it's working again. Should another rpm be built for this, or is there any other way? Thank you, Rui | ||||
| Additional Information | CentOS version: 7.4 Kernel version: 3.10.0-693.11.1.el7.x86_64 | ||||
| Tags | No tags attached. | ||||
| Reported upstream | |||||
|
|
Can you try the following commands to load the e1000e module? modprobe pps_core modprobe ptp insmod /lib/modules/3.10.0-693.el7.x86_64/extra/e1000e/e1000e.ko (You can ignore the SecureBoot-related message) |
|
|
Loading the modules manually works if, after that, you use insmod to load the e1000e module directly. But a simple modprobe e1000e will still load the 3.2.6-k version, despite the kmod being present on the weak-updates, being correctly linked Hoppe this helps. Let me know if you need anything else. |
|
|
Thanks for the note. Your original errors (Unknown symbol ptp_xxx etc) indicated lack of the ptp_xx modules that are required by e1000e. Now, the e1000e.ko file in the weak-updates directory not being used is the issue that needs to be dealt with. We will investigate it. |
|
|
Turns out this is a problem with the current version of the kmod package ( kmod-20-15.el7_4.6 ): https://bugzilla.redhat.com/show_bug.cgi?id=1522994 I believe the patched version gets released soon. |
|
|
it was fixed in kmod-20-15.el7_4.7 : https://access.redhat.com/errata/RHBA-2018:0159 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-12-29 10:34 | rsantos | New Issue | |
| 2017-12-29 10:34 | rsantos | Status | new => assigned |
| 2017-12-29 10:34 | rsantos | Assigned To | => toracat |
| 2017-12-30 15:03 | toracat | Note Added: 0005647 | |
| 2018-01-02 02:38 | rsantos | Note Added: 0005648 | |
| 2018-01-02 10:18 | toracat | Note Added: 0005649 | |
| 2018-01-02 11:12 | toracat | Note Added: 0005650 | |
| 2018-02-06 01:17 | toracat | Note Added: 0005697 | |
| 2018-02-06 01:17 | toracat | Status | assigned => resolved |
| 2018-02-06 01:17 | toracat | Resolution | open => fixed |
