Bug 113498
Summary: | modules.dep points to the wrong driver | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Brian Baggett <brian> |
Component: | kernel | Assignee: | Jason Baron <jbaron> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | katzj, knoel, notting, riel |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-02-03 20:02:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brian Baggett
2004-01-14 18:29:35 UTC
I don't see this at all under e.34 or e.35 kernels. I get 3 separate line for a grep of e1000 in the modules.dep file: chai / 10# grep e1000 /lib/modules/2.4.9-e.35enterprise/modules.dep|wc -l 3 chai / 11# grep e1000 /lib/modules/2.4.9-e.35enterprise/modules.dep /lib/modules/2.4.9-e.35enterprise/kernel/drivers/addon/e1000/e1000_5043k1.o: /lib/modules/2.4.9-e.35enterprise/kernel/drivers/addon/e1000_4412k1/e1000_4412k1.o: /lib/modules/2.4.9-e.35enterprise/kernel/drivers/addon/e1000_5220k1/e1000.o: I've seen it each and every time. The hardware I'm using are Dell PowerEdge 2650's with BIOS A17 when an Intel PRO/1000 MT Dual Port Server Adapter (version on the card: 82546GB, version on the box: A85400-006) is present. They are done with a fresh kickstart via PXE boot from update 3 of RHEL v2.1. Incidentally, our tests indicate that you *must* have the card in question to get the behavior. i just installed U3, and e.34 came up fine withe the e1000 driver. i then ran up2date and rebooted into e.35, which failed to set up networking b/c the dependency metioned aboved showed up in the modules.dep file. i re-ran depmod serveral times and the dependency went away and the module loaded fine. i'm really not sure why depmod is producing different results. Workaround to be applied immediately after updating to the 2.4.9-e.35 enterprise kernel: FILE=/lib/modules/2.4.9-e.35enterprise/modules.dep cp $FILE $FILE.save sed -e ' /\/lib\/modules\/2.4.9-e.35enterprise\/kernel\/drivers\/addon\/e1000_5220k1\/e10 00.o:/{ i \ /lib/modules/2.4.9-e.35enterprise/kernel/drivers/addon/e1000_5220k1/e1000.o: d } ' $FILE.save > $FILE thanks for helping us get to the bottom of this. The issue will be fixed in the next kernel update, which should be fairly soon. in the meantime, if you want to test with the release candidate its e.37 and on my ppl page, however its not an 'officially' supported kernel yet. http://people.redhat.com/~jbaron/.private/stable/2.4.9-e.37/ changing to modified state, as this issue should be resolved. An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2004-044.html |