Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S941208AbcKXS6j (ORCPT ); Thu, 24 Nov 2016 13:58:39 -0500 Received: from pb-sasl1.pobox.com ([64.147.108.66]:61446 "EHLO sasl.smtp.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935677AbcKXS6h (ORCPT ); Thu, 24 Nov 2016 13:58:37 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject:to :references:cc:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sasl; b=QVXHJB ADNbwPPcQgcGIP3ObzypKyvCu6LZ6IWeMMko50ebvJ+fOSK38BVF/kBaq24sdw61 B3zQKUw5wfHNEKuUbbnlCwLqrBz6R7fndW25UQp/nRJo8FSjLu7QYUCpdw1LskTM 6o60bvQCI7qMPSnIhihjaclShij1UxH53s4OE= Subject: Re: [PATCH net 1/2] r8152: fix the sw rx checksum is unavailable To: Greg KH References: <95fa9f67-3af6-6749-0e2b-c95406486f7d@pobox.com> <0835B3720019904CB8F7AA43166CEEB201055ED8@RTITMBSV03.realtek.com.tw> <20161124.112152.692025478489876693.davem@davemloft.net> <23e0c132-8844-0a34-3e0b-e412f76493ba@pobox.com> <20161124184253.GA23483@kroah.com> Cc: David Miller , hayeswang@realtek.com, netdev@vger.kernel.org, nic_swsd@realtek.com, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org From: Mark Lord Message-ID: Date: Thu, 24 Nov 2016 13:58:34 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161124184253.GA23483@kroah.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 002F5E3C-B278-11E6-AF34-B2316462E9F6-82205200!pb-sasl1.pobox.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 865 Lines: 20 On 16-11-24 01:42 PM, Greg KH wrote: > > Have you tried using usbmon? This system is running rootfs over NFS, so usbmon isn't realistically going to be usable in that scenario without a lot of reconfiguration of the setup (which in itself might obscure the original problem). There is a hardware USB analyzer in the building though. But it requires a MS-Windows machine (very scarce here, I don't have one) for the incredibly user-unfriendly software. I'm not sure if it can be setup to stop the trace somehow at the right point either, as it takes overnight runs usually to catch an occurrence of the issue. I also seem to recall that it only exports data captures in a proprietary format that only that brand of software/device can read, but perhaps that might not be true. Would still need to find a MS-Windows machine/license to even check it out though.