June 10, 201214 yr Hi there i just came across a some line in my syslog and would like to know if they are normal or not: Jun 10 13:33:16 HTMS kernel: r8169 0000:02:00.0: eth0: link up Jun 10 13:33:20 HTMS last message repeated 9 times Jun 10 13:33:22 HTMS kernel: net_ratelimit: 1 callbacks suppressed Jun 10 13:33:22 HTMS kernel: r8169 0000:02:00.0: eth0: link up Jun 10 13:33:44 HTMS last message repeated 35 times Jun 10 13:33:46 HTMS kernel: net_ratelimit: 1 callbacks suppressed Jun 10 13:33:46 HTMS kernel: r8169 0000:02:00.0: eth0: link up Jun 10 13:33:51 HTMS last message repeated 9 times Jun 10 13:33:52 HTMS kernel: net_ratelimit: 1 callbacks suppressed Jun 10 13:33:52 HTMS kernel: r8169 0000:02:00.0: eth0: link up Jun 10 13:34:02 HTMS last message repeated 17 times Jun 10 13:34:04 HTMS kernel: net_ratelimit: 4 callbacks suppressed Jun 10 13:34:04 HTMS kernel: r8169 0000:02:00.0: eth0: link up Jun 10 13:34:35 HTMS last message repeated 41 times Jun 10 13:34:47 HTMS last message repeated 19 times Jun 10 13:34:48 HTMS kernel: net_ratelimit: 1 callbacks suppressed Jun 10 13:34:48 HTMS kernel: r8169 0000:02:00.0: eth0: link up Jun 10 13:35:20 HTMS last message repeated 44 times Jun 10 13:35:36 HTMS last message repeated 25 times Jun 10 13:35:38 HTMS kernel: net_ratelimit: 4 callbacks suppressed Jun 10 13:35:38 HTMS kernel: r8169 0000:02:00.0: eth0: link up Jun 10 13:35:41 HTMS last message repeated 9 times Jun 10 13:35:43 HTMS kernel: net_ratelimit: 4 callbacks suppressed Jun 10 13:35:43 HTMS kernel: r8169 0000:02:00.0: eth0: link up Jun 10 13:35:48 HTMS last message repeated 9 times Jun 10 13:35:49 HTMS kernel: net_ratelimit: 1 callbacks suppressed Jun 10 13:35:49 HTMS kernel: r8169 0000:02:00.0: eth0: link up Jun 10 13:36:12 HTMS last message repeated 35 times Jun 10 13:36:13 HTMS kernel: net_ratelimit: 2 callbacks suppressed Jun 10 13:36:13 HTMS kernel: r8169 0000:02:00.0: eth0: link up Jun 10 13:36:30 HTMS last message repeated 21 times In my opinion last message repeated xxx times means no good, but maybe i am just worry too much?
June 10, 201214 yr I get this too. I will be diagnosing if it is the NIC or drivers, but given now you have the same issue then I think it is drivers. (Performance is impacted due to the fact the NIC keeps (what I think is happening) crashing)
June 10, 201214 yr Author Jep i have the same problem, write speed to the cache drive drasticly slow down when that accurs (i can see the transfer speeds hopping from round 50MB/s to 200kb/s) when this happens. Till now i gthought it would have something to do with the cache drive i fitted yetsreday into my unRaid Server, but than i found these Messages. What Board are you using, or better to say what NIC?
June 11, 201214 yr Jep i have the same problem, write speed to the cache drive drasticly slow down when that accurs (i can see the transfer speeds hopping from round 50MB/s to 200kb/s) when this happens. Till now i gthought it would have something to do with the cache drive i fitted yetsreday into my unRaid Server, but than i found these Messages. What Board are you using, or better to say what NIC? Realtek 8112L IIRC. Asus M4A78LT-M
June 11, 201214 yr Author Okay than we share the same board. Are you also on RC3 or did you already try RC4? I can remember times ago unraid used the driver by Realtek to avoid problems with that NIC's, but i have no idea if this is still the case in the RC Version or if the Driver which belongs to the Kernel is used. Edit: Seems that the original r8169 driver was restored with b13, when unRaid switched to Kernel 3.1. Now we are back to Kernel 3.0 and i dont know if there was a fix in the meantime for that NIC. I dont know if there is maybe something like a backport of the 3.1 driver for Kernel 3.0. Edit2: Okay from what i have seen in another Thread there is no backport of this fixes till now to the Kernel 3.0.
June 12, 201214 yr Okay than we share the same board. Are you also on RC3 or did you already try RC4? I can remember times ago unraid used the driver by Realtek to avoid problems with that NIC's, but i have no idea if this is still the case in the RC Version or if the Driver which belongs to the Kernel is used. Edit: Seems that the original r8169 driver was restored with b13, when unRaid switched to Kernel 3.1. Now we are back to Kernel 3.0 and i dont know if there was a fix in the meantime for that NIC. I dont know if there is maybe something like a backport of the 3.1 driver for Kernel 3.0. Edit2: Okay from what i have seen in another Thread there is no backport of this fixes till now to the Kernel 3.0. I've had the issue for a while, I think b8 or something was the only version that didn't have the issue.
Archived
This topic is now archived and is closed to further replies.