Bug 125923
Summary: | Bringing up eth0 RTL8139 nic fails with kernel version 457 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Brent Hills <bhills> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | djuran, pfrields |
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: | 2004-11-19 06:32:12 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
Brent Hills
2004-06-14 06:41:17 UTC
Continues to fail with kernel version 435 does it work if you boot with acpi=off ? Continues to fail with or without acpi=off in kernels 435 and 427. It works in 358 which I boot without any acpi options (just defaults). Manually setting a static address and routing without using dhclient also fails to create a working network connection. 'ethtool' reports the same information when booted to a working kernel as when booted to a non-functioning kernel as does 'mii-tool'. Going through messages repeatedly, I found some additional messages that are most likely meaningful. It registers the ehci_hcd to irq 11. Immediately after the "new USB bus registered assigned bus number 1". An irq 11: nobody cared! (screaming interrupt?) Stack pointer is garbage, not printing trace handlers: [<02216a58>] (usb_hcd_irq+0x0/0x4b) Disabling IRQ #11 The irq 11 nobody cared and related messages only occurs when booting with 435 and 427. The nic is also assigned to IRQ 11 later in messages and fails as described previously. My appologies for not noting this or providing the full log initially. is this still a problem in the latest errata kernels ? I can confirm I no longer have this issue with kernel-2.6.9-1.667 on Fedora Core 3. |