netdev - Re: Realtek RTL-8169 having receive errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080325221050.GA2277@electric-eye.fr.zoreil.com>
Date:	Tue, 25 Mar 2008 23:10:50 +0100
From:	Francois Romieu <romieu@...zoreil.com>
To:	Avuton Olrich <avuton@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Realtek RTL-8169 having receive errors

Avuton Olrich <avuton@...il.com> :
[...]
> On my production server, I recently updated to the latest git at the
> time and I'm getting receive errors. I'd like to try to minimize the
> resets, but I'd also like to help track down this problem. Is there a
> way I can debug this, rather then downgrading back to 2.6.22.x (the
> stable kernels in between didn't work for different reasons). Thanks!
[...]
> On device:
> eth1      Link encap:Ethernet  HWaddr 00:14:85:35:CE:4D
>           inet addr:10.0.0.1  Bcast:10.0.0.0  Mask:255.255.0.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:101004007 errors:106876 dropped:0 overruns:0 frame:106876

Please increase the device verbosity level ('ethtool -s eth1 msglvl 255')
and send what appears in dmesg.

Otherwise dmesg from boot, ethtool -S output and /proc/interrupts content
for both a working 2.6.22.x and latest git could be interesting but they
may be harder to collect with a production server.

Trying the 2.6.23 driver with a 2.6.22.x kernel would help narrow the
regression too.

-- 
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html