Bug 221951
| Summary: | ETH0 stops working after update to kernel 2869 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Olaf Pasveer <olaf> | ||||||||||||||
| Component: | kernel | Assignee: | John W. Linville <linville> | ||||||||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> | ||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | medium | ||||||||||||||||
| Version: | 6 | CC: | davej, wtogami | ||||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | i686 | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2007-08-07 18:51:42 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: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Olaf Pasveer
2007-01-09 07:51:19 UTC
I'm running the i686 2.6.18-1.2869.fc6 kernel on my T43 and the tg3 ethernet device is working fine. Can you include the output of running 'lspci'? Attaching the output of 'dmesg' immediately after booting both the 2868 and 2869 kernels might be helpful as well. Please make sure to make an attempt to use the tg3 device (e.g. ifup eth0 ; ping somehost.on.your.network) before capturing the dmesg output. Created attachment 145229 [details]
Output of 'rpm -qa | grep kernel'
Created attachment 145230 [details]
Output of 'rpm -qa | grep kernel'
Created attachment 145231 [details]
Output of dmesg with kernel 2869
Created attachment 145232 [details]
Output of dmesg with kernel 2868
Created attachment 145233 [details]
Output of lspci with kernel 2869
Created attachment 145234 [details]
Output of lspci with kernel 2868
When I did a 'locate' on the tg3.ko file it could only be found within the 2868 kernel/driver/net directory. Navigating to the 2869 kernel/driver/net directory I found out, that the 'driver' directory doesn't even exist. I enclosed the output of dmesg and lspci for both kernels. Also I enclosed the output of 'rpm -qa | grep kernel' Given comment 8, I would speculate that something went wrong with your 2869 kernel rpm install. Please try removing the 2869 kernel and reinstalling it from a freshly downloaded copy of the rpm. Does that make things better? Removed the kernel and kernel-devel. After install did a yum update which now included dependencies for glibc, gcc, libgcc etc. Checking in directory /lib/modules/2.6.18-1.2869.fc6/kernel/drivers there are now various subdirectories containing (amongst others) the tg3 drivers. Thanks for your help (can be closed)! Closing as NOTABUG under the presumption that the rpm install failed due to some unidentified external event. Yesterday evening I booted into 2869 the first time and could work without any problems. This morning I booted into 2869 only to find out that the subdirectories in /lib/modules/2.6.18-1.2869.fc6/kernel are missing again. In other words my ETH0 tg3 drivers were missing as well as some other drivers. Seems that upon shutdown after using the kernel the first time these directories are deleted (for whatever reason). I can only suspect that there is _something_ configured on your system that is molesting your /lib/modules directory. This behavior is certainly not observable on any system at my disposal. I'm afraid that I'll have to ask you to perform a clean installation of FC6, then to attempt to recreate this problem there. Can this issue be observed on a clean (i.e. absolute minimum configuration and no 3rd-party packages) FC6 installation? Closed due to lack of response...please reopen if this can be recreated with F7 installation. |