Using the r8169 driver in 2.6.35-2.6.37 I get the following errors when sending a large amount of data:
Feb 8 22:40:16 codis kernel: [47801.730128] NOHZ: local_softirq_pending 08
Feb 8 22:50:22 codis kernel: [48407.812624] r8169 0000:05:00.0: eth0: link up
Feb 8 22:50:22 codis kernel: [48407.812638] NOHZ: local_softirq_pending 08
Feb 8 22:58:13 codis kernel: [48878.640170] r8169 0000:05:00.0: eth0: link up
Feb 8 22:58:13 codis kernel: [48878.640182] NOHZ: local_softirq_pending 08
Feb 8 23:00:39 codis kernel: [49024.430358] r8169 0000:05:00.0: eth0: link up
Feb 8 23:00:39 codis kernel: [49024.430374] NOHZ: local_softirq_pending 08
Feb 8 23:03:00 codis kernel: [49165.080070] r8169 0000:05:00.0: eth0: link up
Tested 2 hosts, at about 300-400mb/s, no errors. On another host where I can hit 800-900mb/s with the realtek r8168 driver module.
With the 8169 module, with the above error messages, I can only average around 170mb/s or so.
r8169 0000:05:00.0: eth0: RTL8168b/8111b at 0xffffc90011824000, 20:cf:30:76:ff:15, XID 0c200000 IRQ 43
This is a R8111E chip on an Asus M4A89GTD Pro/USB3 board.
lspci -nn output:
05:00.0 Ethernet controller : Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
Was about to try this patch (http://www.spinics.net/lists/linux-net/msg17539.html), but found the Realtek driver worked as well. Will try it in a day or two and report back.
Oops, can someone reassign to Drivers->Network? I don't seem to have the privileges necessary to reassign.
Created attachment 48682 [details]
Fatal cast error
The first patch above is not needed for your 8168 revision if
you want to try current kernel -git (as of -rc6) but it should
avoid collateral damages with innocent testers.
I'm hitting a more serious issue here, but with the same output in kernel log.
kernel is 2.6.38 vanilla
Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Just now I was piping some data from one machine to this one through a ssh tunnel. The remote machine is also connected via GBit network, like this machine is.
Anyway, suddenly the system just instantly rebooted -- display went black (first I thought I did exhaust the battery) and soon the BIOS status appeared.
Forgot to add that the affected system is a Fujitsu Lifebook A530.
This patch doesn't work against 2.6.35 (function being patched doesn't exist!), can you provide a patch for 2.6.35? I'll look into a more recent kernel when I have more time as well.
(In reply to comment #3)
> The first patch above is not needed for your 8168 revision if
> you want to try current kernel -git (as of -rc6) but it should
> avoid collateral damages with innocent testers.
Still occurs with vanilla 18.104.22.168.
And more triaging in this bug:
This XID 0c200000 should be correctly recognized but the needed bits are in
David Miller's net-next tree.
Some related comments may be found in :
It should not be possible to trigger local_softirq_pending warnings with
current 3.5-rc since 7dbb491878a2c51d372a8890fa45a8ff80358af1.
Please update status if needed.