From: Francois Romieu <romieu@fr.zoreil.com>
To: Robert Grasso <robert.grasso@modulonet.fr>
Cc: Realtek linux nic maintainers <nic_swsd@realtek.com>,
netdev@vger.kernel.org
Subject: Re: driver r8169 suddenly failed
Date: Tue, 27 Dec 2016 01:12:48 +0100 [thread overview]
Message-ID: <20161227001248.GA20172@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <428aa40c-e313-99ae-d3ae-97b6a5ef40e4@modulonet.fr>
Robert Grasso <robert.grasso@modulonet.fr> :
[dhcp snafu]
> First of all, can you confirm that I am doing right in posting to you
> (addresses found in README.Debian) ?
It isn't completely wrong.
> If I do, can you help ? I am not very proficient with Ethernet, and I am not
> able to figure out what my provider changed : their hotline is
> underqualified, they are just able to tell that "the signal on the line is
> ok".
You're spoiled. It is more than decent for a company whose core business
used to sell cable TV.
> But if you want me to run various tests, try new versions, I would be
> glad to do so : I would appreciate if I could salvage this Shuttle.
Please try a recent stable vanilla kernel and send a complete dmesg
from boot. I need to identify the specific 816x chipset.
Then record some traffic:
# touch gonzo.pcap && tshark -w gonzo.pcap -i eth1
It should only exhibit small outgoing packets but, well, one never knows.
Check the leds activity to be sure that the network interfaces have not
been renumbered.
Use ethtool to check that tso is disabled. If it isn't, disable it.
--
Ueimor
next prev parent reply other threads:[~2016-12-27 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 8:01 driver r8169 suddenly failed Robert Grasso
2016-12-27 0:12 ` Francois Romieu [this message]
2016-12-27 7:33 ` Robert Grasso
2016-12-27 19:41 ` Robert Grasso
2016-12-27 23:12 ` Francois Romieu
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=20161227001248.GA20172@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=robert.grasso@modulonet.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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