From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 00:03:22 2010 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 920341065679; Sun, 14 Nov 2010 00:03:22 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 66DFD8FC18; Sun, 14 Nov 2010 00:03:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAE03Mp8019530; Sun, 14 Nov 2010 00:03:22 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAE03MLM019514; Sun, 14 Nov 2010 00:03:22 GMT (envelope-from arundel) Date: Sun, 14 Nov 2010 00:03:22 GMT Message-Id: <201011140003.oAE03MLM019514@freefall.freebsd.org> To: rehsack@googlemail.com, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/138570: [usb67] [panic] USB mass device panics current 7.2-STABLE X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 00:03:22 -0000 Synopsis: [usb67] [panic] USB mass device panics current 7.2-STABLE State-Changed-From-To: feedback->suspended State-Changed-By: arundel State-Changed-When: Sun Nov 14 00:00:40 UTC 2010 State-Changed-Why: Originator cannot help with this PR. Changes are very good this issue was fixed with the introduction of the new USB stack (FreeBSD 8.x), but whether the panic still occurs under 7.x is unclear. http://www.freebsd.org/cgi/query-pr.cgi?pr=138570 From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 00:04:44 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 661C81065674; Sun, 14 Nov 2010 00:04:44 +0000 (UTC) Date: Sun, 14 Nov 2010 00:04:44 +0000 From: Alexander Best To: Jens Rehsack Message-ID: <20101114000444.GA31223@freebsd.org> References: <201011131435.oADEZ2HN027517@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-usb@freebsd.org Subject: Re: usb/138570: [usb67] [panic] USB mass device panics current 7.2-STABLE X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 00:04:44 -0000 On Sat Nov 13 10, Jens Rehsack wrote: > 2010/11/13 : > > Old Synopsis: [usb] [panic] USB mass device panics current 7.2-STABLE > > New Synopsis: [usb67] [panic] USB mass device panics current 7.2-STABLE > > > > State-Changed-From-To: open->feedback > > State-Changed-By: arundel > > State-Changed-When: Sat Nov 13 14:33:29 UTC 2010 > > State-Changed-Why: > > Does this panic also occur with a more recent stable snapshot? > > I'm on the road for jobs and can't test again (to busy and no time to > restore the machine in case of a panic destroys something). > I moved most tasks away from the FSBD machine meanwhile, > from my point of view this PR can be closed (no feedback from > reporter), because I can confirm that I don't have time to take > care the next 6 month. thanks for your help. i've suspended the PR. i'll close it once 7.x goes EoL, since i don't think this issue occurs under the new USb stack (FreeBSD 8.x). cheers. alex > > > Have you tried the device under FreBSD 8.x? > > No - but on NetBSD 5-CURRENT and Ubuntu 10.04, and it works > fine there. > > Best regards, > Jens > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=138570 > > -- a13x From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 01:31:43 2010 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 E0C671065672; Sun, 14 Nov 2010 01:31:43 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B59AA8FC0C; Sun, 14 Nov 2010 01:31:43 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAE1Vhdx015146; Sun, 14 Nov 2010 01:31:43 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAE1Vhgg015138; Sun, 14 Nov 2010 01:31:43 GMT (envelope-from arundel) Date: Sun, 14 Nov 2010 01:31:43 GMT Message-Id: <201011140131.oAE1Vhgg015138@freefall.freebsd.org> To: arundel@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/141777: [usb8] [rum] [patch] Support usbdevs / rum(4) for Buffalo WLI-UC-G X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 01:31:44 -0000 Old Synopsis: [rum] [patch] Support usbdevs / rum(4) for Buffalo WLI-UC-G New Synopsis: [usb8] [rum] [patch] Support usbdevs / rum(4) for Buffalo WLI-UC-G Responsible-Changed-From-To: freebsd-net->freebsd-usb Responsible-Changed-By: arundel Responsible-Changed-When: Sun Nov 14 01:29:21 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). This looks more usb related than anything else. http://www.freebsd.org/cgi/query-pr.cgi?pr=141777 From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 20:10:23 2010 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 5AF181065670; Sun, 14 Nov 2010 20:10:23 +0000 (UTC) (envelope-from brucec@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 305D78FC0A; Sun, 14 Nov 2010 20:10:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAEKANxE018218; Sun, 14 Nov 2010 20:10:23 GMT (envelope-from brucec@freefall.freebsd.org) Received: (from brucec@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAEKAMJR018187; Sun, 14 Nov 2010 20:10:22 GMT (envelope-from brucec) Date: Sun, 14 Nov 2010 20:10:22 GMT Message-Id: <201011142010.oAEKAMJR018187@freefall.freebsd.org> To: wernerleh@arcor.de, brucec@FreeBSD.org, freebsd-sysinstall@FreeBSD.org, freebsd-usb@FreeBSD.org From: brucec@FreeBSD.org Cc: Subject: Re: i386/147475: [install] FreeBSD 8.x does not install on ASUS K8N4-E Mainboard X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 20:10:23 -0000 Synopsis: [install] FreeBSD 8.x does not install on ASUS K8N4-E Mainboard State-Changed-From-To: feedback->open State-Changed-By: brucec State-Changed-When: Sun Nov 14 20:01:20 UTC 2010 State-Changed-Why: This looks like it might be a problem with probing USB. >From the screenshot Werner sent: ohci0: at device 2.0 on pci0 ohci0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0x80000000 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x80000000 pcib0: matched entry for 0.2.INTA (src \_SB_.PCI0.APCF:0) pci_link21: Picked IRQ 23 with weight 0 pcib0: slot 2 INTA routed to irq23 via \_SB_.PCI0.APCF ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 0 vector 49 ohci0: [MPSAFE] ohci0: [ITHREAD] usbus0: SMM does not respond, resetting usbus0: reset timeout ohci0: USB init failed device_attach: ohci0 attach returned 6 ehci0: at device 2.1 on pci0 ehci0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0x80000000 ehci0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0x80000000 pcib0: matched entry for 0.2.INTB (src \_SB_.PCI0.APCL:0) pci_link27: Picked IRQ 20 with weight 1 pcib0: slot 2 INTB routed to irq 20 via \_SB_.PCI0.APCL ioapic0: routing intpin 20 (PCI IRQ 20) to lapic 0 vector 49 ehci0: [MPSAFE] ehci0: [ITHREAD] [ system hangs ] Responsible-Changed-From-To: freebsd-sysinstall->freebsd-usb Responsible-Changed-By: brucec Responsible-Changed-When: Sun Nov 14 20:01:20 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). As explained in the state change section, this looks like it might be a problem with probing USB on 8.x. http://www.freebsd.org/cgi/query-pr.cgi?pr=147475 From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 20:13:22 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B333106566B for ; Sun, 14 Nov 2010 20:13:22 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.freebsd.org (Postfix) with ESMTP id ADD498FC0A for ; Sun, 14 Nov 2010 20:13:21 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=pSMQvMxz67uBPld/2YzXd4n8EUsHq22vR+JpH4ELdfA= c=1 sm=1 a=uGoALJSjcJMA:10 a=Q9fys5e9bTEA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=6I5d2MoRAAAA:8 a=rgLZsLJYFxFvymwMnzwA:9 a=2wpLJUzzQWQHz48WPFwA:7 a=z6ZsDueuHaDqVIZHw6Uam11n_2AA:4 a=PUjeQqilurYA:10 a=SV7veod9ZcQA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 48384614; Sun, 14 Nov 2010 21:13:20 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Sun, 14 Nov 2010 21:14:19 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <201011142010.oAEKAMJR018187@freefall.freebsd.org> In-Reply-To: <201011142010.oAEKAMJR018187@freefall.freebsd.org> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201011142114.19759.hselasky@c2i.net> Cc: wernerleh@arcor.de, freebsd-sysinstall@freebsd.org, brucec@freebsd.org Subject: Re: i386/147475: [install] FreeBSD 8.x does not install on ASUS K8N4-E Mainboard X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 20:13:22 -0000 On Sunday 14 November 2010 21:10:22 brucec@freebsd.org wrote: > Synopsis: [install] FreeBSD 8.x does not install on ASUS K8N4-E Mainboard > > State-Changed-From-To: feedback->open > State-Changed-By: brucec > State-Changed-When: Sun Nov 14 20:01:20 UTC 2010 > State-Changed-Why: > This looks like it might be a problem with probing USB. > > >From the screenshot Werner sent: > ohci0: at device 2.0 on pci0 > ohci0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0x80000000 > ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x80000000 > pcib0: matched entry for 0.2.INTA (src \_SB_.PCI0.APCF:0) > pci_link21: Picked IRQ 23 with weight 0 > pcib0: slot 2 INTA routed to irq23 via \_SB_.PCI0.APCF > ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 0 vector 49 > ohci0: [MPSAFE] > ohci0: [ITHREAD] > usbus0: SMM does not respond, resetting > usbus0: reset timeout > ohci0: USB init failed > device_attach: ohci0 attach returned 6 > ehci0: at device 2.1 on pci0 > ehci0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0x80000000 > ehci0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0x80000000 > pcib0: matched entry for 0.2.INTB (src \_SB_.PCI0.APCL:0) > pci_link27: Picked IRQ 20 with weight 1 > pcib0: slot 2 INTB routed to irq 20 via \_SB_.PCI0.APCL > ioapic0: routing intpin 20 (PCI IRQ 20) to lapic 0 vector 49 > ehci0: [MPSAFE] > ehci0: [ITHREAD] > [ system hangs ] > > > Responsible-Changed-From-To: freebsd-sysinstall->freebsd-usb > Responsible-Changed-By: brucec > Responsible-Changed-When: Sun Nov 14 20:01:20 UTC 2010 > Responsible-Changed-Why: > Over to maintainer(s). As explained in the state change section, this > looks like it might be a problem with probing USB on 8.x. > Try to boot having the verbose option set. --HPS From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 20:47:10 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7FBB106564A; Sun, 14 Nov 2010 20:47:10 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 6E30F8FC12; Sun, 14 Nov 2010 20:47:10 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 91658E71EC; Sun, 14 Nov 2010 20:47:09 +0000 (GMT) Received: from core.nessbank (client-86-27-19-226.glfd.adsl.virginmedia.com [86.27.19.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Sun, 14 Nov 2010 20:47:08 +0000 (GMT) From: Bruce Cran To: Hans Petter Selasky Date: Sun, 14 Nov 2010 20:47:07 +0000 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.5.2; amd64; ; ) References: <201011142010.oAEKAMJR018187@freefall.freebsd.org> <201011142114.19759.hselasky@c2i.net> In-Reply-To: <201011142114.19759.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201011142047.08138.bruce@cran.org.uk> Cc: wernerleh@arcor.de, freebsd-usb@freebsd.org, brucec@freebsd.org Subject: Re: i386/147475: [install] FreeBSD 8.x does not install on ASUS K8N4-E Mainboard X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 20:47:10 -0000 On Sunday 14 November 2010 20:14:19 Hans Petter Selasky wrote: > Try to boot having the verbose option set. That already is a verbose boot. -- Bruce Cran From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 21:19:49 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DF661065675 for ; Sun, 14 Nov 2010 21:19:49 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 023268FC0C for ; Sun, 14 Nov 2010 21:19:49 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 50215E71EC; Sun, 14 Nov 2010 21:19:48 +0000 (GMT) Received: from core.nessbank (client-86-27-19-226.glfd.adsl.virginmedia.com [86.27.19.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Sun, 14 Nov 2010 21:19:47 +0000 (GMT) From: Bruce Cran To: freebsd-usb@freebsd.org Date: Sun, 14 Nov 2010 21:19:46 +0000 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.5.2; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201011142119.46709.bruce@cran.org.uk> Cc: bzeeb+freebsd+lor@zabbadoz.net Subject: LOR: USB config SX lock vs. USB suspend and resume SX lock X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 21:19:49 -0000 I'm running -CURRENT on a laptop which has a wireless switch. When I boot with it enabled and then switch it off, the following LOR gets logged: lock order reversal: 1st 0xffffff000466d070 USB config SX lock (USB config SX lock) @ /usr/src/head/sys/dev/usb/usb_device.c:2671 2nd 0xffffff000466d090 USB suspend and resume SX lock (USB suspend and resume SX lock) @ /usr/src/head/sys/dev/usb/usb_device.c:2672 3rd 0xffffff0004501870 USB config SX lock (USB config SX lock) @ /usr/src/head/sys/dev/usb/usb_device.c:2671 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x807 _sx_xlock() at _sx_xlock+0x55 usbd_enum_lock() at usbd_enum_lock+0x2a usb_unconfigure() at usb_unconfigure+0x16a usb_free_device() at usb_free_device+0x184 uhub_detach() at uhub_detach+0x6a device_detach() at device_detach+0xa4 usb_detach_device() at usb_detach_device+0x78 usb_unconfigure() at usb_unconfigure+0x34 usb_free_device() at usb_free_device+0x184 uhub_explore() at uhub_explore+0x18e usb_bus_explore() at usb_bus_explore+0xc1 usb_process() at usb_process+0xbb fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff81238cecf0, rbp = 0 --- During boot I get the following errors logged: uhub_reattach_port: port 6 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 6 uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 2 Before the LOR, some devices get disconnected: ugen5.2: at usbus5 (disconnected) uhub7: at uhub5, port 2, addr 2 (disconnected) ugen5.3: at usbus5 (disconnected) And after, more: ugen5.4: at usbus5 (disconnected) ukbd0: at uhub7, port 2, addr 4 (disconnected) ugen5.5: at usbus5 (disconnected) ums0: at uhub7, port 3, addr 5 (disconnected) -- Bruce Cran From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 21:27:04 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28F70106564A for ; Sun, 14 Nov 2010 21:27:04 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id B086E8FC15 for ; Sun, 14 Nov 2010 21:27:03 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=vDUu4pv7IaR8DTRzVjjCCOYxZ4yAx/7/dG3VXczAVmg= c=1 sm=1 a=aFhn9fKtkHwA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=fa7RAxo4OQZFlvMMwQkA:9 a=v-Ctrk1zKviOBJAqJSwA:7 a=mJD5eabTmCjXlknfzRLU7CHI-owA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe07.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 48921851; Sun, 14 Nov 2010 22:27:02 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Sun, 14 Nov 2010 22:28:02 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <201011142119.46709.bruce@cran.org.uk> In-Reply-To: <201011142119.46709.bruce@cran.org.uk> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011142228.02765.hselasky@c2i.net> Cc: bzeeb+freebsd+lor@zabbadoz.net Subject: Re: LOR: USB config SX lock vs. USB suspend and resume SX lock X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 21:27:04 -0000 On Sunday 14 November 2010 22:19:46 Bruce Cran wrote: > I'm running -CURRENT on a laptop which has a wireless switch. > When I boot with it enabled and then switch it off, the following > LOR gets logged: Can you verify that this LOR is real, and that it is not due to SX-locks having similar names? --HPS > > lock order reversal: > 1st 0xffffff000466d070 USB config SX lock (USB config SX lock) @ > /usr/src/head/sys/dev/usb/usb_device.c:2671 2nd 0xffffff000466d090 USB > suspend and resume SX lock (USB suspend and resume SX lock) @ > /usr/src/head/sys/dev/usb/usb_device.c:2672 3rd 0xffffff0004501870 USB > config SX lock (USB config SX lock) @ > /usr/src/head/sys/dev/usb/usb_device.c:2671 KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > kdb_backtrace() at kdb_backtrace+0x37 > _witness_debugger() at _witness_debugger+0x2e > witness_checkorder() at witness_checkorder+0x807 > _sx_xlock() at _sx_xlock+0x55 > usbd_enum_lock() at usbd_enum_lock+0x2a > usb_unconfigure() at usb_unconfigure+0x16a > usb_free_device() at usb_free_device+0x184 > uhub_detach() at uhub_detach+0x6a > device_detach() at device_detach+0xa4 > usb_detach_device() at usb_detach_device+0x78 > usb_unconfigure() at usb_unconfigure+0x34 > usb_free_device() at usb_free_device+0x184 > uhub_explore() at uhub_explore+0x18e > usb_bus_explore() at usb_bus_explore+0xc1 > usb_process() at usb_process+0xbb > fork_exit() at fork_exit+0x12a > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff81238cecf0, rbp = 0 --- > > During boot I get the following errors logged: > > uhub_reattach_port: port 6 reset failed, error=USB_ERR_TIMEOUT > uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 6 > uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT > uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 2 > > Before the LOR, some devices get disconnected: > > ugen5.2: at usbus5 (disconnected) > uhub7: at uhub5, port 2, addr 2 (disconnected) > ugen5.3: at usbus5 (disconnected) > > And after, more: > > ugen5.4: at usbus5 (disconnected) > ukbd0: at uhub7, port 2, addr 4 (disconnected) > ugen5.5: at usbus5 (disconnected) > ums0: at uhub7, port 3, addr 5 (disconnected) From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 21:37:00 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 095A9106564A for ; Sun, 14 Nov 2010 21:37:00 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 9843A8FC17 for ; Sun, 14 Nov 2010 21:36:59 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id E78A7E71EC for ; Sun, 14 Nov 2010 21:36:58 +0000 (GMT) Received: from core.nessbank (client-86-27-19-226.glfd.adsl.virginmedia.com [86.27.19.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA for ; Sun, 14 Nov 2010 21:36:57 +0000 (GMT) From: Bruce Cran To: freebsd-usb@freebsd.org Date: Sun, 14 Nov 2010 21:36:57 +0000 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.5.2; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201011142136.57161.bruce@cran.org.uk> Subject: USB controller error logged when resuming after suspend X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 21:37:00 -0000 I've been trying to get my laptop working with suspend/resume. It comes back, but USB seems rather unhappy about something for a while. Despite this, plugging a flash drive in does attach to the EHCI controller at usbus6. uhci2: wake_prep disabled wake for \\_SB_.PCI0.USB1 (S3) uhci3: wake_prep disabled wake for \\_SB_.PCI0.USB2 (S3) uhci4: wake_prep disabled wake for \\_SB_.PCI0.USB3 (S3) uhci0: wake_prep disabled wake for \\_SB_.PCI0.USB4 (S3) uhci1: wake_prep disabled wake for \\_SB_.PCI0.USB5 (S3) ehci0: wake_prep disabled wake for \\_SB_.PCI0.EHC2 (S3) ehci1: wake_prep disabled wake for \\_SB_.PCI0.EHCI (S3) acpi_lid0: wake_prep enabled for \\_SB_.LID_ (S3) acpi_button0: wake_prep enabled for \\_SB_.PBTN (S3) vga0: saving 68 bytes of video state vga0: saving color palette pci0:1:0:0: Transition from D0 to D3 pci0:0:1:0: Transition from D0 to D3 uhci_interrupt: resume detect pci0:9:0:0: Transition from D0 to D3 pci0:0:28:0: Transition from D0 to D3 pci0:0:28:1: Transition from D0 to D3 pci0:12:0:0: Transition from D0 to D3 pci0:0:28:4: Transition from D0 to D3 pci0:0:26:7: Transition from D0 to D3 pci0:0:29:7: Transition from D0 to D3 ehci_interrupt: unrecoverable error, controller halted cmd=0xffffffff EHCI_CMD_ITC_1 EHCI_CMD_ITC_2 EHCI_CMD_ITC_4 EHCI_CMD_ITC_8 EHCI_CMD_ITC_16 EHCI_CMD_ITC_32 EHCI_CMD_ITC_64 EHCI_CMD_ASPME EHCI_CMD_ASPMC EHCI_CMD_LHCR EHCI_CMD_IAAD EHCI_CMD_ASE EHCI_CMD_PSE EHCI_CMD_FLS_M EHCI_CMD_HCRESET EHCI_CMD_RS sts=0xffffffff EHCI_STS_ASS EHCI_STS_PSS EHCI_STS_REC EHCI_STS_HCH EHCI_STS_IAA EHCI_STS_HSE EHCI_STS_FLR EHCI_STS_PCD EHCI_STS_ERRINT EHCI_STS_INT ien=0xffffffff frindex=0xffffffff ctrdsegm=0xffffffff periodic=0xffffffff async=0xffffffff port 1 status=0xffffffff port 2 status=0xffffffff port 3 status=0xffffffff port 4 status=0xffffffff port 5 status=0xffffffff port 6 status=0xffffffff ehci_dump_isoc: isochronous dump from frame 0x07f: ITD(0xffffff81248e3000) at 0x054b5000 next=0x05535004 status[0]=0x00000000; <> status[1]=0x00000000; <> status[2]=0x00000000; <> status[3]=0x00000000; <> status[4]=0x00000000; <> status[5]=0x00000000; <> status[6]=0x00000000; <> status[7]=0x00000000; <> bp[0]=0x00000000 addr=0x00; endpt=0x0 bp[1]=0x00000000 dir=out; mpl=0x00 bp[2..6]=0x00000000,0x00000000,0x00000000,0x00000000,0x00000000 bp_hi=0x00000000,0x00000000,0x00000000,0x00000000, 0x00000000,0x00000000,0x00000000 SITD(0xffffff8124963000) at 0x05535000 next=0x053f5002 portaddr=0x00000000 dir=out addr=0 endpt=0x0 port=0x0 huba=0x0 mask=0x00000000 status=0x00000000 <> len=0x0 back=0x00000001, bp=0x00000000,0x00000000,0x00000000,0x00000000 ehci_interrupt: blocking interrupts 0x10 pci0:0:31:2: Transition from D0 to D3 usbus6: port reset timeout uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1 ct_to_ts([2010-11-14 21:30:44]) = 1289770244.000000000 acpi_lid0: run_prep cleaned up for \\_SB_.LID_ acpi_button0: run_prep cleaned up for \\_SB_.PBTN ugen2.2: at usbus2 (disconnected) uhci_interrupt: resume detect uhci_interrupt: host system error uhci_interrupt: host controller process error pci0: set ACPI power state D0 on \\_SB_.PCI0.AGP_ uhci_interrupt: resume detect uhci_interrupt: host system error uhci_interrupt: host controller process error pci0: set ACPI power state D0 on \\_SB_.PCI0.USB4 pci0: set ACPI power state D0 on \\_SB_.PCI0.USB5 pci0: set ACPI power state D0 on \\_SB_.PCI0.EHC2 uhci_interrupt: resume detect uhci_interrupt: host system error uhci_interrupt: host controller process error pci0: set ACPI power state D0 on \\_SB_.PCI0.RP01 pci0: set ACPI power state D0 on \\_SB_.PCI0.RP02 uhci_interrupt: resume detect uhci_interrupt: host system error uhci_interrupt: host controller process error pci0: set ACPI power state D0 on \\_SB_.PCI0.RP05 pci0: set ACPI power state D0 on \\_SB_.PCI0.USB1 pci0: set ACPI power state D0 on \\_SB_.PCI0.USB2 uhci_interrupt: resume detect uhci_interrupt: host system error uhci_interrupt: host controller process error pci0: set ACPI power state D0 on \\_SB_.PCI0.USB3 pci0: set ACPI power state D0 on \\_SB_.PCI0.EHCI uhci_interrupt: resume detect uhci_interrupt: host system error uhci_interrupt: host controller process error pci0: set ACPI power state D0 on \\_SB_.PCI0.PCIE uhci_interrupt: resume detect uhci_interrupt: host system error uhci_interrupt: host controller process error pci0: set ACPI power state D0 on \\_SB_.PCI0.ISAB pci0: set ACPI power state D0 on \\_SB_.PCI0.IDE1uhci_interrupt: resume detect uhci_interrupt: host system error uhci_interrupt: host controller process error pci0: set ACPI power state D0 on \\_SB_.PCI0.IDE0 pci0: set ACPI power state D0 on \\_SB_.PCI0.AGP_ uhci_interrupt: resume detect pci1: set ACPI power state D0 on \\_SB_.PCI0.AGP_.VID_ usbus2: port reset timeout uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1 pci0: set ACPI power state D0 on \\_SB_.PCI0.RP01 pci9: set ACPI power state D0 on \\_SB_.PCI0.RP01.PXS1 pci0: set ACPI power state D0 on \\_SB_.PCI0.RP02 msk0: link state changed to DOWN pci0: set ACPI power state D0 on \\_SB_.PCI0.RP05 pci12: set ACPI power state D0 on \\_SB_.PCI0.RP05.PXS5 msk1: link state changed to DOWN ugen0.2: at usbus0 (disconnected) pci0: set ACPI power state D0 on \\_SB_.PCI0.PCIE [ATA messages] uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 2 [battery, keyboard and ATA messages] ugen0.2: at usbus0 -- Bruce Cran From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 21:46:05 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19B1D1065768 for ; Sun, 14 Nov 2010 21:46:01 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 001278FC16 for ; Sun, 14 Nov 2010 21:46:00 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 53FC6E6095; Sun, 14 Nov 2010 21:46:00 +0000 (GMT) Received: from core.nessbank (client-86-27-19-226.glfd.adsl.virginmedia.com [86.27.19.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Sun, 14 Nov 2010 21:45:59 +0000 (GMT) From: Bruce Cran To: Hans Petter Selasky Date: Sun, 14 Nov 2010 21:45:59 +0000 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.5.2; amd64; ; ) References: <201011142119.46709.bruce@cran.org.uk> <201011142228.02765.hselasky@c2i.net> In-Reply-To: <201011142228.02765.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011142145.59397.bruce@cran.org.uk> Cc: bzeeb+freebsd+lor@zabbadoz.net, freebsd-usb@freebsd.org Subject: Re: LOR: USB config SX lock vs. USB suspend and resume SX lock X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 21:46:05 -0000 On Sunday 14 November 2010 21:28:02 Hans Petter Selasky wrote: > Can you verify that this LOR is real, and that it is not due to SX-locks > having similar names? I'm not sure how to do that, but "show alllocks" in ddb returns: Process 14 (usb) thread 0xffffff0005402450 (100051) exclusive sleep mutex Giant (Giant) r = 0 (0xffffffff80835d40 locked @ /usr/src/head/sys/dev/usb/usb_transfer.c:3121 exclusive sx USB suspend and resume SX lock (USB suspend and resume SX lock) r = 0 (0xffffff00057c2090) locked @ /usr/src/head/sys/dev/usb/usb_device.c:2672 exclusive sx USB config SX lock (USB config SX lock) r = 0 (0xffffff00057c2070) locked @ /usr/src/head/sys/dev/usb/usb_device.c:2671 -- Bruce Cran From owner-freebsd-usb@FreeBSD.ORG Sun Nov 14 23:49:18 2010 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 850E81065672; Sun, 14 Nov 2010 23:49:18 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5A8768FC0A; Sun, 14 Nov 2010 23:49:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAENnIer042738; Sun, 14 Nov 2010 23:49:18 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAENnIC3042734; Sun, 14 Nov 2010 23:49:18 GMT (envelope-from arundel) Date: Sun, 14 Nov 2010 23:49:18 GMT Message-Id: <201011142349.oAENnIC3042734@freefall.freebsd.org> To: yerenkow@gmail.com, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have unknown activity X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 23:49:18 -0000 Synopsis: [usb67] [usb8] usb devices periodically have unknown activity State-Changed-From-To: open->feedback State-Changed-By: arundel State-Changed-When: Sun Nov 14 23:45:48 UTC 2010 State-Changed-Why: I'm sorry to put this back into feedback state, but Alexander Yerenkow has not answered an important question: Does your device actually work? Looking at this PR it appears that the only issue you're having are the blinking leds of your usb stick. If that is the case please note that whether polling a device regularly or not is dependant upon the implementation of the USB stack in a specific OS and should not be considered an actual bug. http://www.freebsd.org/cgi/query-pr.cgi?pr=138548 From owner-freebsd-usb@FreeBSD.ORG Mon Nov 15 08:01:35 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E87EE1065675; Mon, 15 Nov 2010 08:01:35 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8DE0C8FC12; Mon, 15 Nov 2010 08:01:35 +0000 (UTC) Received: by gyg13 with SMTP id 13so1735500gyg.13 for ; Mon, 15 Nov 2010 00:01:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=mFvBUYCu464JDO7uhOFNqHG/Amaz3Lpz5EbTVbQ+z30=; b=Z3nWng8l/cmWIOlo/tbv3Lb+kUJvY9VpHu8+lqSGHIY/dO9unUkis3490kThly5lVM DX6WGBDNdTPaySUpP+gslue+EvDD3roAIyTpoTszTwYLTb9ala5tQRtQTFS/0orfN55q 2nc7myfbKDP06JivPVro1MUTv5bj96QyZR8Oo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=j4xD2Kviqh0h4FlvM88+QDNXYIg8tIYV/xVq1d+q7J2+iEZMq5Pn7yYvWj1QGOJrxB 3DfrIyWdHcL08+onzaGCHDlrInhs5tgMQkxaJXjcTbNIJJsMMvnIwVrQPePW89cR1bjB OKqM1elCoA0oqi7L9Z/b9rV/tI/pYI5bYPpPw= MIME-Version: 1.0 Received: by 10.91.45.9 with SMTP id x9mr7406851agj.89.1289806329957; Sun, 14 Nov 2010 23:32:09 -0800 (PST) Received: by 10.90.82.17 with HTTP; Sun, 14 Nov 2010 23:32:09 -0800 (PST) In-Reply-To: <201011142349.oAENnIC3042734@freefall.freebsd.org> References: <201011142349.oAENnIC3042734@freefall.freebsd.org> Date: Mon, 15 Nov 2010 09:32:09 +0200 Message-ID: From: Alexander Yerenkow To: arundel@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-usb@freebsd.org Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have unknown activity X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 08:01:36 -0000 2010/11/15 > Synopsis: [usb67] [usb8] usb devices periodically have unknown activity > State-Changed-From-To: open->feedback > State-Changed-By: arundel > State-Changed-When: Sun Nov 14 23:45:48 UTC 2010 > State-Changed-Why: > I'm sorry to put this back into feedback state, but Alexander Yerenkow has > not > answered an important question: > > Does your device actually work? Looking at this PR it appears that the only > issue you're having are the blinking leds of your usb stick. If that is the > case please note that whether polling a device regularly or not is > dependant > upon the implementation of the USB stack in a specific OS and should not be > considered an actual bug. > Sorry that this wasn't clear from the beginning. Both devices function properly, via bluetooth I was using mobile -phone connection and dial-up; At usb stick I hold docs and files, which was readed just fine. The only problem - is that both devices blinking. Since I don't see blinking when devices inactive under other OSes, I assume that in FreeBSD there is some additional, not needed device polling forgotten to be disabled, or I don't know. If device is blinking, then something queries it, spending CPU cycles :) I'll give you more feedback in evening, will run again same tests with latest FreeBSD to see if it's still actual. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=138548 > -- Regards, Alexander Yerenkow From owner-freebsd-usb@FreeBSD.ORG Mon Nov 15 09:00:24 2010 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 773F31065672 for ; Mon, 15 Nov 2010 09:00:24 +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 4B82E8FC0C for ; Mon, 15 Nov 2010 09:00:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAF90OiK048262 for ; Mon, 15 Nov 2010 09:00:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAF90OV4048247; Mon, 15 Nov 2010 09:00:24 GMT (envelope-from gnats) Date: Mon, 15 Nov 2010 09:00:24 GMT Message-Id: <201011150900.oAF90OV4048247@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have unknown activity X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 09:00:24 -0000 The following reply was made to PR usb/138548; it has been noted by GNATS. From: Andriy Gapon To: bug-followup@freebsd.org, yerenkow@gmail.com Cc: Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have unknown activity Date: Mon, 15 Nov 2010 10:50:19 +0200 BTW, just a guess, the source of activity could be hald. -- Andriy Gapon From owner-freebsd-usb@FreeBSD.ORG Mon Nov 15 11:07:07 2010 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FFBB106571C for ; Mon, 15 Nov 2010 11:07:07 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4C3F38FC18 for ; Mon, 15 Nov 2010 11:07:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAFB77Wo086457 for ; Mon, 15 Nov 2010 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAFB76CD086455 for freebsd-usb@FreeBSD.org; Mon, 15 Nov 2010 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Nov 2010 11:07:06 GMT Message-Id: <201011151107.oAFB76CD086455@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-usb@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 11:07:07 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o usb/151862 usb adding support of USB GSM modem Falcom Twist o usb/151851 usb libusb(3) libusb_control_transfer() return value is in o usb/151043 usb Please add USB device MELCO WLR-UC-G o usb/150989 usb [patch] Add Netgear WG111V2_2 support to upgt(4) o usb/150892 usb [zyd] Whenever network contacted in any shape, way or p usb/150546 usb libusb(3) libusb_control_transfer() prototype is incor o usb/150401 usb [umass] [usb8] Errors from USB drives mixed between UF o usb/150189 usb [run] [usb8] [patch] if_run appears to corrupt IP traf p usb/149934 usb [patch] [usb8] Transcend JetFlash V85 poor performance o usb/149900 usb [uftdi] [patch] FreeBSD 8.1 uftdi patch to support usb p usb/149764 usb [u3g] [patch] usbdevs update: Huawei K3765 3G modem o usb/149675 usb [uftdi] [usb_serial] doesn't react to break properly o usb/149528 usb [zyd] Wireless USB stick not detected - vendor id 0x08 o usb/149283 usb [uftdi] avrdude unable to talk to Arduino board (via u o usb/149162 usb [ural] ASUS WL-167g doesn't work in 8.1 (continue of 1 o usb/149039 usb [uhso] [patch] Binding problem with uhso s usb/148702 usb [usb8] [request] IO DATA USB-RSAQ5 support on FreeBSD- o usb/148080 usb usbconfig(8) sometimes does not turn off the device o usb/147516 usb [umass] [usb67] kernel unable to deal with Olympus USB o i386/147475 usb [install] FreeBSD 8.x does not install on ASUS K8N4-E p usb/146871 usb [usbdevs] [usb8] [patch] provide descriprive string fo o usb/146840 usb [hang] FreeBSD 7.2 / 7.3 / 8.0 hang at startup after e o usb/146153 usb [axe] [usb8] Hosts in network doesn't receive any pack o usb/146054 usb [urtw] [usb8] urtw driver potentially out of date f usb/145513 usb [usb8] New USB stack: no new devices after forced usb p usb/145455 usb [usb8] [patch] USB debug support cannot be disabled o usb/145415 usb [umass] [usb8] USB card reader does not create slices a usb/145184 usb GENERIC can't mount root from USB on Asus EEE o usb/145165 usb [keyboard] [usb8] ukbd_set_leds_callback: error=USB_ER f kern/144938 usb [keyboard] [boot] Boot Failure with Apple (MB869LL/A) o usb/144387 usb [run] [panic] if_run panic o usb/144043 usb [umass] [usb8] USB DLT tape drive throws random errors a usb/143790 usb [boot] [cam] can not boot from usb hdd f usb/143620 usb [cdce] [usb8] the module if_cdce doesn't support my Op f usb/143294 usb [usb8] copying process stops at some time (10 - 50 sec o usb/143286 usb [ukbd] [usb8] [boot] boot failures on RELENG_8 system p usb/143186 usb [usbdevs] [usb8] [patch] add USB device IDs for Google a usb/143139 usb [umass] [usb8] [patch] Quirk for Century EX35SW4_SB4 J o usb/143045 usb [umass] [usb8] [patch] mounting Fujitsu 2600Z camera d o usb/142991 usb [uftdi] [usb67] [patch] Patch to add Crystalfontz 533 f usb/142989 usb [usb8] canon eos 50D attaches but detaches after few s f usb/142957 usb [umass] [usb8] [patch] patch for USB disk SYNCHRONIZE o usb/142719 usb [urtw] [usb8] AirLive WL-1600USB (RTL8187L chipset) fa o usb/142713 usb [usb67] [panic] Kernel Panik when connecting an IPhone f usb/142276 usb [umass] [usb8] Cache Synchronization Error with Olympu o usb/142229 usb [ums] [usb8] [hang] connecting a USB mouse to a Dell P o usb/141777 usb [usb8] [usbdevs] [rum] [patch] Support usbdevs / rum(4 o usb/141680 usb [uath] [usb8] Netgear WG111T not working with uath dri o usb/141664 usb [pcm] [usb8] Logitech USB microphone failure [regressi o usb/141474 usb [boot] [usb8] FreeBSD 8.0 can not install from USB CDR o usb/141327 usb [ukbd] [usb67] USB kbd not working with 7.1+PAE on IBM o usb/141212 usb [ukbd] [usb8] ukbd_set_leds_callback:700: error=USB_ER o kern/141011 usb [usb8] Encrypted root, geli password at boot; enter ke o usb/140920 usb [install] [usb8] USB based install fails on 8.0-RELEAS o usb/140893 usb [urtw] [usb8] WPA2 not working on rtl8187b f usb/140883 usb [axe] [usb8] USB gigabit ethernet hangs after short pe o kern/140849 usb [ums] [usb8] USB mouse doesn't work under FreeBSD 8.0- a usb/140810 usb [uftdi] [usb8] 8.X copy and paste problem / tty overfl o usb/140477 usb [umass] [usb8] [patch] allow boot-time attachment of d o usb/140236 usb [msdosfs] [usb8] Labels wiped on external Journaled US o usb/140160 usb [usb8] [acpi] USB ports are no longer "active" after A s usb/139990 usb [panic] [patch] [usb67] Kernel frequently panics after a usb/139598 usb [umass] [usb8] CAM reports "xptioctl: put "device pass o usb/139243 usb [uhci] [usb67] unplug prolific USB serial -> uhci_abor a usb/138904 usb [rum] [panic] [usb67] unpluging USB wifi card panics s f usb/138882 usb [ohci] [panic] [usb67] Can't install FreeBSD 7.2 due t o usb/138798 usb [boot] [usb8] 8.0-BETA4 can't boot from USB flash driv o usb/138659 usb [usb8][uftdi] driver broken in RELENG_8/CURRENT s usb/138570 usb [usb67] [panic] USB mass device panics current 7.2-STA f usb/138548 usb [usb67] [usb8] usb devices periodically have unknown a o usb/138175 usb [usb67] [boot] System cannot boot, when USB reader wit o usb/138124 usb [snd_uaudio] [usb8] Axed uaudio functionality in the u o usb/138119 usb [usb67] [usb8] MultiBay CDROM (probably on USB bus) is o usb/137872 usb [usb67] [boot] slow booting on usb flash drive o usb/137806 usb [ukbd] [usb67] USB keyboard doesn't work until it's un o usb/137763 usb [usb67][ukbd] Logitech wireless keyboard media keys no o usb/137377 usb [usb8] request support for Huawei E180 o usb/137341 usb [usb8][rum] driver if_rum doesn't work at all and thro f usb/137190 usb [usb8][patch] inhibit spurious button releases for som o usb/137189 usb [usb8][patch] create and use sysctl nodes for HID repo p usb/137188 usb [usb8][patch] correctly handle USB report descriptors o usb/137129 usb [ums] [usb8] SteelSeries Ikari USB laser mouse not att p usb/136761 usb [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H o usb/135938 usb [aue] [usb67] aue driver only passes traffic in promis o usb/135542 usb [keyboard] boot loader does not work with a usb keyboa o usb/135348 usb [umass] [patch] USB Drive Hangs with ZFS (JMicron USB2 o usb/135206 usb machine reboots when inserted USB device o usb/135200 usb SAMSUNG i740 usb mass: Synchronize cache failed, statu o usb/135182 usb UMASS quirk - Olympus FE20 camera o usb/134950 usb Lowering DTR for USB-modem via ubsa is not possible o usb/134299 usb Kernel Panic plugging in MF626 USB UMTS Stick u3g o usb/134193 usb System freeze on usb MP3 player insertion o usb/134085 usb [umass] Adding usb quirk for Sony USB flash drive o usb/133989 usb [usb8] [ukbd] USB keyboard dead at mountroot> prompt o usb/133712 usb [ural] [patch] RE: Fixed an issue with ural(4) that wa o usb/133390 usb umass crashes system in 7.1 when Olympus D-540 attache o usb/133296 usb [rum] driver not working properly in hostap mode o usb/132594 usb USB subsystem causes page fault and crashes o usb/132312 usb [hang] Xorg 7.4 halts USB controller o usb/132080 usb [patch] [usb] [rum] [panic] Kernel panic after NOMEM c o usb/132066 usb [ukbd] Keyboard failure USB keyboard DELL 760 o usb/132036 usb [panic] page fault when connecting Olympus C740 camera o usb/131583 usb [umass] Failure when detaching umass Device o usb/131576 usb [aue] ADMtek USB To LAN Converter can't send data o usb/131521 usb Registering Belkin UPS to usb_quirks.c p usb/131123 usb [patch] [usb67] re-add UQ_ASSUME_CM_OVER_DATA USB quir o usb/131074 usb no run-time detection of usb devices plugged into exte o usb/130736 usb Page fault unplugging USB stick o usb/130230 usb [patch] [quirk] [usb67] [usb] [cam] [umass] Samsung El o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [usb8] DVD drive detects as 'da' device f usb/129766 usb [usb] [panic] plugging in usb modem HUAWEI E226 panics o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb67] [patch] uaudio is not full duplex p usb/128803 usb [usbdevs] [patch] Quirk for I-Tuner Networks USBLCD4X2 o usb/128485 usb [umodem] [patch] Nokia N80 modem support o usb/128425 usb [umass] Cannot Connect Maxtor Onetouch 4 USB drive o usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/127926 usb [boot] USB Timeout during bootup s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should p docs/127406 usb [patch] update umodem man page: Sony Ericsson W810i o usb/127342 usb [boot] [panic] enabling usb keyboard and mouse support o usb/127248 usb [ucom] panic while uplcom devices attach and detach o usb/127222 usb [ohci] Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c o usb/126848 usb [usb]: USB Keyboard hangs during Installation o usb/126740 usb [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be o usb/126519 usb [usb] [panic] panic when plugging in an iphone o kern/126396 usb [panic] kernel panic after unplug USB Bluetooth device o usb/125631 usb [ums] [panic] kernel panic during bootup while 'Logite o usb/125510 usb [panic] repeated plug and unplug of USB mass storage d o usb/125450 usb [panic] Removing USB flash card while being accessed c o usb/125238 usb [ums] Habu Mouse turns off in X o usb/125088 usb [keyboard] Touchpad not detected on Adesso AKB-430UG U o usb/124980 usb [panic] kernel panic on detaching unmounted umass devi o kern/124777 usb [ucom] USB cua devices don't revert to tty devices whe o usb/124758 usb [rum] [panic] rum panics SMP kernel o usb/124708 usb [panic] Kernel panic on USB KVM reattach f usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work o kern/124130 usb [usb] gmirror fails to start usb devices that were pre o usb/123969 usb [usb] Supermicro H8SMi-2 usb problem: port reset faile o usb/123714 usb [usb] [panic] Panic when hald-storage-probe runs with o usb/123691 usb usbd(8): usbd hangs o usb/123690 usb [usb] [panic] Panic on USB device insertion when usb l o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122936 usb [ucom] [ubsa] Device does not receive interrupt o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa f usb/122819 usb [usb] [patch] Patch to provide dynamic additions to th o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122547 usb [ehci] USB Printer not being recognized after reboot o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/121755 usb [ohci] [patch] Fix panic after ohci/uhub cardbus devic o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121275 usb [boot] [panic] FreeBSD fails to boot with usb legacy s f usb/121232 usb [usb67] [panic] USB CardBus card removal causes reboot p usb/121184 usb [uipaq] [patch] add ids from linux ipaq driver (plus a o usb/121169 usb [umass] Issues with usb mp3 player o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS f usb/120786 usb [usb] [panic] Kernel panic when forced umount of a det o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120572 usb [usb67] [umass] [patch] quirk to support ASUS P535 as o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119513 usb [irq] inserting dlink dwl-g630 wireless card results i o usb/119509 usb [usb] USB flaky on Dell Optiplex 755 o usb/119481 usb [hang] FreeBSD not responding after connecting USB-Mas o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117598 usb [snd_uaudio] [patch] Not possible to record with Plant o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a p usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th p usb/116699 usb [usbhid] USB HID devices do not initialize at system b o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/114682 usb [umass] generic USB media-card reader unusable o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114068 usb [usb67] [usb8] [umass] [patch] Problem with connection o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113060 usb [usb67] [ulpt] [patch] Samsung printer not working in o usb/110856 usb [usb67] [ugen] [patch] interrupt in msgs are truncated o usb/107827 usb [usb67] [ohci] [panic] ohci_add_done addr not found o usb/107388 usb [usb67] [usb8] [new driver] [patch] add utoppy device o usb/106041 usb [usb67] [usb8] [request] FreeBSD does not recognise Mu o usb/105361 usb [usb67] [panic] Kernel panic during unmounting mass st s usb/103917 usb [usb67] [uhub] USB driver reports "Addr 0 should never o usb/103418 usb [usb67] [usb8] [patch] [request] usbhidctl(8) add abil o usb/103046 usb [usb67] [ulpt] [patch] ulpt event driven I/O with sele o usb/101775 usb [usb67] [usb8] [libusbhid] [patch] possible error in r o usb/101761 usb [usb67] [patch] [request] usb.h: increase maximal size o usb/100746 usb [usb67] [ukbd] system does not boot due to USB keyboar o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o kern/99200 usb [usb67] SMP-Kernel crashes reliably when Bluetooth con o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/96457 usb [umass] [panic] fatback on umass = reboot o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync s usb/96120 usb [ums] [request] USB mouse not always detected s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb s usb/95348 usb [keyboard] USB keyboard unplug causes noise on screen o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg f usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/89954 usb [umass] [panic] USB Disk driver race condition? s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg o usb/88408 usb [axe] axe0 read PHY failed o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/87224 usb [usb] Cannot mount USB Zip750 o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/86298 usb [mouse] Known good USB mouse won't work with correct s s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/83863 usb [ugen] Communication problem between opensc/openct via o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe o usb/83563 usb [umass] [panic] Page Fault while detaching Mpman Usb d o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/82660 usb [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic s usb/82569 usb [umass] [panic] USB mass storage plug/unplug causes sy o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me s usb/80777 usb [request] usb_rem_task() should wait for callback to c s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " f usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails f usb/80040 usb [sound] [hang] Use of sound mixer causes system freeze o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/78984 usb [umass] [patch] Creative MUVO umass failure f usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/76732 usb [ums] Mouse problems with USB KVM Switch o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by f usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn f usb/75797 usb [sound] [regression] 5.3-STABLE(2005 1/4) detect USB h o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for f usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) f usb/74771 usb [umass] [hang] mounting write-protected umass device a s usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R o usb/73307 usb [panic] Kernel panics on USB disconnect s usb/72733 usb [ucom] [request] Kyocera 7135 Palm OS connection probl o usb/71455 usb [umass] Slow USB umass performance of 5.3 o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/70523 usb [umct] [patch] umct sending/receiving wrong characters o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/67301 usb [uftdi] [panic] RTS and system panic o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s o usb/59698 usb [keyboard] [patch] Rework of ukbd HID to AT code trans s bin/57255 usb [patch] usbd(8) and multi-function devices s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 s usb/51958 usb [urio] [patch] update for urio driver o usb/40948 usb [umass] [request] USB HP CDW8200 does not work o usb/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem 317 problems total. From owner-freebsd-usb@FreeBSD.ORG Mon Nov 15 12:13:46 2010 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 6DDDD1065696; Mon, 15 Nov 2010 12:13:46 +0000 (UTC) Date: Mon, 15 Nov 2010 12:13:46 +0000 From: Alexander Best To: Andriy Gapon Message-ID: <20101115121346.GA34865@freebsd.org> References: <201011150900.oAF90OV4048247@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201011150900.oAF90OV4048247@freefall.freebsd.org> Cc: Alexander Yerenkow , freebsd-usb@FreeBSD.org Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have unknown activity X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 12:13:46 -0000 On Mon Nov 15 10, Andriy Gapon wrote: > The following reply was made to PR usb/138548; it has been noted by GNATS. > > From: Andriy Gapon > To: bug-followup@freebsd.org, yerenkow@gmail.com > Cc: > Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have unknown > activity > Date: Mon, 15 Nov 2010 10:50:19 +0200 > > BTW, just a guess, the source of activity could be hald. good point! :) Alexander, could you please try the following before plugging in the usb device: /usr/local/etc/rc.d/hald stop does that solve the 'blinking' issue? cheers. alex > -- > Andriy Gapon -- a13x From owner-freebsd-usb@FreeBSD.ORG Mon Nov 15 12:26:58 2010 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 D1FA41065675; Mon, 15 Nov 2010 12:26:58 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A7DE28FC1F; Mon, 15 Nov 2010 12:26:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAFCQw9x073371; Mon, 15 Nov 2010 12:26:58 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAFCQwc1073367; Mon, 15 Nov 2010 12:26:58 GMT (envelope-from arundel) Date: Mon, 15 Nov 2010 12:26:58 GMT Message-Id: <201011151226.oAFCQwc1073367@freefall.freebsd.org> To: walker.643@gmail.com, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/87224: [usb] Cannot mount USB Zip750 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 12:26:58 -0000 Synopsis: [usb] Cannot mount USB Zip750 State-Changed-From-To: open->feedback State-Changed-By: arundel State-Changed-When: Mon Nov 15 12:26:15 UTC 2010 State-Changed-Why: So you still own that device and could test whether it works properly under FreeBSD 7.x or even better yet FreeBSD 8.x? http://www.freebsd.org/cgi/query-pr.cgi?pr=87224 From owner-freebsd-usb@FreeBSD.ORG Mon Nov 15 12:37:47 2010 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 D31C51065694; Mon, 15 Nov 2010 12:37:47 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A8D928FC14; Mon, 15 Nov 2010 12:37:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAFCblUi084801; Mon, 15 Nov 2010 12:37:47 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAFCbl9b084797; Mon, 15 Nov 2010 12:37:47 GMT (envelope-from arundel) Date: Mon, 15 Nov 2010 12:37:47 GMT Message-Id: <201011151237.oAFCbl9b084797@freefall.freebsd.org> To: yerenkow@gmail.com, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have unknown activity X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 12:37:47 -0000 Synopsis: [usb67] [usb8] usb devices periodically have unknown activity State-Changed-From-To: feedback->open State-Changed-By: arundel State-Changed-When: Mon Nov 15 12:36:06 UTC 2010 State-Changed-Why: Please note that feedback was received on freebsd-usb@ and this issue is currently being worked on. http://www.freebsd.org/cgi/query-pr.cgi?pr=138548 From owner-freebsd-usb@FreeBSD.ORG Mon Nov 15 17:34:44 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB81B1065672; Mon, 15 Nov 2010 17:34:43 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7CE378FC22; Mon, 15 Nov 2010 17:34:43 +0000 (UTC) Received: by gwj20 with SMTP id 20so2801212gwj.13 for ; Mon, 15 Nov 2010 09:34:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=JoFvOPKgTv855ZXEFORwPSYU/7beLzd2roJudCwpBYU=; b=C6yqR1rJ3D05ee17AaEiWuFNRJKcc8LnDaqW/Pc6fsq8lOOXkuOnY6cT1Za8ZlIJku u+8Ezpc+oRzHkSFsyvM0k8XmjB50OkrDiBc3FMgEPjFbluRHjiwl4tDqoHDozWozrMWP DYjAi6a/BVEQxyeodwzHQg0RzU/VufjFR7fLI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=JoN4N2zHvEpnuPyA7/eNEhzkchh4hZDPjPGwmJL+Zv9ml6crHtF0jIdlMEd9iLgxAd ek2MWzwJ0F1DHBEz3znxxWPFR4soe8eFPEEV0tygPjf063bYF+0OZFxM9Mxh5HjMIkE+ B7JcKeNJFlcVA7u9l2h9ibkpAWuxtU9/8MnxM= MIME-Version: 1.0 Received: by 10.90.186.1 with SMTP id j1mr8080421agf.170.1289842482680; Mon, 15 Nov 2010 09:34:42 -0800 (PST) Received: by 10.90.82.17 with HTTP; Mon, 15 Nov 2010 09:34:41 -0800 (PST) In-Reply-To: <20101115121346.GA34865@freebsd.org> References: <201011150900.oAF90OV4048247@freefall.freebsd.org> <20101115121346.GA34865@freebsd.org> Date: Mon, 15 Nov 2010 19:34:41 +0200 Message-ID: From: Alexander Yerenkow To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-usb@freebsd.org, Andriy Gapon Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have unknown activity X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 17:34:44 -0000 2010/11/15 Alexander Best > On Mon Nov 15 10, Andriy Gapon wrote: > > The following reply was made to PR usb/138548; it has been noted by > GNATS. > > > > From: Andriy Gapon > > To: bug-followup@freebsd.org, yerenkow@gmail.com > > Cc: > > Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have > unknown > > activity > > Date: Mon, 15 Nov 2010 10:50:19 +0200 > > > > BTW, just a guess, the source of activity could be hald. > > good point! :) > > Alexander, could you please try the following before plugging in the usb > device: > > /usr/local/etc/rc.d/hald stop > > does that solve the 'blinking' issue? > Well, yes, it solves under 8.0 and hal-0.5.13_14 :) Interesting, that in latest 9.0 it not blinking even with hal (tested with hal-0.5.14_9.tbz) I think this PR can be closed as "not our bug". > > cheers. > alex > > > -- > > Andriy Gapon > > -- > a13x > -- Regards, Alexander Yerenkow From owner-freebsd-usb@FreeBSD.ORG Mon Nov 15 19:16:27 2010 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 C998F1065670; Mon, 15 Nov 2010 19:16:27 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9FB408FC17; Mon, 15 Nov 2010 19:16:27 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAFJGRe4000563; Mon, 15 Nov 2010 19:16:27 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAFJGRpr000559; Mon, 15 Nov 2010 19:16:27 GMT (envelope-from arundel) Date: Mon, 15 Nov 2010 19:16:27 GMT Message-Id: <201011151916.oAFJGRpr000559@freefall.freebsd.org> To: yerenkow@gmail.com, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have unknown activity X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 19:16:27 -0000 Synopsis: [usb67] [usb8] usb devices periodically have unknown activity State-Changed-From-To: open->closed State-Changed-By: arundel State-Changed-When: Mon Nov 15 19:15:02 UTC 2010 State-Changed-Why: The cause of this issue was not the USB stack, but HAL. Originator requested that this PR shall be closed. http://www.freebsd.org/cgi/query-pr.cgi?pr=138548 From owner-freebsd-usb@FreeBSD.ORG Tue Nov 16 15:19:58 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6912C106564A for ; Tue, 16 Nov 2010 15:19:58 +0000 (UTC) (envelope-from sorem-real-atualcard@sorem.onda.com.br) Received: from sorem.onda.com.br (sorem.onda.com.br [200.195.197.42]) by mx1.freebsd.org (Postfix) with ESMTP id A7BED8FC0C for ; Tue, 16 Nov 2010 15:19:57 +0000 (UTC) Received: by sorem.onda.com.br (Postfix, from userid 0) id 1B8C422583F2; Tue, 16 Nov 2010 12:52:03 -0200 (BRST) To: freebsd-usb@freebsd.org From: REVENDA BRINDES Content-Transfer-Encoding: 7bit X-SOREM-Campaign-ID: 38_309343001289916828 X-Mailer: SOREM Message-Id: <20101116145203.1B8C422583F2@sorem.onda.com.br> Date: Tue, 16 Nov 2010 12:52:03 -0200 (BRST) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Chaveiro Moto por 0,39 e Canetas por 0,67 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: REVENDA BRINDES List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2010 15:19:58 -0000 [1]REVENDABRINDES.COM.BR [2]REVENDABRINDES.COM.BR [3]Chaveiro Metálico Anzol por R$ 0,96 cada [4]Chaveiro de moto por R$ 0,39 cada [5]Canetas Plásticas impressas em uma cor por R$0,67 cada [6]REVENDABRINDES.COM.BR [7]VÁRIAS FORMAS DE PAGAMENTO Caso você não queira receber nossas mensagens, [8]clique aqui que seu e-mail será retirado imediatamente de nossa lista. References 1. http://sorem.onda.com.br/sorem/click.php?s=94275876c08c3d230eb03f62e099a967&e=6694e375c1ac0cbac92796553984c731&u=http://www.revendabrindes.com.br 2. http://sorem.onda.com.br/sorem/click.php?s=94275876c08c3d230eb03f62e099a967&e=6694e375c1ac0cbac92796553984c731&u=http://www.revendabrindes.com.br 3. http://sorem.onda.com.br/sorem/click.php?s=94275876c08c3d230eb03f62e099a967&e=6694e375c1ac0cbac92796553984c731&u=http://www.revendabrindes.com.br/produto/info/16/chaveiros-metalicos-1-cod-108-mosquetao-cromado.html 4. http://sorem.onda.com.br/sorem/click.php?s=94275876c08c3d230eb03f62e099a967&e=6694e375c1ac0cbac92796553984c731&u=http://www.revendabrindes.com.br/produto/lista/36/moto.html 5. http://sorem.onda.com.br/sorem/click.php?s=94275876c08c3d230eb03f62e099a967&e=6694e375c1ac0cbac92796553984c731&u=http://www.revendabrindes.com.br 6. http://sorem.onda.com.br/sorem/click.php?s=94275876c08c3d230eb03f62e099a967&e=6694e375c1ac0cbac92796553984c731&u=http://www.revendabrindes.com.br/produto/lista/6/plasticas.html 7. http://sorem.onda.com.br/sorem/click.php?s=94275876c08c3d230eb03f62e099a967&e=6694e375c1ac0cbac92796553984c731&u=http://www.revendabrindes.com.br 8. http://sorem.onda.com.br/sorem/optout.php?s=94275876c08c3d230eb03f62e099a967&e=6694e375c1ac0cbac92796553984c731&u=http://www.ondaexpress.com.br From owner-freebsd-usb@FreeBSD.ORG Wed Nov 17 12:08:56 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEB43106566B for ; Wed, 17 Nov 2010 12:08:56 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 9AE748FC13 for ; Wed, 17 Nov 2010 12:08:56 +0000 (UTC) Received: from [193.31.11.193] (helo=current.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PIgon-0007uy-Sh for freebsd-usb@freebsd.org; Wed, 17 Nov 2010 13:08:54 +0100 Received: from current.Sisis.de (current [127.0.0.1]) by current.Sisis.de (8.14.3/8.14.3) with ESMTP id oAHC8qT5002485 for ; Wed, 17 Nov 2010 13:08:52 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id oAHC8qvr002484 for freebsd-usb@freebsd.org; Wed, 17 Nov 2010 13:08:52 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Wed, 17 Nov 2010 13:08:52 +0100 From: Matthias Apitz To: freebsd-usb@freebsd.org Message-ID: <20101117120852.GA2458@current.Sisis.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 193.31.11.193 Subject: restore(8) to USB key: terrible slow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 12:08:56 -0000 Hello, I've a dump(8) created from another USB key of ~3 GByte size and I'm restoring it into a new created file system on a key which says on attach: ugen7.2: at usbus7 umass0: on usbus7 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:3:0:-1: Attached to scbus3 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 3853MB (7892087 512 byte sectors: 255H 63S/T 491C) after around 90 minutes of restore the taget file system says 19 MByte used (i.e restored): $ df -kh /mnt Filesystem Size Used Avail Capacity Mounted on /dev/da0s1a 3.6G 19M 3.3G 1% /mnt What is wrong with this? If this does matter: 8-CURRENT. Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Wed Nov 17 12:16:13 2010 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 0B39E1065674; Wed, 17 Nov 2010 12:16:13 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D47A48FC1A; Wed, 17 Nov 2010 12:16:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAHCGCV1023626; Wed, 17 Nov 2010 12:16:12 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAHCGC2G023622; Wed, 17 Nov 2010 12:16:12 GMT (envelope-from arundel) Date: Wed, 17 Nov 2010 12:16:12 GMT Message-Id: <201011171216.oAHCGC2G023622@freefall.freebsd.org> To: arundel@FreeBSD.org, freebsd-usb@FreeBSD.org, hselasky@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/151851: libusb(3) libusb_control_transfer() return value is incorrect X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 12:16:13 -0000 Synopsis: libusb(3) libusb_control_transfer() return value is incorrect Responsible-Changed-From-To: freebsd-usb->hselasky Responsible-Changed-By: arundel Responsible-Changed-When: Wed Nov 17 12:14:45 UTC 2010 Responsible-Changed-Why: Hans Petter, could you please do a MfP4 of this commit to HEAD? http://www.freebsd.org/cgi/query-pr.cgi?pr=151851 From owner-freebsd-usb@FreeBSD.ORG Wed Nov 17 12:23:27 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 767DA1065672 for ; Wed, 17 Nov 2010 12:23:27 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.c2i.net [212.247.154.2]) by mx1.freebsd.org (Postfix) with ESMTP id 090E48FC1D for ; Wed, 17 Nov 2010 12:23:26 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=omSrwDgyMf70S47Fr5SNr0rQzcmIOo0IafWlB/wSLLo= c=1 sm=1 a=M4YSOkT-fgUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=6lDhL-oblQDxyqEFUDcA:9 a=quF37YEVUNnIMfXjXHkA:7 a=rNrhNBuI2h1Su9BZN-AZpBw5ZIIA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 50912387; Wed, 17 Nov 2010 13:13:23 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org, Matthias Apitz Date: Wed, 17 Nov 2010 13:14:19 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <20101117120852.GA2458@current.Sisis.de> In-Reply-To: <20101117120852.GA2458@current.Sisis.de> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011171314.19524.hselasky@c2i.net> Cc: Subject: Re: restore(8) to USB key: terrible slow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 12:23:27 -0000 On Wednesday 17 November 2010 13:08:52 Matthias Apitz wrote: > Hello, > > I've a dump(8) created from another USB key of ~3 GByte size and I'm > restoring it into a new created file system on a key which says on > attach: > > ugen7.2: at usbus7 > umass0: 2.00/1.00, addr 2> on usbus7 > umass0: SCSI over Bulk-Only; quirks = 0x0000 > umass0:3:0:-1: Attached to scbus3 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: 40.000MB/s transfers > da0: 3853MB (7892087 512 byte sectors: 255H 63S/T 491C) > > after around 90 minutes of restore the taget file system says 19 MByte > used (i.e restored): > > $ df -kh /mnt > Filesystem Size Used Avail Capacity Mounted on > /dev/da0s1a 3.6G 19M 3.3G 1% /mnt > > What is wrong with this? If this does matter: 8-CURRENT. > > Thanks > > matthias Hi, Maybe you get some answers from: sysctl hw.usb.umass.debug=-1 Kernel needs to be compiled with: options USB_DEBUG --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Nov 17 13:39:18 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2065D1065673 for ; Wed, 17 Nov 2010 13:39:18 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id D0B7D8FC0A for ; Wed, 17 Nov 2010 13:39:17 +0000 (UTC) Received: from [193.31.11.193] (helo=current.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PIiEF-00007u-K2; Wed, 17 Nov 2010 14:39:16 +0100 Received: from current.Sisis.de (current [127.0.0.1]) by current.Sisis.de (8.14.3/8.14.3) with ESMTP id oAHDdEY1002920; Wed, 17 Nov 2010 14:39:14 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id oAHDdEra002919; Wed, 17 Nov 2010 14:39:14 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Wed, 17 Nov 2010 14:39:14 +0100 From: Matthias Apitz To: Hans Petter Selasky Message-ID: <20101117133914.GA2895@current.Sisis.de> References: <20101117120852.GA2458@current.Sisis.de> <201011171314.19524.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201011171314.19524.hselasky@c2i.net> X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 193.31.11.193 Cc: freebsd-usb@freebsd.org Subject: Re: restore(8) to USB key: terrible slow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 13:39:18 -0000 El día Wednesday, November 17, 2010 a las 01:14:19PM +0100, Hans Petter Selasky escribió: > > after around 90 minutes of restore the taget file system says 19 MByte > > used (i.e restored): > > > > $ df -kh /mnt > > Filesystem Size Used Avail Capacity Mounted on > > /dev/da0s1a 3.6G 19M 3.3G 1% /mnt > > > > What is wrong with this? If this does matter: 8-CURRENT. > > > > Thanks > > > > matthias > > Hi, > > Maybe you get some answers from: > > sysctl hw.usb.umass.debug=-1 > > Kernel needs to be compiled with: > > options USB_DEBUG Thanks; I have to build a kernel for this ... When I write the key just with dd(1) it performs normal with big blocks: # dd if=/home/guru/usb9root.dmp of=/dev/da0 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 16.650550 secs (6297546 bytes/sec) and slow with 512 byte blocks: # dd if=/home/guru/usb9root.dmp of=/dev/da0 count=100 100+0 records in 100+0 records out 51200 bytes transferred in 1.997130 secs (25637 bytes/sec) any idea or do we need the debug output? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Wed Nov 17 13:43:42 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A96A61065670 for ; Wed, 17 Nov 2010 13:43:42 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.c2i.net [212.247.154.98]) by mx1.freebsd.org (Postfix) with ESMTP id 38D7B8FC0A for ; Wed, 17 Nov 2010 13:43:41 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=gl0LPzB4YDQuuzpDoHYit7deEV0cOo++Sg28kyvF6vg= c=1 sm=1 a=M4YSOkT-fgUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=8QIXNKRKugDFIO5eqVYA:9 a=OxGuVhD0ojtUCug3lUoA:7 a=FBvmddIH6boCFyB7RDGVqPZOiucA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 49930367; Wed, 17 Nov 2010 14:43:40 +0100 From: Hans Petter Selasky To: Matthias Apitz Date: Wed, 17 Nov 2010 14:44:35 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <20101117120852.GA2458@current.Sisis.de> <201011171314.19524.hselasky@c2i.net> <20101117133914.GA2895@current.Sisis.de> In-Reply-To: <20101117133914.GA2895@current.Sisis.de> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'( =?iso-8859-1?q?=3B=5FIjlA=3A=0A=09hGE=2E=2EEw?=, =?iso-8859-1?q?XAQ*o=23=5C/M=7ESC=3DS1-f9=7BEzRfT=27=7CHhll5Q=5Dha5Bt-s=7Co?= =?iso-8859-1?q?TlKMusi=3A1e=5BwJl=7Dkd=7DGR=0A=09Z0adGx-x=5F0zGbZj=27e?=(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201011171444.35916.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: restore(8) to USB key: terrible slow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 13:43:42 -0000 On Wednesday 17 November 2010 14:39:14 Matthias Apitz wrote: > El d=EDa Wednesday, November 17, 2010 a las 01:14:19PM +0100, Hans Petter= =20 Selasky escribi=F3: > > > after around 90 minutes of restore the taget file system says 19 MByte > > > used (i.e restored): > > >=20 > > > $ df -kh /mnt > > > Filesystem Size Used Avail Capacity Mounted on > > > /dev/da0s1a 3.6G 19M 3.3G 1% /mnt > > >=20 > > > What is wrong with this? If this does matter: 8-CURRENT. > > >=20 > > > Thanks > > >=20 > > > matthias > >=20 > > Hi, > >=20 > > Maybe you get some answers from: > >=20 > > sysctl hw.usb.umass.debug=3D-1 > >=20 > > Kernel needs to be compiled with: > >=20 > > options USB_DEBUG >=20 > Thanks; I have to build a kernel for this ... >=20 > When I write the key just with dd(1) it performs normal with big blocks: >=20 > # dd if=3D/home/guru/usb9root.dmp of=3D/dev/da0 bs=3D1m count=3D100 > 100+0 records in > 100+0 records out > 104857600 bytes transferred in 16.650550 secs (6297546 bytes/sec) >=20 > and slow with 512 byte blocks: >=20 > # dd if=3D/home/guru/usb9root.dmp of=3D/dev/da0 count=3D100 > 100+0 records in > 100+0 records out > 51200 bytes transferred in 1.997130 secs (25637 bytes/sec) >=20 > any idea or do we need the debug output? >=20 > matthias What block size does the dump utility use? =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Wed Nov 17 13:44:28 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8178C1065697 for ; Wed, 17 Nov 2010 13:44:28 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.c2i.net [212.247.154.34]) by mx1.freebsd.org (Postfix) with ESMTP id 0C1428FC12 for ; Wed, 17 Nov 2010 13:44:27 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=yevn+QCjI6xy199BDvBOOiO14qYvyLq62he9tTtU3M8= c=1 sm=1 a=M4YSOkT-fgUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=FMFlLhu1KDioe_ojvVkA:9 a=xkeEB5QTXV9Z8wOR6M7mKRW2CdEA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 50314124; Wed, 17 Nov 2010 14:44:26 +0100 From: Hans Petter Selasky To: Matthias Apitz Date: Wed, 17 Nov 2010 14:45:23 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <20101117120852.GA2458@current.Sisis.de> <201011171314.19524.hselasky@c2i.net> <20101117133914.GA2895@current.Sisis.de> In-Reply-To: <20101117133914.GA2895@current.Sisis.de> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'( =?iso-8859-1?q?=3B=5FIjlA=3A=0A=09hGE=2E=2EEw?=, =?iso-8859-1?q?XAQ*o=23=5C/M=7ESC=3DS1-f9=7BEzRfT=27=7CHhll5Q=5Dha5Bt-s=7Co?= =?iso-8859-1?q?TlKMusi=3A1e=5BwJl=7Dkd=7DGR=0A=09Z0adGx-x=5F0zGbZj=27e?=(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011171445.23110.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: restore(8) to USB key: terrible slow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 13:44:28 -0000 > any idea or do we need the debug output? restore -b 65536 ? --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Nov 17 13:52:59 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id C358B1065696; Wed, 17 Nov 2010 13:52:59 +0000 (UTC) Date: Wed, 17 Nov 2010 13:52:59 +0000 From: Alexander Best To: Hans Petter Selasky Message-ID: <20101117135259.GA74544@freebsd.org> References: <20101117120852.GA2458@current.Sisis.de> <201011171314.19524.hselasky@c2i.net> <20101117133914.GA2895@current.Sisis.de> <201011171444.35916.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201011171444.35916.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: restore(8) to USB key: terrible slow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 13:52:59 -0000 On Wed Nov 17 10, Hans Petter Selasky wrote: > On Wednesday 17 November 2010 14:39:14 Matthias Apitz wrote: > > El día Wednesday, November 17, 2010 a las 01:14:19PM +0100, Hans Petter > Selasky escribió: > > > > after around 90 minutes of restore the taget file system says 19 MByte > > > > used (i.e restored): > > > > > > > > $ df -kh /mnt > > > > Filesystem Size Used Avail Capacity Mounted on > > > > /dev/da0s1a 3.6G 19M 3.3G 1% /mnt > > > > > > > > What is wrong with this? If this does matter: 8-CURRENT. > > > > > > > > Thanks > > > > > > > > matthias > > > > > > Hi, > > > > > > Maybe you get some answers from: > > > > > > sysctl hw.usb.umass.debug=-1 > > > > > > Kernel needs to be compiled with: > > > > > > options USB_DEBUG > > > > Thanks; I have to build a kernel for this ... > > > > When I write the key just with dd(1) it performs normal with big blocks: > > > > # dd if=/home/guru/usb9root.dmp of=/dev/da0 bs=1m count=100 > > 100+0 records in > > 100+0 records out > > 104857600 bytes transferred in 16.650550 secs (6297546 bytes/sec) > > > > and slow with 512 byte blocks: > > > > # dd if=/home/guru/usb9root.dmp of=/dev/da0 count=100 > > 100+0 records in > > 100+0 records out > > 51200 bytes transferred in 1.997130 secs (25637 bytes/sec) > > > > any idea or do we need the debug output? > > > > matthias > > What block size does the dump utility use? dump(8) says 10k. > > --HPS -- a13x From owner-freebsd-usb@FreeBSD.ORG Wed Nov 17 14:09:22 2010 Return-Path: Delivered-To: freebsd-usb@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E717C106564A for ; Wed, 17 Nov 2010 14:09:22 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 7864E8FC16 for ; Wed, 17 Nov 2010 14:09:22 +0000 (UTC) Received: from [193.31.11.193] (helo=current.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PIihL-0005db-Lh; Wed, 17 Nov 2010 15:09:19 +0100 Received: from current.Sisis.de (current [127.0.0.1]) by current.Sisis.de (8.14.3/8.14.3) with ESMTP id oAHE9Ix5003166; Wed, 17 Nov 2010 15:09:18 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id oAHE9ITV003165; Wed, 17 Nov 2010 15:09:18 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Wed, 17 Nov 2010 15:09:18 +0100 From: Matthias Apitz To: Alexander Best Message-ID: <20101117140918.GA3123@current.Sisis.de> References: <20101117120852.GA2458@current.Sisis.de> <201011171314.19524.hselasky@c2i.net> <20101117133914.GA2895@current.Sisis.de> <201011171444.35916.hselasky@c2i.net> <20101117135259.GA74544@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20101117135259.GA74544@freebsd.org> X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 193.31.11.193 Cc: freebsd-usb@FreeBSD.ORG Subject: Re: restore(8) to USB key: terrible slow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 14:09:23 -0000 El día Wednesday, November 17, 2010 a las 01:52:59PM +0000, Alexander Best escribió: > > > Thanks; I have to build a kernel for this ... > > > > > > When I write the key just with dd(1) it performs normal with big blocks: > > > > > > # dd if=/home/guru/usb9root.dmp of=/dev/da0 bs=1m count=100 > > > 100+0 records in > > > 100+0 records out > > > 104857600 bytes transferred in 16.650550 secs (6297546 bytes/sec) > > > > > > and slow with 512 byte blocks: > > > > > > # dd if=/home/guru/usb9root.dmp of=/dev/da0 count=100 > > > 100+0 records in > > > 100+0 records out > > > 51200 bytes transferred in 1.997130 secs (25637 bytes/sec) > > > > > > any idea or do we need the debug output? > > > > > > matthias > > > > What block size does the dump utility use? > > dump(8) says 10k. The -b of dump(8) is for the output device (which in my case was a plain file, and the 3 GByte was dumped in ~10 minutes). I think it does not influence the write performance of restore(8). Interestingly, after the above write with dd(1) over sector 0 (...) and after recreating the FreeBSD layout on the key (fdisk(8), bsdlabel(8), newfs(8)), the restore(8) now works much faster. There are a lot of small files (a complete /usr/src/sys after SVN checkout with all SVN control files) and a complete FreeBSD live system in this dump(8). The dump(8) and restore(8) is only to make from a 16 GByte bootable USB key with a lot of free space on it a smaller 4 GByte key to give it away to some FreeBSD lovers in Cuba so that they can distribute it there, not needing such a big 16 GByte USB key. Any other idea to shrink a 16 GB file system to 4 GB on a 2nd key? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Thu Nov 18 08:44:12 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9858F1065670 for ; Thu, 18 Nov 2010 08:44:12 +0000 (UTC) (envelope-from hselasky@freebsd.org) Received: from swip.net (mailfe04.c2i.net [212.247.154.98]) by mx1.freebsd.org (Postfix) with ESMTP id 2003B8FC12 for ; Thu, 18 Nov 2010 08:44:11 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=gl0LPzB4YDQuuzpDoHYit7deEV0cOo++Sg28kyvF6vg= c=1 sm=1 a=yDwUScyJ9MwA:10 a=N659UExz7-8A:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=6I5d2MoRAAAA:8 a=P1ShyLeF0_UoVhbOcwQA:9 a=ARUIICaDNlB7ENyZrwYa3ACcl1sA:4 a=pILNOxqGKmIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 50241235; Thu, 18 Nov 2010 09:34:08 +0100 Received-SPF: softfail receiver=mailfe04.swip.net; client-ip=188.126.198.129; envelope-from=hselasky@freebsd.org From: Hans Petter Selasky To: arundel@freebsd.org Date: Thu, 18 Nov 2010 09:35:03 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <201011171216.oAHCGC2G023622@freefall.freebsd.org> In-Reply-To: <201011171216.oAHCGC2G023622@freefall.freebsd.org> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <201011180935.03236.hselasky@freebsd.org> Cc: "freebsd-usb@FreeBSD.org" Subject: Re: usb/151851: libusb(3) libusb_control_transfer() return value is incorrect X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2010 08:44:12 -0000 http://svn.freebsd.org/changeset/base/215450 --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Nov 18 15:10:08 2010 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 4344D1065697 for ; Thu, 18 Nov 2010 15:10:08 +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 2EE198FC28 for ; Thu, 18 Nov 2010 15:10:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAIFA7sV034211 for ; Thu, 18 Nov 2010 15:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAIFA7SZ034209; Thu, 18 Nov 2010 15:10:07 GMT (envelope-from gnats) Date: Thu, 18 Nov 2010 15:10:07 GMT Message-Id: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Derrick Brashear Cc: Subject: Re: usb/140883: [axe] [usb8] 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: Derrick Brashear List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2010 15:10:08 -0000 The following reply was made to PR usb/140883; it has been noted by GNATS. From: Derrick Brashear To: bug-followup@FreeBSD.org, sub.mesa@gmail.com Cc: Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic Date: Thu, 18 Nov 2010 09:36:50 -0500 Pyun has provided an updated driver which avoids several issues including using a too-large transmit buffer (the chipset claims only 8k) but none of the fixes worked until he disabled frame combining for transmit. With only a single packet being sent per frame (as was the case in FreeBSD 7, apparently) seems to make the issue go away. None of the cases I could use to reproduce the issue now happen. -- Derrick From owner-freebsd-usb@FreeBSD.ORG Thu Nov 18 18:38:24 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36E3E106564A for ; Thu, 18 Nov 2010 18:38:24 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id D94EB8FC0A for ; Thu, 18 Nov 2010 18:38:23 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id 9DEAF1CC45; Thu, 18 Nov 2010 15:20:51 -0300 (BRT) Received: from 187.114.198.138 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Thu, 18 Nov 2010 16:20:51 -0200 Message-ID: <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> In-Reply-To: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> Date: Thu, 18 Nov 2010 16:20:51 -0200 From: "Nenhum_de_Nos" To: freebsd-usb@freebsd.org User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2010 18:38:24 -0000 On Thu, November 18, 2010 13:10, Derrick Brashear wrote: > The following reply was made to PR usb/140883; it has been noted by GNATS. > > From: Derrick Brashear > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com > Cc: > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after > short > period of traffic > Date: Thu, 18 Nov 2010 09:36:50 -0500 > > Pyun has provided an updated driver which avoids several issues > including using a too-large transmit buffer (the chipset claims only > 8k) but none of the fixes worked until he disabled frame combining for > transmit. With only a single packet being sent per frame (as was the > case in FreeBSD 7, apparently) seems to make the issue go away. None > of the cases I could use to reproduce the issue now happen. > > -- > Derrick is this already in 8-stable ? I have a couple of axe(4) based nic's they're not ok on 8-stable. I've talked to Pyun before, and that time seemed do solve the issue (with gigabit belkin axe based) but now I can't get them to work anymore. even fast ethernet linksys axe are just dying when in a bridge (switched to OpenBSD to have it working). how ca I try this to help ? thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Thu Nov 18 20:53:15 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C4881065673 for ; Thu, 18 Nov 2010 20:53:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3366C8FC24 for ; Thu, 18 Nov 2010 20:53:14 +0000 (UTC) Received: by yxh35 with SMTP id 35so2263426yxh.13 for ; Thu, 18 Nov 2010 12:53:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=eNmWiq1uHwGJ1ckr2jTLfYHNvakfS8IA8sVG5muMvTE=; b=UbzzrY7KTph9C5Jw51QFZenDSnUIljHzt7Uz5zewag4BSdA3a7e1afal7nTwRn2JZC 5qbG7DV4cd0ckb9hg26ujOeN/J/WGzCOGkFggL8Vy2BaIykQGd3JczhM3eGQtblWIGHu nUY8NXsGp9pdmAEPFUE05l+6qkX4erqejpsck= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=XwfIDBEY6oceMQ+3HvHnhVJFpcg6tq/XgnUpMOO9i7AyPKlmtAxAl+5FVLflQk4Tj2 /grh6wAjqI7H5fo1fNH8epoYG0nOJbiR1Ytwmnj8wgApFKqXf/Nb7Ify8BQPlv/+hhBw 2/O4YTPCHXtlXXIEkc/SDzzJm45jLKGOKJ6R4= Received: by 10.150.181.20 with SMTP id d20mr1935659ybf.126.1290111869747; Thu, 18 Nov 2010 12:24:29 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id p30sm533320ybk.8.2010.11.18.12.24.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 18 Nov 2010 12:24:27 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 18 Nov 2010 12:24:26 -0800 From: Pyun YongHyeon Date: Thu, 18 Nov 2010 12:24:26 -0800 To: Nenhum_de_Nos Message-ID: <20101118202426.GB8512@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] 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: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2010 20:53:15 -0000 On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos wrote: > > On Thu, November 18, 2010 13:10, Derrick Brashear wrote: > > The following reply was made to PR usb/140883; it has been noted by GNATS. > > > > From: Derrick Brashear > > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com > > Cc: > > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after > > short > > period of traffic > > Date: Thu, 18 Nov 2010 09:36:50 -0500 > > > > Pyun has provided an updated driver which avoids several issues > > including using a too-large transmit buffer (the chipset claims only > > 8k) but none of the fixes worked until he disabled frame combining for > > transmit. With only a single packet being sent per frame (as was the > > case in FreeBSD 7, apparently) seems to make the issue go away. None > > of the cases I could use to reproduce the issue now happen. > > > > -- > > Derrick > > is this already in 8-stable ? I have a couple of axe(4) based nic's > they're not ok on 8-stable. I've talked to Pyun before, and that time > seemed do solve the issue (with gigabit belkin axe based) but now I can't > get them to work anymore. even fast ethernet linksys axe are just dying > when in a bridge (switched to OpenBSD to have it working). > > how ca I try this to help ? > I uploaded updated if_axe.c/if_axereg.h to the following URL. http://people.freebsd.org/~yongari/axe/if_axe.c http://people.freebsd.org/~yongari/axe/if_axereg.h That files seem to fix axe(4) hang which were seen on AX88772A controller. One of most notable changes are removing combining multiple TX frames in TX path such that this change may result in sub-optimal performance for most axe(4) controllers. However it seems that change makes Derrick's controller work without problems. Generally I prefer driver stability over performance so if this change also fixes other axe(4) stability issues reported so far, I want to check in the change. Thanks. From owner-freebsd-usb@FreeBSD.ORG Thu Nov 18 21:53:47 2010 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 5A6C0106566B; Thu, 18 Nov 2010 21:53:47 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 341158FC13; Thu, 18 Nov 2010 21:53:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAILrla0059904; Thu, 18 Nov 2010 21:53:47 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAILrk63059900; Thu, 18 Nov 2010 21:53:46 GMT (envelope-from arundel) Date: Thu, 18 Nov 2010 21:53:46 GMT Message-Id: <201011182153.oAILrk63059900@freefall.freebsd.org> To: credo8@yandex.ru, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/135200: SAMSUNG i740 usb mass: Synchronize cache failed, status == 0x39, scsi status == 0x0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2010 21:53:47 -0000 Synopsis: SAMSUNG i740 usb mass: Synchronize cache failed, status == 0x39, scsi status == 0x0 State-Changed-From-To: open->feedback State-Changed-By: arundel State-Changed-When: Thu Nov 18 21:50:32 UTC 2010 State-Changed-Why: Did the quirk merely get rid of the warning, or did you have actual issues with this device? If so please post the actual failures. The point i ask is, because adding a quirk requires an actual problem with the device. If you're merely seeing warnings being issued to the console that is not a sufficient reason to add a quirk (see sys/cam/README.quirks). http://www.freebsd.org/cgi/query-pr.cgi?pr=135200 From owner-freebsd-usb@FreeBSD.ORG Thu Nov 18 22:21:10 2010 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 9E839106567A; Thu, 18 Nov 2010 22:21:10 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 780D48FC20; Thu, 18 Nov 2010 22:21:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAIMLALm091996; Thu, 18 Nov 2010 22:21:10 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAIML9Lv091932; Thu, 18 Nov 2010 22:21:09 GMT (envelope-from arundel) Date: Thu, 18 Nov 2010 22:21:09 GMT Message-Id: <201011182221.oAIML9Lv091932@freefall.freebsd.org> To: amdmi3@mail.ru, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/101775: [usb67] [libusbhid] [patch] possible error in report descriptor parsing X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2010 22:21:10 -0000 Old Synopsis: [usb67] [usb8] [libusbhid] [patch] possible error in report descriptor parsing New Synopsis: [usb67] [libusbhid] [patch] possible error in report descriptor parsing State-Changed-From-To: open->patched State-Changed-By: arundel State-Changed-When: Thu Nov 18 22:20:22 UTC 2010 State-Changed-Why: Fixed in HEAD (101775) and MFC'ed to 8.x (208262). http://www.freebsd.org/cgi/query-pr.cgi?pr=101775 From owner-freebsd-usb@FreeBSD.ORG Thu Nov 18 22:29:03 2010 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 57702106570B; Thu, 18 Nov 2010 22:29:03 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 32C2B8FC1A; Thu, 18 Nov 2010 22:29:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAIMT3Em092393; Thu, 18 Nov 2010 22:29:03 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAIMT2Vi092389; Thu, 18 Nov 2010 22:29:02 GMT (envelope-from arundel) Date: Thu, 18 Nov 2010 22:29:02 GMT Message-Id: <201011182229.oAIMT2Vi092389@freefall.freebsd.org> To: freebsd@insightbb.com, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/141680: [uath] [usb8] Netgear WG111T not working with uath driver X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2010 22:29:03 -0000 Synopsis: [uath] [usb8] Netgear WG111T not working with uath driver State-Changed-From-To: open->feedback State-Changed-By: arundel State-Changed-When: Thu Nov 18 22:28:38 UTC 2010 State-Changed-Why: Please note that feedback has been requested. http://www.freebsd.org/cgi/query-pr.cgi?pr=141680 From owner-freebsd-usb@FreeBSD.ORG Thu Nov 18 23:12:17 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F977106566B for ; Thu, 18 Nov 2010 23:12:17 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id 3AB188FC1A for ; Thu, 18 Nov 2010 23:12:17 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id 5B10E1CC3E; Thu, 18 Nov 2010 20:12:13 -0300 (BRT) Received: from 187.114.198.138 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Thu, 18 Nov 2010 21:12:13 -0200 Message-ID: In-Reply-To: <20101118202426.GB8512@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> <20101118202426.GB8512@michelle.cdnetworks.com> Date: Thu, 18 Nov 2010 21:12:13 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2010 23:12:17 -0000 On Thu, November 18, 2010 18:24, Pyun YongHyeon wrote: > On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos wrote: >> >> On Thu, November 18, 2010 13:10, Derrick Brashear wrote: >> > The following reply was made to PR usb/140883; it has been noted by >> GNATS. >> > >> > From: Derrick Brashear >> > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com >> > Cc: >> > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after >> > short >> > period of traffic >> > Date: Thu, 18 Nov 2010 09:36:50 -0500 >> > >> > Pyun has provided an updated driver which avoids several issues >> > including using a too-large transmit buffer (the chipset claims only >> > 8k) but none of the fixes worked until he disabled frame combining >> for >> > transmit. With only a single packet being sent per frame (as was the >> > case in FreeBSD 7, apparently) seems to make the issue go away. None >> > of the cases I could use to reproduce the issue now happen. >> > >> > -- >> > Derrick >> >> is this already in 8-stable ? I have a couple of axe(4) based nic's >> they're not ok on 8-stable. I've talked to Pyun before, and that time >> seemed do solve the issue (with gigabit belkin axe based) but now I >> can't >> get them to work anymore. even fast ethernet linksys axe are just dying >> when in a bridge (switched to OpenBSD to have it working). >> >> how ca I try this to help ? >> > > I uploaded updated if_axe.c/if_axereg.h to the following URL. > http://people.freebsd.org/~yongari/axe/if_axe.c > http://people.freebsd.org/~yongari/axe/if_axereg.h > > That files seem to fix axe(4) hang which were seen on AX88772A > controller. One of most notable changes are removing combining > multiple TX frames in TX path such that this change may result in > sub-optimal performance for most axe(4) controllers. However it > seems that change makes Derrick's controller work without problems. > Generally I prefer driver stability over performance so if this > change also fixes other axe(4) stability issues reported so far, I > want to check in the change. > > Thanks. well, things did got better here. but the link state UP and DOWN are still there :( ugen2.3: at usbus2 axe1: on usbus2 axe1: PHYADDR 0xe0:0x01 miibus2: on axe1 ukphy2: PHY 1 on miibus2 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FD X, auto ue1: on axe1 ue1: Ethernet address: "my mac shown here :)" ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ugen1.2: at usbus1 (disconnected) ukbd0: at uhub1, port 1, addr 2 (disconnected) ums0: at uhub1, port 1, addr 2 (disconnected) uhid0: at uhub1, port 1, addr 2 (disconnected) ue1: link state changed to DOWN ue1: link state changed to UP the good thing is, it usually never got recognized, and was said not to have a PHY (or something alike). so I get this: ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2): 56 data bytes ping: sendto: No route to host 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.912 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.842 ms ping: sendto: No route to host 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=1.015 ms 64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=0.774 ms 64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=0.789 ms 64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=0.851 ms 64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=0.915 ms ^C --- 192.168.1.2 ping statistics --- 11 packets transmitted, 7 packets received, 36.4% packet loss round-trip min/avg/max/stddev = 0.774/0.871/1.015/0.077 ms on local network. thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 00:06:23 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 154FB106566B for ; Fri, 19 Nov 2010 00:06:23 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id BC9078FC1A for ; Fri, 19 Nov 2010 00:06:22 +0000 (UTC) Received: by gwj20 with SMTP id 20so2406148gwj.13 for ; Thu, 18 Nov 2010 16:06:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=WGQkwuCdxgnlVe6tTNEWI6n70kun/O/UCUlv5/sTfNw=; b=v727lAg1gDTsOmYyNSs4+NgQQ9BJMPGjDd9GZXYyqQzaBy0EAUBWjJvG2kwXFKdO9F sOITWFNn+xu9GzOnTbzwcqaWTSH/dsLr9FqhVoTMs0n3RvjW2DkG3s5dC4mx3UwgYTGB AMzZm1+38XkaU6KMofGEkYYM0v+x8PqQ1Du70= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=BpqnT5gCEEXX1athrZbrIBeHUNEQM5m9k463n7nQWoDVYL4Q5zDX1V5fixsYQQzgC7 0WHWeoScE/CkFCgEHxhe9DDOiu8xU9r7CSnb16aN1sB8QeNgmccg1PRrGahTWxkp4Sza v2HFLKA/AKMo1QGNl0sHPaC93ijAJWfF2lugs= Received: by 10.151.15.7 with SMTP id s7mr2292048ybi.243.1290125181710; Thu, 18 Nov 2010 16:06:21 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id y11sm618345yhc.8.2010.11.18.16.06.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 18 Nov 2010 16:06:20 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 18 Nov 2010 16:06:18 -0800 From: Pyun YongHyeon Date: Thu, 18 Nov 2010 16:06:18 -0800 To: Nenhum_de_Nos Message-ID: <20101119000618.GC8512@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> <20101118202426.GB8512@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] 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: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 00:06:23 -0000 On Thu, Nov 18, 2010 at 09:12:13PM -0200, Nenhum_de_Nos wrote: > > On Thu, November 18, 2010 18:24, Pyun YongHyeon wrote: > > On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos wrote: > >> > >> On Thu, November 18, 2010 13:10, Derrick Brashear wrote: > >> > The following reply was made to PR usb/140883; it has been noted by > >> GNATS. > >> > > >> > From: Derrick Brashear > >> > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com > >> > Cc: > >> > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after > >> > short > >> > period of traffic > >> > Date: Thu, 18 Nov 2010 09:36:50 -0500 > >> > > >> > Pyun has provided an updated driver which avoids several issues > >> > including using a too-large transmit buffer (the chipset claims only > >> > 8k) but none of the fixes worked until he disabled frame combining > >> for > >> > transmit. With only a single packet being sent per frame (as was the > >> > case in FreeBSD 7, apparently) seems to make the issue go away. None > >> > of the cases I could use to reproduce the issue now happen. > >> > > >> > -- > >> > Derrick > >> > >> is this already in 8-stable ? I have a couple of axe(4) based nic's > >> they're not ok on 8-stable. I've talked to Pyun before, and that time > >> seemed do solve the issue (with gigabit belkin axe based) but now I > >> can't > >> get them to work anymore. even fast ethernet linksys axe are just dying > >> when in a bridge (switched to OpenBSD to have it working). > >> > >> how ca I try this to help ? > >> > > > > I uploaded updated if_axe.c/if_axereg.h to the following URL. > > http://people.freebsd.org/~yongari/axe/if_axe.c > > http://people.freebsd.org/~yongari/axe/if_axereg.h > > > > That files seem to fix axe(4) hang which were seen on AX88772A > > controller. One of most notable changes are removing combining > > multiple TX frames in TX path such that this change may result in > > sub-optimal performance for most axe(4) controllers. However it > > seems that change makes Derrick's controller work without problems. > > Generally I prefer driver stability over performance so if this > > change also fixes other axe(4) stability issues reported so far, I > > want to check in the change. > > > > Thanks. > > well, > > things did got better here. but the link state UP and DOWN are still there :( > > ugen2.3: at usbus2 > axe1: on usbus2 > axe1: PHYADDR 0xe0:0x01 > miibus2: on axe1 > ukphy2: PHY 1 on miibus2 > ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > 1000baseT-FD > X, auto It seems you have PHY driver issue. Normally all gigabit PHYs should have their own PHY driver since most PHYs hardwares tend to have a special register that reports link state changes. Show me the output of "devinfo -rv | grep phy". > ue1: on axe1 > ue1: Ethernet address: "my mac shown here :)" > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ugen1.2: at usbus1 (disconnected) > ukbd0: at uhub1, port 1, addr 2 (disconnected) > ums0: at uhub1, port 1, addr 2 (disconnected) > uhid0: at uhub1, port 1, addr 2 (disconnected) > ue1: link state changed to DOWN > ue1: link state changed to UP > > the good thing is, it usually never got recognized, and was said not to > have a PHY (or something alike). > Are you using 8.1-RELEASE? If yes, please give it try stable/8 and use axe(4) I posted. > so I get this: > > ping 192.168.1.2 > PING 192.168.1.2 (192.168.1.2): 56 data bytes > ping: sendto: No route to host > 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.912 ms > 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.842 ms > ping: sendto: No route to host > 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=1.015 ms > 64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=0.774 ms > 64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=0.789 ms > 64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=0.851 ms > 64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=0.915 ms > ^C > --- 192.168.1.2 ping statistics --- > 11 packets transmitted, 7 packets received, 36.4% packet loss > round-trip min/avg/max/stddev = 0.774/0.871/1.015/0.077 ms > > on local network. > > thanks, > > matheus > > > -- > We will call you cygnus, > The God of balance you shall be > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > > http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 00:40:17 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57E001065672 for ; Fri, 19 Nov 2010 00:40:17 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id 1C4338FC12 for ; Fri, 19 Nov 2010 00:40:16 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id D868A1CC3E; Thu, 18 Nov 2010 21:40:10 -0300 (BRT) Received: from 187.114.198.138 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Thu, 18 Nov 2010 22:40:10 -0200 Message-ID: <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> In-Reply-To: <20101119000618.GC8512@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> <20101118202426.GB8512@michelle.cdnetworks.com> <20101119000618.GC8512@michelle.cdnetworks.com> Date: Thu, 18 Nov 2010 22:40:10 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 00:40:17 -0000 On Thu, November 18, 2010 22:06, Pyun YongHyeon wrote: > On Thu, Nov 18, 2010 at 09:12:13PM -0200, Nenhum_de_Nos wrote: >> >> On Thu, November 18, 2010 18:24, Pyun YongHyeon wrote: >> > On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos wrote: >> >> >> >> On Thu, November 18, 2010 13:10, Derrick Brashear wrote: >> >> > The following reply was made to PR usb/140883; it has been noted by >> >> GNATS. >> >> > >> >> > From: Derrick Brashear >> >> > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com >> >> > Cc: >> >> > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs >> after >> >> > short >> >> > period of traffic >> >> > Date: Thu, 18 Nov 2010 09:36:50 -0500 >> >> > >> >> > Pyun has provided an updated driver which avoids several issues >> >> > including using a too-large transmit buffer (the chipset claims >> only >> >> > 8k) but none of the fixes worked until he disabled frame combining >> >> for >> >> > transmit. With only a single packet being sent per frame (as was >> the >> >> > case in FreeBSD 7, apparently) seems to make the issue go away. >> None >> >> > of the cases I could use to reproduce the issue now happen. >> >> > >> >> > -- >> >> > Derrick >> >> >> >> is this already in 8-stable ? I have a couple of axe(4) based nic's >> >> they're not ok on 8-stable. I've talked to Pyun before, and that time >> >> seemed do solve the issue (with gigabit belkin axe based) but now I >> >> can't >> >> get them to work anymore. even fast ethernet linksys axe are just >> dying >> >> when in a bridge (switched to OpenBSD to have it working). >> >> >> >> how ca I try this to help ? >> >> >> > >> > I uploaded updated if_axe.c/if_axereg.h to the following URL. >> > http://people.freebsd.org/~yongari/axe/if_axe.c >> > http://people.freebsd.org/~yongari/axe/if_axereg.h >> > >> > That files seem to fix axe(4) hang which were seen on AX88772A >> > controller. One of most notable changes are removing combining >> > multiple TX frames in TX path such that this change may result in >> > sub-optimal performance for most axe(4) controllers. However it >> > seems that change makes Derrick's controller work without problems. >> > Generally I prefer driver stability over performance so if this >> > change also fixes other axe(4) stability issues reported so far, I >> > want to check in the change. >> > >> > Thanks. >> >> well, >> >> things did got better here. but the link state UP and DOWN are still >> there :( >> >> ugen2.3: at usbus2 >> axe1: on usbus2 >> axe1: PHYADDR 0xe0:0x01 >> miibus2: on axe1 >> ukphy2: PHY 1 on miibus2 >> ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> 1000baseT-FD >> X, auto > > It seems you have PHY driver issue. Normally all gigabit PHYs > should have their own PHY driver since most PHYs hardwares tend to > have a special register that reports link state changes. > Show me the output of "devinfo -rv | grep phy". there you are: devinfo -rv|grep phy ukphy1 pnpinfo oui=0xec6 model=0x1 rev=0x1 at phyno=16 ukphy2 pnpinfo oui=0xa080 model=0x28 rev=0x2 at phyno=1 ukphy0 pnpinfo oui=0x4063 model=0x32 rev=0xa at phyno=1 >> ue1: on axe1 >> ue1: Ethernet address: "my mac shown here :)" >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ugen1.2: at usbus1 (disconnected) >> ukbd0: at uhub1, port 1, addr 2 (disconnected) >> ums0: at uhub1, port 1, addr 2 (disconnected) >> uhid0: at uhub1, port 1, addr 2 (disconnected) >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> >> the good thing is, it usually never got recognized, and was said not to >> have a PHY (or something alike). >> > > Are you using 8.1-RELEASE? If yes, please give it try stable/8 and > use axe(4) I posted. sorry, forgot to add: uname -a FreeBSD valfenda.apartnet 8.1-STABLE FreeBSD 8.1-STABLE #2: Fri Nov 5 01:52:06 BRT 2010 root@valfenda.apartnet:/usr/obj/usr/src/sys/valfenda i386 and this is using that axe(4) you posted :) just got a little deeper, and put two of them (all I have) connected. when in 1000Base-TX FullDuplex, the throughput is horrible., never get more then 3% of the link (on side this FreeBSD Stable shown above, the other Win7 and belkin drivers for it). when I force for 100BaseTX FullDuplex on Windows, and this way I get 68Mbps out of it (need to say the windows task manager keeps showing 90% link utilization quite all time, some falls from time to time though). thanks as usual, matheus >> so I get this: >> >> ping 192.168.1.2 >> PING 192.168.1.2 (192.168.1.2): 56 data bytes >> ping: sendto: No route to host >> 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.912 ms >> 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.842 ms >> ping: sendto: No route to host >> 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=1.015 ms >> 64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=0.774 ms >> 64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=0.789 ms >> 64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=0.851 ms >> 64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=0.915 ms >> ^C >> --- 192.168.1.2 ping statistics --- >> 11 packets transmitted, 7 packets received, 36.4% packet loss >> round-trip min/avg/max/stddev = 0.774/0.871/1.015/0.077 ms >> >> on local network. >> >> thanks, >> >> matheus >> >> >> -- >> We will call you cygnus, >> The God of balance you shall be >> >> A: Because it messes up the order in which people normally read text. >> Q: Why is top-posting such a bad thing? >> >> http://en.wikipedia.org/wiki/Posting_style > -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 01:30:16 2010 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 EB66610656AA for ; Fri, 19 Nov 2010 01:30:16 +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 C82CE8FC19 for ; Fri, 19 Nov 2010 01:30:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAJ1UGCV079163 for ; Fri, 19 Nov 2010 01:30:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAJ1UGCu079153; Fri, 19 Nov 2010 01:30:16 GMT (envelope-from gnats) Date: Fri, 19 Nov 2010 01:30:16 GMT Message-Id: <201011190130.oAJ1UGCu079153@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: usb/119981: commit references a PR X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 01:30:17 -0000 The following reply was made to PR usb/119981; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/119981: commit references a PR Date: Fri, 19 Nov 2010 01:24:41 +0000 (UTC) Author: thompsa Date: Fri Nov 19 01:24:36 2010 New Revision: 215479 URL: http://svn.freebsd.org/changeset/base/215479 Log: MFC r212980 Add new device ids. Buffalo (Melco Inc.) LUA3-U2-AGT Logitec LAN-GTJ/U2A(usb/119981) PR: usb/119981 Modified: Directory Properties: stable/8/share/man/man4/ (props changed) stable/8/sys/ (props changed) stable/8/sys/amd64/include/xen/ (props changed) stable/8/sys/cddl/contrib/opensolaris/ (props changed) stable/8/sys/contrib/dev/acpica/ (props changed) stable/8/sys/contrib/pf/ (props changed) stable/8/sys/dev/xen/xenpci/ (props changed) _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 01:39:02 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE35B1065670 for ; Fri, 19 Nov 2010 01:39:02 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7FD048FC15 for ; Fri, 19 Nov 2010 01:39:01 +0000 (UTC) Received: by gxk21 with SMTP id 21so23313gxk.13 for ; Thu, 18 Nov 2010 17:39:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=kZlQUpftPYIrz6IAShLD6CUMXPhns0wCOzOvxj58Qew=; b=bszpeegZJnwBN6gkFkm+7aJEh4HpqOx9fsXAKth/PWd2lTYaJ1LMH5eEZP3rsng8cj d3Z65IWDdmj8clsYyAdSO5BDo+vxxcvKs7YPvguCvBWQM4BGHMNzn2Q/KcRdBdTipet9 Pg/jZYHzTXWmYGn4Kq9JWpfIm7qwdwG1ujXyI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=uddWq0UDCivdM3nxwKr+4vUiH3HSL+hh0yKw6/rjFV1cpWBZZ/s8h81t2wmQmlt6g9 wBCuCwSNHMyMRFa9yDECqip9yDyzJ+Uy3q83GPL6a/KCaQcrEBIZhehSCf5XlIVlH2bH +DXSIqMHB/1/6reJk0ftOj81ldfnRZVe8fdMU= Received: by 10.90.2.10 with SMTP id 10mr1707318agb.81.1290130740303; Thu, 18 Nov 2010 17:39:00 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id k52sm670586yhg.39.2010.11.18.17.38.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 18 Nov 2010 17:38:59 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 18 Nov 2010 17:38:57 -0800 From: Pyun YongHyeon Date: Thu, 18 Nov 2010 17:38:57 -0800 To: Nenhum_de_Nos Message-ID: <20101119013857.GE8512@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> <20101118202426.GB8512@michelle.cdnetworks.com> <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] 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: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 01:39:02 -0000 On Thu, Nov 18, 2010 at 10:40:10PM -0200, Nenhum_de_Nos wrote: > > On Thu, November 18, 2010 22:06, Pyun YongHyeon wrote: > > On Thu, Nov 18, 2010 at 09:12:13PM -0200, Nenhum_de_Nos wrote: > >> > >> On Thu, November 18, 2010 18:24, Pyun YongHyeon wrote: > >> > On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos wrote: > >> >> > >> >> On Thu, November 18, 2010 13:10, Derrick Brashear wrote: > >> >> > The following reply was made to PR usb/140883; it has been noted by > >> >> GNATS. > >> >> > > >> >> > From: Derrick Brashear > >> >> > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com > >> >> > Cc: > >> >> > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs > >> after > >> >> > short > >> >> > period of traffic > >> >> > Date: Thu, 18 Nov 2010 09:36:50 -0500 > >> >> > > >> >> > Pyun has provided an updated driver which avoids several issues > >> >> > including using a too-large transmit buffer (the chipset claims > >> only > >> >> > 8k) but none of the fixes worked until he disabled frame combining > >> >> for > >> >> > transmit. With only a single packet being sent per frame (as was > >> the > >> >> > case in FreeBSD 7, apparently) seems to make the issue go away. > >> None > >> >> > of the cases I could use to reproduce the issue now happen. > >> >> > > >> >> > -- > >> >> > Derrick > >> >> > >> >> is this already in 8-stable ? I have a couple of axe(4) based nic's > >> >> they're not ok on 8-stable. I've talked to Pyun before, and that time > >> >> seemed do solve the issue (with gigabit belkin axe based) but now I > >> >> can't > >> >> get them to work anymore. even fast ethernet linksys axe are just > >> dying > >> >> when in a bridge (switched to OpenBSD to have it working). > >> >> > >> >> how ca I try this to help ? > >> >> > >> > > >> > I uploaded updated if_axe.c/if_axereg.h to the following URL. > >> > http://people.freebsd.org/~yongari/axe/if_axe.c > >> > http://people.freebsd.org/~yongari/axe/if_axereg.h > >> > > >> > That files seem to fix axe(4) hang which were seen on AX88772A > >> > controller. One of most notable changes are removing combining > >> > multiple TX frames in TX path such that this change may result in > >> > sub-optimal performance for most axe(4) controllers. However it > >> > seems that change makes Derrick's controller work without problems. > >> > Generally I prefer driver stability over performance so if this > >> > change also fixes other axe(4) stability issues reported so far, I > >> > want to check in the change. > >> > > >> > Thanks. > >> > >> well, > >> > >> things did got better here. but the link state UP and DOWN are still > >> there :( > >> > >> ugen2.3: at usbus2 > >> axe1: on usbus2 > >> axe1: PHYADDR 0xe0:0x01 > >> miibus2: on axe1 > >> ukphy2: PHY 1 on miibus2 > >> ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> 1000baseT-FD > >> X, auto > > > > It seems you have PHY driver issue. Normally all gigabit PHYs > > should have their own PHY driver since most PHYs hardwares tend to > > have a special register that reports link state changes. > > Show me the output of "devinfo -rv | grep phy". > > there you are: > > devinfo -rv|grep phy > ukphy1 pnpinfo oui=0xec6 model=0x1 rev=0x1 at phyno=16 > ukphy2 pnpinfo oui=0xa080 model=0x28 rev=0x2 at phyno=1 > ukphy0 pnpinfo oui=0x4063 model=0x32 rev=0xa at phyno=1 > Hmm.... You have many ukphys there. :-) I think the PHY attached to the USB controller is ukphy2. The OUI indicates its maker is ASIX. Unfortunately there is no dedicated PHY driver for this PHY. I guess it may use a modified CICADA PHY though. Updated driver to force GPIO configuration for this PHY. Would you try again after downloading if_axe.c/if_axereg.h? It may show "unknown PHY mode : 0xXX" if my guess is wrong. > > >> ue1: on axe1 > >> ue1: Ethernet address: "my mac shown here :)" > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> ugen1.2: at usbus1 (disconnected) > >> ukbd0: at uhub1, port 1, addr 2 (disconnected) > >> ums0: at uhub1, port 1, addr 2 (disconnected) > >> uhid0: at uhub1, port 1, addr 2 (disconnected) > >> ue1: link state changed to DOWN > >> ue1: link state changed to UP > >> > >> the good thing is, it usually never got recognized, and was said not to > >> have a PHY (or something alike). > >> > > > > Are you using 8.1-RELEASE? If yes, please give it try stable/8 and > > use axe(4) I posted. > > sorry, forgot to add: > > uname -a > FreeBSD valfenda.apartnet 8.1-STABLE FreeBSD 8.1-STABLE #2: Fri Nov 5 > 01:52:06 BRT 2010 root@valfenda.apartnet:/usr/obj/usr/src/sys/valfenda > i386 > > and this is using that axe(4) you posted :) > > just got a little deeper, and put two of them (all I have) connected. when > in 1000Base-TX FullDuplex, the throughput is horrible., never get more > then 3% of the link (on side this FreeBSD Stable shown above, the other I'm not surprised with the poor performance since you have link flapping issues. :-( > Win7 and belkin drivers for it). when I force for 100BaseTX FullDuplex on > Windows, and this way I get 68Mbps out of it (need to say the windows task > manager keeps showing 90% link utilization quite all time, some falls from > time to time though). > > thanks as usual, > From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 01:40:11 2010 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 A58B5106566B for ; Fri, 19 Nov 2010 01:40:11 +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 95C4F8FC08 for ; Fri, 19 Nov 2010 01:40:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAJ1e9PG089385 for ; Fri, 19 Nov 2010 01:40:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAJ1e9uF089384; Fri, 19 Nov 2010 01:40:09 GMT (envelope-from gnats) Date: Fri, 19 Nov 2010 01:40:09 GMT Message-Id: <201011190140.oAJ1e9uF089384@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: usb/135575: commit references a PR X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 01:40:11 -0000 The following reply was made to PR usb/135575; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/135575: commit references a PR Date: Fri, 19 Nov 2010 01:36:06 +0000 (UTC) Author: thompsa Date: Fri Nov 19 01:35:57 2010 New Revision: 215488 URL: http://svn.freebsd.org/changeset/base/215488 Log: MFC r210469 Give a name to the HTC Wizard Smartphone PR: usb/135575 Modified: stable/8/sys/dev/usb/serial/uipaq.c stable/8/sys/dev/usb/usbdevs Directory Properties: stable/8/sys/ (props changed) stable/8/sys/amd64/include/xen/ (props changed) stable/8/sys/cddl/contrib/opensolaris/ (props changed) stable/8/sys/contrib/dev/acpica/ (props changed) stable/8/sys/contrib/pf/ (props changed) stable/8/sys/dev/xen/xenpci/ (props changed) Modified: stable/8/sys/dev/usb/serial/uipaq.c ============================================================================== --- stable/8/sys/dev/usb/serial/uipaq.c Fri Nov 19 01:35:14 2010 (r215487) +++ stable/8/sys/dev/usb/serial/uipaq.c Fri Nov 19 01:35:57 2010 (r215488) @@ -690,14 +690,14 @@ static const struct usb_device_id uipaq_ {USB_VPI(USB_VENDOR_HTC, 0x0a9e, 0)}, /* SmartPhone USB Sync */ {USB_VPI(USB_VENDOR_HTC, 0x0a9f, 0)}, - /* "High Tech Computer Corp" */ - {USB_VPI(USB_VENDOR_HTC, 0x0bce, 0)}, /**/ {USB_VPI(USB_VENDOR_HTC, USB_PRODUCT_HTC_PPC6700MODEM, 0)}, /**/ {USB_VPI(USB_VENDOR_HTC, USB_PRODUCT_HTC_SMARTPHONE, 0)}, /**/ {USB_VPI(USB_VENDOR_HTC, USB_PRODUCT_HTC_WINMOBILE, 0)}, + /* High Tech Computer Wizard Smartphone */ + {USB_VPI(USB_VENDOR_HTC, USB_PRODUCT_HTC_WIZARD, 0)}, /* JVC USB Sync */ {USB_VPI(USB_VENDOR_JVC, 0x3011, 0)}, /* JVC USB Sync */ Modified: stable/8/sys/dev/usb/usbdevs ============================================================================== --- stable/8/sys/dev/usb/usbdevs Fri Nov 19 01:35:14 2010 (r215487) +++ stable/8/sys/dev/usb/usbdevs Fri Nov 19 01:35:57 2010 (r215488) @@ -1761,6 +1761,7 @@ product HP HS2300 0x1e1d hs2300 HSDPA product HTC WINMOBILE 0x00ce HTC USB Sync product HTC PPC6700MODEM 0x00cf PPC6700 Modem product HTC SMARTPHONE 0x0a51 SmartPhone USB Sync +product HTC WIZARD 0x0bce HTC Wizard USB Sync /* HUAWEI products */ product HUAWEI MOBILE 0x1001 Huawei Mobile _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 01:50:13 2010 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 66DE71065674 for ; Fri, 19 Nov 2010 01:50:13 +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 574008FC1C for ; Fri, 19 Nov 2010 01:50:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAJ1oDOI098724 for ; Fri, 19 Nov 2010 01:50:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAJ1oDfg098723; Fri, 19 Nov 2010 01:50:13 GMT (envelope-from gnats) Date: Fri, 19 Nov 2010 01:50:13 GMT Message-Id: <201011190150.oAJ1oDfg098723@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: usb/141212: commit references a PR X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 01:50:13 -0000 The following reply was made to PR usb/141212; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/141212: commit references a PR Date: Fri, 19 Nov 2010 01:43:14 +0000 (UTC) Author: thompsa Date: Fri Nov 19 01:43:08 2010 New Revision: 215494 URL: http://svn.freebsd.org/changeset/base/215494 Log: MFC r212128 Silence debug error by default. PR: usb/141212 Modified: stable/8/sys/dev/usb/input/ukbd.c Directory Properties: stable/8/sys/ (props changed) stable/8/sys/amd64/include/xen/ (props changed) stable/8/sys/cddl/contrib/opensolaris/ (props changed) stable/8/sys/contrib/dev/acpica/ (props changed) stable/8/sys/contrib/pf/ (props changed) stable/8/sys/dev/xen/xenpci/ (props changed) Modified: stable/8/sys/dev/usb/input/ukbd.c ============================================================================== --- stable/8/sys/dev/usb/input/ukbd.c Fri Nov 19 01:42:13 2010 (r215493) +++ stable/8/sys/dev/usb/input/ukbd.c Fri Nov 19 01:43:08 2010 (r215494) @@ -727,7 +727,7 @@ ukbd_set_leds_callback(struct usb_xfer * break; default: /* Error */ - DPRINTFN(0, "error=%s\n", usbd_errstr(error)); + DPRINTFN(1, "error=%s\n", usbd_errstr(error)); break; } } _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 05:19:30 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7154106566B for ; Fri, 19 Nov 2010 05:19:30 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id 731138FC19 for ; Fri, 19 Nov 2010 05:19:30 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id 7978C1CC3E; Fri, 19 Nov 2010 02:19:26 -0300 (BRT) Received: from 187.114.198.138 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Fri, 19 Nov 2010 03:19:26 -0200 Message-ID: <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> In-Reply-To: <20101119013857.GE8512@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> <20101118202426.GB8512@michelle.cdnetworks.com> <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> Date: Fri, 19 Nov 2010 03:19:26 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 05:19:31 -0000 On Thu, November 18, 2010 23:38, Pyun YongHyeon wrote: > On Thu, Nov 18, 2010 at 10:40:10PM -0200, Nenhum_de_Nos wrote: >> >> On Thu, November 18, 2010 22:06, Pyun YongHyeon wrote: >> > On Thu, Nov 18, 2010 at 09:12:13PM -0200, Nenhum_de_Nos wrote: >> >> >> >> On Thu, November 18, 2010 18:24, Pyun YongHyeon wrote: >> >> > On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos wrote: >> >> >> >> >> >> On Thu, November 18, 2010 13:10, Derrick Brashear wrote: >> >> >> > The following reply was made to PR usb/140883; it has been noted >> by >> >> >> GNATS. >> >> >> > >> >> >> > From: Derrick Brashear >> >> >> > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com >> >> >> > Cc: >> >> >> > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs >> >> after >> >> >> > short >> >> >> > period of traffic >> >> >> > Date: Thu, 18 Nov 2010 09:36:50 -0500 >> >> >> > >> >> >> > Pyun has provided an updated driver which avoids several issues >> >> >> > including using a too-large transmit buffer (the chipset claims >> >> only >> >> >> > 8k) but none of the fixes worked until he disabled frame >> combining >> >> >> for >> >> >> > transmit. With only a single packet being sent per frame (as >> was >> >> the >> >> >> > case in FreeBSD 7, apparently) seems to make the issue go away. >> >> None >> >> >> > of the cases I could use to reproduce the issue now happen. >> >> >> > >> >> >> > -- >> >> >> > Derrick >> >> >> >> >> >> is this already in 8-stable ? I have a couple of axe(4) based >> nic's >> >> >> they're not ok on 8-stable. I've talked to Pyun before, and that >> time >> >> >> seemed do solve the issue (with gigabit belkin axe based) but now >> I >> >> >> can't >> >> >> get them to work anymore. even fast ethernet linksys axe are just >> >> dying >> >> >> when in a bridge (switched to OpenBSD to have it working). >> >> >> >> >> >> how ca I try this to help ? >> >> >> >> >> > >> >> > I uploaded updated if_axe.c/if_axereg.h to the following URL. >> >> > http://people.freebsd.org/~yongari/axe/if_axe.c >> >> > http://people.freebsd.org/~yongari/axe/if_axereg.h >> >> > >> >> > That files seem to fix axe(4) hang which were seen on AX88772A >> >> > controller. One of most notable changes are removing combining >> >> > multiple TX frames in TX path such that this change may result in >> >> > sub-optimal performance for most axe(4) controllers. However it >> >> > seems that change makes Derrick's controller work without problems. >> >> > Generally I prefer driver stability over performance so if this >> >> > change also fixes other axe(4) stability issues reported so far, I >> >> > want to check in the change. >> >> > >> >> > Thanks. >> >> >> >> well, >> >> >> >> things did got better here. but the link state UP and DOWN are still >> >> there :( >> >> >> >> ugen2.3: at usbus2 >> >> axe1: on usbus2 >> >> axe1: PHYADDR 0xe0:0x01 >> >> miibus2: on axe1 >> >> ukphy2: PHY 1 on miibus2 >> >> ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> >> 1000baseT-FD >> >> X, auto >> > >> > It seems you have PHY driver issue. Normally all gigabit PHYs >> > should have their own PHY driver since most PHYs hardwares tend to >> > have a special register that reports link state changes. >> > Show me the output of "devinfo -rv | grep phy". >> >> there you are: >> >> devinfo -rv|grep phy >> ukphy1 pnpinfo oui=0xec6 model=0x1 rev=0x1 at phyno=16 >> ukphy2 pnpinfo oui=0xa080 model=0x28 rev=0x2 at >> phyno=1 >> ukphy0 pnpinfo oui=0x4063 model=0x32 rev=0xa at phyno=1 >> > > Hmm.... You have many ukphys there. :-) I think the PHY attached to > the USB controller is ukphy2. The OUI indicates its maker is ASIX. > Unfortunately there is no dedicated PHY driver for this PHY. I > guess it may use a modified CICADA PHY though. Updated driver to > force GPIO configuration for this PHY. Would you try again after > downloading if_axe.c/if_axereg.h? It may show > "unknown PHY mode : 0xXX" if my guess is wrong. I downloaded again from above links and are the same as the last: valfenda# md5 if_axe* MD5 (if_axe.c) = 388b7aa84f0d2471f8b144033103618b MD5 (if_axe.c.original) = c528c7cb5eb964a792d4c14dfaed47cf MD5 (if_axe.c.v1) = 388b7aa84f0d2471f8b144033103618b MD5 (if_axereg.h) = 10f85490cab59b8e40de261fd7ad81a5 MD5 (if_axereg.h.original) = 46f37d0f02a3c09463ceec58b743c6ce MD5 (if_axereg.h.v1) = 10f85490cab59b8e40de261fd7ad81a5 .original are files from 8-stable (via csup) .v1 are the files from http://people.freebsd.org/~yongari/axe/ downloaded when the fist test using those files were made. regular .c files were downloaded now when I read this mail. did you uploaded some new version in http://people.freebsd.org/~yongari/axe/ ? or I didn't got it ? :) should this modified version be a good test to fast ethernet axe nics ? my linksys USB200M failed when in bridge after some time of use :( same hardware I'm testing now. and the nics are ok, tested in OpenBSD with same hardware and same bridge and same pf conf file. thanks, matheus >> >> >> ue1: on axe1 >> >> ue1: Ethernet address: "my mac shown here :)" >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> ugen1.2: at usbus1 (disconnected) >> >> ukbd0: at uhub1, port 1, addr 2 (disconnected) >> >> ums0: at uhub1, port 1, addr 2 (disconnected) >> >> uhid0: at uhub1, port 1, addr 2 (disconnected) >> >> ue1: link state changed to DOWN >> >> ue1: link state changed to UP >> >> >> >> the good thing is, it usually never got recognized, and was said not >> to >> >> have a PHY (or something alike). >> >> >> > >> > Are you using 8.1-RELEASE? If yes, please give it try stable/8 and >> > use axe(4) I posted. >> >> sorry, forgot to add: >> >> uname -a >> FreeBSD valfenda.apartnet 8.1-STABLE FreeBSD 8.1-STABLE #2: Fri Nov 5 >> 01:52:06 BRT 2010 >> root@valfenda.apartnet:/usr/obj/usr/src/sys/valfenda >> i386 >> >> and this is using that axe(4) you posted :) >> >> just got a little deeper, and put two of them (all I have) connected. >> when >> in 1000Base-TX FullDuplex, the throughput is horrible., never get more >> then 3% of the link (on side this FreeBSD Stable shown above, the other > > I'm not surprised with the poor performance since you have link > flapping issues. :-( > >> Win7 and belkin drivers for it). when I force for 100BaseTX FullDuplex >> on >> Windows, and this way I get 68Mbps out of it (need to say the windows >> task >> manager keeps showing 90% link utilization quite all time, some falls >> from >> time to time though). >> >> thanks as usual, >> > -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 14:33:43 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AC76106566B for ; Fri, 19 Nov 2010 14:33:43 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 4B63E8FC18 for ; Fri, 19 Nov 2010 14:33:43 +0000 (UTC) Received: from [88.217.17.230] (helo=current.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PJS20-0002KO-GT for freebsd-usb@freebsd.org; Fri, 19 Nov 2010 15:33:40 +0100 Received: from current.Sisis.de (current [127.0.0.1]) by current.Sisis.de (8.14.3/8.14.3) with ESMTP id oAJEXcBm003080 for ; Fri, 19 Nov 2010 15:33:38 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id oAJEXbCq003079 for freebsd-usb@freebsd.org; Fri, 19 Nov 2010 15:33:37 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Fri, 19 Nov 2010 15:33:37 +0100 From: Matthias Apitz To: freebsd-usb@freebsd.org Message-ID: <20101119143337.GA3023@current.Sisis.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 88.217.17.230 Subject: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 14:33:43 -0000 Hello, How is this possible: $ dd if=/dev/da0 of=f1 7892087+0 records in 7892087+0 records out $ dd if=/dev/da0 of=f2 7892087+0 records in 7892087+0 records out $ diff f1 f1 Files f1 and f2 differ (and no, /dev/da0s1a is not mounted). Thx matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 14:36:34 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E0AC106566C for ; Fri, 19 Nov 2010 14:36:34 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.c2i.net [212.247.154.66]) by mx1.freebsd.org (Postfix) with ESMTP id E70768FC0A for ; Fri, 19 Nov 2010 14:36:33 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=drJD7N2WYgraSrvx4WFOmF+tWOmhzpnKhDnOdsziBzQ= c=1 sm=1 a=fsDGt_0-TPkA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=k8Rp0gd5krMBuSC2jNcA:9 a=ZdFMwY5RIs6QTxh0DuM69M5fsKAA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 51475620; Fri, 19 Nov 2010 15:36:31 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org, Matthias Apitz Date: Fri, 19 Nov 2010 15:37:25 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <20101119143337.GA3023@current.Sisis.de> In-Reply-To: <20101119143337.GA3023@current.Sisis.de> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011191537.25867.hselasky@c2i.net> Cc: Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 14:36:34 -0000 On Friday 19 November 2010 15:33:37 Matthias Apitz wrote: > Hello, > > How is this possible: > > $ dd if=/dev/da0 of=f1 > 7892087+0 records in > 7892087+0 records out > $ dd if=/dev/da0 of=f2 > 7892087+0 records in > 7892087+0 records out > $ diff f1 f1 > Files f1 and f2 differ > > (and no, /dev/da0s1a is not mounted). > > Thx > > matthias Hi, Can you dump the data into hex using hexdump -C and show us the difference. Usually you would use bs=65536 (Does that change anything)? --HPS From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 15:55:33 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17E9A106564A for ; Fri, 19 Nov 2010 15:55:33 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from ftp.translate.ru (ftp.translate.ru [80.249.188.42]) by mx1.freebsd.org (Postfix) with ESMTP id CBB0F8FC08 for ; Fri, 19 Nov 2010 15:55:32 +0000 (UTC) Received: from desktop.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id BAF6913DF46 for ; Fri, 19 Nov 2010 18:55:30 +0300 (MSK) Date: Fri, 19 Nov 2010 18:55:27 +0300 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <441397602.20101119185527@serebryakov.spb.ru> To: freebsd-usb@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Subject: Two questions: how to specify module-load function for driver module and which name of driver is better (according to "standards") X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 15:55:33 -0000 Hello, Freebsd-usb. I've implemented driver (ucom-subdriver) for MosChip 7820 and 7840 USB2COM multiport bridges. I have two questions: (1) How should I specify module-load function? DRIVER_MODULE() doesn't help much. I need to run some code only once, at very beginning, not for each probe/attach. GEOM modules have methods for it, but I can not find such methods for drivers. (2) Which name should I choose? Working name of module/driver/device is "mos7840", but it seems, that it is bad name: (a) All existing ucom-based drivers is "uXXXcom" (b) Driver instances looks ugly (like "mos78400") Is "umos7840com" good name or it is too long? :) We have "umoscom" driver for older MosChip chip in base already. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 16:19:26 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 667ED106564A for ; Fri, 19 Nov 2010 16:19:26 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.c2i.net [212.247.154.34]) by mx1.freebsd.org (Postfix) with ESMTP id E496E8FC08 for ; Fri, 19 Nov 2010 16:19:25 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=yevn+QCjI6xy199BDvBOOiO14qYvyLq62he9tTtU3M8= c=1 sm=1 a=Dyoqhi_TatcA:10 a=Az84e6_TBBoA:10 a=Cfj4BQAnxiAA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=uiEJq9c6V-77wL5lJw4A:9 a=6nN2yKmZUWJc456s0lQxGNvQmWsA:4 a=Ft8UYL4EG9YA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 51338368; Fri, 19 Nov 2010 17:19:23 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Fri, 19 Nov 2010 17:20:15 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <441397602.20101119185527@serebryakov.spb.ru> In-Reply-To: <441397602.20101119185527@serebryakov.spb.ru> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1251" Content-Transfer-Encoding: 7bit Message-Id: <201011191720.15402.hselasky@c2i.net> Cc: Lev Serebryakov Subject: Re: Two questions: how to specify module-load function for driver module and which name of driver is better (according to "standards") X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 16:19:26 -0000 On Friday 19 November 2010 16:55:27 Lev Serebryakov wrote: > Hello, Freebsd-usb. > > I've implemented driver (ucom-subdriver) for MosChip 7820 and 7840 > USB2COM multiport bridges. I have two questions: > Hi, > (1) How should I specify module-load function? DRIVER_MODULE() > doesn't help much. I need to run some code only once, at very > beginning, not for each probe/attach. GEOM modules have methods for > it, but I can not find such methods for drivers. Look at ubt_modevent in sys/netgraph/bluetooth/drivers/ubt/ng_ubt.c. Or use a so-called SYSINIT() or SYSUNINIT(). > > (2) Which name should I choose? Working name of module/driver/device > is "mos7840", but it seems, that it is bad name: > (a) All existing ucom-based drivers is "uXXXcom" > (b) Driver instances looks ugly (like "mos78400") umos78400 ? > > Is "umos7840com" good name or it is too long? :) We have "umoscom" > driver for older MosChip chip in base already. Maybe someone else has some comments. --HPS From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 16:39:08 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17666106566B for ; Fri, 19 Nov 2010 16:39:08 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from ftp.translate.ru (ftp.translate.ru [80.249.188.42]) by mx1.freebsd.org (Postfix) with ESMTP id C751E8FC0A for ; Fri, 19 Nov 2010 16:39:07 +0000 (UTC) Received: from desktop.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id 6A0EF13DF46; Fri, 19 Nov 2010 19:39:06 +0300 (MSK) Date: Fri, 19 Nov 2010 19:39:02 +0300 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <371920971.20101119193902@serebryakov.spb.ru> To: Andriy Gapon In-Reply-To: <4CE6A5EF.9010105@freebsd.org> References: <441397602.20101119185527@serebryakov.spb.ru> <4CE6A5EF.9010105@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb@freebsd.org Subject: Re: Two questions: how to specify module-load function for driver module and which name of driver is better (according to "standards") X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 16:39:08 -0000 Hello, Andriy. You wrote 19 =ED=EE=FF=E1=F0=FF 2010 =E3., 19:29:35: >> I've implemented driver (ucom-subdriver) for MosChip 7820 and 7840 >> USB2COM multiport bridges. I have two questions: >>=20 >> (1) How should I specify module-load function? DRIVER_MODULE() >> doesn't help much. > Are you sure? > The last two arguments to DRIVER_MODULE() look like what you want. Yes, it my fault, it works after hint from Hans Petter Selasky. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 16:46:58 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D71C106566B for ; Fri, 19 Nov 2010 16:46:58 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D29678FC14 for ; Fri, 19 Nov 2010 16:46:57 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA15611; Fri, 19 Nov 2010 18:29:36 +0200 (EET) (envelope-from avg@freebsd.org) Message-ID: <4CE6A5EF.9010105@freebsd.org> Date: Fri, 19 Nov 2010 18:29:35 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101029 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Lev Serebryakov References: <441397602.20101119185527@serebryakov.spb.ru> In-Reply-To: <441397602.20101119185527@serebryakov.spb.ru> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org Subject: Re: Two questions: how to specify module-load function for driver module and which name of driver is better (according to "standards") X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 16:46:58 -0000 on 19/11/2010 17:55 Lev Serebryakov said the following: > Hello, Freebsd-usb. > > I've implemented driver (ucom-subdriver) for MosChip 7820 and 7840 > USB2COM multiport bridges. I have two questions: > > (1) How should I specify module-load function? DRIVER_MODULE() > doesn't help much. Are you sure? The last two arguments to DRIVER_MODULE() look like what you want. > I need to run some code only once, at very > beginning, not for each probe/attach. -- Andriy Gapon From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 17:03:05 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3711106564A for ; Fri, 19 Nov 2010 17:03:05 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 6F7A58FC14 for ; Fri, 19 Nov 2010 17:03:05 +0000 (UTC) Received: from [88.217.17.230] (helo=current.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PJUMZ-0000Az-0L; Fri, 19 Nov 2010 18:03:03 +0100 Received: from current.Sisis.de (current [127.0.0.1]) by current.Sisis.de (8.14.3/8.14.3) with ESMTP id oAJH306o003799; Fri, 19 Nov 2010 18:03:00 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id oAJH2xSe003798; Fri, 19 Nov 2010 18:02:59 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Fri, 19 Nov 2010 18:02:59 +0100 From: Matthias Apitz To: Hans Petter Selasky Message-ID: <20101119170259.GA3741@current.Sisis.de> References: <20101119143337.GA3023@current.Sisis.de> <201011191537.25867.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201011191537.25867.hselasky@c2i.net> X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 88.217.17.230 Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 17:03:05 -0000 El día Friday, November 19, 2010 a las 03:37:25PM +0100, Hans Petter Selasky escribió: > On Friday 19 November 2010 15:33:37 Matthias Apitz wrote: > > Hello, > > > > How is this possible: > > > > $ dd if=/dev/da0 of=f1 > > 7892087+0 records in > > 7892087+0 records out > > $ dd if=/dev/da0 of=f2 > > 7892087+0 records in > > 7892087+0 records out > > $ diff f1 f1 > > Files f1 and f2 differ > > > > (and no, /dev/da0s1a is not mounted). > > > > Thx > > > > matthias > > Hi, > > Can you dump the data into hex using hexdump -C and show us the difference. Note: the output of the dd(1) is around 3.8 GByte. I compared the 1st 2.000.000 lines of the hexdump: no diff; any better tool to show the 1st block which differs? > Usually you would use bs=65536 (Does that change anything)? Same result: they differ :-( matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 17:13:29 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4C4D1065674 for ; Fri, 19 Nov 2010 17:13:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5D32B8FC1C for ; Fri, 19 Nov 2010 17:13:28 +0000 (UTC) Received: by pvc22 with SMTP id 22so1149588pvc.13 for ; Fri, 19 Nov 2010 09:13:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=wL6ACJZgsRc1j0sulVGBkQuj/GKgPhToU/6mydskyjE=; b=TQAB9y4JnPLMuLgZXB/FyEuViOIvK0UEG4uxugQB+YiICqF67zUv/NoZFFnQXl8kJA mnyHWAb1p28hWOVX8TedFFUIDnlx4hXvgnjDsX6+IOESESKMYTPW2zLuzfpHxJVWscPT dN+fg/ngOtYMqzIMfHHNnmWohUK7m5z+zphfA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=C78Nq+hvA9N7KLY2gux9PLBwicGt9uLk3lF/+XLRvl9nouMUizQxz6AI4rkU+eZ8Od Cbr79NO7dPsBGwPS2o+jFjlZpUbGQVKln0l+zdSrG+4118nr0zjdYclb61PwGaoGwoNK /0VZcnyx9ko49fvOjATk4pEP0ws4jpNJlVIYs= Received: by 10.142.161.12 with SMTP id j12mr1912428wfe.201.1290186808632; Fri, 19 Nov 2010 09:13:28 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id q13sm2121774wfc.17.2010.11.19.09.13.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Nov 2010 09:13:24 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 19 Nov 2010 09:13:24 -0800 From: Pyun YongHyeon Date: Fri, 19 Nov 2010 09:13:24 -0800 To: Nenhum_de_Nos Message-ID: <20101119171324.GA13317@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> <20101118202426.GB8512@michelle.cdnetworks.com> <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] 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: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 17:13:29 -0000 On Fri, Nov 19, 2010 at 03:19:26AM -0200, Nenhum_de_Nos wrote: > > On Thu, November 18, 2010 23:38, Pyun YongHyeon wrote: > > On Thu, Nov 18, 2010 at 10:40:10PM -0200, Nenhum_de_Nos wrote: > >> > >> On Thu, November 18, 2010 22:06, Pyun YongHyeon wrote: > >> > On Thu, Nov 18, 2010 at 09:12:13PM -0200, Nenhum_de_Nos wrote: > >> >> > >> >> On Thu, November 18, 2010 18:24, Pyun YongHyeon wrote: > >> >> > On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos wrote: > >> >> >> > >> >> >> On Thu, November 18, 2010 13:10, Derrick Brashear wrote: > >> >> >> > The following reply was made to PR usb/140883; it has been noted > >> by > >> >> >> GNATS. > >> >> >> > > >> >> >> > From: Derrick Brashear > >> >> >> > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com > >> >> >> > Cc: > >> >> >> > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs > >> >> after > >> >> >> > short > >> >> >> > period of traffic > >> >> >> > Date: Thu, 18 Nov 2010 09:36:50 -0500 > >> >> >> > > >> >> >> > Pyun has provided an updated driver which avoids several issues > >> >> >> > including using a too-large transmit buffer (the chipset claims > >> >> only > >> >> >> > 8k) but none of the fixes worked until he disabled frame > >> combining > >> >> >> for > >> >> >> > transmit. With only a single packet being sent per frame (as > >> was > >> >> the > >> >> >> > case in FreeBSD 7, apparently) seems to make the issue go away. > >> >> None > >> >> >> > of the cases I could use to reproduce the issue now happen. > >> >> >> > > >> >> >> > -- > >> >> >> > Derrick > >> >> >> > >> >> >> is this already in 8-stable ? I have a couple of axe(4) based > >> nic's > >> >> >> they're not ok on 8-stable. I've talked to Pyun before, and that > >> time > >> >> >> seemed do solve the issue (with gigabit belkin axe based) but now > >> I > >> >> >> can't > >> >> >> get them to work anymore. even fast ethernet linksys axe are just > >> >> dying > >> >> >> when in a bridge (switched to OpenBSD to have it working). > >> >> >> > >> >> >> how ca I try this to help ? > >> >> >> > >> >> > > >> >> > I uploaded updated if_axe.c/if_axereg.h to the following URL. > >> >> > http://people.freebsd.org/~yongari/axe/if_axe.c > >> >> > http://people.freebsd.org/~yongari/axe/if_axereg.h > >> >> > > >> >> > That files seem to fix axe(4) hang which were seen on AX88772A > >> >> > controller. One of most notable changes are removing combining > >> >> > multiple TX frames in TX path such that this change may result in > >> >> > sub-optimal performance for most axe(4) controllers. However it > >> >> > seems that change makes Derrick's controller work without problems. > >> >> > Generally I prefer driver stability over performance so if this > >> >> > change also fixes other axe(4) stability issues reported so far, I > >> >> > want to check in the change. > >> >> > > >> >> > Thanks. > >> >> > >> >> well, > >> >> > >> >> things did got better here. but the link state UP and DOWN are still > >> >> there :( > >> >> > >> >> ugen2.3: at usbus2 > >> >> axe1: on usbus2 > >> >> axe1: PHYADDR 0xe0:0x01 > >> >> miibus2: on axe1 > >> >> ukphy2: PHY 1 on miibus2 > >> >> ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> >> 1000baseT-FD > >> >> X, auto > >> > > >> > It seems you have PHY driver issue. Normally all gigabit PHYs > >> > should have their own PHY driver since most PHYs hardwares tend to > >> > have a special register that reports link state changes. > >> > Show me the output of "devinfo -rv | grep phy". > >> > >> there you are: > >> > >> devinfo -rv|grep phy > >> ukphy1 pnpinfo oui=0xec6 model=0x1 rev=0x1 at phyno=16 > >> ukphy2 pnpinfo oui=0xa080 model=0x28 rev=0x2 at > >> phyno=1 > >> ukphy0 pnpinfo oui=0x4063 model=0x32 rev=0xa at phyno=1 > >> > > > > Hmm.... You have many ukphys there. :-) I think the PHY attached to > > the USB controller is ukphy2. The OUI indicates its maker is ASIX. > > Unfortunately there is no dedicated PHY driver for this PHY. I > > guess it may use a modified CICADA PHY though. Updated driver to > > force GPIO configuration for this PHY. Would you try again after > > downloading if_axe.c/if_axereg.h? It may show > > "unknown PHY mode : 0xXX" if my guess is wrong. > > I downloaded again from above links and are the same as the last: > > valfenda# md5 if_axe* > MD5 (if_axe.c) = 388b7aa84f0d2471f8b144033103618b > MD5 (if_axe.c.original) = c528c7cb5eb964a792d4c14dfaed47cf > MD5 (if_axe.c.v1) = 388b7aa84f0d2471f8b144033103618b > MD5 (if_axereg.h) = 10f85490cab59b8e40de261fd7ad81a5 > MD5 (if_axereg.h.original) = 46f37d0f02a3c09463ceec58b743c6ce > MD5 (if_axereg.h.v1) = 10f85490cab59b8e40de261fd7ad81a5 > > .original are files from 8-stable (via csup) > .v1 are the files from http://people.freebsd.org/~yongari/axe/ downloaded > when the fist test using those files were made. > regular .c files were downloaded now when I read this mail. > > did you uploaded some new version in > http://people.freebsd.org/~yongari/axe/ ? or I didn't got it ? :) > Oops, it seems I forgot to upload it after modifying it. Please download again. MD5 should be 507a672946e7c0394e83c79d1a12c9b5 (if_axe.c) and 10f85490cab59b8e40de261fd7ad81a5 (if_axereg.h) > should this modified version be a good test to fast ethernet axe nics ? my > linksys USB200M failed when in bridge after some time of use :( same Yes, the change made in if_axe.c is for AX88178, AX88772 and AX8872A. The change has no effect for AX88172. Your controller would be either AX88772 or AX88772A so chances are good to see different behavior than ever before. > hardware I'm testing now. and the nics are ok, tested in OpenBSD with same > hardware and same bridge and same pf conf file. > > thanks, > > matheus > From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 17:20:20 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0DF0106564A for ; Fri, 19 Nov 2010 17:20:20 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.c2i.net [212.247.154.194]) by mx1.freebsd.org (Postfix) with ESMTP id 5CE068FC14 for ; Fri, 19 Nov 2010 17:20:19 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=vDUu4pv7IaR8DTRzVjjCCOYxZ4yAx/7/dG3VXczAVmg= c=1 sm=1 a=fsDGt_0-TPkA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=puUwJJ0ZExkaHy4e0kUA:9 a=Ze3zplmwjXIvDBarvuzZG24AtFkA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe07.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 51322612; Fri, 19 Nov 2010 18:20:17 +0100 From: Hans Petter Selasky To: Matthias Apitz Date: Fri, 19 Nov 2010 18:21:09 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <20101119143337.GA3023@current.Sisis.de> <201011191537.25867.hselasky@c2i.net> <20101119170259.GA3741@current.Sisis.de> In-Reply-To: <20101119170259.GA3741@current.Sisis.de> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'( =?iso-8859-1?q?=3B=5FIjlA=3A=0A=09hGE=2E=2EEw?=, =?iso-8859-1?q?XAQ*o=23=5C/M=7ESC=3DS1-f9=7BEzRfT=27=7CHhll5Q=5Dha5Bt-s=7Co?= =?iso-8859-1?q?TlKMusi=3A1e=5BwJl=7Dkd=7DGR=0A=09Z0adGx-x=5F0zGbZj=27e?=(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201011191821.09308.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 17:20:20 -0000 On Friday 19 November 2010 18:02:59 Matthias Apitz wrote: > El d=EDa Friday, November 19, 2010 a las 03:37:25PM +0100, Hans Petter Se= lasky=20 escribi=F3: > > On Friday 19 November 2010 15:33:37 Matthias Apitz wrote: > > > Hello, > > >=20 > > > How is this possible: > > >=20 > > > $ dd if=3D/dev/da0 of=3Df1 > > > 7892087+0 records in > > > 7892087+0 records out > > > $ dd if=3D/dev/da0 of=3Df2 > > > 7892087+0 records in > > > 7892087+0 records out > > > $ diff f1 f1 > > > Files f1 and f2 differ > > >=20 > > > (and no, /dev/da0s1a is not mounted). > > >=20 > > > Thx > > >=20 > > > matthias > >=20 > > Hi, > >=20 > > Can you dump the data into hex using hexdump -C and show us the > > difference. >=20 > Note: the output of the dd(1) is around 3.8 GByte. I compared the 1st > 2.000.000 lines of the hexdump: no diff; any better tool to show the 1st > block which differs? >=20 > > Usually you would use bs=3D65536 (Does that change anything)? >=20 > Same result: they differ :-( >=20 > matthias bsdiff ? =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 17:25:54 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FADB1065672 for ; Fri, 19 Nov 2010 17:25:54 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8C8698FC08 for ; Fri, 19 Nov 2010 17:25:53 +0000 (UTC) Received: by eyb7 with SMTP id 7so2841438eyb.13 for ; Fri, 19 Nov 2010 09:25:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=1cLdeXj6Nv7kPAE97/5Ua9PkN1JE2zvylI/1AorQUf8=; b=VyCl1b8/OEVOehz7u0EEnA9UI3zVUCluuMWKqIfgpHL5177n5dRWDsVwJ1vUB/EwKG 35hIhVSr8UVVKvPBcRYMeIIkYCKeRibLkzMxsk5N1dYgAYlmqn1G7lEG1qNP9io+Fhpv 93j78ndtZbadhNCvYUaRxeXqJ5ugu9LG9pMYs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=Y80/vS8O2tnuV0cdL3vEIWI5N7plNKdeCe2jeCAQQcoiEhNO5jLrCQeipUwSbph+F5 eEQYR/R0Vm93TgSkP1Mg8oL1nMKKPe3riWpCPKe+0422/MPXboZLCZREoqOCE2TJ5xBO HJt3QvK+4n6R0903Egff2ny3roksg9SiQaFF0= Received: by 10.216.164.194 with SMTP id c44mr1979355wel.107.1290185806569; Fri, 19 Nov 2010 08:56:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.234.82 with HTTP; Fri, 19 Nov 2010 08:56:26 -0800 (PST) In-Reply-To: <201011191720.15402.hselasky@c2i.net> References: <441397602.20101119185527@serebryakov.spb.ru> <201011191720.15402.hselasky@c2i.net> From: Paul B Mahol Date: Fri, 19 Nov 2010 16:56:26 +0000 Message-ID: To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Lev Serebryakov , freebsd-usb@freebsd.org Subject: Re: Two questions: how to specify module-load function for driver module and which name of driver is better (according to "standards") X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 17:25:54 -0000 2010/11/19 Hans Petter Selasky : > On Friday 19 November 2010 16:55:27 Lev Serebryakov wrote: >> Hello, Freebsd-usb. >> >> =A0 I've =A0implemented =A0driver (ucom-subdriver) for MosChip 7820 and = 7840 >> =A0USB2COM multiport bridges. I have two questions: >> > > Hi, > >> =A0 (1) =A0How =A0should =A0I =A0specify =A0module-load =A0function? DRI= VER_MODULE() >> =A0 doesn't =A0 help =A0 much. =A0I =A0need =A0to run some code only onc= e, at very >> =A0 beginning, =A0not =A0for each probe/attach. GEOM modules have method= s for >> =A0 it, but I can not find such methods for drivers. > > Look at ubt_modevent in sys/netgraph/bluetooth/drivers/ubt/ng_ubt.c. Or u= se a > so-called SYSINIT() or SYSUNINIT(). > >> >> =A0 (2) Which name should I choose? Working name of module/driver/device >> =A0 is "mos7840", but it seems, that it is bad name: >> =A0 =A0(a) All existing ucom-based drivers is "uXXXcom" >> =A0 =A0(b) Driver instances looks ugly (like "mos78400") > umos78400 ? > >> >> =A0 Is =A0"umos7840com" =A0good name or it is too long? :) We have "umos= com" >> =A0 driver for older MosChip chip in base already. > > Maybe someone else has some comments. Is it possible/sane to integrate two drivers in one? From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 17:35:25 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 683D61065672 for ; Fri, 19 Nov 2010 17:35:25 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 232F28FC1E for ; Fri, 19 Nov 2010 17:35:24 +0000 (UTC) Received: from [88.217.17.230] (helo=current.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PJUrq-0003UJ-GP; Fri, 19 Nov 2010 18:35:22 +0100 Received: from current.Sisis.de (current [127.0.0.1]) by current.Sisis.de (8.14.3/8.14.3) with ESMTP id oAJHZKjR003970; Fri, 19 Nov 2010 18:35:20 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id oAJHZJxb003969; Fri, 19 Nov 2010 18:35:19 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Fri, 19 Nov 2010 18:35:19 +0100 From: Matthias Apitz To: Hans Petter Selasky Message-ID: <20101119173519.GA3933@current.Sisis.de> References: <20101119143337.GA3023@current.Sisis.de> <201011191537.25867.hselasky@c2i.net> <20101119170259.GA3741@current.Sisis.de> <201011191821.09308.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201011191821.09308.hselasky@c2i.net> X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 88.217.17.230 Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 17:35:25 -0000 El día Friday, November 19, 2010 a las 06:21:09PM +0100, Hans Petter Selasky escribió: > > > Can you dump the data into hex using hexdump -C and show us the > > > difference. > > > > Note: the output of the dd(1) is around 3.8 GByte. I compared the 1st > > 2.000.000 lines of the hexdump: no diff; any better tool to show the 1st > > block which differs? > > > > > Usually you would use bs=65536 (Does that change anything)? > > > > Same result: they differ :-( > > > > matthias > > bsdiff ? This will not work with such big files (requires 8x memory of the file): I was thinking in a tool just reading each file block by block, comparing the blocks and noting the 1st diff with block offset number. (some 10 lines of C code :-)) matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 18:16:03 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 823201065672 for ; Fri, 19 Nov 2010 18:16:03 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.c2i.net [212.247.154.98]) by mx1.freebsd.org (Postfix) with ESMTP id 12F628FC12 for ; Fri, 19 Nov 2010 18:16:02 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=gl0LPzB4YDQuuzpDoHYit7deEV0cOo++Sg28kyvF6vg= c=1 sm=1 a=fsDGt_0-TPkA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=ZnDvwpOZXaLstvJc0roA:9 a=NyDgTqPoXz3CD0a1ggYA:7 a=-ZDLh2HW7Rv9ZGaZ9Z5XHG6IHs8A:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 51010412; Fri, 19 Nov 2010 19:16:01 +0100 From: Hans Petter Selasky To: Matthias Apitz Date: Fri, 19 Nov 2010 19:16:53 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <20101119143337.GA3023@current.Sisis.de> <201011191821.09308.hselasky@c2i.net> <20101119173519.GA3933@current.Sisis.de> In-Reply-To: <20101119173519.GA3933@current.Sisis.de> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'( =?iso-8859-1?q?=3B=5FIjlA=3A=0A=09hGE=2E=2EEw?=, =?iso-8859-1?q?XAQ*o=23=5C/M=7ESC=3DS1-f9=7BEzRfT=27=7CHhll5Q=5Dha5Bt-s=7Co?= =?iso-8859-1?q?TlKMusi=3A1e=5BwJl=7Dkd=7DGR=0A=09Z0adGx-x=5F0zGbZj=27e?=(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201011191916.53655.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 18:16:03 -0000 On Friday 19 November 2010 18:35:19 Matthias Apitz wrote: > El d=EDa Friday, November 19, 2010 a las 06:21:09PM +0100, Hans Petter Se= lasky=20 escribi=F3: > > > > Can you dump the data into hex using hexdump -C and show us the > > > > difference. > > >=20 > > > Note: the output of the dd(1) is around 3.8 GByte. I compared the 1st > > > 2.000.000 lines of the hexdump: no diff; any better tool to show the > > > 1st block which differs? > > >=20 > > > > Usually you would use bs=3D65536 (Does that change anything)? > > >=20 > > > Same result: they differ :-( > > >=20 > > > matthias > >=20 > > bsdiff ? >=20 > This will not work with such big files (requires 8x memory of the file): >=20 > I was thinking in a tool just reading each file block by block, > comparing the blocks and noting the 1st diff with block offset number. > (some 10 lines of C code :-)) >=20 > matthias Maybe you need to write a small C-program to do that. You can use bcmp() to compare two buffers. =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 18:23:27 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F42321065672 for ; Fri, 19 Nov 2010 18:23:26 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id ACB658FC12 for ; Fri, 19 Nov 2010 18:23:26 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id 98C201CC3E; Fri, 19 Nov 2010 15:23:20 -0300 (BRT) Received: from 187.114.192.104 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Fri, 19 Nov 2010 16:23:20 -0200 Message-ID: <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> In-Reply-To: <20101119171324.GA13317@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> <20101118202426.GB8512@michelle.cdnetworks.com> <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> Date: Fri, 19 Nov 2010 16:23:20 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 18:23:27 -0000 On Fri, November 19, 2010 15:13, Pyun YongHyeon wrote: > On Fri, Nov 19, 2010 at 03:19:26AM -0200, Nenhum_de_Nos wrote: >> >> On Thu, November 18, 2010 23:38, Pyun YongHyeon wrote: >> > On Thu, Nov 18, 2010 at 10:40:10PM -0200, Nenhum_de_Nos wrote: >> >> >> >> On Thu, November 18, 2010 22:06, Pyun YongHyeon wrote: >> >> > On Thu, Nov 18, 2010 at 09:12:13PM -0200, Nenhum_de_Nos wrote: >> >> >> >> >> >> On Thu, November 18, 2010 18:24, Pyun YongHyeon wrote: >> >> >> > On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos wrote: >> >> >> >> >> >> >> >> On Thu, November 18, 2010 13:10, Derrick Brashear wrote: >> >> >> >> > The following reply was made to PR usb/140883; it has been >> noted >> >> by >> >> >> >> GNATS. >> >> >> >> > >> >> >> >> > From: Derrick Brashear >> >> >> >> > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com >> >> >> >> > Cc: >> >> >> >> > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet >> hangs >> >> >> after >> >> >> >> > short >> >> >> >> > period of traffic >> >> >> >> > Date: Thu, 18 Nov 2010 09:36:50 -0500 >> >> >> >> > >> >> >> >> > Pyun has provided an updated driver which avoids several >> issues >> >> >> >> > including using a too-large transmit buffer (the chipset >> claims >> >> >> only >> >> >> >> > 8k) but none of the fixes worked until he disabled frame >> >> combining >> >> >> >> for >> >> >> >> > transmit. With only a single packet being sent per frame (as >> >> was >> >> >> the >> >> >> >> > case in FreeBSD 7, apparently) seems to make the issue go >> away. >> >> >> None >> >> >> >> > of the cases I could use to reproduce the issue now happen. >> >> >> >> > >> >> >> >> > -- >> >> >> >> > Derrick >> >> >> >> >> >> >> >> is this already in 8-stable ? I have a couple of axe(4) based >> >> nic's >> >> >> >> they're not ok on 8-stable. I've talked to Pyun before, and >> that >> >> time >> >> >> >> seemed do solve the issue (with gigabit belkin axe based) but >> now >> >> I >> >> >> >> can't >> >> >> >> get them to work anymore. even fast ethernet linksys axe are >> just >> >> >> dying >> >> >> >> when in a bridge (switched to OpenBSD to have it working). >> >> >> >> >> >> >> >> how ca I try this to help ? >> >> >> >> >> >> >> > >> >> >> > I uploaded updated if_axe.c/if_axereg.h to the following URL. >> >> >> > http://people.freebsd.org/~yongari/axe/if_axe.c >> >> >> > http://people.freebsd.org/~yongari/axe/if_axereg.h >> >> >> > >> >> >> > That files seem to fix axe(4) hang which were seen on AX88772A >> >> >> > controller. One of most notable changes are removing combining >> >> >> > multiple TX frames in TX path such that this change may result >> in >> >> >> > sub-optimal performance for most axe(4) controllers. However it >> >> >> > seems that change makes Derrick's controller work without >> problems. >> >> >> > Generally I prefer driver stability over performance so if this >> >> >> > change also fixes other axe(4) stability issues reported so far, >> I >> >> >> > want to check in the change. >> >> >> > >> >> >> > Thanks. >> >> >> >> >> >> well, >> >> >> >> >> >> things did got better here. but the link state UP and DOWN are >> still >> >> >> there :( >> >> >> >> >> >> ugen2.3: at usbus2 >> >> >> axe1: on >> usbus2 >> >> >> axe1: PHYADDR 0xe0:0x01 >> >> >> miibus2: on axe1 >> >> >> ukphy2: PHY 1 on miibus2 >> >> >> ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> 1000baseT, >> >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> >> >> 1000baseT-FD >> >> >> X, auto >> >> > >> >> > It seems you have PHY driver issue. Normally all gigabit PHYs >> >> > should have their own PHY driver since most PHYs hardwares tend to >> >> > have a special register that reports link state changes. >> >> > Show me the output of "devinfo -rv | grep phy". >> >> >> >> there you are: >> >> >> >> devinfo -rv|grep phy >> >> ukphy1 pnpinfo oui=0xec6 model=0x1 rev=0x1 at >> phyno=16 >> >> ukphy2 pnpinfo oui=0xa080 model=0x28 rev=0x2 at >> >> phyno=1 >> >> ukphy0 pnpinfo oui=0x4063 model=0x32 rev=0xa at phyno=1 >> >> >> > >> > Hmm.... You have many ukphys there. :-) I think the PHY attached to >> > the USB controller is ukphy2. The OUI indicates its maker is ASIX. >> > Unfortunately there is no dedicated PHY driver for this PHY. I >> > guess it may use a modified CICADA PHY though. Updated driver to >> > force GPIO configuration for this PHY. Would you try again after >> > downloading if_axe.c/if_axereg.h? It may show >> > "unknown PHY mode : 0xXX" if my guess is wrong. back to this, no problem of unknown PHY: ugen2.2: at usbus2 axe0: on usbus2 axe0: PHYADDR 0xe0:0x10 Root mount waiting for: usbus2 miibus1: on axe0 ukphy1: PHY 16 on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: on axe0 ue0: Ethernet address: my mac here ugen2.3: at usbus2 axe1: on usbus2 axe1: PHYADDR 0xe0:0x01 Trying to mount root from ufs:/dev/ad0s3a miibus2: on axe1 ukphy2: PHY 1 on miibus2 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto ue1: on axe1 ue1: Ethernet address: my other mac here the ping still shows problems (on gbit controller at 100BaseTX): 62 packets transmitted, 55 packets received, 11.3% packet loss round-trip min/avg/max/stddev = 0.873/1.957/51.408/6.730 ms when in gigabit, no good: ping 192.168.1.3 PING 192.168.1.3 (192.168.1.3): 56 data bytes 64 bytes from 192.168.1.3: icmp_seq=2 ttl=128 time=1.533 ms 64 bytes from 192.168.1.3: icmp_seq=3 ttl=128 time=1001.806 ms 64 bytes from 192.168.1.3: icmp_seq=4 ttl=128 time=1.151 ms 64 bytes from 192.168.1.3: icmp_seq=5 ttl=128 time=1001.860 ms 64 bytes from 192.168.1.3: icmp_seq=6 ttl=128 time=1.317 ms 64 bytes from 192.168.1.3: icmp_seq=7 ttl=128 time=1.036 ms 64 bytes from 192.168.1.3: icmp_seq=8 ttl=128 time=1001.899 ms 64 bytes from 192.168.1.3: icmp_seq=9 ttl=128 time=1.273 ms ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host 64 bytes from 192.168.1.3: icmp_seq=16 ttl=128 time=0.992 ms 64 bytes from 192.168.1.3: icmp_seq=18 ttl=128 time=0.860 ms ping: sendto: No route to host 64 bytes from 192.168.1.3: icmp_seq=25 ttl=128 time=1.132 ms ping: sendto: No route to host 64 bytes from 192.168.1.3: icmp_seq=34 ttl=128 time=3003.569 ms 64 bytes from 192.168.1.3: icmp_seq=35 ttl=128 time=2002.963 ms 64 bytes from 192.168.1.3: icmp_seq=36 ttl=128 time=1002.208 ms 64 bytes from 192.168.1.3: icmp_seq=37 ttl=128 time=1.454 ms ^C --- 192.168.1.3 ping statistics --- 38 packets transmitted, 15 packets received, 60.5% packet loss round-trip min/avg/max/stddev = 0.860/601.670/3003.569/880.104 ms and: ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP ue1: link state changed to DOWN ue1: link state changed to UP >> I downloaded again from above links and are the same as the last: >> >> valfenda# md5 if_axe* >> MD5 (if_axe.c) = 388b7aa84f0d2471f8b144033103618b >> MD5 (if_axe.c.original) = c528c7cb5eb964a792d4c14dfaed47cf >> MD5 (if_axe.c.v1) = 388b7aa84f0d2471f8b144033103618b >> MD5 (if_axereg.h) = 10f85490cab59b8e40de261fd7ad81a5 >> MD5 (if_axereg.h.original) = 46f37d0f02a3c09463ceec58b743c6ce >> MD5 (if_axereg.h.v1) = 10f85490cab59b8e40de261fd7ad81a5 >> >> .original are files from 8-stable (via csup) >> .v1 are the files from http://people.freebsd.org/~yongari/axe/ >> downloaded >> when the fist test using those files were made. >> regular .c files were downloaded now when I read this mail. >> >> did you uploaded some new version in >> http://people.freebsd.org/~yongari/axe/ ? or I didn't got it ? :) >> > > Oops, it seems I forgot to upload it after modifying it. > Please download again. MD5 should be > 507a672946e7c0394e83c79d1a12c9b5 (if_axe.c) and > 10f85490cab59b8e40de261fd7ad81a5 (if_axereg.h) > >> should this modified version be a good test to fast ethernet axe nics ? >> my >> linksys USB200M failed when in bridge after some time of use :( same > > Yes, the change made in if_axe.c is for AX88178, AX88772 and > AX8872A. The change has no effect for AX88172. Your controller would > be either AX88772 or AX88772A so chances are good to see different > behavior than ever before. I have no idea on how to see this ... is there anyway ? >> hardware I'm testing now. and the nics are ok, tested in OpenBSD with >> same >> hardware and same bridge and same pf conf file. >> >> thanks, >> >> matheus by the way, you would not know if an interrupt storm on the irq of the fast ethernet axe would have anything to do with its driver, right ? it just happens when in bridge mode (I figured out why the bridge was stopping working - the other nic keeps working fine). thanks as usual, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 18:39:06 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C330106564A for ; Fri, 19 Nov 2010 18:39:06 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id DE1518FC0A for ; Fri, 19 Nov 2010 18:39:05 +0000 (UTC) Received: from [109.41.253.170] (helo=tiny.Sisis.de.) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PJVrT-0007Mw-Ac; Fri, 19 Nov 2010 19:39:04 +0100 Received: from tiny.Sisis.de. (localhost [127.0.0.1]) by tiny.Sisis.de. (8.14.3/8.14.3) with ESMTP id oAJId2IK001230; Fri, 19 Nov 2010 19:39:02 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by tiny.Sisis.de. (8.14.3/8.14.3/Submit) id oAJId1Os001229; Fri, 19 Nov 2010 19:39:01 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: tiny.Sisis.de.: guru set sender to guru@unixarea.de using -f Date: Fri, 19 Nov 2010 19:39:00 +0100 From: Matthias Apitz To: Hans Petter Selasky Message-ID: <20101119183900.GA1221@tiny.Sisis.de> References: <20101119143337.GA3023@current.Sisis.de> <201011191821.09308.hselasky@c2i.net> <20101119173519.GA3933@current.Sisis.de> <201011191916.53655.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201011191916.53655.hselasky@c2i.net> X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 109.41.253.170 Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 18:39:06 -0000 El día Friday, November 19, 2010 a las 07:16:53PM +0100, Hans Petter Selasky escribió: > > I was thinking in a tool just reading each file block by block, > > comparing the blocks and noting the 1st diff with block offset number. > > (some 10 lines of C code :-)) > > > > matthias > > Maybe you need to write a small C-program to do that. > > You can use bcmp() to compare two buffers. Will do that tomorrow. Just an idea: The USB key in question was new and I only created the file system on it the usual way (fdisk, bsdlabel, newfs). Then I restored the dump on it (which took 26 hours for 3.1 GByte dump file). The USB key boots fine, btw. Could it be that unwritten/unformatted blocks are read as random data from that USB key? Should I overwrite the full USB key from /dev/zero? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 18:51:46 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7F4E1065670 for ; Fri, 19 Nov 2010 18:51:46 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5C4B48FC13 for ; Fri, 19 Nov 2010 18:51:46 +0000 (UTC) Received: by gxk22 with SMTP id 22so326084gxk.13 for ; Fri, 19 Nov 2010 10:51:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=pU4nS4prfivIYVo1J73RR3YEnBLU6g8kOq+lfLFanUg=; b=sgPNNs4H10cPa9PSuGsKn47+/y+1N7BRHxD1Cc9FSkSsvxStKAxM+DH3MOpuPE2909 pOLHg/eH+Qq7q2VJ3P/XglSX/2Rlo8LUkaPGQEDayfb3/SfBhMU0aM+x6wVwON03lU7T d4USGK0+63bw1TNi6UmwpdBP4QXPBcLdXWtnA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=lG9NuhluTQ0LbNFgEhlG7jbKcgsdXuC49mxyfNB0rCezgSxSdE49HWMiyXjn8DMp8Z HSN4VPjtIBp0Z0uZmOW4H6vBP+0urqgl+9SD/D/aR+ctkRgKnikOEkN5MMYVd/nueTqL 9yG7FJmnNo3PytabL+g4JBzYvzHSSl1afDzdA= Received: by 10.223.81.78 with SMTP id w14mr1225624fak.5.1290192704838; Fri, 19 Nov 2010 10:51:44 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id a24sm202517fak.3.2010.11.19.10.51.42 (version=SSLv3 cipher=RC4-MD5); Fri, 19 Nov 2010 10:51:43 -0800 (PST) Sender: Alexander Motin Message-ID: <4CE6C73A.4070208@FreeBSD.org> Date: Fri, 19 Nov 2010 20:51:38 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101104 Thunderbird/3.1.6 MIME-Version: 1.0 To: Matthias Apitz , freebsd-usb@freebsd.org References: <201011191916.53655.hselasky@c2i.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 18:51:46 -0000 On 19.11.2010 20:39, Matthias Apitz wrote: > El día Friday, November 19, 2010 a las 07:16:53PM +0100, Hans Petter Selasky escribió: > >>> I was thinking in a tool just reading each file block by block, >>> comparing the blocks and noting the 1st diff with block offset number. >>> (some 10 lines of C code :-)) >>> >>> matthias >> >> Maybe you need to write a small C-program to do that. >> >> You can use bcmp() to compare two buffers. > > Will do that tomorrow. > > Just an idea: The USB key in question was new and I only created the > file system on it the usual way (fdisk, bsdlabel, newfs). Then I > restored the dump on it (which took 26 hours for 3.1 GByte dump file). > The USB key boots fine, btw. > > Could it be that unwritten/unformatted blocks are read as random data > from that USB key? Should I overwrite the full USB key from /dev/zero? It is allowed behavior for SATA SSDs with TRIM command support. Deleted blocks can be not guarantied to return any predictable or even repeatable value. May be this logic could be extended to USB devices. -- Alexander Motin From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 19:27:36 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28D3B1065672 for ; Fri, 19 Nov 2010 19:27:36 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id E42728FC15 for ; Fri, 19 Nov 2010 19:27:35 +0000 (UTC) Received: by pvc22 with SMTP id 22so1180972pvc.13 for ; Fri, 19 Nov 2010 11:27:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=y7N+INE18n5Rt0N7yb6ir0iDjitP8B9M7F5b+/0PyKM=; b=c4/3cGi4BS4bg8udXe9e668XNqYl0qXb86Lnb32A3gODUkLI4o8mvUT54HANGM1/+n E+O7R35+9Uky5UdigS5Q7xVdpxbcCtv+Kc5t4jMCZ0h/i334PEu9NA+NvKqR9BBY3Oc5 OlYOn03SiHhKwatMX1wFODckIiFOKwAXT6qjQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=M/Gw/yQDA5Z/FL+rngSnTpN8ch8ui/OD0tJ9oWaFlshkaQBwVg83lNJlsMuIGy5K2x h7aumlhcqIVK98OIfDErdSYELhFwxLBMly1dR3Rs3sR22pOf31aBXD0wtj2rX0w0/Sm0 0mb5QAtXGS//NOVsu6YePFotVOyRSyk7QQ6XE= Received: by 10.143.14.13 with SMTP id r13mr2097051wfi.50.1290194853565; Fri, 19 Nov 2010 11:27:33 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id q13sm2243912wfc.5.2010.11.19.11.27.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Nov 2010 11:27:31 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 19 Nov 2010 11:27:31 -0800 From: Pyun YongHyeon Date: Fri, 19 Nov 2010 11:27:31 -0800 To: Nenhum_de_Nos Message-ID: <20101119192731.GB13317@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> <20101118202426.GB8512@michelle.cdnetworks.com> <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] 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: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 19:27:36 -0000 On Fri, Nov 19, 2010 at 04:23:20PM -0200, Nenhum_de_Nos wrote: > > On Fri, November 19, 2010 15:13, Pyun YongHyeon wrote: > > On Fri, Nov 19, 2010 at 03:19:26AM -0200, Nenhum_de_Nos wrote: > >> > >> On Thu, November 18, 2010 23:38, Pyun YongHyeon wrote: > >> > On Thu, Nov 18, 2010 at 10:40:10PM -0200, Nenhum_de_Nos wrote: > >> >> > >> >> On Thu, November 18, 2010 22:06, Pyun YongHyeon wrote: > >> >> > On Thu, Nov 18, 2010 at 09:12:13PM -0200, Nenhum_de_Nos wrote: > >> >> >> > >> >> >> On Thu, November 18, 2010 18:24, Pyun YongHyeon wrote: > >> >> >> > On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos wrote: > >> >> >> >> > >> >> >> >> On Thu, November 18, 2010 13:10, Derrick Brashear wrote: > >> >> >> >> > The following reply was made to PR usb/140883; it has been > >> noted > >> >> by > >> >> >> >> GNATS. > >> >> >> >> > > >> >> >> >> > From: Derrick Brashear > >> >> >> >> > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com > >> >> >> >> > Cc: > >> >> >> >> > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet > >> hangs > >> >> >> after > >> >> >> >> > short > >> >> >> >> > period of traffic > >> >> >> >> > Date: Thu, 18 Nov 2010 09:36:50 -0500 > >> >> >> >> > > >> >> >> >> > Pyun has provided an updated driver which avoids several > >> issues > >> >> >> >> > including using a too-large transmit buffer (the chipset > >> claims > >> >> >> only > >> >> >> >> > 8k) but none of the fixes worked until he disabled frame > >> >> combining > >> >> >> >> for > >> >> >> >> > transmit. With only a single packet being sent per frame (as > >> >> was > >> >> >> the > >> >> >> >> > case in FreeBSD 7, apparently) seems to make the issue go > >> away. > >> >> >> None > >> >> >> >> > of the cases I could use to reproduce the issue now happen. > >> >> >> >> > > >> >> >> >> > -- > >> >> >> >> > Derrick > >> >> >> >> > >> >> >> >> is this already in 8-stable ? I have a couple of axe(4) based > >> >> nic's > >> >> >> >> they're not ok on 8-stable. I've talked to Pyun before, and > >> that > >> >> time > >> >> >> >> seemed do solve the issue (with gigabit belkin axe based) but > >> now > >> >> I > >> >> >> >> can't > >> >> >> >> get them to work anymore. even fast ethernet linksys axe are > >> just > >> >> >> dying > >> >> >> >> when in a bridge (switched to OpenBSD to have it working). > >> >> >> >> > >> >> >> >> how ca I try this to help ? > >> >> >> >> > >> >> >> > > >> >> >> > I uploaded updated if_axe.c/if_axereg.h to the following URL. > >> >> >> > http://people.freebsd.org/~yongari/axe/if_axe.c > >> >> >> > http://people.freebsd.org/~yongari/axe/if_axereg.h > >> >> >> > > >> >> >> > That files seem to fix axe(4) hang which were seen on AX88772A > >> >> >> > controller. One of most notable changes are removing combining > >> >> >> > multiple TX frames in TX path such that this change may result > >> in > >> >> >> > sub-optimal performance for most axe(4) controllers. However it > >> >> >> > seems that change makes Derrick's controller work without > >> problems. > >> >> >> > Generally I prefer driver stability over performance so if this > >> >> >> > change also fixes other axe(4) stability issues reported so far, > >> I > >> >> >> > want to check in the change. > >> >> >> > > >> >> >> > Thanks. > >> >> >> > >> >> >> well, > >> >> >> > >> >> >> things did got better here. but the link state UP and DOWN are > >> still > >> >> >> there :( > >> >> >> > >> >> >> ugen2.3: at usbus2 > >> >> >> axe1: on > >> usbus2 > >> >> >> axe1: PHYADDR 0xe0:0x01 > >> >> >> miibus2: on axe1 > >> >> >> ukphy2: PHY 1 on miibus2 > >> >> >> ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > >> 1000baseT, > >> >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> >> >> 1000baseT-FD > >> >> >> X, auto > >> >> > > >> >> > It seems you have PHY driver issue. Normally all gigabit PHYs > >> >> > should have their own PHY driver since most PHYs hardwares tend to > >> >> > have a special register that reports link state changes. > >> >> > Show me the output of "devinfo -rv | grep phy". > >> >> > >> >> there you are: > >> >> > >> >> devinfo -rv|grep phy > >> >> ukphy1 pnpinfo oui=0xec6 model=0x1 rev=0x1 at > >> phyno=16 > >> >> ukphy2 pnpinfo oui=0xa080 model=0x28 rev=0x2 at > >> >> phyno=1 > >> >> ukphy0 pnpinfo oui=0x4063 model=0x32 rev=0xa at phyno=1 > >> >> > >> > > >> > Hmm.... You have many ukphys there. :-) I think the PHY attached to > >> > the USB controller is ukphy2. The OUI indicates its maker is ASIX. > >> > Unfortunately there is no dedicated PHY driver for this PHY. I > >> > guess it may use a modified CICADA PHY though. Updated driver to > >> > force GPIO configuration for this PHY. Would you try again after > >> > downloading if_axe.c/if_axereg.h? It may show > >> > "unknown PHY mode : 0xXX" if my guess is wrong. > > back to this, no problem of unknown PHY: > > ugen2.2: at usbus2 > axe0: on usbus2 > axe0: PHYADDR 0xe0:0x10 > Root mount waiting for: usbus2 > miibus1: on axe0 > ukphy1: PHY 16 on miibus1 > ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on axe0 > ue0: Ethernet address: my mac here > ugen2.3: at usbus2 > axe1: on usbus2 > axe1: PHYADDR 0xe0:0x01 > Trying to mount root from ufs:/dev/ad0s3a > miibus2: on axe1 > ukphy2: PHY 1 on miibus2 > ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > ue1: on axe1 > ue1: Ethernet address: my other mac here > > the ping still shows problems (on gbit controller at 100BaseTX): > > 62 packets transmitted, 55 packets received, 11.3% packet loss > round-trip min/avg/max/stddev = 0.873/1.957/51.408/6.730 ms > > when in gigabit, no good: > Ok, try again after downloading new if_axe.c and let me know the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your console. > ping 192.168.1.3 > PING 192.168.1.3 (192.168.1.3): 56 data bytes > 64 bytes from 192.168.1.3: icmp_seq=2 ttl=128 time=1.533 ms > 64 bytes from 192.168.1.3: icmp_seq=3 ttl=128 time=1001.806 ms > 64 bytes from 192.168.1.3: icmp_seq=4 ttl=128 time=1.151 ms > 64 bytes from 192.168.1.3: icmp_seq=5 ttl=128 time=1001.860 ms > 64 bytes from 192.168.1.3: icmp_seq=6 ttl=128 time=1.317 ms > 64 bytes from 192.168.1.3: icmp_seq=7 ttl=128 time=1.036 ms > 64 bytes from 192.168.1.3: icmp_seq=8 ttl=128 time=1001.899 ms > 64 bytes from 192.168.1.3: icmp_seq=9 ttl=128 time=1.273 ms > ping: sendto: No route to host > ping: sendto: No route to host > ping: sendto: No route to host > 64 bytes from 192.168.1.3: icmp_seq=16 ttl=128 time=0.992 ms > 64 bytes from 192.168.1.3: icmp_seq=18 ttl=128 time=0.860 ms > ping: sendto: No route to host > 64 bytes from 192.168.1.3: icmp_seq=25 ttl=128 time=1.132 ms > ping: sendto: No route to host > 64 bytes from 192.168.1.3: icmp_seq=34 ttl=128 time=3003.569 ms > 64 bytes from 192.168.1.3: icmp_seq=35 ttl=128 time=2002.963 ms > 64 bytes from 192.168.1.3: icmp_seq=36 ttl=128 time=1002.208 ms > 64 bytes from 192.168.1.3: icmp_seq=37 ttl=128 time=1.454 ms > ^C > --- 192.168.1.3 ping statistics --- > 38 packets transmitted, 15 packets received, 60.5% packet loss > round-trip min/avg/max/stddev = 0.860/601.670/3003.569/880.104 ms > > and: > > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > ue1: link state changed to DOWN > ue1: link state changed to UP > > >> I downloaded again from above links and are the same as the last: > >> > >> valfenda# md5 if_axe* > >> MD5 (if_axe.c) = 388b7aa84f0d2471f8b144033103618b > >> MD5 (if_axe.c.original) = c528c7cb5eb964a792d4c14dfaed47cf > >> MD5 (if_axe.c.v1) = 388b7aa84f0d2471f8b144033103618b > >> MD5 (if_axereg.h) = 10f85490cab59b8e40de261fd7ad81a5 > >> MD5 (if_axereg.h.original) = 46f37d0f02a3c09463ceec58b743c6ce > >> MD5 (if_axereg.h.v1) = 10f85490cab59b8e40de261fd7ad81a5 > >> > >> .original are files from 8-stable (via csup) > >> .v1 are the files from http://people.freebsd.org/~yongari/axe/ > >> downloaded > >> when the fist test using those files were made. > >> regular .c files were downloaded now when I read this mail. > >> > >> did you uploaded some new version in > >> http://people.freebsd.org/~yongari/axe/ ? or I didn't got it ? :) > >> > > > > Oops, it seems I forgot to upload it after modifying it. > > Please download again. MD5 should be > > 507a672946e7c0394e83c79d1a12c9b5 (if_axe.c) and > > 10f85490cab59b8e40de261fd7ad81a5 (if_axereg.h) > > > >> should this modified version be a good test to fast ethernet axe nics ? > >> my > >> linksys USB200M failed when in bridge after some time of use :( same > > > > Yes, the change made in if_axe.c is for AX88178, AX88772 and > > AX8872A. The change has no effect for AX88172. Your controller would > > be either AX88772 or AX88772A so chances are good to see different > > behavior than ever before. > > I have no idea on how to see this ... is there anyway ? > >From the output you posted: axe0: on usbus2 axe0: PHYADDR 0xe0:0x10 product is 0x0018 which means Cisco USB200M V2 and its controller is AX88772A. > >> hardware I'm testing now. and the nics are ok, tested in OpenBSD with > >> same > >> hardware and same bridge and same pf conf file. > >> > >> thanks, > >> > >> matheus > > by the way, you would not know if an interrupt storm on the irq of the > fast ethernet axe would have anything to do with its driver, right ? it > just happens when in bridge mode (I figured out why the bridge was > stopping working - the other nic keeps working fine). > Normally bridge mode will put the controller into promiscuous mode. If there is a bug in setting promiscuous mode, you should have seen it whenever you use tcpdump on that interface. So if you run tcpdump on that interface, do you see interrupt storm? If you don't, it would be different issue, I guess. From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 19:39:20 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 134061065696 for ; Fri, 19 Nov 2010 19:39:20 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id C78168FC18 for ; Fri, 19 Nov 2010 19:39:19 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id oAJJdDu3095986; Fri, 19 Nov 2010 12:39:13 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id oAJJdDVF095983; Fri, 19 Nov 2010 12:39:13 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 19 Nov 2010 12:39:13 -0700 (MST) From: Warren Block To: Matthias Apitz In-Reply-To: <20101119183900.GA1221@tiny.Sisis.de> Message-ID: References: <20101119143337.GA3023@current.Sisis.de> <201011191821.09308.hselasky@c2i.net> <20101119173519.GA3933@current.Sisis.de> <201011191916.53655.hselasky@c2i.net> <20101119183900.GA1221@tiny.Sisis.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (wonkity.com [127.0.0.1]); Fri, 19 Nov 2010 12:39:13 -0700 (MST) Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 19:39:20 -0000 On Fri, 19 Nov 2010, Matthias Apitz wrote: > El d?a Friday, November 19, 2010 a las 07:16:53PM +0100, Hans Petter Selasky escribi?: > >>> I was thinking in a tool just reading each file block by block, >>> comparing the blocks and noting the 1st diff with block offset number. >>> (some 10 lines of C code :-)) >>> >>> matthias >> >> Maybe you need to write a small C-program to do that. >> >> You can use bcmp() to compare two buffers. > > Will do that tomorrow. > > Just an idea: The USB key in question was new and I only created the > file system on it the usual way (fdisk, bsdlabel, newfs). Then I > restored the dump on it (which took 26 hours for 3.1 GByte dump file). > The USB key boots fine, btw. 26 *hours*? USB 1.1? > Could it be that unwritten/unformatted blocks are read as random data > from that USB key? Well, they could be anything. But the original filesystem has formerly-used blocks with old data from deleted files. dump doesn't copy those, but dd does. > Should I overwrite the full USB key from /dev/zero? Possibly there would still be differences. Filesystem metadata like date last mounted, for example. If you want a block-by-block duplicate, the brute-force method is to just dd the whole drive. Use bs=64k or bs=1m to help reduce overhead. From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 20:24:06 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F239106564A for ; Fri, 19 Nov 2010 20:24:06 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id 241A68FC0A for ; Fri, 19 Nov 2010 20:24:06 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id C74451CC40; Fri, 19 Nov 2010 17:23:50 -0300 (BRT) Received: from 187.114.192.104 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Fri, 19 Nov 2010 18:23:50 -0200 Message-ID: <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> In-Reply-To: <20101119192731.GB13317@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> <20101118202426.GB8512@michelle.cdnetworks.com> <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> Date: Fri, 19 Nov 2010 18:23:50 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: multipart/mixed;boundary="----=_20101119182350_44597" X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 20:24:06 -0000 ------=_20101119182350_44597 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit On Fri, November 19, 2010 17:27, Pyun YongHyeon wrote: > On Fri, Nov 19, 2010 at 04:23:20PM -0200, Nenhum_de_Nos wrote: >> >> On Fri, November 19, 2010 15:13, Pyun YongHyeon wrote: >> > On Fri, Nov 19, 2010 at 03:19:26AM -0200, Nenhum_de_Nos wrote: >> >> >> >> On Thu, November 18, 2010 23:38, Pyun YongHyeon wrote: >> >> > On Thu, Nov 18, 2010 at 10:40:10PM -0200, Nenhum_de_Nos wrote: >> >> >> >> >> >> On Thu, November 18, 2010 22:06, Pyun YongHyeon wrote: >> >> >> > On Thu, Nov 18, 2010 at 09:12:13PM -0200, Nenhum_de_Nos wrote: >> >> >> >> >> >> >> >> On Thu, November 18, 2010 18:24, Pyun YongHyeon wrote: >> >> >> >> > On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos >> wrote: >> >> >> >> >> >> >> >> >> >> On Thu, November 18, 2010 13:10, Derrick Brashear wrote: >> >> >> >> >> > The following reply was made to PR usb/140883; it has been >> >> noted >> >> >> by >> >> >> >> >> GNATS. >> >> >> >> >> > >> >> >> >> >> > From: Derrick Brashear >> >> >> >> >> > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com >> >> >> >> >> > Cc: >> >> >> >> >> > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet >> >> hangs >> >> >> >> after >> >> >> >> >> > short >> >> >> >> >> > period of traffic >> >> >> >> >> > Date: Thu, 18 Nov 2010 09:36:50 -0500 >> >> >> >> >> > >> >> >> >> >> > Pyun has provided an updated driver which avoids several >> >> issues >> >> >> >> >> > including using a too-large transmit buffer (the chipset >> >> claims >> >> >> >> only >> >> >> >> >> > 8k) but none of the fixes worked until he disabled frame >> >> >> combining >> >> >> >> >> for >> >> >> >> >> > transmit. With only a single packet being sent per frame >> (as >> >> >> was >> >> >> >> the >> >> >> >> >> > case in FreeBSD 7, apparently) seems to make the issue go >> >> away. >> >> >> >> None >> >> >> >> >> > of the cases I could use to reproduce the issue now >> happen. >> >> >> >> >> > >> >> >> >> >> > -- >> >> >> >> >> > Derrick >> >> >> >> >> >> >> >> >> >> is this already in 8-stable ? I have a couple of axe(4) >> based >> >> >> nic's >> >> >> >> >> they're not ok on 8-stable. I've talked to Pyun before, and >> >> that >> >> >> time >> >> >> >> >> seemed do solve the issue (with gigabit belkin axe based) >> but >> >> now >> >> >> I >> >> >> >> >> can't >> >> >> >> >> get them to work anymore. even fast ethernet linksys axe are >> >> just >> >> >> >> dying >> >> >> >> >> when in a bridge (switched to OpenBSD to have it working). >> >> >> >> >> >> >> >> >> >> how ca I try this to help ? >> >> >> >> >> >> >> >> >> > >> >> >> >> > I uploaded updated if_axe.c/if_axereg.h to the following URL. >> >> >> >> > http://people.freebsd.org/~yongari/axe/if_axe.c >> >> >> >> > http://people.freebsd.org/~yongari/axe/if_axereg.h >> >> >> >> > >> >> >> >> > That files seem to fix axe(4) hang which were seen on >> AX88772A >> >> >> >> > controller. One of most notable changes are removing >> combining >> >> >> >> > multiple TX frames in TX path such that this change may >> result >> >> in >> >> >> >> > sub-optimal performance for most axe(4) controllers. However >> it >> >> >> >> > seems that change makes Derrick's controller work without >> >> problems. >> >> >> >> > Generally I prefer driver stability over performance so if >> this >> >> >> >> > change also fixes other axe(4) stability issues reported so >> far, >> >> I >> >> >> >> > want to check in the change. >> >> >> >> > >> >> >> >> > Thanks. >> >> >> >> >> >> >> >> well, >> >> >> >> >> >> >> >> things did got better here. but the link state UP and DOWN are >> >> still >> >> >> >> there :( >> >> >> >> >> >> >> >> ugen2.3: at usbus2 >> >> >> >> axe1: on >> >> usbus2 >> >> >> >> axe1: PHYADDR 0xe0:0x01 >> >> >> >> miibus2: on axe1 >> >> >> >> ukphy2: PHY 1 on miibus2 >> >> >> >> ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> >> 1000baseT, >> >> >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> >> >> >> 1000baseT-FD >> >> >> >> X, auto >> >> >> > >> >> >> > It seems you have PHY driver issue. Normally all gigabit PHYs >> >> >> > should have their own PHY driver since most PHYs hardwares tend >> to >> >> >> > have a special register that reports link state changes. >> >> >> > Show me the output of "devinfo -rv | grep phy". >> >> >> >> >> >> there you are: >> >> >> >> >> >> devinfo -rv|grep phy >> >> >> ukphy1 pnpinfo oui=0xec6 model=0x1 rev=0x1 at >> >> phyno=16 >> >> >> ukphy2 pnpinfo oui=0xa080 model=0x28 rev=0x2 at >> >> >> phyno=1 >> >> >> ukphy0 pnpinfo oui=0x4063 model=0x32 rev=0xa at >> phyno=1 >> >> >> >> >> > >> >> > Hmm.... You have many ukphys there. :-) I think the PHY attached to >> >> > the USB controller is ukphy2. The OUI indicates its maker is ASIX. >> >> > Unfortunately there is no dedicated PHY driver for this PHY. I >> >> > guess it may use a modified CICADA PHY though. Updated driver to >> >> > force GPIO configuration for this PHY. Would you try again after >> >> > downloading if_axe.c/if_axereg.h? It may show >> >> > "unknown PHY mode : 0xXX" if my guess is wrong. >> >> back to this, no problem of unknown PHY: >> >> ugen2.2: at usbus2 >> axe0: on usbus2 >> axe0: PHYADDR 0xe0:0x10 >> Root mount waiting for: usbus2 >> miibus1: on axe0 >> ukphy1: PHY 16 on miibus1 >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> ue0: on axe0 >> ue0: Ethernet address: my mac here >> ugen2.3: at usbus2 >> axe1: on usbus2 >> axe1: PHYADDR 0xe0:0x01 >> Trying to mount root from ufs:/dev/ad0s3a >> miibus2: on axe1 >> ukphy2: PHY 1 on miibus2 >> ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> 1000baseT-FDX, auto >> ue1: on axe1 >> ue1: Ethernet address: my other mac here >> >> the ping still shows problems (on gbit controller at 100BaseTX): >> >> 62 packets transmitted, 55 packets received, 11.3% packet loss >> round-trip min/avg/max/stddev = 0.873/1.957/51.408/6.730 ms >> >> when in gigabit, no good: >> > > Ok, try again after downloading new if_axe.c and let me know > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your > console. never got to see that message. I saw the diff to previous version, and did boot into verbose mode (dmesg attached). there were just the belkin gigabit nic on boot. after, the linksys USB200M: axe1: on usbus2 axe1: PHYADDR 0xe0:0x10 miibus2: on axe1 ukphy1: PHY 16 on miibus2 ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue1: on axe1 ue1: bpf attached invalid media SR 0x700 invalid media SR 0x700 and the other gigabit: ugen2.4: at usbus2 axe2: on usbus2 axe2: PHYADDR 0xe0:0x01 miibus3: on axe2 truephy1: PHY 1 on miibus3 truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto ue2: on axe2 ue2: bpf attached ue2: Ethernet address: my mac here ue2: link state changed to DOWN and never got to see the EEPROM message. >> ping 192.168.1.3 >> PING 192.168.1.3 (192.168.1.3): 56 data bytes >> 64 bytes from 192.168.1.3: icmp_seq=2 ttl=128 time=1.533 ms >> 64 bytes from 192.168.1.3: icmp_seq=3 ttl=128 time=1001.806 ms >> 64 bytes from 192.168.1.3: icmp_seq=4 ttl=128 time=1.151 ms >> 64 bytes from 192.168.1.3: icmp_seq=5 ttl=128 time=1001.860 ms >> 64 bytes from 192.168.1.3: icmp_seq=6 ttl=128 time=1.317 ms >> 64 bytes from 192.168.1.3: icmp_seq=7 ttl=128 time=1.036 ms >> 64 bytes from 192.168.1.3: icmp_seq=8 ttl=128 time=1001.899 ms >> 64 bytes from 192.168.1.3: icmp_seq=9 ttl=128 time=1.273 ms >> ping: sendto: No route to host >> ping: sendto: No route to host >> ping: sendto: No route to host >> 64 bytes from 192.168.1.3: icmp_seq=16 ttl=128 time=0.992 ms >> 64 bytes from 192.168.1.3: icmp_seq=18 ttl=128 time=0.860 ms >> ping: sendto: No route to host >> 64 bytes from 192.168.1.3: icmp_seq=25 ttl=128 time=1.132 ms >> ping: sendto: No route to host >> 64 bytes from 192.168.1.3: icmp_seq=34 ttl=128 time=3003.569 ms >> 64 bytes from 192.168.1.3: icmp_seq=35 ttl=128 time=2002.963 ms >> 64 bytes from 192.168.1.3: icmp_seq=36 ttl=128 time=1002.208 ms >> 64 bytes from 192.168.1.3: icmp_seq=37 ttl=128 time=1.454 ms >> ^C >> --- 192.168.1.3 ping statistics --- >> 38 packets transmitted, 15 packets received, 60.5% packet loss >> round-trip min/avg/max/stddev = 0.860/601.670/3003.569/880.104 ms >> >> and: >> >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> >> >> I downloaded again from above links and are the same as the last: >> >> >> >> valfenda# md5 if_axe* >> >> MD5 (if_axe.c) = 388b7aa84f0d2471f8b144033103618b >> >> MD5 (if_axe.c.original) = c528c7cb5eb964a792d4c14dfaed47cf >> >> MD5 (if_axe.c.v1) = 388b7aa84f0d2471f8b144033103618b >> >> MD5 (if_axereg.h) = 10f85490cab59b8e40de261fd7ad81a5 >> >> MD5 (if_axereg.h.original) = 46f37d0f02a3c09463ceec58b743c6ce >> >> MD5 (if_axereg.h.v1) = 10f85490cab59b8e40de261fd7ad81a5 >> >> >> >> .original are files from 8-stable (via csup) >> >> .v1 are the files from http://people.freebsd.org/~yongari/axe/ >> >> downloaded >> >> when the fist test using those files were made. >> >> regular .c files were downloaded now when I read this mail. >> >> >> >> did you uploaded some new version in >> >> http://people.freebsd.org/~yongari/axe/ ? or I didn't got it ? :) >> >> >> > >> > Oops, it seems I forgot to upload it after modifying it. >> > Please download again. MD5 should be >> > 507a672946e7c0394e83c79d1a12c9b5 (if_axe.c) and >> > 10f85490cab59b8e40de261fd7ad81a5 (if_axereg.h) >> > >> >> should this modified version be a good test to fast ethernet axe nics >> ? >> >> my >> >> linksys USB200M failed when in bridge after some time of use :( same >> > >> > Yes, the change made in if_axe.c is for AX88178, AX88772 and >> > AX8872A. The change has no effect for AX88172. Your controller would >> > be either AX88772 or AX88772A so chances are good to see different >> > behavior than ever before. >> >> I have no idea on how to see this ... is there anyway ? >> > > From the output you posted: > axe0: on usbus2 > axe0: PHYADDR 0xe0:0x10 > product is 0x0018 which means Cisco USB200M V2 and its controller > is AX88772A. great :) >> >> hardware I'm testing now. and the nics are ok, tested in OpenBSD with >> >> same >> >> hardware and same bridge and same pf conf file. >> >> >> >> thanks, >> >> >> >> matheus >> >> by the way, you would not know if an interrupt storm on the irq of the >> fast ethernet axe would have anything to do with its driver, right ? it >> just happens when in bridge mode (I figured out why the bridge was >> stopping working - the other nic keeps working fine). >> > > Normally bridge mode will put the controller into promiscuous mode. > If there is a bug in setting promiscuous mode, you should have seen > it whenever you use tcpdump on that interface. So if you run > tcpdump on that interface, do you see interrupt storm? > If you don't, it would be different issue, I guess. I'm trying this, usb nic out of bridge, its own IP, tcpdump and iperf. few minutes and no problem so far. let's see in some time. when bridging for my DSL, it got something around 1~3Mbps of traffic. and in less then a night (8 hours) the usb nic would say goodbye ... thanks again, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ------=_20101119182350_44597 Content-Type: application/octet-stream; name="dmesg.usb" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="dmesg.usb" Q29weXJpZ2h0IChjKSAxOTkyLTIwMTAgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj KSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAx OTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLgpGcmVlQlNEIGlzIGEgcmVnaXN0ZXJlZCB0cmFkZW1hcmsgb2YgVGhlIEZy ZWVCU0QgRm91bmRhdGlvbi4KRnJlZUJTRCA4LjEtU1RBQkxFICMyOiBGcmkgTm92ICA1IDAxOjUy OjA2IEJSVCAyMDEwCiAgICByb290QHZhbGZlbmRhLmFwYXJ0bmV0Oi91c3Ivb2JqL3Vzci9zcmMv c3lzL3ZhbGZlbmRhIGkzODYKUHJlbG9hZGVkIGVsZiBrZXJuZWwgIi9ib290L2tlcm5lbC9rZXJu ZWwiIGF0IDB4YzEwMTcwMDAuClRpbWVjb3VudGVyICJpODI1NCIgZnJlcXVlbmN5IDExOTMxODIg SHogcXVhbGl0eSAwCkNhbGlicmF0aW5nIFRTQyBjbG9jayAuLi4gVFNDIGNsb2NrOiA3OTgxMzAw OTYgSHoKQ1BVOiBUcmFuc21ldGEodG0pIENydXNvZSh0bSkgUHJvY2Vzc29yIFRNNTcwMCAoNzk4 LjEzLU1IeiA1ODYtY2xhc3MgQ1BVKQogIE9yaWdpbiA9ICJHZW51aW5lVE14ODYiICBJZCA9IDB4 NTQzICBGYW1pbHkgPSA1ICBNb2RlbCA9IDQgIFN0ZXBwaW5nID0gMwogIEZlYXR1cmVzPTB4ODQ4 OTNmPEZQVSxWTUUsREUsUFNFLFRTQyxNU1IsQ1g4LFNFUCxDTU9WLFBOLE1NWD4KICBQcm9jZXNz b3IgcmV2aXNpb24gMS41LjAuMgogIENvZGUgTW9ycGhpbmcgU29mdHdhcmUgcmV2aXNpb24gNC41 LjItMTItMTEKICAyMDA0MDYxNCAxNTowMCBvZmZpY2lhbCByZWxlYXNlIDQuNS4yIzEKcmVhbCBt ZW1vcnkgID0gNTM4OTY4MDY0ICg1MTQgTUIpClBoeXNpY2FsIG1lbW9yeSBjaHVuayhzKToKMHgw MDAwMDAwMDAwMDAxMDAwIC0gMHgwMDAwMDAwMDAwMDk5ZmZmLCA2MjY2ODggYnl0ZXMgKDE1MyBw YWdlcykKMHgwMDAwMDAwMDAwMTAwMDAwIC0gMHgwMDAwMDAwMDAwM2ZmZmZmLCAzMTQ1NzI4IGJ5 dGVzICg3NjggcGFnZXMpCjB4MDAwMDAwMDAwMTQyNjAwMCAtIDB4MDAwMDAwMDAxZTZmMWZmZiwg NDg5NDcyMDAwIGJ5dGVzICgxMTk1MDAgcGFnZXMpCmF2YWlsIG1lbW9yeSA9IDQ4OTkyNjY1NiAo NDY3IE1CKQp4ODZiaW9zOiAgIElWVCAweDAwMDAwMC0weDAwMDRmZiBhdCAweGMwMDAwMDAwCng4 NmJpb3M6ICBTU0VHIDB4MDEwMDAwLTB4MDFmZmZmIGF0IDB4YzMzMWMwMDAKeDg2YmlvczogIEVC REEgMHgwOWYwMDAtMHgwOWZmZmYgYXQgMHhjMDA5ZjAwMAp4ODZiaW9zOiAgIFJPTSAweDBhMDAw MC0weDBlZmZmZiBhdCAweGMwMGEwMDAwCmJpb3MzMjogRm91bmQgQklPUzMyIFNlcnZpY2UgRGly ZWN0b3J5IGhlYWRlciBhdCAweGMwMGY5ZGUwCmJpb3MzMjogRW50cnkgPSAweGZhMjYwIChjMDBm YTI2MCkgIFJldiA9IDAgIExlbiA9IDEKcGNpYmlvczogUENJIEJJT1MgZW50cnkgYXQgMHhmMDAw MCsweGEyOTAKcG5wYmlvczogRm91bmQgUG5QIEJJT1MgZGF0YSBhdCAweGMwMGZhY2YwCnBucGJp b3M6IEVudHJ5ID0gZjAwMDA6YWQyMCAgUmV2ID0gMS4wCk90aGVyIEJJT1Mgc2lnbmF0dXJlcyBm b3VuZDoKVUxFOiBzZXR1cCBjcHUgMAp3bGFuOiA8ODAyLjExIExpbmsgTGF5ZXI+Cm51bGw6IDxu dWxsIGRldmljZSwgemVybyBkZXZpY2U+CnJhbmRvbTogPGVudHJvcHkgc291cmNlLCBTb2Z0d2Fy ZSwgWWFycm93PgpuZnNsb2NrOiBwc2V1ZG8tZGV2aWNlCmlvOiA8SS9PPgprYmQ6IG5ldyBhcnJh eSBzaXplIDQKa2JkMSBhdCBrYmRtdXgwCm1lbTogPG1lbW9yeT4KaHB0cnI6IFJvY2tldFJBSUQg MTd4eC8yeHh4IFNBVEEgY29udHJvbGxlciBkcml2ZXIgdjEuMgpBQ1BJOiBSU0RQIDB4ZjY2MjAg MDAwMTQgKHYwMCBJLUJBU0UpCkFDUEk6IFJTRFQgMHgxZWZmMzAwMCAwMDAyOCAodjAxIEktQkFT RSBBV1JEQUNQSSA0MjMwMkUzMSBBV1JEIDAwMDAwMDAwKQpBQ1BJOiBGQUNQIDB4MWVmZjMwNDAg MDAwNzQgKHYwMSBJLUJBU0UgQVdSREFDUEkgNDIzMDJFMzEgQVdSRCAwMDAwMDAwMCkKQUNQSTog RFNEVCAweDFlZmYzMGMwIDAxQzE2ICh2MDEgSS1CQVNFIEFXUkRBQ1BJIDAwMDAxMDAwIE1TRlQg MDEwMDAwMEMpCkFDUEk6IEZBQ1MgMHgxZWZmMDAwMCAwMDA0MApucHgwOiBJTlQgMTYgaW50ZXJm YWNlCmFjcGkwOiA8SS1CQVNFIEFXUkRBQ1BJPiBvbiBtb3RoZXJib2FyZAphY3BpMDogW01QU0FG RV0KYWNwaTA6IFtJVEhSRUFEXQphY3BpMDogUG93ZXIgQnV0dG9uIChmaXhlZCkKYWNwaTA6IFNs ZWVwIEJ1dHRvbiAoZml4ZWQpCmFjcGkwOiB3YWtldXAgY29kZSB2YSAweGMzMTU5MDAwIHBhIDB4 MTAwMApwY2lfb3BlbigxKToJbW9kZSAxIGFkZHIgcG9ydCAoMHgwY2Y4KSBpcyAweDgwMDAwMDU4 CnBjaV9vcGVuKDFhKToJbW9kZTFyZXM9MHg4MDAwMDAwMCAoMHg4MDAwMDAwMCkKcGNpX2NmZ2No ZWNrOglkZXZpY2UgMCBbY2xhc3M9MDYwMDAwXSBbaGRyPTgwXSBpcyB0aGVyZSAoaWQ9MDM5NTEy NzkpCnBjaWJpb3M6IEJJT1MgdmVyc2lvbiAyLjEwCmFjcGlfYnVzX251bWJlcjogcm9vdCBidXMg aGFzIG5vIF9CQk4sIGFzc3VtaW5nIDAKQWNwaU9zRGVyaXZlUGNpSWQ6IFxcX1NCXy5QQ0kwLlZU ODYuU0I3MCAtPiBidXMgMCBkZXYgMTcgZnVuYyAwCmFjcGlfYnVzX251bWJlcjogcm9vdCBidXMg aGFzIG5vIF9CQk4sIGFzc3VtaW5nIDAKQWNwaU9zRGVyaXZlUGNpSWQ6IFxcX1NCXy5QQ0kwLlZU ODYuUElSUSAtPiBidXMgMCBkZXYgMTcgZnVuYyAwCmFjcGkwOiByZXNlcnZhdGlvbiBvZiAwLCBh MDAwMCAoMykgZmFpbGVkCmFjcGkwOiByZXNlcnZhdGlvbiBvZiAxMDAwMDAsIDFlZWYwMDAwICgz KSBmYWlsZWQKQUNQSSB0aW1lcjogMC8xMDU0IDAvNiAwLzYgMC82IDAvNyAwLzggMC82IDAvOCAw LzYgMC81IC0+IDAKVGltZWNvdW50ZXIgIkFDUEktc2FmZSIgZnJlcXVlbmN5IDM1Nzk1NDUgSHog cXVhbGl0eSA4NTAKYWNwaV90aW1lcjA6IDwyNC1iaXQgdGltZXIgYXQgMy41Nzk1NDVNSHo+IHBv cnQgMHg0MDA4LTB4NDAwYiBvbiBhY3BpMApjcHUwOiA8QUNQSSBDUFU+IG9uIGFjcGkwCmNwdTA6 IHN3aXRjaGluZyB0byBnZW5lcmljIEN4IG1vZGUKcGNpX2xpbmswOiAgICAgICAgSW5kZXggIElS USAgUnRkICBSZWYgIElSUXMKICBJbml0aWFsIFByb2JlICAgICAgIDAgICAxNSAgIE4gICAgIDAg IDEgMyA0IDUgNiA3IDEwIDExIDEyIDE0IDE1CiAgVmFsaWRhdGlvbiAgICAgICAgICAwICAgMTUg ICBOICAgICAwICAxIDMgNCA1IDYgNyAxMCAxMSAxMiAxNCAxNQogIEFmdGVyIERpc2FibGUgICAg ICAgMCAgMjU1ICAgTiAgICAgMCAgMSAzIDQgNSA2IDcgMTAgMTEgMTIgMTQgMTUKcGNpX2xpbmsx OiAgICAgICAgSW5kZXggIElSUSAgUnRkICBSZWYgIElSUXMKICBJbml0aWFsIFByb2JlICAgICAg IDAgICAgNSAgIE4gICAgIDAgIDEgMyA0IDUgNiA3IDEwIDExIDEyIDE0IDE1CiAgVmFsaWRhdGlv biAgICAgICAgICAwICAgIDUgICBOICAgICAwICAxIDMgNCA1IDYgNyAxMCAxMSAxMiAxNCAxNQog IEFmdGVyIERpc2FibGUgICAgICAgMCAgMjU1ICAgTiAgICAgMCAgMSAzIDQgNSA2IDcgMTAgMTEg MTIgMTQgMTUKcGNpX2xpbmsyOiAgICAgICAgSW5kZXggIElSUSAgUnRkICBSZWYgIElSUXMKICBJ bml0aWFsIFByb2JlICAgICAgIDAgICAxMCAgIE4gICAgIDAgIDEgMyA0IDUgNiA3IDEwIDExIDEy IDE0IDE1CiAgVmFsaWRhdGlvbiAgICAgICAgICAwICAgMTAgICBOICAgICAwICAxIDMgNCA1IDYg NyAxMCAxMSAxMiAxNCAxNQogIEFmdGVyIERpc2FibGUgICAgICAgMCAgMjU1ICAgTiAgICAgMCAg MSAzIDQgNSA2IDcgMTAgMTEgMTIgMTQgMTUKcGNpX2xpbmszOiAgICAgICAgSW5kZXggIElSUSAg UnRkICBSZWYgIElSUXMKICBJbml0aWFsIFByb2JlICAgICAgIDAgICAxMSAgIE4gICAgIDAgIDEg MyA0IDUgNiA3IDEwIDExIDEyIDE0IDE1CiAgVmFsaWRhdGlvbiAgICAgICAgICAwICAgMTEgICBO ICAgICAwICAxIDMgNCA1IDYgNyAxMCAxMSAxMiAxNCAxNQogIEFmdGVyIERpc2FibGUgICAgICAg MCAgMjU1ICAgTiAgICAgMCAgMSAzIDQgNSA2IDcgMTAgMTEgMTIgMTQgMTUKYWNwaV9idXR0b24w OiA8UG93ZXIgQnV0dG9uPiBvbiBhY3BpMApwY2liMDogPEFDUEkgSG9zdC1QQ0kgYnJpZGdlPiBw b3J0IDB4Y2Y4LTB4Y2ZmLDB4NDAwMC0weDQwN2YsMHg0MDgwLTB4NDBmZiwweDUwMDAtMHg1MDBm IG9uIGFjcGkwCkFDUEk6IEZvdW5kIG1hdGNoaW5nIHBpbiBmb3IgMC4xMy5JTlRBIGF0IGZ1bmMg MDogMTEKQUNQSTogRm91bmQgbWF0Y2hpbmcgcGluIGZvciAwLjkuSU5UQSBhdCBmdW5jIDA6IDE1 CkFDUEk6IEZvdW5kIG1hdGNoaW5nIHBpbiBmb3IgMC45LklOVEIgYXQgZnVuYyAxOiA1CkFDUEk6 IEZvdW5kIG1hdGNoaW5nIHBpbiBmb3IgMC45LklOVEMgYXQgZnVuYyAyOiAxMApBQ1BJOiBGb3Vu ZCBtYXRjaGluZyBwaW4gZm9yIDAuMTguSU5UQSBhdCBmdW5jIDA6IDE1CnBjaTA6IDxBQ1BJIFBD SSBidXM+IG9uIHBjaWIwCnBjaTA6IGRvbWFpbj0wLCBwaHlzaWNhbCBidXM9MApmb3VuZC0+CXZl bmRvcj0weDEyNzksIGRldj0weDAzOTUsIHJldmlkPTB4MDQKCWRvbWFpbj0wLCBidXM9MCwgc2xv dD0wLCBmdW5jPTAKCWNsYXNzPTA2LTAwLTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTEKCWNtZHJl Zz0weDAwMDYsIHN0YXRyZWc9MHgyMjAwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9 MHgyMCAoOTYwIG5zKSwgbWluZ250PTB4MDAgKDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykKCW1h cFsxMF06IHR5cGUgTWVtb3J5LCByYW5nZSAzMiwgYmFzZSAweGU4MDAwMDAwLCBzaXplIDIwLCBl bmFibGVkCmZvdW5kLT4JdmVuZG9yPTB4MTI3OSwgZGV2PTB4MDM5NiwgcmV2aWQ9MHgwMAoJZG9t YWluPTAsIGJ1cz0wLCBzbG90PTAsIGZ1bmM9MQoJY2xhc3M9MDUtMDAtMDAsIGhkcnR5cGU9MHgw MCwgbWZkZXY9MQoJY21kcmVnPTB4MDAwMCwgc3RhdHJlZz0weDAwMDAsIGNhY2hlbG5zej0wIChk d29yZHMpCglsYXR0aW1lcj0weDAwICgwIG5zKSwgbWluZ250PTB4MDAgKDAgbnMpLCBtYXhsYXQ9 MHgwMCAoMCBucykKZm91bmQtPgl2ZW5kb3I9MHgxMjc5LCBkZXY9MHgwMzk3LCByZXZpZD0weDAw Cglkb21haW49MCwgYnVzPTAsIHNsb3Q9MCwgZnVuYz0yCgljbGFzcz0wNS0wMC0wMCwgaGRydHlw ZT0weDAwLCBtZmRldj0xCgljbWRyZWc9MHgwMDAwLCBzdGF0cmVnPTB4MDAwMCwgY2FjaGVsbnN6 PTAgKGR3b3JkcykKCWxhdHRpbWVyPTB4MDAgKDAgbnMpLCBtaW5nbnQ9MHgwMCAoMCBucyksIG1h eGxhdD0weDAwICgwIG5zKQpmb3VuZC0+CXZlbmRvcj0weDEyNzksIGRldj0weDAzOTksIHJldmlk PTB4MDAKCWRvbWFpbj0wLCBidXM9MCwgc2xvdD0wLCBmdW5jPTMKCWNsYXNzPTA1LTAwLTAwLCBo ZHJ0eXBlPTB4MDAsIG1mZGV2PTEKCWNtZHJlZz0weDAwMDAsIHN0YXRyZWc9MHgwMDAwLCBjYWNo ZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9MHgwMCAoMCBucyksIG1pbmdudD0weDAwICgwIG5z KSwgbWF4bGF0PTB4MDAgKDAgbnMpCmZvdW5kLT4JdmVuZG9yPTB4MTEwNiwgZGV2PTB4MzAzOCwg cmV2aWQ9MHg2MQoJZG9tYWluPTAsIGJ1cz0wLCBzbG90PTksIGZ1bmM9MAoJY2xhc3M9MGMtMDMt MDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MQoJY21kcmVnPTB4MDE0Nywgc3RhdHJlZz0weDAyMTAs IGNhY2hlbG5zej04IChkd29yZHMpCglsYXR0aW1lcj0weDIwICg5NjAgbnMpLCBtaW5nbnQ9MHgw MCAoMCBucyksIG1heGxhdD0weDAwICgwIG5zKQoJaW50cGluPWEsIGlycT0xNQoJcG93ZXJzcGVj IDIgIHN1cHBvcnRzIEQwIEQxIEQyIEQzICBjdXJyZW50IEQwCgltYXBbMjBdOiB0eXBlIEkvTyBQ b3J0LCByYW5nZSAzMiwgYmFzZSAweGUwMDAsIHNpemUgIDUsIGVuYWJsZWQKcGNpYjA6IG1hdGNo ZWQgZW50cnkgZm9yIDAuOS5JTlRBIChzcmMgXFxfU0JfLlBDSTAuTE5LQTowKQpwY2liMDogc2xv dCA5IElOVEEgcm91dGVkIHRvIGlycSAxNSB2aWEgXFxfU0JfLlBDSTAuTE5LQQp1bmtub3duOiBS ZXNlcnZlZCAweDIwIGJ5dGVzIGZvciByaWQgMHgyMCB0eXBlIDQgYXQgMHhlMDAwCmZvdW5kLT4J dmVuZG9yPTB4MTEwNiwgZGV2PTB4MzAzOCwgcmV2aWQ9MHg2MQoJZG9tYWluPTAsIGJ1cz0wLCBz bG90PTksIGZ1bmM9MQoJY2xhc3M9MGMtMDMtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MQoJY21k cmVnPTB4MDE0Nywgc3RhdHJlZz0weDAyMTAsIGNhY2hlbG5zej04IChkd29yZHMpCglsYXR0aW1l cj0weDIwICg5NjAgbnMpLCBtaW5nbnQ9MHgwMCAoMCBucyksIG1heGxhdD0weDAwICgwIG5zKQoJ aW50cGluPWIsIGlycT01Cglwb3dlcnNwZWMgMiAgc3VwcG9ydHMgRDAgRDEgRDIgRDMgIGN1cnJl bnQgRDAKCW1hcFsyMF06IHR5cGUgSS9PIFBvcnQsIHJhbmdlIDMyLCBiYXNlIDB4ZTEwMCwgc2l6 ZSAgNSwgZW5hYmxlZApwY2liMDogbWF0Y2hlZCBlbnRyeSBmb3IgMC45LklOVEIgKHNyYyBcXF9T Ql8uUENJMC5MTktCOjApCnBjaWIwOiBzbG90IDkgSU5UQiByb3V0ZWQgdG8gaXJxIDUgdmlhIFxc X1NCXy5QQ0kwLkxOS0IKdW5rbm93bjogUmVzZXJ2ZWQgMHgyMCBieXRlcyBmb3IgcmlkIDB4MjAg dHlwZSA0IGF0IDB4ZTEwMApmb3VuZC0+CXZlbmRvcj0weDExMDYsIGRldj0weDMxMDQsIHJldmlk PTB4NjMKCWRvbWFpbj0wLCBidXM9MCwgc2xvdD05LCBmdW5jPTIKCWNsYXNzPTBjLTAzLTIwLCBo ZHJ0eXBlPTB4MDAsIG1mZGV2PTEKCWNtZHJlZz0weDAxNDcsIHN0YXRyZWc9MHgwMjEwLCBjYWNo ZWxuc3o9OCAoZHdvcmRzKQoJbGF0dGltZXI9MHgyMCAoOTYwIG5zKSwgbWluZ250PTB4MDAgKDAg bnMpLCBtYXhsYXQ9MHgwMCAoMCBucykKCWludHBpbj1jLCBpcnE9MTAKCXBvd2Vyc3BlYyAyICBz dXBwb3J0cyBEMCBEMSBEMiBEMyAgY3VycmVudCBEMAoJbWFwWzEwXTogdHlwZSBNZW1vcnksIHJh bmdlIDMyLCBiYXNlIDB4ZTgxMzEwMDAsIHNpemUgIDgsIGVuYWJsZWQKcGNpYjA6IG1hdGNoZWQg ZW50cnkgZm9yIDAuOS5JTlRDIChzcmMgXFxfU0JfLlBDSTAuTE5LQzowKQpwY2liMDogc2xvdCA5 IElOVEMgcm91dGVkIHRvIGlycSAxMCB2aWEgXFxfU0JfLlBDSTAuTE5LQwp1bmtub3duOiBSZXNl cnZlZCAweDEwMCBieXRlcyBmb3IgcmlkIDB4MTAgdHlwZSAzIGF0IDB4ZTgxMzEwMDAKZm91bmQt Pgl2ZW5kb3I9MHgxMDAyLCBkZXY9MHg1MTU5LCByZXZpZD0weDAwCglkb21haW49MCwgYnVzPTAs IHNsb3Q9MTMsIGZ1bmM9MAoJY2xhc3M9MDMtMDAtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MAoJ Y21kcmVnPTB4MDE4Nywgc3RhdHJlZz0weDAyOTAsIGNhY2hlbG5zej04IChkd29yZHMpCglsYXR0 aW1lcj0weDIwICg5NjAgbnMpLCBtaW5nbnQ9MHgwOCAoMjAwMCBucyksIG1heGxhdD0weDAwICgw IG5zKQoJaW50cGluPWEsIGlycT0xMQoJcG93ZXJzcGVjIDIgIHN1cHBvcnRzIEQwIEQxIEQyIEQz ICBjdXJyZW50IEQwCgltYXBbMTBdOiB0eXBlIFByZWZldGNoYWJsZSBNZW1vcnksIHJhbmdlIDMy LCBiYXNlIDB4ZTAwMDAwMDAsIHNpemUgMjcsIGVuYWJsZWQKCW1hcFsxNF06IHR5cGUgSS9PIFBv cnQsIHJhbmdlIDMyLCBiYXNlIDB4ZTIwMCwgc2l6ZSAgOCwgZW5hYmxlZAoJbWFwWzE4XTogdHlw ZSBNZW1vcnksIHJhbmdlIDMyLCBiYXNlIDB4ZTgxMjAwMDAsIHNpemUgMTYsIGVuYWJsZWQKcGNp YjA6IG1hdGNoZWQgZW50cnkgZm9yIDAuMTMuSU5UQSAoc3JjIFxcX1NCXy5QQ0kwLkxOS0Q6MCkK cGNpYjA6IHNsb3QgMTMgSU5UQSByb3V0ZWQgdG8gaXJxIDExIHZpYSBcXF9TQl8uUENJMC5MTktE CmZvdW5kLT4JdmVuZG9yPTB4MTEwNiwgZGV2PTB4ODIzMSwgcmV2aWQ9MHgxMAoJZG9tYWluPTAs IGJ1cz0wLCBzbG90PTE3LCBmdW5jPTAKCWNsYXNzPTA2LTAxLTAwLCBoZHJ0eXBlPTB4MDAsIG1m ZGV2PTEKCWNtZHJlZz0weDAwODcsIHN0YXRyZWc9MHgwMjEwLCBjYWNoZWxuc3o9MCAoZHdvcmRz KQoJbGF0dGltZXI9MHgwMCAoMCBucyksIG1pbmdudD0weDAwICgwIG5zKSwgbWF4bGF0PTB4MDAg KDAgbnMpCglwb3dlcnNwZWMgMiAgc3VwcG9ydHMgRDAgRDMgIGN1cnJlbnQgRDAKZm91bmQtPgl2 ZW5kb3I9MHgxMTA2LCBkZXY9MHgwNTcxLCByZXZpZD0weDA2Cglkb21haW49MCwgYnVzPTAsIHNs b3Q9MTcsIGZ1bmM9MQoJY2xhc3M9MDEtMDEtOGEsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MAoJY21k cmVnPTB4MDAwNywgc3RhdHJlZz0weDAyOTAsIGNhY2hlbG5zej0wIChkd29yZHMpCglsYXR0aW1l cj0weDIwICg5NjAgbnMpLCBtaW5nbnQ9MHgwMCAoMCBucyksIG1heGxhdD0weDAwICgwIG5zKQoJ cG93ZXJzcGVjIDIgIHN1cHBvcnRzIEQwIEQzICBjdXJyZW50IEQwCgltYXBbMjBdOiB0eXBlIEkv TyBQb3J0LCByYW5nZSAzMiwgYmFzZSAweGUzMDAsIHNpemUgIDQsIGVuYWJsZWQKZm91bmQtPgl2 ZW5kb3I9MHgxMTA2LCBkZXY9MHg4MjM1LCByZXZpZD0weDEwCglkb21haW49MCwgYnVzPTAsIHNs b3Q9MTcsIGZ1bmM9NAoJY2xhc3M9MDYtODAtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MAoJY21k cmVnPTB4MDAwMCwgc3RhdHJlZz0weDAyOTAsIGNhY2hlbG5zej0wIChkd29yZHMpCglsYXR0aW1l cj0weDAwICgwIG5zKSwgbWluZ250PTB4MDAgKDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykKCXBv d2Vyc3BlYyAyICBzdXBwb3J0cyBEMCBEMyAgY3VycmVudCBEMApmb3VuZC0+CXZlbmRvcj0weDEx MDYsIGRldj0weDMwNjUsIHJldmlkPTB4NTEKCWRvbWFpbj0wLCBidXM9MCwgc2xvdD0xOCwgZnVu Yz0wCgljbGFzcz0wMi0wMC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0wCgljbWRyZWc9MHgwMTQ3 LCBzdGF0cmVnPTB4MDIxMCwgY2FjaGVsbnN6PTggKGR3b3JkcykKCWxhdHRpbWVyPTB4MjAgKDk2 MCBucyksIG1pbmdudD0weDAzICg3NTAgbnMpLCBtYXhsYXQ9MHgwOCAoMjAwMCBucykKCWludHBp bj1hLCBpcnE9MTUKCXBvd2Vyc3BlYyAyICBzdXBwb3J0cyBEMCBEMSBEMiBEMyAgY3VycmVudCBE MAoJbWFwWzEwXTogdHlwZSBJL08gUG9ydCwgcmFuZ2UgMzIsIGJhc2UgMHhlNjAwLCBzaXplICA4 LCBlbmFibGVkCgltYXBbMTRdOiB0eXBlIE1lbW9yeSwgcmFuZ2UgMzIsIGJhc2UgMHhlODEzMDAw MCwgc2l6ZSAgOCwgZW5hYmxlZApwY2liMDogbWF0Y2hlZCBlbnRyeSBmb3IgMC4xOC5JTlRBIChz cmMgXFxfU0JfLlBDSTAuTE5LQTowKQpwY2liMDogc2xvdCAxOCBJTlRBIHJvdXRlZCB0byBpcnEg MTUgdmlhIFxcX1NCXy5QQ0kwLkxOS0EKcGNpMDogPG1lbW9yeSwgUkFNPiBhdCBkZXZpY2UgMC4x IChubyBkcml2ZXIgYXR0YWNoZWQpCnBjaTA6IDxtZW1vcnksIFJBTT4gYXQgZGV2aWNlIDAuMiAo bm8gZHJpdmVyIGF0dGFjaGVkKQpwY2kwOiA8bWVtb3J5LCBSQU0+IGF0IGRldmljZSAwLjMgKG5v IGRyaXZlciBhdHRhY2hlZCkKdWhjaTA6IDxWSUEgODNDNTcyIFVTQiBjb250cm9sbGVyPiBwb3J0 IDB4ZTAwMC0weGUwMWYgaXJxIDE1IGF0IGRldmljZSA5LjAgb24gcGNpMAp1aGNpMDogW01QU0FG RV0KdWhjaTA6IFtJVEhSRUFEXQp1c2J1czA6IDxWSUEgODNDNTcyIFVTQiBjb250cm9sbGVyPiBv biB1aGNpMAp1aGNpMTogPFZJQSA4M0M1NzIgVVNCIGNvbnRyb2xsZXI+IHBvcnQgMHhlMTAwLTB4 ZTExZiBpcnEgNSBhdCBkZXZpY2UgOS4xIG9uIHBjaTAKdWhjaTE6IFtNUFNBRkVdCnVoY2kxOiBb SVRIUkVBRF0KdXNidXMxOiA8VklBIDgzQzU3MiBVU0IgY29udHJvbGxlcj4gb24gdWhjaTEKZWhj aTA6IDxWSUEgVlQ2MjAyIFVTQiAyLjAgY29udHJvbGxlcj4gbWVtIDB4ZTgxMzEwMDAtMHhlODEz MTBmZiBpcnEgMTAgYXQgZGV2aWNlIDkuMiBvbiBwY2kwCmVoY2kwOiBbTVBTQUZFXQplaGNpMDog W0lUSFJFQURdCmVoY2kwOiBEcm9wcGVkIGludGVycnVwdHMgd29ya2Fyb3VuZCBlbmFibGVkCnVz YnVzMjogRUhDSSB2ZXJzaW9uIDEuMAp1c2J1czI6IDxWSUEgVlQ2MjAyIFVTQiAyLjAgY29udHJv bGxlcj4gb24gZWhjaTAKdmdhcGNpMDogPFZHQS1jb21wYXRpYmxlIGRpc3BsYXk+IHBvcnQgMHhl MjAwLTB4ZTJmZiBtZW0gMHhlMDAwMDAwMC0weGU3ZmZmZmZmLDB4ZTgxMjAwMDAtMHhlODEyZmZm ZiBpcnEgMTEgYXQgZGV2aWNlIDEzLjAgb24gcGNpMAppc2FiMDogPFBDSS1JU0EgYnJpZGdlPiBh dCBkZXZpY2UgMTcuMCBvbiBwY2kwCmlzYTA6IDxJU0EgYnVzPiBvbiBpc2FiMAphdGFwY2kwOiA8 VklBIDgyMzEgVURNQTEwMCBjb250cm9sbGVyPiBwb3J0IDB4MWYwLTB4MWY3LDB4M2Y2LDB4MTcw LTB4MTc3LDB4Mzc2LDB4ZTMwMC0weGUzMGYgYXQgZGV2aWNlIDE3LjEgb24gcGNpMAphdGFwY2kw OiBSZXNlcnZlZCAweDEwIGJ5dGVzIGZvciByaWQgMHgyMCB0eXBlIDQgYXQgMHhlMzAwCmF0YTA6 IDxBVEEgY2hhbm5lbCAwPiBvbiBhdGFwY2kwCmF0YXBjaTA6IFJlc2VydmVkIDB4OCBieXRlcyBm b3IgcmlkIDB4MTAgdHlwZSA0IGF0IDB4MWYwCmF0YXBjaTA6IFJlc2VydmVkIDB4MSBieXRlcyBm b3IgcmlkIDB4MTQgdHlwZSA0IGF0IDB4M2Y2CmF0YTA6IHJlc2V0IHRwMSBtYXNrPTAzIG9zdGF0 MD01MCBvc3RhdDE9MDAKYXRhMDogc3RhdDA9MHg1MCBlcnI9MHgwMSBsc2I9MHgwMCBtc2I9MHgw MAphdGEwOiBzdGF0MT0weDAwIGVycj0weDAxIGxzYj0weDAwIG1zYj0weDAwCmF0YTA6IHJlc2V0 IHRwMiBzdGF0MD01MCBzdGF0MT0wMCBkZXZpY2VzPTB4MQphdGEwOiBbTVBTQUZFXQphdGEwOiBb SVRIUkVBRF0KYXRhMTogPEFUQSBjaGFubmVsIDE+IG9uIGF0YXBjaTAKYXRhcGNpMDogUmVzZXJ2 ZWQgMHg4IGJ5dGVzIGZvciByaWQgMHgxOCB0eXBlIDQgYXQgMHgxNzAKYXRhcGNpMDogUmVzZXJ2 ZWQgMHgxIGJ5dGVzIGZvciByaWQgMHgxYyB0eXBlIDQgYXQgMHgzNzYKYXRhMTogcmVzZXQgdHAx IG1hc2s9MDAgb3N0YXQwPWZmIG9zdGF0MT1mZgphdGExOiBbTVBTQUZFXQphdGExOiBbSVRIUkVB RF0KcGNpMDogPGJyaWRnZT4gYXQgZGV2aWNlIDE3LjQgKG5vIGRyaXZlciBhdHRhY2hlZCkKdnIw OiA8VklBIFZUNjEwMiBSaGluZSBJSSAxMC8xMDBCYXNlVFg+IHBvcnQgMHhlNjAwLTB4ZTZmZiBt ZW0gMHhlODEzMDAwMC0weGU4MTMwMGZmIGlycSAxNSBhdCBkZXZpY2UgMTguMCBvbiBwY2kwCnZy MDogUXVpcmtzOiAweDAKdnIwOiBSZXZpc2lvbjogMHg1MQp2cjA6IFJlc2VydmVkIDB4MTAwIGJ5 dGVzIGZvciByaWQgMHgxMCB0eXBlIDQgYXQgMHhlNjAwCm1paWJ1czA6IDxNSUkgYnVzPiBvbiB2 cjAKdWtwaHkwOiA8R2VuZXJpYyBJRUVFIDgwMi4zdSBtZWRpYSBpbnRlcmZhY2U+IFBIWSAxIG9u IG1paWJ1czAKdWtwaHkwOiBPVUkgMHgwMDQwNjMsIG1vZGVsIDB4MDAzMiwgcmV2LiAxMAp1a3Bo eTA6ICAxMGJhc2VULCAxMGJhc2VULUZEWCwgMTAwYmFzZVRYLCAxMDBiYXNlVFgtRkRYLCBhdXRv CnZyMDogYnBmIGF0dGFjaGVkCnZyMDogRXRoZXJuZXQgYWRkcmVzczogMDA6MTM6MjE6ZWU6OGQ6 ZDQKdnIwOiBbTVBTQUZFXQp2cjA6IFtJVEhSRUFEXQphdHJ0YzA6IDxBVCByZWFsdGltZSBjbG9j az4gcG9ydCAweDcwLTB4NzMgaXJxIDggb24gYWNwaTAKYXRydGMwOiByZWdpc3RlcmVkIGFzIGEg dGltZS1vZi1kYXkgY2xvY2sgKHJlc29sdXRpb24gMTAwMDAwMHVzKQpwcGMwOiB1c2luZyBleHRl bmRlZCBJL08gcG9ydCByYW5nZQpwcGMwOiBTUFAgRVBQCnBwYzA6IDxQYXJhbGxlbCBwb3J0PiBw b3J0IDB4Mzc4LTB4MzdmIGlycSA3IG9uIGFjcGkwCnBwYzA6IEdlbmVyaWMgY2hpcHNldCAoRVBQ L05JQkJMRSkgaW4gQ09NUEFUSUJMRSBtb2RlCnBwYzA6IFtNUFNBRkVdCnBwYzA6IFtJVEhSRUFE XQpwcGJ1czA6IDxQYXJhbGxlbCBwb3J0IGJ1cz4gb24gcHBjMApwbGlwMDogPFBMSVAgbmV0d29y ayBpbnRlcmZhY2U+IG9uIHBwYnVzMApwbGlwMDogYnBmIGF0dGFjaGVkCnBsaXAwOiBbTVBTQUZF XQpwbGlwMDogW0lUSFJFQURdCmxwdDA6IDxQcmludGVyPiBvbiBwcGJ1czAKbHB0MDogW01QU0FG RV0KbHB0MDogW0lUSFJFQURdCmxwdDA6IEludGVycnVwdC1kcml2ZW4gcG9ydApwcGkwOiA8UGFy YWxsZWwgSS9PPiBvbiBwcGJ1czAKYXRrYmRjMDogPEtleWJvYXJkIGNvbnRyb2xsZXIgKGk4MDQy KT4gcG9ydCAweDYwLDB4NjQgaXJxIDEgb24gYWNwaTAKYXRrYmQwOiA8QVQgS2V5Ym9hcmQ+IGly cSAxIG9uIGF0a2JkYzAKYXRrYmQ6IHRoZSBjdXJyZW50IGtiZCBjb250cm9sbGVyIGNvbW1hbmQg Ynl0ZSAwMDQ3CmF0a2JkOiBrZXlib2FyZCBJRCAweDQxYWIgKDIpCmtiZDAgYXQgYXRrYmQwCmti ZDA6IGF0a2JkMCwgQVQgMTAxLzEwMiAoMiksIGNvbmZpZzoweDAsIGZsYWdzOjB4M2QwMDAwCmF0 a2JkMDogW0dJQU5ULUxPQ0tFRF0KYXRrYmQwOiBbSVRIUkVBRF0KcHNtMDogdW5hYmxlIHRvIGFs bG9jYXRlIElSUQp1bmtub3duOiBzdGF0dXMgcmVnIHRlc3QgZmFpbGVkIGZmCnVua25vd246IHN0 YXR1cyByZWcgdGVzdCBmYWlsZWQgZmYKdW5rbm93bjogc3RhdHVzIHJlZyB0ZXN0IGZhaWxlZCBm Zgp1bmtub3duOiBzdGF0dXMgcmVnIHRlc3QgZmFpbGVkIGZmCnVua25vd246IHN0YXR1cyByZWcg dGVzdCBmYWlsZWQgZmYKdW5rbm93bjogc3RhdHVzIHJlZyB0ZXN0IGZhaWxlZCBmZgpleF9pc2Ff aWRlbnRpZnkoKQpwbnBfaWRlbnRpZnk6IFRyeWluZyBSZWFkX1BvcnQgYXQgMjAzCnBucF9pZGVu dGlmeTogVHJ5aW5nIFJlYWRfUG9ydCBhdCAyNDMKcG5wX2lkZW50aWZ5OiBUcnlpbmcgUmVhZF9Q b3J0IGF0IDI4MwpwbnBfaWRlbnRpZnk6IFRyeWluZyBSZWFkX1BvcnQgYXQgMmMzCnBucF9pZGVu dGlmeTogVHJ5aW5nIFJlYWRfUG9ydCBhdCAzMDMKcG5wX2lkZW50aWZ5OiBUcnlpbmcgUmVhZF9Q b3J0IGF0IDM0MwpwbnBfaWRlbnRpZnk6IFRyeWluZyBSZWFkX1BvcnQgYXQgMzgzCnBucF9pZGVu dGlmeTogVHJ5aW5nIFJlYWRfUG9ydCBhdCAzYzMKUE5QIElkZW50aWZ5IGNvbXBsZXRlCmlzYV9w cm9iZV9jaGlsZHJlbjogZGlzYWJsaW5nIFBuUCBkZXZpY2VzCnBtdGltZXIwIG9uIGlzYTAKaXNh X3Byb2JlX2NoaWxkcmVuOiBwcm9iaW5nIG5vbi1QblAgZGV2aWNlcwpvcm0wOiA8SVNBIE9wdGlv biBST01zPiBhdCBpb21lbSAweGMwMDAwLTB4YzhmZmYsMHhjYzAwMC0weGQ1ZmZmIHBucGlkIE9S TTAwMDAgb24gaXNhMApzYzA6IDxTeXN0ZW0gY29uc29sZT4gb24gaXNhMApzYzA6IFZHQSA8MTYg dmlydHVhbCBjb25zb2xlcywgZmxhZ3M9MHgzMDA+CnNjMDogZmIwLCBrYmQxLCB0ZXJtaW5hbCBl bXVsYXRvcjogc2N0ZWtlbiAodGVrZW4gdGVybWluYWwpCnZnYTA6IDxHZW5lcmljIElTQSBWR0E+ IGF0IHBvcnQgMHgzYzAtMHgzZGYgaW9tZW0gMHhhMDAwMC0weGJmZmZmIG9uIGlzYTAKaXNhX3By b2JlX2NoaWxkcmVuOiBwcm9iaW5nIFBuUCBkZXZpY2VzCmFjcGlfdGhyb3R0bGUwOiA8QUNQSSBD UFUgVGhyb3R0bGluZz4gb24gY3B1MAphY3BpX3Rocm90dGxlMDogUF9DTlQgZnJvbSBQX0JMSyAw eDQwMTAKRGV2aWNlIGNvbmZpZ3VyYXRpb24gZmluaXNoZWQuCnByb2NmcyByZWdpc3RlcmVkClRp bWVjb3VudGVyICJUU0MiIGZyZXF1ZW5jeSA3OTgxMzAwOTYgSHogcXVhbGl0eSA4MDAKVGltZWNv dW50ZXJzIHRpY2sgZXZlcnkgMS4wMDAgbXNlYwp2bGFuOiBpbml0aWFsaXplZCwgdXNpbmcgaGFz aCB0YWJsZXMgd2l0aCBjaGFpbmluZwpsbzA6IGJwZiBhdHRhY2hlZApwZnN5bmMwOiBicGYgYXR0 YWNoZWQKcGZsb2cwOiBicGYgYXR0YWNoZWQKaHB0cnI6IG5vIGNvbnRyb2xsZXIgZGV0ZWN0ZWQu CmF0YTA6IElkZW50aWZ5aW5nIGRldmljZXM6IDAwMDAwMDAxCmF0YTA6IE5ldyBkZXZpY2VzOiAw MDAwMDAwMQp1c2J1czA6IDEyTWJwcyBGdWxsIFNwZWVkIFVTQiB2MS4wCnVzYnVzMTogMTJNYnBz IEZ1bGwgU3BlZWQgVVNCIHYxLjAKdXNidXMyOiA0ODBNYnBzIEhpZ2ggU3BlZWQgVVNCIHYyLjAK YXRhMC1tYXN0ZXI6IHBpbz1QSU80IHdkbWE9V0RNQTIgdWRtYT1VRE1BMzMgY2FibGU9NDAgd2ly ZQp1Z2VuMC4xOiA8VklBPiBhdCB1c2J1czAKdWh1YjA6IDxWSUEgVUhDSSByb290IEhVQiwgY2xh c3MgOS8wLCByZXYgMS4wMC8xLjAwLCBhZGRyIDE+IG9uIHVzYnVzMAp1Z2VuMS4xOiA8VklBPiBh dCB1c2J1czEKdWh1YjE6IDxWSUEgVUhDSSByb290IEhVQiwgY2xhc3MgOS8wLCByZXYgMS4wMC8x LjAwLCBhZGRyIDE+IG9uIHVzYnVzMQp1Z2VuMi4xOiA8VklBPiBhdCB1c2J1czIKdWh1YjI6IDxW SUEgRUhDSSByb290IEhVQiwgY2xhc3MgOS8wLCByZXYgMi4wMC8xLjAwLCBhZGRyIDE+IG9uIHVz YnVzMgphZDA6IHNldHRpbmcgVURNQTMzCmFkMDogNTg1OU1CIDxITVMzNjA2MDZENUNGMDAgRFA2 QUMzMEg+IGF0IGF0YTAtbWFzdGVyIFVETUEzMyAKYWQwOiAxMjAwMDU1NiBzZWN0b3JzIFsxMTkw NUMvMTZILzYzU10gMTYgc2VjdG9ycy9pbnRlcnJ1cHQgMSBkZXB0aCBxdWV1ZQpHRU9NOiBuZXcg ZGlzayBhZDAKYWQwOiBWSUEgY2hlY2sxIGZhaWxlZAphZDA6IEFkYXB0ZWMgY2hlY2sxIGZhaWxl ZAphZDA6IExTSSAodjMpIGNoZWNrMSBmYWlsZWQKYWQwOiBMU0kgKHYyKSBjaGVjazEgZmFpbGVk CnVodWIwOiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZAp1aHViMTogMiBw b3J0cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQKYWQwOiBGcmVlQlNEIGNoZWNrMSBm YWlsZWQKYXRhMTogSWRlbnRpZnlpbmcgZGV2aWNlczogMDAwMDAwMDAKYXRhMTogTmV3IGRldmlj ZXM6IDAwMDAwMDAwCkFUQSBQc2V1ZG9SQUlEIGxvYWRlZAp1aHViMjogNCBwb3J0cyB3aXRoIDQg cmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQKUm9vdCBtb3VudCB3YWl0aW5nIGZvcjogdXNidXMyCnVn ZW4yLjI6IDx2ZW5kb3IgMHgwNTBkPiBhdCB1c2J1czIKYXhlMDogPHZlbmRvciAweDA1MGQgcHJv ZHVjdCAweDUwNTUsIHJldiAyLjAwLzAuMDEsIGFkZHIgMj4gb24gdXNidXMyCmF4ZTA6IFBIWUFE RFIgMHhlMDoweDAxClRyeWluZyB0byBtb3VudCByb290IGZyb20gdWZzOi9kZXYvYWQwczNhCmN0 X3RvX3RzKFsyMDEwLTExLTE5IDE5OjU4OjA2XSkgPSAxMjkwMTk2Njg2LjAwMDAwMDAwMApzdGFy dF9pbml0OiB0cnlpbmcgL3NiaW4vaW5pdAptaWlidXMxOiA8TUlJIGJ1cz4gb24gYXhlMAp0cnVl cGh5MDogPEVUMTAxMSAxMC8xMDAvMTAwMGJhc2VUIFBIWT4gUEhZIDEgb24gbWlpYnVzMQp0cnVl cGh5MDogIDEwYmFzZVQsIDEwYmFzZVQtRkRYLCAxMDBiYXNlVFgsIDEwMGJhc2VUWC1GRFgsIDEw MDBiYXNlVC1GRFgsIGF1dG8KdWUwOiA8VVNCIEV0aGVybmV0PiBvbiBheGUwCnVlMDogYnBmIGF0 dGFjaGVkCnVlMDogRXRoZXJuZXQgYWRkcmVzczogMDA6MTE6NTA6ZTc6Mzk6ZTkKYnJpZGdlMDog YnBmIGF0dGFjaGVkCmJyaWRnZTA6IEV0aGVybmV0IGFkZHJlc3M6IGRlOmQ1OjM3OjhmOjNmOmMy CnNwbGFzaDogaW1hZ2UgZGVjb2RlciBmb3VuZDogZ3JlZW5fc2F2ZXIKdWUwOiBsaW5rIHN0YXRl IGNoYW5nZWQgdG8gRE9XTgp1ZTA6IGxpbmsgc3RhdGUgY2hhbmdlZCB0byBVUAp1ZTA6IGxpbmsg c3RhdGUgY2hhbmdlZCB0byBET1dOCnVlMDogbGluayBzdGF0ZSBjaGFuZ2VkIHRvIFVQCnVlMDog bGluayBzdGF0ZSBjaGFuZ2VkIHRvIERPV04KdWUwOiBsaW5rIHN0YXRlIGNoYW5nZWQgdG8gVVAK dWUwOiBsaW5rIHN0YXRlIGNoYW5nZWQgdG8gRE9XTgp1ZTA6IGxpbmsgc3RhdGUgY2hhbmdlZCB0 byBVUAp1ZTA6IGxpbmsgc3RhdGUgY2hhbmdlZCB0byBET1dOCnVlMDogbGluayBzdGF0ZSBjaGFu Z2VkIHRvIFVQCnVlMDogbGluayBzdGF0ZSBjaGFuZ2VkIHRvIERPV04KdWUwOiBsaW5rIHN0YXRl IGNoYW5nZWQgdG8gVVAKdWUwOiBsaW5rIHN0YXRlIGNoYW5nZWQgdG8gRE9XTgp1ZTA6IGxpbmsg c3RhdGUgY2hhbmdlZCB0byBVUAp1ZTA6IGxpbmsgc3RhdGUgY2hhbmdlZCB0byBET1dOCnVlMDog bGluayBzdGF0ZSBjaGFuZ2VkIHRvIFVQCnVlMDogbGluayBzdGF0ZSBjaGFuZ2VkIHRvIERPV04K dWUwOiBsaW5rIHN0YXRlIGNoYW5nZWQgdG8gVVAK ------=_20101119182350_44597-- From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 20:42:17 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 317E0106566C for ; Fri, 19 Nov 2010 20:42:17 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from ftp.translate.ru (ftp.translate.ru [80.249.188.42]) by mx1.freebsd.org (Postfix) with ESMTP id E1E4C8FC0C for ; Fri, 19 Nov 2010 20:42:16 +0000 (UTC) Received: from desktop.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id 6D2F513DF46; Fri, 19 Nov 2010 23:42:15 +0300 (MSK) Date: Fri, 19 Nov 2010 23:42:11 +0300 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <12210339806.20101119234211@serebryakov.spb.ru> To: Paul B Mahol In-Reply-To: References: <441397602.20101119185527@serebryakov.spb.ru> <201011191720.15402.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb@freebsd.org Subject: Re: Two questions: how to specify module-load function for driver module and which name of driver is better (according to "standards") X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 20:42:17 -0000 Hello, Paul. You wrote 19 =ED=EE=FF=E1=F0=FF 2010 =E3., 19:56:26: > Is it possible/sane to integrate two drivers in one? No, they are almost totally different. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 20:46:57 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D6D1106564A for ; Fri, 19 Nov 2010 20:46:57 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 2768A8FC1B for ; Fri, 19 Nov 2010 20:46:56 +0000 (UTC) Received: from [109.41.253.170] (helo=tiny.Sisis.de.) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PJXr8-0000VG-On; Fri, 19 Nov 2010 21:46:51 +0100 Received: from tiny.Sisis.de. (localhost [127.0.0.1]) by tiny.Sisis.de. (8.14.3/8.14.3) with ESMTP id oAJKkhYK001534; Fri, 19 Nov 2010 21:46:44 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by tiny.Sisis.de. (8.14.3/8.14.3/Submit) id oAJKkeXQ001533; Fri, 19 Nov 2010 21:46:40 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: tiny.Sisis.de.: guru set sender to guru@unixarea.de using -f Date: Fri, 19 Nov 2010 21:46:39 +0100 From: Matthias Apitz To: Warren Block Message-ID: <20101119204639.GA1521@tiny.Sisis.de> References: <20101119143337.GA3023@current.Sisis.de> <201011191821.09308.hselasky@c2i.net> <20101119173519.GA3933@current.Sisis.de> <201011191916.53655.hselasky@c2i.net> <20101119183900.GA1221@tiny.Sisis.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 109.41.253.170 Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 20:46:57 -0000 El día Friday, November 19, 2010 a las 12:39:13PM -0700, Warren Block escribió: > > Just an idea: The USB key in question was new and I only created the > > file system on it the usual way (fdisk, bsdlabel, newfs). Then I > > restored the dump on it (which took 26 hours for 3.1 GByte dump file). > > The USB key boots fine, btw. > > 26 *hours*? USB 1.1? I don't think so. It is the Acer One D250 netbook. > Well, they could be anything. But the original filesystem has > formerly-used blocks with old data from deleted files. dump doesn't > copy those, but dd does. > > > Should I overwrite the full USB key from /dev/zero? > > Possibly there would still be differences. Filesystem metadata like > date last mounted, for example. If you want a block-by-block duplicate, > the brute-force method is to just dd the whole drive. Use bs=64k or > bs=1m to help reduce overhead. Warren, perhaps you missed my point. I have a prepared boot-able key and I want to give away a copy of it as a file on DVD. So I dd(1)'ed the key to disk and did this twice to ensure that the copy was fine, but the two files differ. How can I make sure that the file on disk (or DVD) is a exact copy of the key? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 21:10:07 2010 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 6058210656A4 for ; Fri, 19 Nov 2010 21:10:07 +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 05CBF8FC08 for ; Fri, 19 Nov 2010 21:10:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAJLA5j3012477 for ; Fri, 19 Nov 2010 21:10:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAJLA595012476; Fri, 19 Nov 2010 21:10:05 GMT (envelope-from gnats) Date: Fri, 19 Nov 2010 21:10:05 GMT Message-Id: <201011192110.oAJLA595012476@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: usb/150546: commit references a PR X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 21:10:07 -0000 The following reply was made to PR usb/150546; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/150546: commit references a PR Date: Fri, 19 Nov 2010 21:04:24 +0000 (UTC) Author: thompsa Date: Fri Nov 19 21:04:18 2010 New Revision: 215546 URL: http://svn.freebsd.org/changeset/base/215546 Log: MFC r213853 - Add missing LibUSB API functions: * libusb_strerror() * libusb_get_driver[_np]() * libusb_detach_kernel_driver[_np]() - Factor out setting of non-blocking flag inside libusb. - Add missing NULL check after libusb_get_device() call. - Correct some wrong error codes due to copy and paste error. PR: usb/150546 Submitted by: Robert Jenssen, Alexander Leidinger Modified: stable/8/lib/libusb/libusb.3 stable/8/lib/libusb/libusb.h stable/8/lib/libusb/libusb10.c stable/8/lib/libusb/libusb20.3 Directory Properties: stable/8/lib/libusb/ (props changed) stable/8/lib/libusb/usb.h (props changed) Modified: stable/8/lib/libusb/libusb.3 ============================================================================== --- stable/8/lib/libusb/libusb.3 Fri Nov 19 20:23:01 2010 (r215545) +++ stable/8/lib/libusb/libusb.3 Fri Nov 19 21:04:18 2010 (r215546) @@ -26,7 +26,7 @@ .\" .\" $FreeBSD$ .\" -.Dd June 22, 2009 +.Dd October 14, 2010 .Dt LIBUSB 3 .Os .Sh NAME @@ -72,6 +72,15 @@ Deinitialise libusb. Must be called at t . .Pp . +.Ft const char * +.Fn libusb_strerror "int code" +Get ASCII representation of the error given by the +.Fa code +argument. +. +. +.Pp +. .Ft void .Fn libusb_set_debug "libusb_context *ctx" "int level" Set debug to the @@ -239,12 +248,37 @@ if the device has been disconnected and .Pp . .Ft int +.Fn libusb_get_driver "libusb_device_handle *devh" "int interface" "char *name" "int namelen" +or +.Ft int +.Fn libusb_get_driver_np "libusb_device_handle *devh" "int interface" "char *name" "int namelen" +Gets the name of the driver attached to the given +.Fa device +and +.Fa interface +into the buffer given by +.Fa name +and +.Fa namelen . +Returns 0 on success, LIBUSB_ERROR_NOT_FOUND if no kernel driver is attached +to the given interface and LIBUSB_ERROR_INVALID_PARAM if the interface does +not exist. +This function is non-portable. +The buffer pointed to by +.Fa name +is only zero terminated on success. +. +.Pp +. +.Ft int .Fn libusb_detach_kernel_driver "libusb_device_handle *devh" "int interface" -Detach a kernel driver from an interface. This is needed to claim an interface -required by a kernel driver. Returns 0 on success, LIBUSB_ERROR_NOT_FOUND if -no kernel driver was active, LIBUSB_ERROR_INVALID_PARAM if the interface does not -exist, LIBUSB_ERROR_NO_DEVICE if the device has been disconnected and a -LIBUSB_ERROR code on failure. +or +.Ft int +.Fn libusb_detach_kernel_driver_np "libusb_device_handle *devh" "int interface" +Detach a kernel driver from an interface. +This is needed to claim an interface required by a kernel driver. +Returns 0 on success, LIBUSB_ERROR_NOT_FOUND if no kernel driver was active, +LIBUSB_ERROR_INVALID_PARAM if the interface does not exist, LIBUSB_ERROR_NO_DEVICE if the device has been disconnected and a LIBUSB_ERROR code on failure. This function is non-portable. . .Pp . @@ -271,7 +305,7 @@ failure. . .Pp .Ft int -.Fn libsub_get_active_config_descriptor "libusb_device *dev" "libusb_device_descriptor **config" +.Fn libsub_get_active_config_descriptor "libusb_device *dev" "struct libusb_config_descriptor **config" Get the USB configuration descriptor for the active configuration. Returns 0 on success, returns LIBUSB_ERROR_NOT_FOUND if the device is in unconfigured state and return another LIBUSB_ERROR code on error. @@ -337,7 +371,7 @@ LIBUSB_ERROR code on failure. . .Pp .Ft int -.Fn libusb_control_transfer "libusb_device_handle *devh" "uint8_t bmRequestType" "uint16_t wIndex" "unsigned char *data" "uint16_t wLength" "unsigned int timeout" +.Fn libusb_control_transfer "libusb_device_handle *devh" "uint8_t bmRequestType" "uint8_t bRequest" "uint16_t wValue" "uint16_t wIndex" "unsigned char *data" "uint16_t wLength" "unsigned int timeout" Perform a USB control transfer. Returns 0 on success, LIBUSB_ERROR_TIMEOUT if the transfer timeout, LIBUSB_ERROR_PIPE if the control request was not supported, LIBUSB_ERROR_NO_DEVICE if the device has been disconnected and Modified: stable/8/lib/libusb/libusb.h ============================================================================== --- stable/8/lib/libusb/libusb.h Fri Nov 19 20:23:01 2010 (r215545) +++ stable/8/lib/libusb/libusb.h Fri Nov 19 21:04:18 2010 (r215546) @@ -294,6 +294,7 @@ typedef struct libusb_transfer { /* Library initialisation */ void libusb_set_debug(libusb_context * ctx, int level); +const char *libusb_strerror(int code); int libusb_init(libusb_context ** context); void libusb_exit(struct libusb_context *ctx); @@ -317,6 +318,9 @@ int libusb_claim_interface(libusb_device int libusb_release_interface(libusb_device_handle * devh, int interface_number); int libusb_reset_device(libusb_device_handle * devh); int libusb_kernel_driver_active(libusb_device_handle * devh, int interface); +int libusb_get_driver_np(libusb_device_handle * devh, int interface, char *name, int namelen); +int libusb_get_driver(libusb_device_handle * devh, int interface, char *name, int namelen); +int libusb_detach_kernel_driver_np(libusb_device_handle * devh, int interface); int libusb_detach_kernel_driver(libusb_device_handle * devh, int interface); int libusb_attach_kernel_driver(libusb_device_handle * devh, int interface); int libusb_set_interface_alt_setting(libusb_device_handle * devh, int interface_number, int alternate_setting); Modified: stable/8/lib/libusb/libusb10.c ============================================================================== --- stable/8/lib/libusb/libusb10.c Fri Nov 19 20:23:01 2010 (r215545) +++ stable/8/lib/libusb/libusb10.c Fri Nov 19 21:04:18 2010 (r215546) @@ -70,12 +70,30 @@ libusb_set_debug(libusb_context *ctx, in ctx->debug = level; } +static void +libusb_set_nonblocking(int f) +{ + int flags; + + /* + * We ignore any failures in this function, hence the + * non-blocking flag is not critical to the operation of + * libUSB. We use F_GETFL and F_SETFL to be compatible with + * Linux. + */ + + flags = fcntl(f, F_GETFL, NULL); + if (flags == -1) + return; + flags |= O_NONBLOCK; + fcntl(f, F_SETFL, flags); +} + int libusb_init(libusb_context **context) { struct libusb_context *ctx; char *debug; - int flag; int ret; ctx = malloc(sizeof(*ctx)); @@ -106,12 +124,8 @@ libusb_init(libusb_context **context) return (LIBUSB_ERROR_OTHER); } /* set non-blocking mode on the control pipe to avoid deadlock */ - flag = 1; - ret = fcntl(ctx->ctrl_pipe[0], O_NONBLOCK, &flag); - assert(ret != -1 && "Couldn't set O_NONBLOCK for ctx->ctrl_pipe[0]"); - flag = 1; - ret = fcntl(ctx->ctrl_pipe[1], O_NONBLOCK, &flag); - assert(ret != -1 && "Couldn't set O_NONBLOCK for ctx->ctrl_pipe[1]"); + libusb_set_nonblocking(ctx->ctrl_pipe[0]); + libusb_set_nonblocking(ctx->ctrl_pipe[1]); libusb10_add_pollfd(ctx, &ctx->ctx_poll, NULL, ctx->ctrl_pipe[0], POLLIN); @@ -356,7 +370,7 @@ libusb_open(libusb_device *dev, libusb_d /* make sure our event loop detects the new device */ dummy = 0; err = write(ctx->ctrl_pipe[1], &dummy, sizeof(dummy)); - if (err < sizeof(dummy)) { + if (err < (int)sizeof(dummy)) { /* ignore error, if any */ DPRINTF(ctx, LIBUSB_DEBUG_FUNCTION, "libusb_open write failed!"); } @@ -431,7 +445,7 @@ libusb_close(struct libusb20_device *pde /* make sure our event loop detects the closed device */ dummy = 0; err = write(ctx->ctrl_pipe[1], &dummy, sizeof(dummy)); - if (err < sizeof(dummy)) { + if (err < (int)sizeof(dummy)) { /* ignore error, if any */ DPRINTF(ctx, LIBUSB_DEBUG_FUNCTION, "libusb_close write failed!"); } @@ -473,7 +487,6 @@ libusb_set_configuration(struct libusb20 uint8_t i; dev = libusb_get_device(pdev); - if (dev == NULL) return (LIBUSB_ERROR_INVALID_PARAM); @@ -620,6 +633,8 @@ libusb_clear_halt(struct libusb20_device return (LIBUSB_ERROR_INVALID_PARAM); dev = libusb_get_device(pdev); + if (dev == NULL) + return (LIBUSB_ERROR_INVALID_PARAM); CTX_LOCK(dev->ctx); err = libusb20_tr_open(xfer, 0, 0, endpoint); @@ -647,7 +662,7 @@ libusb_reset_device(struct libusb20_devi dev = libusb_get_device(pdev); if (dev == NULL) - return (LIBUSB20_ERROR_INVALID_PARAM); + return (LIBUSB_ERROR_INVALID_PARAM); libusb10_cancel_all_transfer(dev); @@ -673,6 +688,45 @@ libusb_kernel_driver_active(struct libus } int +libusb_get_driver_np(struct libusb20_device *pdev, int interface, + char *name, int namelen) +{ + return (libusb_get_driver(pdev, interface, name, namelen)); +} + +int +libusb_get_driver(struct libusb20_device *pdev, int interface, + char *name, int namelen) +{ + char *ptr; + int err; + + if (pdev == NULL) + return (LIBUSB_ERROR_INVALID_PARAM); + if (namelen < 1) + return (LIBUSB_ERROR_INVALID_PARAM); + + err = libusb20_dev_get_iface_desc( + pdev, interface, name, namelen); + + if (err != 0) + return (LIBUSB_ERROR_OTHER); + + /* we only want the driver name */ + ptr = strstr(name, ":"); + if (ptr != NULL) + *ptr = 0; + + return (0); +} + +int +libusb_detach_kernel_driver_np(struct libusb20_device *pdev, int interface) +{ + return (libusb_detach_kernel_driver(pdev, interface)); +} + +int libusb_detach_kernel_driver(struct libusb20_device *pdev, int interface) { int err; @@ -683,7 +737,7 @@ libusb_detach_kernel_driver(struct libus err = libusb20_dev_detach_kernel_driver( pdev, interface); - return (err ? LIBUSB20_ERROR_OTHER : 0); + return (err ? LIBUSB_ERROR_OTHER : 0); } int @@ -1362,3 +1416,9 @@ libusb_le16_to_cpu(uint16_t x) return (le16toh(x)); } +const char * +libusb_strerror(int code) +{ + /* TODO */ + return ("Unknown error"); +} Modified: stable/8/lib/libusb/libusb20.3 ============================================================================== --- stable/8/lib/libusb/libusb20.3 Fri Nov 19 20:23:01 2010 (r215545) +++ stable/8/lib/libusb/libusb20.3 Fri Nov 19 21:04:18 2010 (r215546) @@ -26,7 +26,7 @@ .\" .\" $FreeBSD$ .\" -.Dd November 18, 2009 +.Dd October 14, 2010 .Dt LIBUSB20 3 .Os .Sh NAME @@ -177,7 +177,7 @@ USB access library (libusb -lusb) .Ft int .Fn libusb20_be_set_template "struct libusb20_backend *pbe" "int temp" .Ft int -.Fn libusb20_be_get_dev_quirk "struct libusb20_backend *pber", "uint16_t index" "struct libusb20_quirk *pq" +.Fn libusb20_be_get_dev_quirk "struct libusb20_backend *pber" "uint16_t index" "struct libusb20_quirk *pq" .Ft int .Fn libusb20_be_get_quirk_name "struct libusb20_backend *pbe" "uint16_t index" "struct libusb20_quirk *pq" .Ft int _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 21:23:35 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E107106566B for ; Fri, 19 Nov 2010 21:23:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 25FA08FC18 for ; Fri, 19 Nov 2010 21:23:35 +0000 (UTC) Received: by pxi1 with SMTP id 1so1201562pxi.13 for ; Fri, 19 Nov 2010 13:23:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=SB0xbqPAlSb67ugqdQvOCSTNCZgPIXerXLvSjt5sYA4=; b=EHBKkLhElyjmLE/FctU2wF9QnaW1+nE/coE1O5Pm8ZP5T5W80z7lELF0zcwQRlAOin qG0R1Fh01FB1c/+0gAZnFwEpi9EqzlqM1soU36RXtJZ5iA0bCxD37ustWeHPjML3QoIq jnPUMxnSO9U7rEkXxRDQTpumXQNYFQzYdNocM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=vwLKNGQYC52LXACSSYf9kG+jXGUhO/tfyBzeHfTQRpX7ne6ySm8E5CpaIYEd+3CVS3 DwhSrwbS8efRIisDTTpPk61J7xIH8kW87sYARFziThNpEGUsR9bMyzIH1x/3y9bC7Jyg kmmuE1T6OaTEG7d8lSbqIZpgIlVL68MrtQkNs= Received: by 10.142.49.21 with SMTP id w21mr2258078wfw.157.1290201814467; Fri, 19 Nov 2010 13:23:34 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id y42sm2347705wfd.22.2010.11.19.13.23.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Nov 2010 13:23:33 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 19 Nov 2010 13:23:33 -0800 From: Pyun YongHyeon Date: Fri, 19 Nov 2010 13:23:33 -0800 To: Nenhum_de_Nos Message-ID: <20101119212333.GD13317@michelle.cdnetworks.com> References: <20101118202426.GB8512@michelle.cdnetworks.com> <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] 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: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 21:23:35 -0000 On Fri, Nov 19, 2010 at 06:23:50PM -0200, Nenhum_de_Nos wrote: [...] > > Ok, try again after downloading new if_axe.c and let me know > > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your > > console. > > never got to see that message. I saw the diff to previous version, and did > boot into verbose mode (dmesg attached). there were just the belkin > gigabit nic on boot. after, the linksys USB200M: > > axe1: on usbus2 > axe1: PHYADDR 0xe0:0x10 > miibus2: on axe1 > ukphy1: PHY 16 on miibus2 > ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 > ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue1: on axe1 > ue1: bpf attached > invalid media SR 0x700 > invalid media SR 0x700 > This is normal, the message I said will show up when you use gigabit controller, AX88178. This controller is fast ethernet controller, AX88772A. > > and the other gigabit: > > ugen2.4: at usbus2 > axe2: on usbus2 > axe2: PHYADDR 0xe0:0x01 > miibus3: on axe2 > truephy1: PHY 1 on miibus3 > truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, > auto > ue2: on axe2 > ue2: bpf attached > ue2: Ethernet address: my mac here > ue2: link state changed to DOWN > > and never got to see the EEPROM message. > Two odd things here. This controller looks like Belkin F5D5055 and it is gigabit controller. So it should print the message I mentioned in previous mail. Are you sure you rebuild/reboot your kernel? The second odd thing is now truephy(4) PHY driver is attached to your controller. Previously it was ukphy(4) generic PHY driver. This means accessing GMII is not reliable such that reading OUI of PHY changed its value. Maybe this could the reason why you see lots of link UP/DOWN messages since mii(4) periodically polls a register through GMII. If the register value read through GMII constantly changes it will cause all sorts of problems. I'm not sure whether this is axe(4) issue or USB stack issue. I also have Belkin F5D5055 controller and has no such problems so I guess it could be related with other parts of USB stack. To easily identify issues for a controller, it would be better to remove all other axe(4) controllers except one you want to test. From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 21:50:00 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 166A91065670 for ; Fri, 19 Nov 2010 21:50:00 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id CBAFA8FC12 for ; Fri, 19 Nov 2010 21:49:59 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id A56311CC3E; Fri, 19 Nov 2010 18:49:57 -0300 (BRT) Received: from 187.114.192.104 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Fri, 19 Nov 2010 19:49:57 -0200 Message-ID: In-Reply-To: <20101119212333.GD13317@michelle.cdnetworks.com> References: <20101118202426.GB8512@michelle.cdnetworks.com> <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> <20101119212333.GD13317@michelle.cdnetworks.com> Date: Fri, 19 Nov 2010 19:49:57 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 21:50:00 -0000 On Fri, November 19, 2010 19:23, Pyun YongHyeon wrote: > On Fri, Nov 19, 2010 at 06:23:50PM -0200, Nenhum_de_Nos wrote: > > [...] > >> > Ok, try again after downloading new if_axe.c and let me know >> > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your >> > console. >> >> never got to see that message. I saw the diff to previous version, and >> did >> boot into verbose mode (dmesg attached). there were just the belkin >> gigabit nic on boot. after, the linksys USB200M: >> >> axe1: on usbus2 >> axe1: PHYADDR 0xe0:0x10 >> miibus2: on axe1 >> ukphy1: PHY 16 on miibus2 >> ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> ue1: on axe1 >> ue1: bpf attached >> invalid media SR 0x700 >> invalid media SR 0x700 >> > > This is normal, the message I said will show up when you use > gigabit controller, AX88178. This controller is fast ethernet > controller, AX88772A. yes, I just tried to show that message with other nic. >> >> and the other gigabit: >> >> ugen2.4: at usbus2 >> axe2: on usbus2 >> axe2: PHYADDR 0xe0:0x01 >> miibus3: on axe2 >> truephy1: PHY 1 on miibus3 >> truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> 1000baseT-FDX, >> auto >> ue2: on axe2 >> ue2: bpf attached >> ue2: Ethernet address: my mac here >> ue2: link state changed to DOWN >> >> and never got to see the EEPROM message. >> > > Two odd things here. This controller looks like Belkin F5D5055 and yes, it's this one. > it is gigabit controller. So it should print the message I > mentioned in previous mail. Are you sure you rebuild/reboot your > kernel? as usual, just rebuilt the axe module ... so I'm going to rebuild now. this is a slow box, and might take a couple of hours. Will try to do it also in a notebook running stable to speedup the process. > The second odd thing is now truephy(4) PHY driver is attached to > your controller. Previously it was ukphy(4) generic PHY driver. > This means accessing GMII is not reliable such that reading OUI of > PHY changed its value. Maybe this could the reason why you see lots > of link UP/DOWN messages since mii(4) periodically polls a register > through GMII. If the register value read through GMII constantly > changes it will cause all sorts of problems. > I'm not sure whether this is axe(4) issue or USB stack issue. I > also have Belkin F5D5055 controller and has no such problems so I > guess it could be related with other parts of USB stack. > > To easily identify issues for a controller, it would be better to > remove all other axe(4) controllers except one you want to test. ok, I was also testing that other issue. Will separate things from now on. no problem using stable from October 7, right ? thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 22:02:52 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB85C106566C for ; Fri, 19 Nov 2010 22:02:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 78FC88FC14 for ; Fri, 19 Nov 2010 22:02:52 +0000 (UTC) Received: by gyg13 with SMTP id 13so3155140gyg.13 for ; Fri, 19 Nov 2010 14:02:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=0IjQ/7OqYAboje2b24aega+kyJ7rVQGgbL/nM5Wd2tA=; b=VRZ4kQNDbdN/m9KmVKTi6F6gaRAuzeyjdPeGl0EMosSB9MOcN0cB3ThP8HbL7G874K aKvYiOexbqQnslrsHcrBO+qPH7Qvb/wOv02jL0SgecJqmmeuTMVXE7hubo/VlqcGR9IM v3r+4IOW+0pOPj6IEE29khTq0ksZi5V+d4AjE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=VhJNiqHI7GIleYvwOJbpR5OQMwoD5bjRMHzZItRw85xXGB7mx9HLGhPwfEnTQrsaeQ qvL6B8Ky4gd2wdzN317rtP7paFyy+YuwHNqc7ZXrtv1bNEDGvRCOJ2bXWme4T7CKmb5R RiB3ZQFQgjV7/RSz7L9B9iySAzx3HnsJnEAsI= Received: by 10.150.230.7 with SMTP id c7mr4349376ybh.446.1290204170909; Fri, 19 Nov 2010 14:02:50 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id j9sm308591yha.45.2010.11.19.14.02.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Nov 2010 14:02:49 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 19 Nov 2010 14:02:48 -0800 From: Pyun YongHyeon Date: Fri, 19 Nov 2010 14:02:48 -0800 To: Nenhum_de_Nos Message-ID: <20101119220248.GG13317@michelle.cdnetworks.com> References: <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> <20101119212333.GD13317@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] 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: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 22:02:52 -0000 On Fri, Nov 19, 2010 at 07:49:57PM -0200, Nenhum_de_Nos wrote: > > On Fri, November 19, 2010 19:23, Pyun YongHyeon wrote: > > On Fri, Nov 19, 2010 at 06:23:50PM -0200, Nenhum_de_Nos wrote: > > > > [...] > > > >> > Ok, try again after downloading new if_axe.c and let me know > >> > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your > >> > console. > >> > >> never got to see that message. I saw the diff to previous version, and > >> did > >> boot into verbose mode (dmesg attached). there were just the belkin > >> gigabit nic on boot. after, the linksys USB200M: > >> > >> axe1: on usbus2 > >> axe1: PHYADDR 0xe0:0x10 > >> miibus2: on axe1 > >> ukphy1: PHY 16 on miibus2 > >> ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 > >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > >> ue1: on axe1 > >> ue1: bpf attached > >> invalid media SR 0x700 > >> invalid media SR 0x700 > >> > > > > This is normal, the message I said will show up when you use > > gigabit controller, AX88178. This controller is fast ethernet > > controller, AX88772A. > > yes, I just tried to show that message with other nic. > > >> > >> and the other gigabit: > >> > >> ugen2.4: at usbus2 > >> axe2: on usbus2 > >> axe2: PHYADDR 0xe0:0x01 > >> miibus3: on axe2 > >> truephy1: PHY 1 on miibus3 > >> truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > >> 1000baseT-FDX, > >> auto > >> ue2: on axe2 > >> ue2: bpf attached > >> ue2: Ethernet address: my mac here > >> ue2: link state changed to DOWN > >> > >> and never got to see the EEPROM message. > >> > > > > Two odd things here. This controller looks like Belkin F5D5055 and > > yes, it's this one. > > > it is gigabit controller. So it should print the message I > > mentioned in previous mail. Are you sure you rebuild/reboot your > > kernel? > > as usual, just rebuilt the axe module ... so I'm going to rebuild now. > this is a slow box, and might take a couple of hours. Will try to do it > also in a notebook running stable to speedup the process. > > > The second odd thing is now truephy(4) PHY driver is attached to > > your controller. Previously it was ukphy(4) generic PHY driver. > > This means accessing GMII is not reliable such that reading OUI of > > PHY changed its value. Maybe this could the reason why you see lots > > of link UP/DOWN messages since mii(4) periodically polls a register > > through GMII. If the register value read through GMII constantly > > changes it will cause all sorts of problems. > > I'm not sure whether this is axe(4) issue or USB stack issue. I > > also have Belkin F5D5055 controller and has no such problems so I > > guess it could be related with other parts of USB stack. > > > > To easily identify issues for a controller, it would be better to > > remove all other axe(4) controllers except one you want to test. > > ok, I was also testing that other issue. Will separate things from now on. > no problem using stable from October 7, right ? > Hmm, that depends on your environments. To test USB issues it would be better to use stable/8. > thanks, > > matheus From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 22:07:36 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84A59106566C for ; Fri, 19 Nov 2010 22:07:36 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id 3A0688FC19 for ; Fri, 19 Nov 2010 22:07:32 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id 6E2111CC3E; Fri, 19 Nov 2010 19:07:29 -0300 (BRT) Received: from 187.114.192.104 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Fri, 19 Nov 2010 20:07:29 -0200 Message-ID: In-Reply-To: <20101119220248.GG13317@michelle.cdnetworks.com> References: <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> <20101119212333.GD13317@michelle.cdnetworks.com> <20101119220248.GG13317@michelle.cdnetworks.com> Date: Fri, 19 Nov 2010 20:07:29 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 22:07:36 -0000 On Fri, November 19, 2010 20:02, Pyun YongHyeon wrote: > On Fri, Nov 19, 2010 at 07:49:57PM -0200, Nenhum_de_Nos wrote: >> >> On Fri, November 19, 2010 19:23, Pyun YongHyeon wrote: >> > On Fri, Nov 19, 2010 at 06:23:50PM -0200, Nenhum_de_Nos wrote: >> > >> > [...] >> > >> >> > Ok, try again after downloading new if_axe.c and let me know >> >> > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your >> >> > console. >> >> >> >> never got to see that message. I saw the diff to previous version, >> and >> >> did >> >> boot into verbose mode (dmesg attached). there were just the belkin >> >> gigabit nic on boot. after, the linksys USB200M: >> >> >> >> axe1: on usbus2 >> >> axe1: PHYADDR 0xe0:0x10 >> >> miibus2: on axe1 >> >> ukphy1: PHY 16 on miibus2 >> >> ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 >> >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> >> ue1: on axe1 >> >> ue1: bpf attached >> >> invalid media SR 0x700 >> >> invalid media SR 0x700 >> >> >> > >> > This is normal, the message I said will show up when you use >> > gigabit controller, AX88178. This controller is fast ethernet >> > controller, AX88772A. >> >> yes, I just tried to show that message with other nic. >> >> >> >> >> and the other gigabit: >> >> >> >> ugen2.4: at usbus2 >> >> axe2: on usbus2 >> >> axe2: PHYADDR 0xe0:0x01 >> >> miibus3: on axe2 >> >> truephy1: PHY 1 on miibus3 >> >> truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> >> 1000baseT-FDX, >> >> auto >> >> ue2: on axe2 >> >> ue2: bpf attached >> >> ue2: Ethernet address: my mac here >> >> ue2: link state changed to DOWN >> >> >> >> and never got to see the EEPROM message. >> >> >> > >> > Two odd things here. This controller looks like Belkin F5D5055 and >> >> yes, it's this one. >> >> > it is gigabit controller. So it should print the message I >> > mentioned in previous mail. Are you sure you rebuild/reboot your >> > kernel? >> >> as usual, just rebuilt the axe module ... so I'm going to rebuild now. >> this is a slow box, and might take a couple of hours. Will try to do it >> also in a notebook running stable to speedup the process. >> >> > The second odd thing is now truephy(4) PHY driver is attached to >> > your controller. Previously it was ukphy(4) generic PHY driver. >> > This means accessing GMII is not reliable such that reading OUI of >> > PHY changed its value. Maybe this could the reason why you see lots >> > of link UP/DOWN messages since mii(4) periodically polls a register >> > through GMII. If the register value read through GMII constantly >> > changes it will cause all sorts of problems. >> > I'm not sure whether this is axe(4) issue or USB stack issue. I >> > also have Belkin F5D5055 controller and has no such problems so I >> > guess it could be related with other parts of USB stack. >> > >> > To easily identify issues for a controller, it would be better to >> > remove all other axe(4) controllers except one you want to test. >> >> ok, I was also testing that other issue. Will separate things from now >> on. >> no problem using stable from October 7, right ? >> > > Hmm, that depends on your environments. To test USB issues it would > be better to use stable/8. both are 8-stable from the beginning of October. As the faster is already compiling things, and it takes 1h max, I'll try this way and can after update to today 8-stable. if anything, just say :) thanks, matheus >> thanks, >> >> matheus > -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 22:30:57 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3F0910657BC for ; Fri, 19 Nov 2010 22:30:57 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id 4F8DD8FC13 for ; Fri, 19 Nov 2010 22:30:57 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id 78DC31CC3E; Fri, 19 Nov 2010 19:30:54 -0300 (BRT) Received: from 187.114.192.104 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Fri, 19 Nov 2010 20:30:54 -0200 Message-ID: <94fe065ccecdaf0f391e17fc07af245a.squirrel@eternamente.info> In-Reply-To: References: <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> <20101119212333.GD13317@michelle.cdnetworks.com> <20101119220248.GG13317@michelle.cdnetworks.com> Date: Fri, 19 Nov 2010 20:30:54 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com, freebsd-usb@freebsd.org User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 22:30:57 -0000 On Fri, November 19, 2010 20:07, Nenhum_de_Nos wrote: > > On Fri, November 19, 2010 20:02, Pyun YongHyeon wrote: >> On Fri, Nov 19, 2010 at 07:49:57PM -0200, Nenhum_de_Nos wrote: >>> >>> On Fri, November 19, 2010 19:23, Pyun YongHyeon wrote: >>> > On Fri, Nov 19, 2010 at 06:23:50PM -0200, Nenhum_de_Nos wrote: >>> > >>> > [...] >>> > >>> >> > Ok, try again after downloading new if_axe.c and let me know >>> >> > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your >>> >> > console. >>> >> >>> >> never got to see that message. I saw the diff to previous version, >>> and >>> >> did >>> >> boot into verbose mode (dmesg attached). there were just the belkin >>> >> gigabit nic on boot. after, the linksys USB200M: >>> >> >>> >> axe1: on >>> usbus2 >>> >> axe1: PHYADDR 0xe0:0x10 >>> >> miibus2: on axe1 >>> >> ukphy1: PHY 16 on miibus2 >>> >> ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 >>> >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >>> >> ue1: on axe1 >>> >> ue1: bpf attached >>> >> invalid media SR 0x700 >>> >> invalid media SR 0x700 >>> >> >>> > >>> > This is normal, the message I said will show up when you use >>> > gigabit controller, AX88178. This controller is fast ethernet >>> > controller, AX88772A. >>> >>> yes, I just tried to show that message with other nic. >>> >>> >> >>> >> and the other gigabit: >>> >> >>> >> ugen2.4: at usbus2 >>> >> axe2: on >>> usbus2 >>> >> axe2: PHYADDR 0xe0:0x01 >>> >> miibus3: on axe2 >>> >> truephy1: PHY 1 on miibus3 >>> >> truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >>> >> 1000baseT-FDX, >>> >> auto >>> >> ue2: on axe2 >>> >> ue2: bpf attached >>> >> ue2: Ethernet address: my mac here >>> >> ue2: link state changed to DOWN >>> >> >>> >> and never got to see the EEPROM message. >>> >> >>> > >>> > Two odd things here. This controller looks like Belkin F5D5055 and >>> >>> yes, it's this one. >>> >>> > it is gigabit controller. So it should print the message I >>> > mentioned in previous mail. Are you sure you rebuild/reboot your >>> > kernel? >>> >>> as usual, just rebuilt the axe module ... so I'm going to rebuild now. >>> this is a slow box, and might take a couple of hours. Will try to do it >>> also in a notebook running stable to speedup the process. >>> >>> > The second odd thing is now truephy(4) PHY driver is attached to >>> > your controller. Previously it was ukphy(4) generic PHY driver. >>> > This means accessing GMII is not reliable such that reading OUI of >>> > PHY changed its value. Maybe this could the reason why you see lots >>> > of link UP/DOWN messages since mii(4) periodically polls a register >>> > through GMII. If the register value read through GMII constantly >>> > changes it will cause all sorts of problems. >>> > I'm not sure whether this is axe(4) issue or USB stack issue. I >>> > also have Belkin F5D5055 controller and has no such problems so I >>> > guess it could be related with other parts of USB stack. >>> > >>> > To easily identify issues for a controller, it would be better to >>> > remove all other axe(4) controllers except one you want to test. >>> >>> ok, I was also testing that other issue. Will separate things from now >>> on. >>> no problem using stable from October 7, right ? >>> >> >> Hmm, that depends on your environments. To test USB issues it would >> be better to use stable/8. > > both are 8-stable from the beginning of October. As the faster is already > compiling things, and it takes 1h max, I'll try this way and can after > update to today 8-stable. > > if anything, just say :) > > thanks, > > matheus > >>> thanks, >>> >>> matheus here: ugen0.2: at usbus0 wlan0: Ethernet address: a mac here fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 ugen1.3: at usbus1 axe0: on usbus1 axe0: EEPROM data : 0x0a82, phymode : 02 axe0: MII without any PHY wlan0: link state changed to UP wlan0: link state changed to DOWN wlan0: link state changed to UP ugen1.3: at usbus1 (disconnected) axe0: at uhub1, port 3, addr 3 (disconnected) ugen1.3: at usbus1 axe0: on usbus1 axe0: EEPROM data : 0x0a82, phymode : 02 miibus1: on axe0 ukphy0: PHY 1 on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto ue0: on axe0 ue0: Ethernet address: a mac here ue0: link state changed to DOWN both belkin, each one at a time. will sync world and kernel and make {kernel,world} thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 22:44:26 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3017106564A for ; Fri, 19 Nov 2010 22:44:26 +0000 (UTC) (envelope-from george@m5p.com) Received: from mailhost.m5p.com (unknown [IPv6:2001:418:3fd::3]) by mx1.freebsd.org (Postfix) with ESMTP id 8271E8FC15 for ; Fri, 19 Nov 2010 22:44:26 +0000 (UTC) Received: from m5p.com (wonderland.m5p.com [IPv6:2001:418:3fd::19]) by mailhost.m5p.com (8.14.3/8.14.3) with ESMTP id oAJMiKHL006413 for ; Fri, 19 Nov 2010 17:44:25 -0500 (EST) (envelope-from george@m5p.com) Received: (from george@localhost) by m5p.com (8.14.4/8.13.7/Submit) id oAJMiKl1001393; Fri, 19 Nov 2010 17:44:20 -0500 (EST) Date: Fri, 19 Nov 2010 17:44:20 -0500 (EST) Message-Id: <201011192244.oAJMiKl1001393@m5p.com> From: george+freebsd@m5p.com To: freebsd-usb@freebsd.org X-Spam-Score: -1.5 () BAYES_00 X-Scanned-By: MIMEDefang 2.67 on IPv6:2001:418:3fd::f7 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Fri, 19 Nov 2010 17:44:25 -0500 (EST) Subject: FreeBSD + pilot-link + USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 22:44:27 -0000 Does anybody here know how to use pilot-link on FreeBSD with a Zire 21 over USB? It appears that usb_scan_devices never finds my device. Thanks for any guidance you can give me. -- George Mitchell From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 23:53:33 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71ADA1065670 for ; Fri, 19 Nov 2010 23:53:33 +0000 (UTC) (envelope-from roam@ringlet.net) Received: from erengrad.hoster.bg (erengrad.hoster.bg [77.77.142.9]) by mx1.freebsd.org (Postfix) with ESMTP id DF55B8FC0A for ; Fri, 19 Nov 2010 23:53:32 +0000 (UTC) Received: from middenheim.hoster.bg (middenheim.hoster.bg [77.77.142.11]) by erengrad.hoster.bg (Postfix) with ESMTP id 678BCDC347 for ; Sat, 20 Nov 2010 01:22:00 +0200 (EET) Received: from straylight.ringlet.net (93-152-170-58.ddns.onlinedirect.bg [93.152.170.58]) (Authenticated sender: roam@hoster.bg) by mail.hoster.bg (Postfix) with ESMTP id 1F8615C2EB for ; Sat, 20 Nov 2010 01:21:57 +0200 (EET) Received: from roam (uid 1000) (envelope-from roam@ringlet.net) id 416009 by straylight.ringlet.net (DragonFly Mail Agent) Sat, 20 Nov 2010 01:21:57 +0200 Date: Sat, 20 Nov 2010 01:21:57 +0200 From: Peter Pentchev To: Matthias Apitz Message-ID: <20101119232157.GB4198@straylight.ringlet.net> References: <20101119143337.GA3023@current.Sisis.de> <201011191537.25867.hselasky@c2i.net> <20101119170259.GA3741@current.Sisis.de> <201011191821.09308.hselasky@c2i.net> <20101119173519.GA3933@current.Sisis.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zx4FCpZtqtKETZ7O" Content-Disposition: inline In-Reply-To: <20101119173519.GA3933@current.Sisis.de> User-Agent: Mutt/1.5.20 (2009-06-14) X-MailScanner-ID: 1F8615C2EB.E4AAB X-hoster-MailScanner: Found to be clean X-hoster-MailScanner-SpamCheck: not spam, SpamAssassin (cached, score=0.001, required 10, autolearn=disabled, UNPARSEABLE_RELAY 0.00) X-hoster-MailScanner-From: roam@ringlet.net X-hoster-MailScanner-To: freebsd-usb@freebsd.org X-Spam-Status: No Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 23:53:33 -0000 --zx4FCpZtqtKETZ7O Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 19, 2010 at 06:35:19PM +0100, Matthias Apitz wrote: > El d=C3=ADa Friday, November 19, 2010 a las 06:21:09PM +0100, Hans Petter= Selasky escribi=C3=B3: >=20 > > > > Can you dump the data into hex using hexdump -C and show us the > > > > difference. > > >=20 > > > Note: the output of the dd(1) is around 3.8 GByte. I compared the 1st > > > 2.000.000 lines of the hexdump: no diff; any better tool to show the = 1st > > > block which differs? > > >=20 > > > > Usually you would use bs=3D65536 (Does that change anything)? > > >=20 > > > Same result: they differ :-( > > >=20 > > > matthias > >=20 > > bsdiff ? >=20 > This will not work with such big files (requires 8x memory of the file): >=20 > I was thinking in a tool just reading each file block by block, > comparing the blocks and noting the 1st diff with block offset number. > (some 10 lines of C code :-)) Errrr... are you thinking of cmp(1), maybe with the -l option? :) G'luck, Peter --=20 Peter Pentchev roam@space.bg roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 When you are not looking at it, this sentence is in Spanish. --zx4FCpZtqtKETZ7O Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJM5waUAAoJEGUe77AlJ98TRdYQAJWkNqv6MUfbOGUPtG8wqilA AuE+GbNWIzA14wz+wMdHFLkFb6+HdM10Bxsrnnki7MyZf5IbTUeAazfiYMpcpolc BbKYp6cGvwKnxDGJSIggVQZaDVdENa9HZPvhljkc5G9gYVawYpy2KH7CAzaMr/V7 mXpXPWp5Ko58Jf0EZ7Q/CJkhBesYzoaJq2Io0ru3FZKZCIjhmCDDgu2jWaKcv+0F itjkBHpjdQeBwXVwa31y60mMwOBzjVX3eeLbJtGkvcvdVs2MfLdlKtSiHUxsT0Ok S+LNsnxH+UEUmlH2dqB8cgYLNu/FyR/cMRvcRiT6Y+hkeeNgdlA7eW3kDBzynX1L Gp8KX8jsw/J5BJy6PeccYe6OUzHZ9OaTFjQ35mLWK0NPmTpg7Nls1HPU/xdnm0h6 X0fc8vEIziWSBWjeJNrarWDKdGixulaYHLgc2oX0BLzkjRPdxYYFHhmOqKSQnEku pdUIQ1Py7xhDUniScJhz+wrNgOip8sosd5iHuC3cWsVFLNq8wEHoi2GzignZayK3 9Vy8LJVZ4IYe04lIvHZBbUx5rXlRm3QcgSKUNFWqTV0Oq71LVdjWsNnF6ToG1S9U QAnjsdyXZFXPcR5W4H7hup0gkOTk1qDVGqQA2uWMhq0XvdDk0r2cI1whaB+j3/7X 72siOu4wTdU2ktD6JXl6 =izP8 -----END PGP SIGNATURE----- --zx4FCpZtqtKETZ7O-- From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 00:43:04 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F2F1106564A for ; Sat, 20 Nov 2010 00:43:04 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id DF84C8FC13 for ; Sat, 20 Nov 2010 00:43:03 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id oAK0gvfm097017; Fri, 19 Nov 2010 17:42:57 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id oAK0gvQ0097014; Fri, 19 Nov 2010 17:42:57 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 19 Nov 2010 17:42:57 -0700 (MST) From: Warren Block To: Matthias Apitz In-Reply-To: <20101119204639.GA1521@tiny.Sisis.de> Message-ID: References: <20101119143337.GA3023@current.Sisis.de> <201011191821.09308.hselasky@c2i.net> <20101119173519.GA3933@current.Sisis.de> <201011191916.53655.hselasky@c2i.net> <20101119183900.GA1221@tiny.Sisis.de> <20101119204639.GA1521@tiny.Sisis.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (wonkity.com [127.0.0.1]); Fri, 19 Nov 2010 17:42:58 -0700 (MST) Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 00:43:04 -0000 On Fri, 19 Nov 2010, Matthias Apitz wrote: > El d?a Friday, November 19, 2010 a las 12:39:13PM -0700, Warren Block escribi?: > >>> Should I overwrite the full USB key from /dev/zero? >> >> Possibly there would still be differences. Filesystem metadata like >> date last mounted, for example. If you want a block-by-block duplicate, >> the brute-force method is to just dd the whole drive. Use bs=64k or >> bs=1m to help reduce overhead. > > Warren, perhaps you missed my point. I have a prepared boot-able key and > I want to give away a copy of it as a file on DVD. So I dd(1)'ed the key > to disk and did this twice to ensure that the copy was fine, but the two > files differ. How can I make sure that the file on disk (or DVD) is a > exact copy of the key? Okay, that makes more sense. Did you mount the key in between the two times it was dd-ed? From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 00:52:24 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E751106564A for ; Sat, 20 Nov 2010 00:52:24 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 450368FC1C for ; Sat, 20 Nov 2010 00:52:23 +0000 (UTC) Received: by pzk1 with SMTP id 1so1055050pzk.13 for ; Fri, 19 Nov 2010 16:52:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=bfmbbOIFmSnK1gNcsqp+cdOHj2jMBALdkL1BSr768pA=; b=dq8ErpWFMi/XxtJ0KDqDGHZdL0HZyjLeBYsHM5yJHnEZeOtqB1ZGKaWMEmQ/7acrlk /aIk+N4rr1gGgKiclWoJZdQ5AKZBpP58xcmNLT1s+7oBCXgO7BCrGhxYaHtd3bXie2cf ypJD4pGFFAxp3Lo3yAZ5LJ0wiVdYE9ZnF1vTU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=BF0Dypk8AULcXqa8AjkhIANPY1NW+gSW8IAj2BikQMYjFUgbRiWGsjkCzqk5jDAJgI Evfj0RxdEP/iMiLSKlPTJmEDhTnnO9ox9gAu359SnOqsvgk3U+2eCDtgTL7s/GNOCuWW 47l7Brp1qTe6alZGdCudO7LCY9MrgrWAj/qdo= Received: by 10.142.11.4 with SMTP id 4mr2437683wfk.181.1290214343629; Fri, 19 Nov 2010 16:52:23 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id w14sm2544672wfd.6.2010.11.19.16.52.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Nov 2010 16:52:22 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 19 Nov 2010 16:52:22 -0800 From: Pyun YongHyeon Date: Fri, 19 Nov 2010 16:52:22 -0800 To: Nenhum_de_Nos Message-ID: <20101120005222.GJ13317@michelle.cdnetworks.com> References: <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> <20101119212333.GD13317@michelle.cdnetworks.com> <20101119220248.GG13317@michelle.cdnetworks.com> <94fe065ccecdaf0f391e17fc07af245a.squirrel@eternamente.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <94fe065ccecdaf0f391e17fc07af245a.squirrel@eternamente.info> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] 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: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 00:52:24 -0000 On Fri, Nov 19, 2010 at 08:30:54PM -0200, Nenhum_de_Nos wrote: > > On Fri, November 19, 2010 20:07, Nenhum_de_Nos wrote: > > > > On Fri, November 19, 2010 20:02, Pyun YongHyeon wrote: > >> On Fri, Nov 19, 2010 at 07:49:57PM -0200, Nenhum_de_Nos wrote: > >>> > >>> On Fri, November 19, 2010 19:23, Pyun YongHyeon wrote: > >>> > On Fri, Nov 19, 2010 at 06:23:50PM -0200, Nenhum_de_Nos wrote: > >>> > > >>> > [...] > >>> > > >>> >> > Ok, try again after downloading new if_axe.c and let me know > >>> >> > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your > >>> >> > console. > >>> >> > >>> >> never got to see that message. I saw the diff to previous version, > >>> and > >>> >> did > >>> >> boot into verbose mode (dmesg attached). there were just the belkin > >>> >> gigabit nic on boot. after, the linksys USB200M: > >>> >> > >>> >> axe1: on > >>> usbus2 > >>> >> axe1: PHYADDR 0xe0:0x10 > >>> >> miibus2: on axe1 > >>> >> ukphy1: PHY 16 on miibus2 > >>> >> ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 > >>> >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > >>> >> ue1: on axe1 > >>> >> ue1: bpf attached > >>> >> invalid media SR 0x700 > >>> >> invalid media SR 0x700 > >>> >> > >>> > > >>> > This is normal, the message I said will show up when you use > >>> > gigabit controller, AX88178. This controller is fast ethernet > >>> > controller, AX88772A. > >>> > >>> yes, I just tried to show that message with other nic. > >>> > >>> >> > >>> >> and the other gigabit: > >>> >> > >>> >> ugen2.4: at usbus2 > >>> >> axe2: on > >>> usbus2 > >>> >> axe2: PHYADDR 0xe0:0x01 > >>> >> miibus3: on axe2 > >>> >> truephy1: PHY 1 on miibus3 > >>> >> truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > >>> >> 1000baseT-FDX, > >>> >> auto > >>> >> ue2: on axe2 > >>> >> ue2: bpf attached > >>> >> ue2: Ethernet address: my mac here > >>> >> ue2: link state changed to DOWN > >>> >> > >>> >> and never got to see the EEPROM message. > >>> >> > >>> > > >>> > Two odd things here. This controller looks like Belkin F5D5055 and > >>> > >>> yes, it's this one. > >>> > >>> > it is gigabit controller. So it should print the message I > >>> > mentioned in previous mail. Are you sure you rebuild/reboot your > >>> > kernel? > >>> > >>> as usual, just rebuilt the axe module ... so I'm going to rebuild now. > >>> this is a slow box, and might take a couple of hours. Will try to do it > >>> also in a notebook running stable to speedup the process. > >>> > >>> > The second odd thing is now truephy(4) PHY driver is attached to > >>> > your controller. Previously it was ukphy(4) generic PHY driver. > >>> > This means accessing GMII is not reliable such that reading OUI of > >>> > PHY changed its value. Maybe this could the reason why you see lots > >>> > of link UP/DOWN messages since mii(4) periodically polls a register > >>> > through GMII. If the register value read through GMII constantly > >>> > changes it will cause all sorts of problems. > >>> > I'm not sure whether this is axe(4) issue or USB stack issue. I > >>> > also have Belkin F5D5055 controller and has no such problems so I > >>> > guess it could be related with other parts of USB stack. > >>> > > >>> > To easily identify issues for a controller, it would be better to > >>> > remove all other axe(4) controllers except one you want to test. > >>> > >>> ok, I was also testing that other issue. Will separate things from now > >>> on. > >>> no problem using stable from October 7, right ? > >>> > >> > >> Hmm, that depends on your environments. To test USB issues it would > >> be better to use stable/8. > > > > both are 8-stable from the beginning of October. As the faster is already > > compiling things, and it takes 1h max, I'll try this way and can after > > update to today 8-stable. > > > > if anything, just say :) > > > > thanks, > > > > matheus > > > >>> thanks, > >>> > >>> matheus > > here: > > ugen0.2: at usbus0 > wlan0: Ethernet address: a mac here > fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 > ugen1.3: at usbus1 > axe0: on usbus1 > axe0: EEPROM data : 0x0a82, phymode : 02 > axe0: MII without any PHY > wlan0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > ugen1.3: at usbus1 (disconnected) > axe0: at uhub1, port 3, addr 3 (disconnected) > ugen1.3: at usbus1 > axe0: on usbus1 > axe0: EEPROM data : 0x0a82, phymode : 02 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Thanks. It's big hint. I uploaded updated if_axe.c Let me know it makes any difference. > miibus1: on axe0 > ukphy0: PHY 1 on miibus1 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > ue0: on axe0 > ue0: Ethernet address: a mac here > ue0: link state changed to DOWN > > both belkin, each one at a time. > > will sync world and kernel and make {kernel,world} > > thanks, > > matheus From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 01:20:32 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A79211065670 for ; Sat, 20 Nov 2010 01:20:32 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id 6B43F8FC08 for ; Sat, 20 Nov 2010 01:20:32 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id 52F871CC3E; Fri, 19 Nov 2010 22:20:25 -0300 (BRT) Received: from 187.114.192.104 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Fri, 19 Nov 2010 23:20:25 -0200 Message-ID: <4a747b33d267e46f379607979ad57158.squirrel@eternamente.info> In-Reply-To: <20101120005222.GJ13317@michelle.cdnetworks.com> References: <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> <20101119212333.GD13317@michelle.cdnetworks.com> <20101119220248.GG13317@michelle.cdnetworks.com> <94fe065ccecdaf0f391e17fc07af245a.squirrel@eternamente.info> <20101120005222.GJ13317@michelle.cdnetworks.com> Date: Fri, 19 Nov 2010 23:20:25 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 01:20:32 -0000 On Fri, November 19, 2010 22:52, Pyun YongHyeon wrote: > On Fri, Nov 19, 2010 at 08:30:54PM -0200, Nenhum_de_Nos wrote: >> >> On Fri, November 19, 2010 20:07, Nenhum_de_Nos wrote: >> > >> > On Fri, November 19, 2010 20:02, Pyun YongHyeon wrote: >> >> On Fri, Nov 19, 2010 at 07:49:57PM -0200, Nenhum_de_Nos wrote: >> >>> >> >>> On Fri, November 19, 2010 19:23, Pyun YongHyeon wrote: >> >>> > On Fri, Nov 19, 2010 at 06:23:50PM -0200, Nenhum_de_Nos wrote: >> >>> > >> >>> > [...] >> >>> > >> >>> >> > Ok, try again after downloading new if_axe.c and let me know >> >>> >> > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your >> >>> >> > console. >> >>> >> >> >>> >> never got to see that message. I saw the diff to previous >> version, >> >>> and >> >>> >> did >> >>> >> boot into verbose mode (dmesg attached). there were just the >> belkin >> >>> >> gigabit nic on boot. after, the linksys USB200M: >> >>> >> >> >>> >> axe1: on >> >>> usbus2 >> >>> >> axe1: PHYADDR 0xe0:0x10 >> >>> >> miibus2: on axe1 >> >>> >> ukphy1: PHY 16 on miibus2 >> >>> >> ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 >> >>> >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> >>> >> ue1: on axe1 >> >>> >> ue1: bpf attached >> >>> >> invalid media SR 0x700 >> >>> >> invalid media SR 0x700 >> >>> >> >> >>> > >> >>> > This is normal, the message I said will show up when you use >> >>> > gigabit controller, AX88178. This controller is fast ethernet >> >>> > controller, AX88772A. >> >>> >> >>> yes, I just tried to show that message with other nic. >> >>> >> >>> >> >> >>> >> and the other gigabit: >> >>> >> >> >>> >> ugen2.4: at usbus2 >> >>> >> axe2: on >> >>> usbus2 >> >>> >> axe2: PHYADDR 0xe0:0x01 >> >>> >> miibus3: on axe2 >> >>> >> truephy1: PHY 1 on miibus3 >> >>> >> truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> >>> >> 1000baseT-FDX, >> >>> >> auto >> >>> >> ue2: on axe2 >> >>> >> ue2: bpf attached >> >>> >> ue2: Ethernet address: my mac here >> >>> >> ue2: link state changed to DOWN >> >>> >> >> >>> >> and never got to see the EEPROM message. >> >>> >> >> >>> > >> >>> > Two odd things here. This controller looks like Belkin F5D5055 and >> >>> >> >>> yes, it's this one. >> >>> >> >>> > it is gigabit controller. So it should print the message I >> >>> > mentioned in previous mail. Are you sure you rebuild/reboot your >> >>> > kernel? >> >>> >> >>> as usual, just rebuilt the axe module ... so I'm going to rebuild >> now. >> >>> this is a slow box, and might take a couple of hours. Will try to do >> it >> >>> also in a notebook running stable to speedup the process. >> >>> >> >>> > The second odd thing is now truephy(4) PHY driver is attached to >> >>> > your controller. Previously it was ukphy(4) generic PHY driver. >> >>> > This means accessing GMII is not reliable such that reading OUI of >> >>> > PHY changed its value. Maybe this could the reason why you see >> lots >> >>> > of link UP/DOWN messages since mii(4) periodically polls a >> register >> >>> > through GMII. If the register value read through GMII constantly >> >>> > changes it will cause all sorts of problems. >> >>> > I'm not sure whether this is axe(4) issue or USB stack issue. I >> >>> > also have Belkin F5D5055 controller and has no such problems so I >> >>> > guess it could be related with other parts of USB stack. >> >>> > >> >>> > To easily identify issues for a controller, it would be better to >> >>> > remove all other axe(4) controllers except one you want to test. >> >>> >> >>> ok, I was also testing that other issue. Will separate things from >> now >> >>> on. >> >>> no problem using stable from October 7, right ? >> >>> >> >> >> >> Hmm, that depends on your environments. To test USB issues it would >> >> be better to use stable/8. >> > >> > both are 8-stable from the beginning of October. As the faster is >> already >> > compiling things, and it takes 1h max, I'll try this way and can after >> > update to today 8-stable. >> > >> > if anything, just say :) >> > >> > thanks, >> > >> > matheus >> > >> >>> thanks, >> >>> >> >>> matheus >> >> here: >> >> ugen0.2: at usbus0 >> wlan0: Ethernet address: a mac here >> fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 >> ugen1.3: at usbus1 >> axe0: on usbus1 >> axe0: EEPROM data : 0x0a82, phymode : 02 >> axe0: MII without any PHY >> wlan0: link state changed to UP >> wlan0: link state changed to DOWN >> wlan0: link state changed to UP >> ugen1.3: at usbus1 (disconnected) >> axe0: at uhub1, port 3, addr 3 (disconnected) >> ugen1.3: at usbus1 >> axe0: on usbus1 >> axe0: EEPROM data : 0x0a82, phymode : 02 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Thanks. It's big hint. I uploaded updated if_axe.c > Let me know it makes any difference. need to recompile kernel, or just if_axe ? will do this asap. matheus >> miibus1: on axe0 >> ukphy0: PHY 1 on miibus1 >> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> 1000baseT-FDX, auto >> ue0: on axe0 >> ue0: Ethernet address: a mac here >> ue0: link state changed to DOWN >> >> both belkin, each one at a time. >> >> will sync world and kernel and make {kernel,world} >> >> thanks, >> >> matheus > -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 01:24:58 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1200D106566B for ; Sat, 20 Nov 2010 01:24:58 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id B286D8FC19 for ; Sat, 20 Nov 2010 01:24:57 +0000 (UTC) Received: by yxh35 with SMTP id 35so3212992yxh.13 for ; Fri, 19 Nov 2010 17:24:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=CAh+GtsxPLaXVBHE9N3KjDRvzZE1hxQ1ybpThe3LA3g=; b=Y0YV3ZZazZkBd9eKsXoO1WulT4d3TMmIq4EYZxSsYDq3Cr2Rf2VlndbJKGXlg/OE5x TtTEbulqlQ1PjP2+ee5yH+g4Qa7HkhH6kDxny95tR99v+WiHAMMXZixLCulw2VIwm0EL 9giwFY+d7HMoy6z0njTAljvDYwpz633LYGWSU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Jyy17RzwcKWqO5uuCxNOF1wXLRJMABHfhuHiFAp8cV3NP0UALmG8AJXphgwqXRJQaZ 4/7Fp1nvYovUUCpfEl33TH2WzWc/QRyhAmSNO6algoZCnKNepF22s7AMyjyFJBm4HNEt G8IOEW+qe43p09yqt//LLYtLAnVwmw8ZVnqpE= Received: by 10.151.154.19 with SMTP id g19mr4436396ybo.327.1290216296691; Fri, 19 Nov 2010 17:24:56 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id k2sm210877ybj.20.2010.11.19.17.24.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Nov 2010 17:24:55 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 19 Nov 2010 17:24:55 -0800 From: Pyun YongHyeon Date: Fri, 19 Nov 2010 17:24:55 -0800 To: Nenhum_de_Nos Message-ID: <20101120012455.GK13317@michelle.cdnetworks.com> References: <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> <20101119212333.GD13317@michelle.cdnetworks.com> <20101119220248.GG13317@michelle.cdnetworks.com> <94fe065ccecdaf0f391e17fc07af245a.squirrel@eternamente.info> <20101120005222.GJ13317@michelle.cdnetworks.com> <4a747b33d267e46f379607979ad57158.squirrel@eternamente.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4a747b33d267e46f379607979ad57158.squirrel@eternamente.info> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] 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: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 01:24:58 -0000 On Fri, Nov 19, 2010 at 11:20:25PM -0200, Nenhum_de_Nos wrote: > > On Fri, November 19, 2010 22:52, Pyun YongHyeon wrote: > > On Fri, Nov 19, 2010 at 08:30:54PM -0200, Nenhum_de_Nos wrote: > >> > >> On Fri, November 19, 2010 20:07, Nenhum_de_Nos wrote: > >> > > >> > On Fri, November 19, 2010 20:02, Pyun YongHyeon wrote: > >> >> On Fri, Nov 19, 2010 at 07:49:57PM -0200, Nenhum_de_Nos wrote: > >> >>> > >> >>> On Fri, November 19, 2010 19:23, Pyun YongHyeon wrote: > >> >>> > On Fri, Nov 19, 2010 at 06:23:50PM -0200, Nenhum_de_Nos wrote: > >> >>> > > >> >>> > [...] > >> >>> > > >> >>> >> > Ok, try again after downloading new if_axe.c and let me know > >> >>> >> > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your > >> >>> >> > console. > >> >>> >> > >> >>> >> never got to see that message. I saw the diff to previous > >> version, > >> >>> and > >> >>> >> did > >> >>> >> boot into verbose mode (dmesg attached). there were just the > >> belkin > >> >>> >> gigabit nic on boot. after, the linksys USB200M: > >> >>> >> > >> >>> >> axe1: on > >> >>> usbus2 > >> >>> >> axe1: PHYADDR 0xe0:0x10 > >> >>> >> miibus2: on axe1 > >> >>> >> ukphy1: PHY 16 on miibus2 > >> >>> >> ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 > >> >>> >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > >> >>> >> ue1: on axe1 > >> >>> >> ue1: bpf attached > >> >>> >> invalid media SR 0x700 > >> >>> >> invalid media SR 0x700 > >> >>> >> > >> >>> > > >> >>> > This is normal, the message I said will show up when you use > >> >>> > gigabit controller, AX88178. This controller is fast ethernet > >> >>> > controller, AX88772A. > >> >>> > >> >>> yes, I just tried to show that message with other nic. > >> >>> > >> >>> >> > >> >>> >> and the other gigabit: > >> >>> >> > >> >>> >> ugen2.4: at usbus2 > >> >>> >> axe2: on > >> >>> usbus2 > >> >>> >> axe2: PHYADDR 0xe0:0x01 > >> >>> >> miibus3: on axe2 > >> >>> >> truephy1: PHY 1 on miibus3 > >> >>> >> truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > >> >>> >> 1000baseT-FDX, > >> >>> >> auto > >> >>> >> ue2: on axe2 > >> >>> >> ue2: bpf attached > >> >>> >> ue2: Ethernet address: my mac here > >> >>> >> ue2: link state changed to DOWN > >> >>> >> > >> >>> >> and never got to see the EEPROM message. > >> >>> >> > >> >>> > > >> >>> > Two odd things here. This controller looks like Belkin F5D5055 and > >> >>> > >> >>> yes, it's this one. > >> >>> > >> >>> > it is gigabit controller. So it should print the message I > >> >>> > mentioned in previous mail. Are you sure you rebuild/reboot your > >> >>> > kernel? > >> >>> > >> >>> as usual, just rebuilt the axe module ... so I'm going to rebuild > >> now. > >> >>> this is a slow box, and might take a couple of hours. Will try to do > >> it > >> >>> also in a notebook running stable to speedup the process. > >> >>> > >> >>> > The second odd thing is now truephy(4) PHY driver is attached to > >> >>> > your controller. Previously it was ukphy(4) generic PHY driver. > >> >>> > This means accessing GMII is not reliable such that reading OUI of > >> >>> > PHY changed its value. Maybe this could the reason why you see > >> lots > >> >>> > of link UP/DOWN messages since mii(4) periodically polls a > >> register > >> >>> > through GMII. If the register value read through GMII constantly > >> >>> > changes it will cause all sorts of problems. > >> >>> > I'm not sure whether this is axe(4) issue or USB stack issue. I > >> >>> > also have Belkin F5D5055 controller and has no such problems so I > >> >>> > guess it could be related with other parts of USB stack. > >> >>> > > >> >>> > To easily identify issues for a controller, it would be better to > >> >>> > remove all other axe(4) controllers except one you want to test. > >> >>> > >> >>> ok, I was also testing that other issue. Will separate things from > >> now > >> >>> on. > >> >>> no problem using stable from October 7, right ? > >> >>> > >> >> > >> >> Hmm, that depends on your environments. To test USB issues it would > >> >> be better to use stable/8. > >> > > >> > both are 8-stable from the beginning of October. As the faster is > >> already > >> > compiling things, and it takes 1h max, I'll try this way and can after > >> > update to today 8-stable. > >> > > >> > if anything, just say :) > >> > > >> > thanks, > >> > > >> > matheus > >> > > >> >>> thanks, > >> >>> > >> >>> matheus > >> > >> here: > >> > >> ugen0.2: at usbus0 > >> wlan0: Ethernet address: a mac here > >> fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 > >> ugen1.3: at usbus1 > >> axe0: on usbus1 > >> axe0: EEPROM data : 0x0a82, phymode : 02 > >> axe0: MII without any PHY > >> wlan0: link state changed to UP > >> wlan0: link state changed to DOWN > >> wlan0: link state changed to UP > >> ugen1.3: at usbus1 (disconnected) > >> axe0: at uhub1, port 3, addr 3 (disconnected) > >> ugen1.3: at usbus1 > >> axe0: on usbus1 > >> axe0: EEPROM data : 0x0a82, phymode : 02 > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Thanks. It's big hint. I uploaded updated if_axe.c > > Let me know it makes any difference. > > need to recompile kernel, or just if_axe ? > If you used if_axe module without "device axe" in kernel configuration(i.e. kernel does not include axe(4) driver), rebuilding/reloading if_axe should be enough. Otherwise, you have to rebuild kernel and reboot. > will do this asap. > > matheus > > >> miibus1: on axe0 > >> ukphy0: PHY 1 on miibus1 > >> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > >> 1000baseT-FDX, auto > >> ue0: on axe0 > >> ue0: Ethernet address: a mac here > >> ue0: link state changed to DOWN > >> > >> both belkin, each one at a time. > >> > >> will sync world and kernel and make {kernel,world} > >> > >> thanks, From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 05:37:53 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C8C41065672 for ; Sat, 20 Nov 2010 05:37:53 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id 4D2168FC18 for ; Sat, 20 Nov 2010 05:37:52 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id 90D3A1CC3E; Sat, 20 Nov 2010 02:37:48 -0300 (BRT) Received: from 187.114.192.104 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Sat, 20 Nov 2010 03:37:48 -0200 Message-ID: <2e6af51d55d458ce6ab55e921741a2de.squirrel@eternamente.info> In-Reply-To: <20101120012455.GK13317@michelle.cdnetworks.com> References: <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> <20101119212333.GD13317@michelle.cdnetworks.com> <20101119220248.GG13317@michelle.cdnetworks.com> <94fe065ccecdaf0f391e17fc07af245a.squirrel@eternamente.info> <20101120005222.GJ13317@michelle.cdnetworks.com> <4a747b33d267e46f379607979ad57158.squirrel@eternamente.info> <20101120012455.GK13317@michelle.cdnetworks.com> Date: Sat, 20 Nov 2010 03:37:48 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 05:37:53 -0000 On Fri, November 19, 2010 23:24, Pyun YongHyeon wrote: > On Fri, Nov 19, 2010 at 11:20:25PM -0200, Nenhum_de_Nos wrote: >> >> On Fri, November 19, 2010 22:52, Pyun YongHyeon wrote: >> > On Fri, Nov 19, 2010 at 08:30:54PM -0200, Nenhum_de_Nos wrote: >> >> >> >> On Fri, November 19, 2010 20:07, Nenhum_de_Nos wrote: >> >> > >> >> > On Fri, November 19, 2010 20:02, Pyun YongHyeon wrote: >> >> >> On Fri, Nov 19, 2010 at 07:49:57PM -0200, Nenhum_de_Nos wrote: >> >> >>> >> >> >>> On Fri, November 19, 2010 19:23, Pyun YongHyeon wrote: >> >> >>> > On Fri, Nov 19, 2010 at 06:23:50PM -0200, Nenhum_de_Nos wrote: >> >> >>> > >> >> >>> > [...] >> >> >>> > >> >> >>> >> > Ok, try again after downloading new if_axe.c and let me know >> >> >>> >> > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on >> your >> >> >>> >> > console. >> >> >>> >> >> >> >>> >> never got to see that message. I saw the diff to previous >> >> version, >> >> >>> and >> >> >>> >> did >> >> >>> >> boot into verbose mode (dmesg attached). there were just the >> >> belkin >> >> >>> >> gigabit nic on boot. after, the linksys USB200M: >> >> >>> >> >> >> >>> >> axe1: on >> >> >>> usbus2 >> >> >>> >> axe1: PHYADDR 0xe0:0x10 >> >> >>> >> miibus2: on axe1 >> >> >>> >> ukphy1: PHY 16 on >> miibus2 >> >> >>> >> ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 >> >> >>> >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> >> >>> >> ue1: on axe1 >> >> >>> >> ue1: bpf attached >> >> >>> >> invalid media SR 0x700 >> >> >>> >> invalid media SR 0x700 >> >> >>> >> >> >> >>> > >> >> >>> > This is normal, the message I said will show up when you use >> >> >>> > gigabit controller, AX88178. This controller is fast ethernet >> >> >>> > controller, AX88772A. >> >> >>> >> >> >>> yes, I just tried to show that message with other nic. >> >> >>> >> >> >>> >> >> >> >>> >> and the other gigabit: >> >> >>> >> >> >> >>> >> ugen2.4: at usbus2 >> >> >>> >> axe2: on >> >> >>> usbus2 >> >> >>> >> axe2: PHYADDR 0xe0:0x01 >> >> >>> >> miibus3: on axe2 >> >> >>> >> truephy1: PHY 1 on miibus3 >> >> >>> >> truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> >> >>> >> 1000baseT-FDX, >> >> >>> >> auto >> >> >>> >> ue2: on axe2 >> >> >>> >> ue2: bpf attached >> >> >>> >> ue2: Ethernet address: my mac here >> >> >>> >> ue2: link state changed to DOWN >> >> >>> >> >> >> >>> >> and never got to see the EEPROM message. >> >> >>> >> >> >> >>> > >> >> >>> > Two odd things here. This controller looks like Belkin F5D5055 >> and >> >> >>> >> >> >>> yes, it's this one. >> >> >>> >> >> >>> > it is gigabit controller. So it should print the message I >> >> >>> > mentioned in previous mail. Are you sure you rebuild/reboot >> your >> >> >>> > kernel? >> >> >>> >> >> >>> as usual, just rebuilt the axe module ... so I'm going to rebuild >> >> now. >> >> >>> this is a slow box, and might take a couple of hours. Will try to >> do >> >> it >> >> >>> also in a notebook running stable to speedup the process. >> >> >>> >> >> >>> > The second odd thing is now truephy(4) PHY driver is attached >> to >> >> >>> > your controller. Previously it was ukphy(4) generic PHY driver. >> >> >>> > This means accessing GMII is not reliable such that reading OUI >> of >> >> >>> > PHY changed its value. Maybe this could the reason why you see >> >> lots >> >> >>> > of link UP/DOWN messages since mii(4) periodically polls a >> >> register >> >> >>> > through GMII. If the register value read through GMII >> constantly >> >> >>> > changes it will cause all sorts of problems. >> >> >>> > I'm not sure whether this is axe(4) issue or USB stack issue. I >> >> >>> > also have Belkin F5D5055 controller and has no such problems so >> I >> >> >>> > guess it could be related with other parts of USB stack. >> >> >>> > >> >> >>> > To easily identify issues for a controller, it would be better >> to >> >> >>> > remove all other axe(4) controllers except one you want to >> test. >> >> >>> >> >> >>> ok, I was also testing that other issue. Will separate things >> from >> >> now >> >> >>> on. >> >> >>> no problem using stable from October 7, right ? >> >> >>> >> >> >> >> >> >> Hmm, that depends on your environments. To test USB issues it >> would >> >> >> be better to use stable/8. >> >> > >> >> > both are 8-stable from the beginning of October. As the faster is >> >> already >> >> > compiling things, and it takes 1h max, I'll try this way and can >> after >> >> > update to today 8-stable. >> >> > >> >> > if anything, just say :) >> >> > >> >> > thanks, >> >> > >> >> > matheus >> >> > >> >> >>> thanks, >> >> >>> >> >> >>> matheus >> >> >> >> here: >> >> >> >> ugen0.2: at usbus0 >> >> wlan0: Ethernet address: a mac here >> >> fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 >> >> ugen1.3: at usbus1 >> >> axe0: on usbus1 >> >> axe0: EEPROM data : 0x0a82, phymode : 02 >> >> axe0: MII without any PHY >> >> wlan0: link state changed to UP >> >> wlan0: link state changed to DOWN >> >> wlan0: link state changed to UP >> >> ugen1.3: at usbus1 (disconnected) >> >> axe0: at uhub1, port 3, addr 3 (disconnected) >> >> ugen1.3: at usbus1 >> >> axe0: on usbus1 >> >> axe0: EEPROM data : 0x0a82, phymode : 02 >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> > Thanks. It's big hint. I uploaded updated if_axe.c >> > Let me know it makes any difference. >> >> need to recompile kernel, or just if_axe ? >> > > If you used if_axe module without "device axe" in kernel > configuration(i.e. kernel does not include axe(4) driver), > rebuilding/reloading if_axe should be enough. Otherwise, you have > to rebuild kernel and reboot. axe0: on usbus1 axe0: EEPROM data : 0x0a82, phymode : 02 axe0: attaching PHYs failed ugen1.3: at usbus1 (disconnected) axe0: at uhub1, port 3, addr 3 (disconnected) ugen1.3: at usbus1 axe0: on usbus1 axe0: EEPROM data : 0x0a82, phymode : 02 axe0: attaching PHYs failed wlan0: link state changed to UP [matheus@darkside /usr/home/matheus]$ tried it twice, tried both adapters. just got this. thanks, matheus >> will do this asap. >> >> matheus >> >> >> miibus1: on axe0 >> >> ukphy0: PHY 1 on miibus1 >> >> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> >> 1000baseT-FDX, auto >> >> ue0: on axe0 >> >> ue0: Ethernet address: a mac here >> >> ue0: link state changed to DOWN >> >> >> >> both belkin, each one at a time. >> >> >> >> will sync world and kernel and make {kernel,world} >> >> >> >> thanks, > -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 07:02:42 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAEBC106564A for ; Sat, 20 Nov 2010 07:02:42 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 694868FC0A for ; Sat, 20 Nov 2010 07:02:42 +0000 (UTC) Received: from [93.104.73.12] (helo=current.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PJhT1-00039g-W8; Sat, 20 Nov 2010 08:02:36 +0100 Received: from current.Sisis.de (current [127.0.0.1]) by current.Sisis.de (8.14.3/8.14.3) with ESMTP id oAK72a35002108; Sat, 20 Nov 2010 08:02:36 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id oAK72ZIE002107; Sat, 20 Nov 2010 08:02:35 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Sat, 20 Nov 2010 08:02:35 +0100 From: Matthias Apitz To: Warren Block Message-ID: <20101120070235.GA2091@current.Sisis.de> References: <20101119143337.GA3023@current.Sisis.de> <201011191821.09308.hselasky@c2i.net> <20101119173519.GA3933@current.Sisis.de> <201011191916.53655.hselasky@c2i.net> <20101119183900.GA1221@tiny.Sisis.de> <20101119204639.GA1521@tiny.Sisis.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 93.104.73.12 Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 07:02:43 -0000 El día Friday, November 19, 2010 a las 05:42:57PM -0700, Warren Block escribió: > On Fri, 19 Nov 2010, Matthias Apitz wrote: > > El d?a Friday, November 19, 2010 a las 12:39:13PM -0700, Warren Block escribi?: > > > >>> Should I overwrite the full USB key from /dev/zero? > >> > >> Possibly there would still be differences. Filesystem metadata like > >> date last mounted, for example. If you want a block-by-block duplicate, > >> the brute-force method is to just dd the whole drive. Use bs=64k or > >> bs=1m to help reduce overhead. > > > > Warren, perhaps you missed my point. I have a prepared boot-able key and > > I want to give away a copy of it as a file on DVD. So I dd(1)'ed the key > > to disk and did this twice to ensure that the copy was fine, but the two > > files differ. How can I make sure that the file on disk (or DVD) is a > > exact copy of the key? > > Okay, that makes more sense. Did you mount the key in between the two > times it was dd-ed? No. I just fired up the dd(1) a 2nd time to another file to check if it would produce two times the same result. And, surprise, they differ, they differ each time and in laptops differentes as well. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 11:19:15 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 853991065672 for ; Sat, 20 Nov 2010 11:19:15 +0000 (UTC) (envelope-from roam@ringlet.net) Received: from erengrad.hoster.bg (erengrad.hoster.bg [77.77.142.9]) by mx1.freebsd.org (Postfix) with ESMTP id 047008FC19 for ; Sat, 20 Nov 2010 11:19:14 +0000 (UTC) Received: from middenheim.hoster.bg (middenheim.hoster.bg [77.77.142.11]) by erengrad.hoster.bg (Postfix) with ESMTP id CD716DC200 for ; Sat, 20 Nov 2010 13:19:13 +0200 (EET) Received: from straylight.ringlet.net (host37.office-vpn.int.hoster.bg [10.100.10.37]) (Authenticated sender: roam@hoster.bg) by mail.hoster.bg (Postfix) with ESMTP id B12D25C2FE for ; Sat, 20 Nov 2010 13:19:10 +0200 (EET) Received: from roam (uid 1000) (envelope-from roam@ringlet.net) id 416009 by straylight.ringlet.net (DragonFly Mail Agent) Sat, 20 Nov 2010 13:19:11 +0200 Date: Sat, 20 Nov 2010 13:19:11 +0200 From: Peter Pentchev To: Matthias Apitz Message-ID: <20101120111911.GA4309@straylight.ringlet.net> References: <20101119143337.GA3023@current.Sisis.de> <201011191537.25867.hselasky@c2i.net> <20101119170259.GA3741@current.Sisis.de> <201011191821.09308.hselasky@c2i.net> <20101119173519.GA3933@current.Sisis.de> <20101119232157.GB4198@straylight.ringlet.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <20101119232157.GB4198@straylight.ringlet.net> User-Agent: Mutt/1.5.20 (2009-06-14) X-MailScanner-ID: B12D25C2FE.50408 X-hoster-MailScanner: Found to be clean X-hoster-MailScanner-SpamCheck: not spam, SpamAssassin (cached, score=0.001, required 10, autolearn=disabled, UNPARSEABLE_RELAY 0.00) X-hoster-MailScanner-From: roam@ringlet.net X-hoster-MailScanner-To: freebsd-usb@freebsd.org X-Spam-Status: No Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 11:19:15 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 20, 2010 at 01:21:57AM +0200, Peter Pentchev wrote: > On Fri, Nov 19, 2010 at 06:35:19PM +0100, Matthias Apitz wrote: > > El d=C3=ADa Friday, November 19, 2010 a las 06:21:09PM +0100, Hans Pett= er Selasky escribi=C3=B3: > >=20 > > > > > Can you dump the data into hex using hexdump -C and show us the > > > > > difference. > > > >=20 > > > > Note: the output of the dd(1) is around 3.8 GByte. I compared the 1= st > > > > 2.000.000 lines of the hexdump: no diff; any better tool to show th= e 1st > > > > block which differs? > > > >=20 > > > > > Usually you would use bs=3D65536 (Does that change anything)? > > > >=20 > > > > Same result: they differ :-( > > > >=20 > > > > matthias > > >=20 > > > bsdiff ? > >=20 > > This will not work with such big files (requires 8x memory of the file): > >=20 > > I was thinking in a tool just reading each file block by block, > > comparing the blocks and noting the 1st diff with block offset number. > > (some 10 lines of C code :-)) >=20 > Errrr... are you thinking of cmp(1), maybe with the -l option? :) And just for the record, at http://devel.ringlet.net/textproc/block-summari= ze/ or git://gitorious.org/block-summarize/block-summarize.git you may find a simple utility that summarizes cmp(1)'s output per block. (oof, I just found out that I've still left the default blocksize at 32; will change that for version 0.02, for now there's the -b option :) G'luck, Peter --=20 Peter Pentchev roam@space.bg roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 Nostalgia ain't what it used to be. --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJM566vAAoJEGUe77AlJ98TnbwP/2lySoP4Qm3gf5Z0LfjMhNae IC1qTiQnIHFNNiSLmtQ+wV4rv/H2xbA23FebreMyC/492IUp+5Vi42wgBlXNctV8 +/04uIYG3oL7snulzqDgYuGidSkfxpNqmUwHdsthYIl6wuH2ErB2wlX1X8e/X7TZ T3iFBt/SWzF9t6Z9z8aceVfUYUzBO5nAQ7VYWH5bOiSPZ6Aa1H8f5S0vJvS683oN a8MbNewoL498+7WEv31pFzS9tLQokwNRGX12ETW7E+0SSyad3HLUwiA+0Vshlcg6 /cH0epzCSQoqhCOK4Rw+i/Xnf7mTnDMcbA78smwUfqqu5Itib6iJ0RtdaWhNEdKw XYc2sFozE5usTJzaVmfaxF1WmGmcjTd9yG9/lDMNeTO9l0OGHFdE/5SnXyZIvLrh 01fZvogVcBMdhQdqLSxbEO0jfE5AgEPwUj85tlvbNe6lYa3JmgNdrxaxo8qrkisJ 7wYuGDwaGZxBXLQZocc5afx8RfzU0h0XUxMl8J67g8JoYDbtcGI9klZUU93mhs5M YkqkPaM7yPSd/DS0QWI+9aebOGck4uumoVzvI84a4BPpXBo7oHQStVT+NMi61NoJ mKGDSJniQ/cM7FTwxn7w+sZBb/wGEC9sOKn6gUB2tAKTl55TJDdixjgTbBE2W5U2 E0kQZaY9TD7z5Hl0st+/ =PMIy -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 15:17:00 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D0BD106566C; Sat, 20 Nov 2010 15:17:00 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id CEB488FC08; Sat, 20 Nov 2010 15:16:59 +0000 (UTC) Received: from [93.104.73.12] (helo=current.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PJpBS-00075g-7D; Sat, 20 Nov 2010 16:16:58 +0100 Received: from current.Sisis.de (current [127.0.0.1]) by current.Sisis.de (8.14.3/8.14.3) with ESMTP id oAKFGuVK004043; Sat, 20 Nov 2010 16:16:56 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id oAKFGtCB004042; Sat, 20 Nov 2010 16:16:55 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Sat, 20 Nov 2010 16:16:55 +0100 From: Matthias Apitz To: Alexander Motin Message-ID: <20101120151655.GA4010@current.Sisis.de> References: <201011191916.53655.hselasky@c2i.net> <4CE6C73A.4070208@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4CE6C73A.4070208@FreeBSD.org> X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 93.104.73.12 Cc: freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 15:17:00 -0000 El día Friday, November 19, 2010 a las 08:51:38PM +0200, Alexander Motin escribió: > > Could it be that unwritten/unformatted blocks are read as random data > > from that USB key? Should I overwrite the full USB key from /dev/zero? > > It is allowed behavior for SATA SSDs with TRIM command support. Deleted > blocks can be not guarantied to return any predictable or even > repeatable value. May be this logic could be extended to USB devices. A cmp(1) with -l gives a file like this: $ head -10 diff 196971771 134 34 196971797 134 34 196971833 134 34 196971845 134 34 196971849 134 34 196971875 134 34 196971901 134 34 196971945 134 34 196971955 134 34 196972210 134 34 of 2385059 lines, i.e. of 2385059 bytes which differ in the 3.8 GByte copy; there are only a few patterns of diffs which are repeating: $ sed 's/ */ /g' diff | cut -d' ' -f2,3 | sort -u 0 10 0 104 0 110 0 200 0 204 0 214 0 220 0 234 0 260 0 4 10 0 100 0 110 0 134 0 134 14 134 34 134 4 14 0 200 260 204 234 204 4 214 234 220 260 304 204 34 0 4 0 4 104 4 234 44 0 44 4 (the numbers are in octal). What does this mean? Does not look like errors, in case of random error it whould be more caotic, or? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 16:08:20 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32FEF1065672; Sat, 20 Nov 2010 16:08:20 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 8EBA18FC15; Sat, 20 Nov 2010 16:08:19 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id oAKG8Iai099748; Sat, 20 Nov 2010 09:08:18 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id oAKG8IQW099745; Sat, 20 Nov 2010 09:08:18 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sat, 20 Nov 2010 09:08:18 -0700 (MST) From: Warren Block To: Matthias Apitz In-Reply-To: <20101120151655.GA4010@current.Sisis.de> Message-ID: References: <201011191916.53655.hselasky@c2i.net> <4CE6C73A.4070208@FreeBSD.org> <20101120151655.GA4010@current.Sisis.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (wonkity.com [127.0.0.1]); Sat, 20 Nov 2010 09:08:19 -0700 (MST) Cc: Alexander Motin , freebsd-usb@freebsd.org Subject: Re: copying /dev/da0 with dd(1) to file: output differs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 16:08:20 -0000 On Sat, 20 Nov 2010, Matthias Apitz wrote: > of 2385059 lines, i.e. of 2385059 bytes which differ in the 3.8 GByte > copy; there are only a few patterns of diffs which are repeating: > > $ sed 's/ */ /g' diff | cut -d' ' -f2,3 | sort -u > 0 10 > 0 104 > 0 110 > 0 200 > 0 204 > 0 214 > 0 220 > 0 234 > 0 260 > 0 4 > 10 0 > 100 0 > 110 0 > 134 0 > 134 14 > 134 34 > 134 4 > 14 0 > 200 260 > 204 234 > 204 4 > 214 234 > 220 260 > 304 204 > 34 0 > 4 0 > 4 104 > 4 234 > 44 0 > 44 4 > > (the numbers are in octal). > > What does this mean? Does not look like errors, in case of random error > it whould be more caotic, or? Could you try another USB key to determine whether the error is with the key or the host? From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 21:43:32 2010 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 272381065693; Sat, 20 Nov 2010 21:43:32 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A511B8FC18; Sat, 20 Nov 2010 21:43:31 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAKLhVY0079953; Sat, 20 Nov 2010 21:43:31 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAKLhVMv079949; Sat, 20 Nov 2010 21:43:31 GMT (envelope-from gavin) Date: Sat, 20 Nov 2010 21:43:31 GMT Message-Id: <201011202143.oAKLhVMv079949@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-usb@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: usb/152075: [usb8] [ehci] Add quirk for CS5536 USB X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 21:43:32 -0000 Old Synopsis: Add quirk for CS5536 USB New Synopsis: [usb8] [ehci] Add quirk for CS5536 USB Responsible-Changed-From-To: freebsd-i386->freebsd-usb Responsible-Changed-By: gavin Responsible-Changed-When: Sat Nov 20 21:42:33 UTC 2010 Responsible-Changed-Why: Over to maintainer(s) http://www.freebsd.org/cgi/query-pr.cgi?pr=152075