netdev - Re: r8169 driver cause ssh failure

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-next>] [day] [month] [year] [list]

Date:	Mon, 13 May 2013 08:11:42 +0200
From:	Stefan Bader <stefan.bader@...onical.com>
To:	S L <sl4ever@...il.com>, netdev <netdev@...r.kernel.org>,
	Realtek linux nic maintainers <nic_swsd@...ltek.com>
CC:	Francois Romieu <romieu@...zoreil.com>,
	hayeswang <hayeswang@...ltek.com>
Subject: Re: r8169 driver cause ssh failure

On 12.05.2013 05:13, S L wrote:
> commit e5195c1f31f399289347e043d6abf3ffa80f0005 cause ssh KEXINIT failure.
> the hardware is ASROCK B75 PRO3. dmesg show
> 
> [    1.332961] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> [    1.333262] r8169 0000:03:00.0: irq 42 for MSI/MSI-X
> [    1.333414] r8169 0000:03:00.0 eth0: RTL8168evl/8111evl at
> 0xffffc90000024000, 11:11:11:11:11:11, XID 0c900800 IRQ 42
> [    1.333534] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes,
> tx checksumming: ko]
> 
> lspci -vn show
> 
> 03:00.0 0200: 10ec:8168 (rev 06)
>         Subsystem: 1849:8168
> 

That does not contain much detail information. Also its not too helpful to send
such reports only to one person. I did not see ssh problems on my tests but that
could be a different configuration/environment.

-Stefan


Download attachment "signature.asc" of type "application/pgp-signature" (900 bytes)