From: Stefan Bader <stefan.bader@canonical•com>
To: S L <sl4ever@gmail•com>, netdev <netdev@vger•kernel.org>,
Realtek linux nic maintainers <nic_swsd@realtek•com>
Cc: Francois Romieu <romieu@fr•zoreil.com>,
hayeswang <hayeswang@realtek•com>
Subject: Re: r8169 driver cause ssh failure
Date: Mon, 13 May 2013 08:11:42 +0200 [thread overview]
Message-ID: <5190841E.9090503@canonical.com> (raw)
In-Reply-To: <CA+6wjbxdbTDXmO984sM1CHFT+PJJdvS=+YmwM2iu-10Ws4WouA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next parent reply other threads:[~2013-05-13 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+6wjbxdbTDXmO984sM1CHFT+PJJdvS=+YmwM2iu-10Ws4WouA@mail.gmail.com>
2013-05-13 6:11 ` Stefan Bader [this message]
2013-05-13 6:33 ` r8169 driver cause ssh failure Francois Romieu
2013-05-13 13:24 ` Holger Hoffstaette
2013-05-14 22:54 ` Francois Romieu
2013-05-15 8:16 ` Holger Hoffstätte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5190841E.9090503@canonical.com \
--to=stefan.bader@canonical$(echo .)com \
--cc=hayeswang@realtek$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nic_swsd@realtek$(echo .)com \
--cc=romieu@fr$(echo .)zoreil.com \
--cc=sl4ever@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox