Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1450365

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

From Alan Curry <rlwinm@sdf.org>
Newsgroups linux.kernel
Subject Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)
Date 2016-07-26 06:40 +0200
Message-ID <rZ2jT-5SK-1@gated-at.bofh.it> (permalink)
References <rYvHj-2kq-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

Christian Lamparter wrote:
> 
> As for carl9170: I'm not sure what the driver or firmware can do about
> this at this time. You can try to disable the hardware crypto by setting
> nohwcrypt via the module option. However, this might not do anything at all.

The nohwcrypt parameter didn't make any difference.

> > 
> > lsusb identifies my network device as:
> > 
> > Bus 005 Device 004: ID 0cf3:1002 Atheros Communications, Inc. TP-Link TL-WN821N v2 802.11n [Atheros AR9170]
> > 
> > I have version 1.9.9 of carl9170-1.fw in /lib/firmware
> Just one additional question: Is the TL-WN821N connected to a USB3 port?

It never has been before. I tried it today and it made no difference.

-- 
Alan Curry

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

PROBLEM: network data corruption (bisected to e5a4b0bb803b) Alan Curry <rlwinm@sdf.org> - 2016-07-24 05:50 +0200
  Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Christian Lamparter <chunkeey@googlemail.com> - 2016-07-24 19:50 +0200
    Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Al Viro <viro@ZenIV.linux.org.uk> - 2016-07-24 21:10 +0200
      Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Alan Curry <rlwinm@sdf.org> - 2016-07-26 07:00 +0200
        Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Christian Lamparter <chunkeey@googlemail.com> - 2016-07-26 16:10 +0200
          Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) alexmcwhirter@triadic.us - 2016-07-26 20:30 +0200
            Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Kalle Valo <kvalo@codeaurora.org> - 2016-07-27 08:40 +0200
          Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Alan Curry <rlwinm@sdf.org> - 2016-07-27 03:20 +0200
      Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Alan Curry <rlwinm@sdf.org> - 2016-07-27 12:40 +0200
        Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) alexmcwhirter@triadic.us - 2016-07-27 20:20 +0200
          Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) alexmcwhirter@triadic.us - 2016-07-28 01:20 +0200
            Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) David Miller <davem@davemloft.net> - 2016-07-28 01:50 +0200
              Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) alexmcwhirter@triadic.us - 2016-07-28 02:40 +0200
                Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Al Viro <viro@ZenIV.linux.org.uk> - 2016-07-28 03:30 +0200
                Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Alan Curry <rlwinm@sdf.org> - 2016-08-03 06:00 +0200
                Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Christian Lamparter <chunkeey@googlemail.com> - 2016-08-03 14:50 +0200
                Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Alan Curry <rlwinm@sdf.org> - 2016-08-04 01:50 +0200
              Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Al Viro <viro@ZenIV.linux.org.uk> - 2016-07-28 02:40 +0200
    Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) Alan Curry <rlwinm@sdf.org> - 2016-07-26 06:40 +0200
    Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b) alexmcwhirter@triadic.us - 2016-07-26 06:50 +0200

csiph-web