[Fwd: Ethernet problem in 2895 kernel]

[Jay Cliburn]

Chuck Forsberg WA7KGX N2469R wrote:
> I have tried two or three different manufacturers'
> cards for eth0 with the same result.

What type cards?  You mention your motherboard type below (Asus A8N-E), but you 
indicate the onboard nic (eth1) isn't giving you problems.

Have you tried these PCI add-in nics in different slots?

Posting the output of dmesg and lspci would help identify which driver is in play.

> 
> I do not recall ever seeing this failure with 2869 and older kernels.
> 
> This bug has been present for the last three months.  I wonder if it has
> propagated to the commercial Linix products.
> 
> 
> ------------------------------------------------------------------------
> 
> Subject:
> Ethernet problem in 2895 kernel
> From:
> Chuck Forsberg WA7KGX N2469R <caf at omen.com>
> Date:
> Thu, 01 Feb 2007 10:11:21 -0800
> To:
> Fedora-Test-List <fedora-test-list at redhat.com>
> 
> To:
> Fedora-Test-List <fedora-test-list at redhat.com>
> 
> 
> Since updating to the FC6 386 2895 kernel I have has a number
> of partial failures of the Ethernet system under heavy load.
> System: Asus a8n-e socket 939 with 3 GB RAM running 386 FC6.
> Eth0 is a PCI 10/100 NIC, eth1 is the onboard gigabit NIC.
> NAT controlled by rc.firewall 2.4.  Eth0 connects to the
> cable modem, eth1 to the local net.
> 
> Under heavy load, the following error messages appear
> and then eth0 stops working, severing the internet connection.
> I have not seen this problem prior to the 2895 kernel.
> 
> 
> Jan 31 22:01:19 omen kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Jan 31 22:01:19 omen kernel: eth0: transmit timed out, tx_status 00
> status 8601.
> Jan 31 22:01:19 omen kernel:   diagnostics: net 0cd8 media 8880 dma
> 0000003a fifo 0000
> Jan 31 22:01:19 omen kernel: eth0: Interrupt posted but not delivered --
> IRQ blocked by another device?
> Jan 31 22:01:19 omen kernel:   Flags; bus-master 1, dirty 80(0) current
> 80(0)
> Jan 31 22:01:19 omen kernel:   Transmit list 00000000 vs. f714b200.
> Jan 31 22:01:19 omen kernel:   0: @f714b200  length 80000042 status
> 00010042
> Jan 31 22:01:19 omen kernel:   1: @f714b2a0  length 80000052 status
> 0c010052
> Jan 31 22:01:19 omen kernel:   2: @f714b340  length 80000043 status
> 0c010043
> Jan 31 22:01:19 omen kernel:   3: @f714b3e0  length 80000045 status
> 0c010045
> Jan 31 22:01:19 omen kernel:   4: @f714b480  length 80000042 status
> 00010042
> Jan 31 22:01:19 omen kernel:   5: @f714b520  length 8000004a status
> 0c01004a
> Jan 31 22:01:19 omen kernel:   6: @f714b5c0  length 8000004c status
> 0c01004c
> Jan 31 22:01:19 omen kernel:   7: @f714b660  length 8000004d status
> 0c01004d
> Jan 31 22:01:19 omen kernel:   8: @f714b700  length 80000052 status
> 0c010052
> Jan 31 22:01:19 omen kernel:   9: @f714b7a0  length 80000043 status
> 0c010043
> Jan 31 22:01:19 omen kernel:   10: @f714b840  length 80000045 status
> 0c010045
> Jan 31 22:01:19 omen kernel:   11: @f714b8e0  length 8000004a status
> 0c01004a
> Jan 31 22:01:19 omen kernel:   12: @f714b980  length 8000004c status
> 0c01004c
> Jan 31 22:01:19 omen kernel:   13: @f714ba20  length 8000004c status
> 0c01004c
> Jan 31 22:01:19 omen kernel:   14: @f714bac0  length 80000052 status
> 8c010052
> Jan 31 22:01:19 omen kernel:   15: @f714bb60  length 80000056 status
> 8c010056
> 
> 
>