Bug 131293
| Summary: | kernel 533 kills ethernet | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Phil Schaffner <philip.r.schaffner> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | CC: | pfrields, philip.r.schaffner, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-07-15 22:18:02 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
Phil Schaffner
2004-08-30 19:06:22 UTC
Similar (bad) results for kernel versions 538, 540, 541. Last kernel to have working Ethernet on this hardware was 526, but that broke after last yum update, even after downgrading module-init-tools. Tried FC3T2-candidate anaconda upgrade, then fresh install with no improvement. Not to state the obvious (still kernel-2.6.8-1.541) but the problem persists for FC3T2. Booted from installation CD #1 (linux acpi=off askmethod) and attempted a network install. Starts generating errors as soon as network information is entered to the installer. Wrote today's rawhide images/boot.iso to CD and attempted to boot A21p for NFS network install. Assuming that uses kernel-2.6.8-1.598 - still has problems, although the symptoms have changed. Booted with "linux noacpi" (also tried acpi=off) Entered IP, netmask, gateway, DNS info. Long pause... Finally get prompt for hostname/directory which finally fails saying "That directory could not be mounted from the server." On VC#4 one sees (allowing for typos): ... <4>3c59x: Donald Becker and others. www.scyld.com/network/vortex.html <6>0000:00:03.0: 3Com PCI 3c556B Laptop Hurricane at 0x1800. Vers LK1.1.19 <7>PCI: Setting latency timer of device 0000:00:03.0 to 64 <3>*** EEPROM MAC address in invalid. <3>3c59x: vortex_probe1 fails. Returns -22 <4>3c59x: probe of 0000:00:03.0 failed with error -22 ... stuff about ISO 9660 ... <131>Oct 8 15:53:01 loader: failed to set default route: Network is unreachable No repeating messages about "transmit timed out" as above. Kernel 2.6.8-1.603 - problems persist. FC3 final - same problem. Can't find any way to get NIC to work with recent FC kernels on this laptop. Tried building "generic" 2.6.10-rc2 kernel - without ACPI support as that has been problematic on ThinkPad A21p. Works fine. Problems must be with FC patches or build options. Let me know if info about .config used would be helpful. how do things look with the current errata kernel ? Just rebooted 2.6.9-1.6_FC2 without acpi=off. NIC did not work. Relevant bit from dmesg (very similar to previous reports): PCI: Enabling device 0000:00:03.0 (0000 -> 0003) ACPI: PCI interrupt 0000:00:03.0[A] -> GSI 11 (level, low) -> IRQ 11 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 0000:00:03.0: 3Com PCI 3c556B Laptop Hurricane at 0x1800. Vers LK1.1.19 PCI: Setting latency timer of device 0000:00:03.0 to 64 *** EEPROM MAC address is invalid. 3c59x: vortex_probe1 fails. Returns -22 3c59x: probe of 0000:00:03.0 failed with error -22 ip_tables: (C) 2000-2002 Netfilter core team ip_tables: (C) 2000-2002 Netfilter core team ACPI: PCI interrupt 0000:00:03.0[A] -> GSI 11 (level, low) -> IRQ 11 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 0000:00:03.0: 3Com PCI 3c556B Laptop Hurricane at 0x1800. Vers LK1.1.19 *** EEPROM MAC address is invalid. 3c59x: vortex_probe1 fails. Returns -22 3c59x: probe of 0000:00:03.0 failed with error -22 Should have noted in Comment #8 that the NIC does work with acpi=off, as it has for other FC2 kernels, but not for anything since FC3T1 in the FC3 series. Also took a gamble and installed kernel-2.6.9-1.681_FC3 (on FC2 system) which required updating to modutils-2.4.26-16. Same behavior as 2.6.9-1.6_FC2 (works with acpi=off - which gives me some hope of updating to FC3 on this machine with a yum upgrade). An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. Well, the behavior with acpi=off is different as far as the error output (much less) but the NIC still fails to work. Works with acpi=off, as have kernels tried since kernel-2.6.9-1.681_FC3. The system was previously upgraded to FC3 via yum as suggested above. Tried the FC4 installer for a network install and that works as long as acpi=off is used, unlike the FC3 installation kernel. Changing status to RESOLVED/CURRENTRELEASE. |