Lots of "eth0: link up messages" for some reason?

Running unRaid 4.7, Biostar TA870U3+ mobo. Has a Realtek RTL 8111E controller. Just got my current config up and running on this board last night. Previously on an older mobo with no issues...

For some reason been seeing this come up a bunch while running a tail command...

Apr 17 16:35:18 Tower kernel: r8169: eth0: link up
Apr 17 16:35:49 Tower last message repeated 3 times
Apr 17 16:36:55 Tower last message repeated 23 times
Apr 17 16:37:56 Tower last message repeated 15 times
Apr 17 16:38:57 Tower last message repeated 9 times
Apr 17 16:40:02 Tower last message repeated 9 times
Apr 17 16:44:55 Tower last message repeated 9 times
Apr 17 16:46:05 Tower last message repeated 10 times
Apr 17 16:47:08 Tower last message repeated 10 times
Apr 17 16:47:09 Tower last message repeated 2 times

Network is up, seems stable - just wondering why this message is popping up? Or is it just one of those "informational" messages?  

Thanks,

Shawn

Edit - seems to only occur while copying data TO the server. Streaming content off the server does not generate these...

syslog.txt

Hi All,

I've just noticed mine doing the same thing.

Copying from windows 7 64 bit is also a bit slower, showing around 10MB/sec

Thanks Josh

Hey Josh,

  Read up my other post here. You can also search for Realtek and such. All seem to be related to realtek 8111C/D/E chipsets. More testing I did found in Windows 7, it actually detects the chipset different, so I don't think it is the chipset specifically, but the driver in 4.7 used for the chipset. Maybe 5bx will work better. Most of us that got that error message also experience random freezes. Disable the onboard, add in a PCI or PCI-E nic and all is good.

Shawn

Thanks Shawn,

i've luckily (touch wood) haven't experienced any lockups.

It is the realtek 8111E with the r8169 driver. Same as you only comes up when copying, not reading. I'm also getting slower writes (about 10MBs to disk) from windows 7 whereas before I could get up to 20-30mb.

From memory I don't recall seeing this eth0 repeat error before but my memory isn't that good either.

Thanks Josh

Yep, only ever got this error when writting to the array... when writting a large amount, 10+GB, <pop>.   Hopefully your luck holds out.

Shawn

Luck ran out. Never had a problem for that last 6 months and then twice.

Damn.

Just make sure when you boot back up, run a parity sync, that will correct errors caused by the freeze.

Shawn

If you aren't already, try writing to a cache drive. That should complete faster than parity protected writes and therefore reduce the time away from servicing eth0 interrupts.

Thanks Guys,

Installed a spare intel pro GB nic I had lying around and all good now.

I'll parity check tonight too.

Josh