Re: r8169 Rx ERROR.

2014-05-01 Thread Francois Romieu
Udo : [...] > [354436.656703] r8169 :01:00.0 eth0: Rx ERROR. status = 342ac40d > [354615.387915] r8169 :01:00.0 eth0: Rx ERROR. status = 342cc075 > (and a load more of them) > > What is wrong? Hardware? Ethernet CRC is wrong. Which kind of 816x is it (see XID in kernel log) ? --

Re: r8169 Rx ERROR.

2014-05-01 Thread Francois Romieu
Udo udo...@xs4all.nl : [...] [354436.656703] r8169 :01:00.0 eth0: Rx ERROR. status = 342ac40d [354615.387915] r8169 :01:00.0 eth0: Rx ERROR. status = 342cc075 (and a load more of them) What is wrong? Hardware? Ethernet CRC is wrong. Which kind of 816x is it (see XID in kernel log)

r8169 Rx ERROR.

2014-04-30 Thread Udo
Hello, Found these in dmesg: [344307.090007] r8169 :01:00.0 eth0: Rx ERROR. status = 342ac0ea [344630.822919] r8169 :01:00.0 eth0: Rx ERROR. status = 342ac09d [345763.949918] r8169 :01:00.0 eth0: Rx ERROR. status = 342cc16e [347773.266930] r8169 :01:00.0 eth0: Rx ERROR. status =

r8169 Rx ERROR.

2014-04-30 Thread Udo
Hello, Found these in dmesg: [344307.090007] r8169 :01:00.0 eth0: Rx ERROR. status = 342ac0ea [344630.822919] r8169 :01:00.0 eth0: Rx ERROR. status = 342ac09d [345763.949918] r8169 :01:00.0 eth0: Rx ERROR. status = 342cc16e [347773.266930] r8169 :01:00.0 eth0: Rx ERROR. status =