From owner-freebsd-usb@FreeBSD.ORG Sun Nov 29 02:50:03 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77469106566B for ; Sun, 29 Nov 2009 02:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 64CA18FC0A for ; Sun, 29 Nov 2009 02:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nAT2o3k1086306 for ; Sun, 29 Nov 2009 02:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nAT2o3L7086305; Sun, 29 Nov 2009 02:50:03 GMT (envelope-from gnats) Date: Sun, 29 Nov 2009 02:50:03 GMT Message-Id: <200911290250.nAT2o3L7086305@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Brett Glass Cc: Subject: Re: usb/140883: [axe] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brett Glass List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2009 02:50:03 -0000 The following reply was made to PR usb/140883; it has been noted by GNATS. From: Brett Glass To: bug-followup@FreeBSD.org Cc: sub.mesa@gmail.com Subject: Re: usb/140883: [axe] USB gigabit ethernet hangs after short period of traffic Date: Sat, 28 Nov 2009 19:04:49 -0700 The reason why the vendor name and device name is not appearing is that the USB_VERBOSE option was not included in the configuration of the 8.0-RELEASE GENERIC kernel. The USB_VERBOSE option should be included in GENERIC. Otherwise, any USB device whose driver follows the proper coding convention -- that is, placing vendor and product information in /sys/usb/usbdevs rather than in the driver itself -- will not print the name of the vendor or device. The failure to print the name has nothing to do with the malfunction in the device, which may be due to overruns. (The buffer size currently allowed in the driver -- only 4K -- is extremely small.) --Brett Glass