From owner-freebsd-usb@FreeBSD.ORG Sun Sep 19 00:10:31 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 D578B1065670 for ; Sun, 19 Sep 2010 00:10:31 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from thalia-smout.broadpark.no (thalia-smout.broadpark.no [80.202.8.21]) by mx1.freebsd.org (Postfix) with ESMTP id 928D08FC08 for ; Sun, 19 Sep 2010 00:10:31 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from ignis-smin.broadpark.no ([80.202.8.11]) by thalia-smout.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with ESMTP id <0L8Y00I3RTPGR3A0@thalia-smout.broadpark.no> for freebsd-usb@FreeBSD.org; Sun, 19 Sep 2010 01:10:28 +0200 (CEST) Received: from kg-v2.kg4.no ([80.203.92.226]) by ignis-smin.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with SMTP id <0L8Y00338TPF4F00@ignis-smin.broadpark.no> for freebsd-usb@FreeBSD.org; Sun, 19 Sep 2010 01:10:28 +0200 (CEST) Date: Sun, 19 Sep 2010 01:10:27 +0200 From: Torfinn Ingolfsen To: freebsd-usb@FreeBSD.org Message-id: <20100919011027.9e457282.torfinn.ingolfsen@broadpark.no> X-Mailer: Sylpheed 3.0.3 (GTK+ 2.20.1; amd64-portbld-freebsd8.0) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Cc: Subject: FreeBSD 8.1, if_cdce and an OpenMoko phone 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, 19 Sep 2010 00:10:31 -0000 Hi, Under FreeBSD 7.3-stable, I could connect my Neo FreeRunner (Openmoko phone) via usb cable to my workstation, kldload if_cdce and get an ethernet interface up. Now running FreeBSD 8.1-release on said workstation: root@kg-work2# uname -a FreeBSD kg-work2.kg4.no 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:55:53 UTC 2010 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 and the FreeRunner is detected like this: root@kg-work2# usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen2.2: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON and cdce(4) is already in the GENERIC kernel. From /var/log/messages: Sep 19 00:06:49 kg-work2 root: Unknown USB device: vendor 0x1457 product 0x5122 bus uhub2 Sep 19 00:06:49 kg-work2 kernel: ugen2.2: at usbus2 Sep 19 00:12:47 kg-work2 kernel: interface cdce.1 already present in the KLD 'kernel'! The problem is of course that therer isn't an ethernet interface for this usb device: root@kg-work2# ifconfig em0: flags=8843 metric 0 mtu 1500 options=209b ether 00:08:74:b3:5e:c8 inet 10.1.150.16 netmask 0xffff0000 broadcast 10.1.255.255 media: Ethernet autoselect (100baseTX ) status: active plip0: flags=8810 metric 0 mtu 1500 lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 nd6 options=3 So, what magic tricks do I need to perform to get this working under 8.1? References: 1) http://wiki.openmoko.org/wiki/Neo_FreeRunner -- Regards, Torfinn Ingolfsen From owner-freebsd-usb@FreeBSD.ORG Sun Sep 19 08:25: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 59D10106564A for ; Sun, 19 Sep 2010 08:25:12 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id E06848FC1E for ; Sun, 19 Sep 2010 08:25:11 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=1CaHf1y8KCnZwQGPpxlMvS9eQdJFbtI71s633RdLVzE= c=1 sm=1 a=bkidOuWdDTEA:10 a=8nJEP1OIZ-IA:10 a=M8b_wTzEtboA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=OCGuPPFrAAAA:8 a=K3atA14Dke95IBwZKvwA:9 a=IQXNxRsx17ghemwwejAA:7 a=7N32ha_Sqkm1176SuZYhsAgeNqEA:4 a=wPNLvfGTeEIA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:117 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe08.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 23063495; Sun, 19 Sep 2010 10:24:23 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Sun, 19 Sep 2010 10:26:18 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <20100919011027.9e457282.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20100919011027.9e457282.torfinn.ingolfsen@broadpark.no> 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: <201009191026.18878.hselasky@c2i.net> Cc: Subject: Re: FreeBSD 8.1, if_cdce and an OpenMoko phone 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, 19 Sep 2010 08:25:12 -0000 On Sunday 19 September 2010 01:10:27 Torfinn Ingolfsen wrote: > Hi, > > Under FreeBSD 7.3-stable, I could connect my Neo FreeRunner (Openmoko > phone) via usb cable to my workstation, kldload if_cdce and get an > ethernet interface up. > Now running FreeBSD 8.1-release on said workstation: > root@kg-work2# uname -a > FreeBSD kg-work2.kg4.no 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 > 02:55:53 UTC 2010 > root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > and the FreeRunner is detected like this: > root@kg-work2# usbconfig > ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) > pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON ugen2.1: at usbus2, cfg=0 md=HOST > spd=FULL (12Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 > md=HOST spd=HIGH (480Mbps) pwr=ON ugen2.2: 2.6.29-rc3-v21 with s3c2410_udc> at usbus2, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON > > and cdce(4) is already in the GENERIC kernel. From /var/log/messages: > Sep 19 00:06:49 kg-work2 root: Unknown USB device: vendor 0x1457 product > 0x5122 bus uhub2 Sep 19 00:06:49 kg-work2 kernel: ugen2.2: 2.6.29-rc3-v21 with s3c2410_udc> at usbus2 Sep 19 00:12:47 kg-work2 > kernel: interface cdce.1 already present in the KLD 'kernel'! > > The problem is of course that therer isn't an ethernet interface for this > usb device: root@kg-work2# ifconfig > em0: flags=8843 metric 0 mtu 1500 > options=209b > ether 00:08:74:b3:5e:c8 > inet 10.1.150.16 netmask 0xffff0000 broadcast 10.1.255.255 > media: Ethernet autoselect (100baseTX ) > status: active > plip0: flags=8810 metric 0 mtu 1500 > lo0: flags=8049 metric 0 mtu 16384 > options=3 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=3 > > So, what magic tricks do I need to perform to get this working under 8.1? > > References: > 1) http://wiki.openmoko.org/wiki/Neo_FreeRunner Hi, You need to: usbconfig -d X.Y set_config 1 To get it working. --HPS From owner-freebsd-usb@FreeBSD.ORG Sun Sep 19 14:40:04 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 3C1711065670 for ; Sun, 19 Sep 2010 14:40:04 +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 110C88FC17 for ; Sun, 19 Sep 2010 14:40:04 +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 o8JEe3sc010437 for ; Sun, 19 Sep 2010 14:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o8JEe3UE010436; Sun, 19 Sep 2010 14:40:03 GMT (envelope-from gnats) Date: Sun, 19 Sep 2010 14:40:03 GMT Message-Id: <201009191440.o8JEe3UE010436@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: MIHIRA Yoshiro Cc: Subject: Re: usb/119981: [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigabit ethernet adapter X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: MIHIRA Yoshiro List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 14:40:04 -0000 The following reply was made to PR usb/119981; it has been noted by GNATS. From: MIHIRA Yoshiro To: "bug-followup@FreeBSD.org" , "be_works_us@yahoo.com" Cc: Subject: Re: usb/119981: [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigabit ethernet adapter Date: Sun, 19 Sep 2010 23:04:22 +0900 Dear OKABE-san Could you test this USB dingle on current or 8-stable version with patch? If you could, I will commit your patch(maybe if_axe.c was samll different fr= om 7-stable). Best regards Yoshiro sanpei MIHIRA sanpei@FreeBSD From owner-freebsd-usb@FreeBSD.ORG Sun Sep 19 17:04: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 22390106566B for ; Sun, 19 Sep 2010 17:04:43 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from thalia-smout.broadpark.no (thalia-smout.broadpark.no [80.202.8.21]) by mx1.freebsd.org (Postfix) with ESMTP id C9D438FC12 for ; Sun, 19 Sep 2010 17:04:42 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from ignis-smin.broadpark.no ([80.202.8.11]) by thalia-smout.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with ESMTP id <0L9000CPL7FNZL50@thalia-smout.broadpark.no> for freebsd-usb@FreeBSD.org; Sun, 19 Sep 2010 19:04:35 +0200 (CEST) Received: from kg-v2.kg4.no ([80.203.92.226]) by ignis-smin.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with SMTP id <0L9000EBS7FNEG50@ignis-smin.broadpark.no> for freebsd-usb@FreeBSD.org; Sun, 19 Sep 2010 19:04:35 +0200 (CEST) Date: Sun, 19 Sep 2010 19:04:31 +0200 From: Torfinn Ingolfsen To: freebsd-usb@FreeBSD.org Message-id: <20100919190431.efa35d48.torfinn.ingolfsen@broadpark.no> In-reply-to: <201009191026.18878.hselasky@c2i.net> References: <20100919011027.9e457282.torfinn.ingolfsen@broadpark.no> <201009191026.18878.hselasky@c2i.net> X-Mailer: Sylpheed 3.0.3 (GTK+ 2.20.1; amd64-portbld-freebsd8.0) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Cc: Subject: Re: FreeBSD 8.1, if_cdce and an OpenMoko phone 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, 19 Sep 2010 17:04:43 -0000 On Sun, 19 Sep 2010 10:26:18 +0200 Hans Petter Selasky wrote: > You need to: > > usbconfig -d X.Y set_config 1 > > To get it working. Indeed, that works nicely: root@kg-work2# usbconfig -d 2.2 set_config 1 root@kg-work2# tail /var/log/messages Sep 19 04:00:00 kg-work2 newsyslog[1242]: logfile turned over due to size>100K Sep 19 18:56:18 kg-work2 kernel: cdce0: on usbus2 Sep 19 18:56:18 kg-work2 kernel: ue0: on cdce0 Sep 19 18:56:18 kg-work2 kernel: ue0: Ethernet address: 00:1f:11:01:0d:39 Sep 19 18:56:19 kg-work2 root: Unknown USB device: vendor 0x1457 product 0x5122 bus uhub2 root@kg-work2# ifconfig ue0 ue0: flags=8802 metric 0 mtu 1500 ether 00:1f:11:01:0d:39 Thanks! For future reference, where is this (things like "set_config 1" and so on) documented? The man page for usbconfig doesn't have any reference to it, nor does usb(4). And perhaps the cdce(4) man page should mention that the interface name will be ueX? HAND -- Torfinn From owner-freebsd-usb@FreeBSD.ORG Sun Sep 19 20:24:50 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 D566E1065670; Sun, 19 Sep 2010 20:24:50 +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 ABCA18FC1F; Sun, 19 Sep 2010 20:24:50 +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 o8JKOomr069079; Sun, 19 Sep 2010 20:24:50 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o8JKOoAm069075; Sun, 19 Sep 2010 20:24:50 GMT (envelope-from gavin) Date: Sun, 19 Sep 2010 20:24:50 GMT Message-Id: <201009192024.o8JKOoAm069075@freefall.freebsd.org> To: danny@cs.huji.ac.il, gavin@FreeBSD.org, freebsd-usb@FreeBSD.org, gavin@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: usb/149826: recognice another PL2303 based usb dongle 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, 19 Sep 2010 20:24:50 -0000 Synopsis: recognice another PL2303 based usb dongle State-Changed-From-To: open->patched State-Changed-By: gavin State-Changed-When: Sun Sep 19 20:23:26 UTC 2010 State-Changed-Why: This was supported in HEAD some time ago (r211111/r211153) and is due to be merged soon. Responsible-Changed-From-To: freebsd-usb->gavin Responsible-Changed-By: gavin Responsible-Changed-When: Sun Sep 19 20:23:26 UTC 2010 Responsible-Changed-Why: I'll be merging this. http://www.freebsd.org/cgi/query-pr.cgi?pr=149826 From owner-freebsd-usb@FreeBSD.ORG Mon Sep 20 01:03: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 B4852106566B for ; Mon, 20 Sep 2010 01:03:20 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [91.121.44.19]) by mx1.freebsd.org (Postfix) with ESMTP id 7C4038FC19 for ; Mon, 20 Sep 2010 01:03:20 +0000 (UTC) Received: from baby-jane.lamaiziere.net (unknown [192.168.1.10]) by smtp.lamaiziere.net (Postfix) with ESMTP id 529C763316D; Mon, 20 Sep 2010 02:48:23 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 7844F2CEC17; Mon, 20 Sep 2010 02:50:32 +0200 (CEST) Date: Mon, 20 Sep 2010 02:50:28 +0200 From: Patrick Lamaiziere To: Matthew Luckie Message-ID: <20100920025028.2d7b1d9b@davenulle.org> In-Reply-To: <4C789A4E.9030409@luckie.org.nz> References: <4C789A4E.9030409@luckie.org.nz> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; i386-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-usb@freebsd.org Subject: Re: ZTE USB 3g stick 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, 20 Sep 2010 01:03:20 -0000 Le Sat, 28 Aug 2010 17:10:38 +1200, Matthew Luckie a écrit : Hello, > I've got a 3g usb stick that works fine with 8.0-STABLE from Jan 3rd > 2010, but does not with 8.1-RELEASE. Its a Vodafone branded stick > bought in New Zealand. I was affected by a very similar issue (It worked before january but not latter) with my ZTE stick. That was fixed by : http://freshbsd.org/2010/02/05/01/47/43 See : http://old.nabble.com/problem-with-lastest-u3g-in-RELENG_8-td27459994.html HTH, Regards. From owner-freebsd-usb@FreeBSD.ORG Mon Sep 20 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 20E12106566B for ; Mon, 20 Sep 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 0D3278FC20 for ; Mon, 20 Sep 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 o8KB765f015112 for ; Mon, 20 Sep 2010 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o8KB76DN015110 for freebsd-usb@FreeBSD.org; Mon, 20 Sep 2010 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Sep 2010 11:07:06 GMT Message-Id: <201009201107.o8KB76DN015110@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, 20 Sep 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 -------------------------------------------------------------------------------- p usb/150546 usb libusb(3) libusb_control_transfer() prototype is incor o usb/150401 usb Errors from USB drives mixed between UFS and ZFS o usb/150189 usb [run] if_run appears to corrupt IP traffic o usb/149934 usb [quirk] Transcend JetFlash V85 poor performance o usb/149900 usb [uftdi] FreeBSD 8.1 uftdi patch to support usb-uirt o usb/149764 usb [u3g] 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 ASUS WL-167g doesn't work in 8.1 (continue of 149058) o usb/149039 usb [uhso] 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 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 o 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 o usb/143790 usb [boot] 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 f 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/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 [usb] Encrypted root, geli password at boot; enter key 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 kern/140614 usb [uplcom] [patch] adding support for Radio Shack Gigwar 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 o usb/138570 usb [usb] [panic] USB mass device panics current 7.2-STABL o 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 Samsung Electronics YP-U3 does not attach in 7.1-RELEA o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [usb8] DVD drive detects as 'da' device o 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/123509 usb [umass] continuous reset Samsung SGH-G600 phone 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 o 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 o usb/121232 usb [usb] [panic] USB CardBus card removal causes reboot s 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 o 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/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab 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 o usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th o 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 s usb/108344 usb [usb67] [atausb] [panic] kernel with atausb panics whe 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 [bluetooth] SMP-Kernel crashes reliably when Bluetooth 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 o 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 314 problems total. From owner-freebsd-usb@FreeBSD.ORG Tue Sep 21 16:10:04 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 53F86106564A for ; Tue, 21 Sep 2010 16:10:04 +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 2928D8FC15 for ; Tue, 21 Sep 2010 16:10:04 +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 o8LGA3QT053741 for ; Tue, 21 Sep 2010 16:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o8LGA3Rx053740; Tue, 21 Sep 2010 16:10:03 GMT (envelope-from gnats) Date: Tue, 21 Sep 2010 16:10:03 GMT Message-Id: <201009211610.o8LGA3Rx053740@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Jim Nasby Cc: Subject: Re: usb/150401: Errors from USB drives mixed between UFS and ZFS X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jim Nasby List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 16:10:04 -0000 The following reply was made to PR usb/150401; it has been noted by GNATS. From: Jim Nasby To: bug-followup@FreeBSD.org, decibel@decibel.org Cc: Subject: Re: usb/150401: Errors from USB drives mixed between UFS and ZFS Date: Tue, 21 Sep 2010 11:03:42 -0500 My best guess at this point is that this issue is caused strictly by = having multiple IO requests out at once. Any operation involving more = than one drive at a time is able to produce errors. Hammering on a = single drive works fine. From owner-freebsd-usb@FreeBSD.ORG Tue Sep 21 22:50:02 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 CD7071065673 for ; Tue, 21 Sep 2010 22:50:02 +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 B214A8FC1B for ; Tue, 21 Sep 2010 22:50:02 +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 o8LMo28V066701 for ; Tue, 21 Sep 2010 22:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o8LMo2sG066699; Tue, 21 Sep 2010 22:50:02 GMT (envelope-from gnats) Date: Tue, 21 Sep 2010 22:50:02 GMT Message-Id: <201009212250.o8LMo2sG066699@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: Tue, 21 Sep 2010 22:50:02 -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: Tue, 21 Sep 2010 22:42:23 +0000 (UTC) Author: sanpei Date: Tue Sep 21 22:42:14 2010 New Revision: 212980 URL: http://svn.freebsd.org/changeset/base/212980 Log: Add new device ids. Buffalo (Melco Inc.) LUA3-U2-AGT Logitec LAN-GTJ/U2A(usb/119981) PR: usb/119981 and me Submitted by: "Y.Okabe" , hiroo at oikumene.gcd.org Reviewed by: thompsa MFC after: 3 days Modified: head/share/man/man4/axe.4 head/sys/dev/usb/net/if_axe.c head/sys/dev/usb/usbdevs Modified: head/share/man/man4/axe.4 ============================================================================== --- head/share/man/man4/axe.4 Tue Sep 21 21:41:45 2010 (r212979) +++ head/share/man/man4/axe.4 Tue Sep 21 22:42:14 2010 (r212980) @@ -169,6 +169,10 @@ AX88178: .It Belkin F5D5055 .It +Logitec LAN-GTJ/U2A +.It +Buffalo (Melco Inc.) LUA3-U2-AGT +.It Planex Communications GU1000T .It Sitecom Europe LN-028 Modified: head/sys/dev/usb/net/if_axe.c ============================================================================== --- head/sys/dev/usb/net/if_axe.c Tue Sep 21 21:41:45 2010 (r212979) +++ head/sys/dev/usb/net/if_axe.c Tue Sep 21 22:42:14 2010 (r212980) @@ -155,7 +155,9 @@ static const struct usb_device_id axe_de AXE_DEV(JVC, MP_PRX1, 0), AXE_DEV(LINKSYS2, USB200M, 0), AXE_DEV(LINKSYS4, USB1000, AXE_FLAG_178), + AXE_DEV(LOGITEC, LAN_GTJU2A, AXE_FLAG_178), AXE_DEV(MELCO, LUAU2KTX, 0), + AXE_DEV(MELCO, LUA3U2AGT, AXE_FLAG_178), AXE_DEV(NETGEAR, FA120, 0), AXE_DEV(OQO, ETHER01PLUS, AXE_FLAG_772), AXE_DEV(PLANEX3, GU1000T, AXE_FLAG_178), Modified: head/sys/dev/usb/usbdevs ============================================================================== --- head/sys/dev/usb/usbdevs Tue Sep 21 21:41:45 2010 (r212979) +++ head/sys/dev/usb/usbdevs Tue Sep 21 22:42:14 2010 (r212980) @@ -2063,6 +2063,7 @@ product LOGITECH QUICKCAMPRO2 0xd001 Qui /* Logitec Corp. products */ product LOGITEC LDR_H443SU2 0x0033 DVD Multi-plus unit LDR-H443SU2 product LOGITEC LDR_H443U2 0x00b3 DVD Multi-plus unit LDR-H443U2 +product LOGITEC LAN_GTJU2A 0x0160 LAN-GTJ/U2A Ethernet product LOGITEC RT2870_1 0x0162 RT2870 product LOGITEC RT2870_2 0x0163 RT2870 product LOGITEC RT2870_3 0x0164 RT2870 @@ -2101,6 +2102,7 @@ product MELCO LUAU2KTX 0x003d LUA-U2-KT product MELCO KG54YB 0x005e WLI-U2-KG54-YB WLAN product MELCO KG54 0x0066 WLI-U2-KG54 WLAN product MELCO KG54AI 0x0067 WLI-U2-KG54-AI WLAN +product MELCO LUA3U2AGT 0x006e LUA3-U2-AGT product MELCO NINWIFI 0x008b Nintendo Wi-Fi product MELCO PCOPRS1 0x00b3 PC-OP-RS1 RemoteStation product MELCO SG54HP 0x00d8 WLI-U2-SG54HP _______________________________________________ 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 Wed Sep 22 05:55: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 DB3FF1065672 for ; Wed, 22 Sep 2010 05:55:10 +0000 (UTC) (envelope-from pki@ex.com.pl) Received: from mx-out.strefa.interia.pl (mx-out.strefa.interia.pl [217.74.66.73]) by mx1.freebsd.org (Postfix) with ESMTP id 965FC8FC15 for ; Wed, 22 Sep 2010 05:55:10 +0000 (UTC) Received: by mx-out.strefa.interia.pl (Postfix, from userid 1235) id EB07718B548; Wed, 22 Sep 2010 07:55:08 +0200 (CEST) Received: from zgred (katastrofa.ex.com.pl [62.121.86.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by poczta.strefa.pl (Postfix) with ESMTPSA id C9CE328004BA8 for ; Wed, 22 Sep 2010 07:55:08 +0200 (CEST) Received: from pki by zgred with local (Exim 4.69) (envelope-from ) id 1OyIIP-00026b-MZ for freebsd-usb@freebsd.org; Wed, 22 Sep 2010 07:55:09 +0200 Date: Wed, 22 Sep 2010 07:55:09 +0200 From: Piotr Isajew To: freebsd-usb@freebsd.org Message-ID: <20100922055509.GA7949@zgred.localnet> Mail-Followup-To: freebsd-usb@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline X-PGP-Key: 0x481BC5D8 User-Agent: Mutt/1.5.20 (2009-06-14) Subject: uhso hangs on incoming call 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, 22 Sep 2010 05:55:10 -0000 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I'm experimenting with uhso driver and Option Icon 031 modem. Modem=20 responds to AT commands in minicom but it hangs as soon as there is any incoming call to the modem (it may or may not output one RING indication - depending on luck). Is this a common problem or am I the first to encounter it? Regards, Piotr --gKMricLos+KVdGMg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkyZmj0ACgkQ0vhon0gbxdiPqwCfbmlK3evuo0ZF+lDfz8/GLJag 6v8Anj+xywe2pSbV3axZi+gnF2YjGYHn =w9eP -----END PGP SIGNATURE----- --gKMricLos+KVdGMg-- From owner-freebsd-usb@FreeBSD.ORG Wed Sep 22 09:42: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 BDDDA106566C for ; Wed, 22 Sep 2010 09:42:44 +0000 (UTC) (envelope-from fli@shapeshifter.se) Received: from mx1.h3q.net (mx1.h3q.net [IPv6:2001:16d8:ffe5:1::f1]) by mx1.freebsd.org (Postfix) with ESMTP id 7E21E8FC0A for ; Wed, 22 Sep 2010 09:42:44 +0000 (UTC) Received: from smtp-auth.h3q.net (smtp-auth.h3q.net [127.0.0.1]) (Authenticated sender: hidden) by mx1.h3q.net (Postfix) with ESMTPSA id B488933D15 ; Wed, 22 Sep 2010 11:42:42 +0200 (CEST) Message-ID: <4C99CF8F.40204@shapeshifter.se> Date: Wed, 22 Sep 2010 11:42:39 +0200 From: Fredrik Lindberg User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.12) Gecko/20100915 Thunderbird/3.0.8 MIME-Version: 1.0 To: freebsd-usb@freebsd.org, pki@ex.com.pl References: <20100922055509.GA7949@zgred.localnet> In-Reply-To: <20100922055509.GA7949@zgred.localnet> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: uhso hangs on incoming call 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, 22 Sep 2010 09:42:44 -0000 On 09/22/2010 07:55 AM, Piotr Isajew wrote: > Hello, > > I'm experimenting with uhso driver and Option Icon 031 modem. Modem > responds to AT commands in minicom but it hangs as soon as there is > any incoming call to the modem (it may or may not output one RING > indication - depending on luck). Is this a common problem or am I the > first to encounter it? > > Regards, > > Piotr uhso hasn't received much testing in this area, mainly because it was designed for newer Option devices that have their raw IP packet interface. We could work to fix this, but if u3g worked for you I suggest using that driver instead. Fredrik From owner-freebsd-usb@FreeBSD.ORG Wed Sep 22 16:30:09 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 518351065674 for ; Wed, 22 Sep 2010 16:30:09 +0000 (UTC) (envelope-from donaldcallen@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id DFEFB8FC23 for ; Wed, 22 Sep 2010 16:30:08 +0000 (UTC) Received: by wyb33 with SMTP id 33so873285wyb.13 for ; Wed, 22 Sep 2010 09:30:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=dY2iuRtOg2dzktkO/w7Tf2fJ1Lp6inA9xYxHStA3AWM=; b=lu6nSylTpa4ZKxx1f7/aNr6N46UCd9WTVjo4Oy9ozXK3+pHHabujgN1xzrexXgeAhH KYvrs7gGPZ3sLjusDnsxQtWoFW0cGSMkihvLMTfTKCfu/z9FFdmcveAB0+NJK2FdsyvF DkxFQvLQzlarjrct+y2KJzwPHT25zfO497mao= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=QuTHYvjtEHH4NWDDUlaFbqBkyMZhs4zKB5PGi89gb+rNjcrxIfQl92F+apkf4kYvqL aXGFz9T3ExDP2eU3JU9k3HQWepTSpSvbzoLUdvunfbBSg/ffBnUwyabYhjdeedIyIdg1 3KpTJQ8RM+kZUJYFetIxDUEKbWDDzj+YylZYc= MIME-Version: 1.0 Received: by 10.216.158.12 with SMTP id p12mr344449wek.48.1285171391645; Wed, 22 Sep 2010 09:03:11 -0700 (PDT) Received: by 10.216.82.69 with HTTP; Wed, 22 Sep 2010 09:03:11 -0700 (PDT) Date: Wed, 22 Sep 2010 12:03:11 -0400 Message-ID: From: Donald Allen To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: USB drives still don't work correctly 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, 22 Sep 2010 16:30:09 -0000 I have tried periodically to use FreeBSD -- a couple of the 7.x releases, 8.0 and now 8.1. I do my backups on Seagate SATA drives in USB shoeboxes with ext2 filesystems. These drives work fine with Linux (Slackware) and OpenBSD. But with FreeBSD, absolutely no luck. The 7.x releases would freeze or crash. The much-needed reimplementation of the USB layer in 8.x gave me new hope, but I'm still experiencing problems. I have 8.1 RELEASE installed on a Thinkpad G41, an old system I use for experimenting. When I plug in one of the USB drives directly to the machine, I get the following in /var/log/messages: Sep 22 09:53:10 elektra kernel: ugen3.2: at usbus3 Sep 22 09:53:10 elektra kernel: umass0: on usbus3 Sep 22 09:53:10 elektra kernel: umass0: SCSI over Bulk-Only; quirks = 0x4000 Sep 22 09:53:10 elektra root: Unknown USB device: vendor 0x04fc product 0x0c15 bus uhub3 Sep 22 09:53:12 elektra kernel: umass0:0:0:-1: Attached to scbus0 Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense failed Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): got CAM status 0x10 Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): fatal error, failed to attach to device Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): lost device Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense failed Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): removing device entry After the above, if I remove the USB connector and plug it back in, X freezes (the cursor moves with the mouse, but no response to clicks, or to keyboard gestures) until I remove the connector. Interestingly, if I plug the drive in prior to booting the system, the system recognizes it properly and I can mount it and display its root directory. So there is a workaround. But after all this time that I've been trying to use FreeBSD and all the effort that's gone into getting the USB layer right, it's discouraging to still be running into issues like this. Hopefully, one of you will have a bright (configuration?) idea that will allow me to use the USB drives as I do on other systems, without the need for the reboot workaround. Thanks -- /Don Allen From owner-freebsd-usb@FreeBSD.ORG Wed Sep 22 19:07:50 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 4D3251065672 for ; Wed, 22 Sep 2010 19:07:50 +0000 (UTC) (envelope-from gofdu-freebsd-usb@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 07DD68FC18 for ; Wed, 22 Sep 2010 19:07:49 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OyUfT-0002XZ-RJ for freebsd-usb@freebsd.org; Wed, 22 Sep 2010 21:07:47 +0200 Received: from k.saper.info ([91.121.151.35]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Sep 2010 21:07:47 +0200 Received: from saper by k.saper.info with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Sep 2010 21:07:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-usb@freebsd.org From: Marcin Cieslak Date: Wed, 22 Sep 2010 19:07:38 +0000 (UTC) Organization: http://saper.info Lines: 12 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: k.saper.info User-Agent: slrn/0.9.9p1 (FreeBSD) Subject: Re: USB drives still don't work correctly 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, 22 Sep 2010 19:07:50 -0000 >> Donald Allen wrote: > > After the above, if I remove the USB connector and plug it back in, X > freezes (the cursor moves with the mouse, but no response to clicks, > or to keyboard gestures) until I remove the connector. Can you try this without running X (or just switch to the first text console with Ctrl-Alt-F1) before you do the test. When you unplug, what happens? Do you get kernel panic or the system just freezes? //Marcin From owner-freebsd-usb@FreeBSD.ORG Wed Sep 22 19:45: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 AB09A1065674 for ; Wed, 22 Sep 2010 19:45:52 +0000 (UTC) (envelope-from donaldcallen@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 435FA8FC12 for ; Wed, 22 Sep 2010 19:45:51 +0000 (UTC) Received: by wyb33 with SMTP id 33so1148304wyb.13 for ; Wed, 22 Sep 2010 12:45:51 -0700 (PDT) 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=LJW0RDiD6hrf448c8IWg4oxvfrRO8Vw8zkr3TQSe5d4=; b=SwnvFKv7wP4EGe4EozAysahhy34Csgrv7dAAeMHLXMc7pLGj6yqFlf/1c1ZiM3AYUb F2pJcsCvDH9nTjoWfpaYwnl5Dc9c9kgvxGc360aPKbvLUXxM8BGNA+/XRAmKeqE+NmGH h9sl1+DcZczAzvt1AMJlXXxZdDV8XA4hIu+h0= 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=eaxnovLYRDp6imDXHF3tgyYIU5oAbnesc/llZMQzH9lZLg6hcMVOQpLZGZfBdsl2tO JemhwWdIHy8g3BIGrvB28xriYm70XpDqLBTc4dB/r4ZhwLvR2UZ8vmkn9jXycjQ/1gOv +4wB8hvYB05gdROs5tPMSi6qODAr0Xu46h5sU= MIME-Version: 1.0 Received: by 10.216.52.135 with SMTP id e7mr548459wec.98.1285184750419; Wed, 22 Sep 2010 12:45:50 -0700 (PDT) Received: by 10.216.82.69 with HTTP; Wed, 22 Sep 2010 12:45:50 -0700 (PDT) In-Reply-To: References: Date: Wed, 22 Sep 2010 15:45:50 -0400 Message-ID: From: Donald Allen To: Marcin Cieslak Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-usb@freebsd.org Subject: Re: USB drives still don't work correctly 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, 22 Sep 2010 19:45:52 -0000 On Wed, Sep 22, 2010 at 3:07 PM, Marcin Cieslak wrote: >>> Donald Allen wrote: >> >> After the above, if I remove the USB connector and plug it back in, X >> freezes (the cursor moves with the mouse, but no response to clicks, >> or to keyboard gestures) until I remove the connector. > > Can you try this without running X (or just switch to the first text console > with Ctrl-Alt-F1) before you do the test. > > When you unplug, what happens? Do you get kernel panic or the system just freezes? I tried this on a freshly booted system, logged in, but did not start X, as you requested. When I plugged in the drive, after a little delay, I got the same "AutoSense failed" chatter. I then unplugged the drive and the system seemed happy -- no panic. I plugged the drive back in and tried to run 'dmesg', which hung. Wondering if I should have tried the dmesg before plugging the drive back in, I tried 'reboot', which also hung. Eventually some timeouts went off and the system tried to reboot, but hung while doing that. I had to power-cycle the machine to bring it back up. It had not properly umount-ed the file-systems, so fsck-ed them when restarted. I waited for that to complete and then repeated the experiment a little more carefully: - plugged in the drive, got the 'AutoSense failed'. I ran dmesg, which worked correctly. - unplugged the drive, ran dmesg, worked correctly. - plugged the drive back in, ran dmesg, which hung (something locked in the kernel?). I then unplugged the drive, which I hadn't done the first time, and dmesg completed. I was then able to reboot the system normally, no fsck-ing. /Don > > //Marcin > > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > From owner-freebsd-usb@FreeBSD.ORG Thu Sep 23 06:33: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 B85FE106564A for ; Thu, 23 Sep 2010 06:33:03 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id 473C68FC13 for ; Thu, 23 Sep 2010 06:33:02 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=mP0fIXPs66IAoGKMhYEg+JOAm42C+ILCAHtGwqW+990= c=1 sm=1 a=8L1WbdCadtwA:10 a=8nJEP1OIZ-IA:10 a=M8b_wTzEtboA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=iFLgImIb7hi7Z1CeQMMA:9 a=3tEYb8eV0RytpSzeQ-IA:7 a=WLnMocAbtlH7823tCg4shn250isA:4 a=wPNLvfGTeEIA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:117 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 25291467; Thu, 23 Sep 2010 08:33:00 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Thu, 23 Sep 2010 08:34:12 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: In-Reply-To: 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: <201009230834.12501.hselasky@c2i.net> Cc: Subject: Re: USB drives still don't work correctly 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, 23 Sep 2010 06:33:03 -0000 On Wednesday 22 September 2010 18:03:11 Donald Allen wrote: > I have tried periodically to use FreeBSD -- a couple of the 7.x > releases, 8.0 and now 8.1. I do my backups on Seagate SATA drives in > USB shoeboxes with ext2 filesystems. These drives work fine with Linux > (Slackware) and OpenBSD. But with FreeBSD, absolutely no luck. The 7.x > releases would freeze or crash. The much-needed reimplementation of > the USB layer in 8.x gave me new hope, but I'm still experiencing > problems. > > I have 8.1 RELEASE installed on a Thinkpad G41, an old system I use > for experimenting. When I plug in one of the USB drives directly to > the machine, I get the following in /var/log/messages: > > Sep 22 09:53:10 elektra kernel: ugen3.2: at > usbus3 Sep 22 09:53:10 elektra kernel: umass0: on > usbus3 Sep 22 09:53:10 elektra kernel: umass0: SCSI over Bulk-Only; > quirks = 0x4000 Sep 22 09:53:10 elektra root: Unknown USB device: vendor > 0x04fc > product 0x0c15 bus uhub3 > Sep 22 09:53:12 elektra kernel: umass0:0:0:-1: Attached to scbus0 > Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense failed > Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): got CAM status 0x10 > Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): fatal error, > failed to attach to device > Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): lost device > Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense failed > Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): removing device > entry > > After the above, if I remove the USB connector and plug it back in, X > freezes (the cursor moves with the mouse, but no response to clicks, > or to keyboard gestures) until I remove the connector. > > Interestingly, if I plug the drive in prior to booting the system, the > system recognizes it properly and I can mount it and display its root > directory. So there is a workaround. But after all this time that I've > been trying to use FreeBSD and all the effort that's gone into getting > the USB layer right, it's discouraging to still be running into issues > like this. Hopefully, one of you will have a bright (configuration?) > idea that will allow me to use the USB drives as I do on other > systems, without the need for the reboot workaround. > > Thanks -- > Hi, Maybe your drive needs an USB quirk to work properly. See: usbconfig -h Look for "quirk". --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Sep 23 10:31:37 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 C78E4106566C; Thu, 23 Sep 2010 10:31:37 +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 9DEB08FC19; Thu, 23 Sep 2010 10:31:37 +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 o8NAVOjU078779; Thu, 23 Sep 2010 10:31:37 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o8NAV2FQ076631; Thu, 23 Sep 2010 10:31:02 GMT (envelope-from gavin) Date: Thu, 23 Sep 2010 10:31:02 GMT Message-Id: <201009231031.o8NAV2FQ076631@freefall.freebsd.org> To: dpd@dpdtech.com, gavin@FreeBSD.org, freebsd-usb@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/140614: [uplcom] [patch] adding support for Radio Shack Gigware USB to Serial cable (26-949) to uplcom 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, 23 Sep 2010 10:31:37 -0000 Synopsis: [uplcom] [patch] adding support for Radio Shack Gigware USB to Serial cable (26-949) to uplcom State-Changed-From-To: open->closed State-Changed-By: gavin State-Changed-When: Thu Sep 23 10:28:38 UTC 2010 State-Changed-Why: This was supported in head in r211111/r2111153, which are now merged to stable/8. Thanks for your submission! http://www.freebsd.org/cgi/query-pr.cgi?pr=140614 From owner-freebsd-usb@FreeBSD.ORG Thu Sep 23 15:08:01 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 16128106564A for ; Thu, 23 Sep 2010 15:08:01 +0000 (UTC) (envelope-from donaldcallen@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9E8998FC0A for ; Thu, 23 Sep 2010 15:08:00 +0000 (UTC) Received: by wyb33 with SMTP id 33so2217572wyb.13 for ; Thu, 23 Sep 2010 08:07:59 -0700 (PDT) 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 :content-transfer-encoding; bh=YOwytzOhD3Fza1LNqXYlAQl1MPhV7Oy2eiAjs1764rg=; b=S+SIAOrl4f5U62oh2K7S960YWcXgiGMiatuKW3nLwh1hNulxMyQLHnYAwlhKNmE1TB w9tmgIHkaDpPjBdM9dDJ5LnnQkruxhzHaA6Dw55mlDMoy5cRunTbLluUr3g4dJ0v3P1P wM8cv0KhrpIJAbwSORE3bLSG1sP08z4A3w8c0= 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:content-transfer-encoding; b=JppPg3jjBhYoMiLFrz3K9Hbz/0TtOZ5zl7tLgWNcDC4OLb9RCRABe118yFl17tkZMQ rMjyeEE3i0iEzb2DYcQCh+BqTV4mcpla7j25DVH2tvgoaYyGYMivg7ePMCHfx9caSG2V HLX8KxCUX0OWSpVZvs5X+2GUolFeOcEUonmeg= MIME-Version: 1.0 Received: by 10.216.231.97 with SMTP id k75mr1653803weq.4.1285254479357; Thu, 23 Sep 2010 08:07:59 -0700 (PDT) Received: by 10.216.82.69 with HTTP; Thu, 23 Sep 2010 08:07:59 -0700 (PDT) In-Reply-To: <201009230834.12501.hselasky@c2i.net> References: <201009230834.12501.hselasky@c2i.net> Date: Thu, 23 Sep 2010 11:07:59 -0400 Message-ID: From: Donald Allen To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb@freebsd.org Subject: Re: USB drives still don't work correctly 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, 23 Sep 2010 15:08:01 -0000 On Thu, Sep 23, 2010 at 2:34 AM, Hans Petter Selasky wro= te: > On Wednesday 22 September 2010 18:03:11 Donald Allen wrote: >> I have tried periodically to use FreeBSD -- a couple of the 7.x >> releases, 8.0 and now 8.1. I do my backups on Seagate SATA drives in >> USB shoeboxes with ext2 filesystems. These drives work fine with Linux >> (Slackware) and OpenBSD. But with FreeBSD, absolutely no luck. The 7.x >> releases would freeze or crash. The much-needed reimplementation of >> the USB layer in 8.x gave me new hope, but I'm still experiencing >> problems. >> >> I have 8.1 RELEASE installed on a Thinkpad G41, an old system I use >> for experimenting. When I plug in one of the USB drives directly to >> the machine, I get =A0the following in /var/log/messages: >> >> Sep 22 09:53:10 elektra kernel: ugen3.2: at >> usbus3 Sep 22 09:53:10 elektra kernel: umass0: on >> usbus3 Sep 22 09:53:10 elektra kernel: umass0: =A0SCSI over Bulk-Only; >> quirks =3D 0x4000 Sep 22 09:53:10 elektra root: Unknown USB device: vend= or >> 0x04fc >> product 0x0c15 bus uhub3 >> Sep 22 09:53:12 elektra kernel: umass0:0:0:-1: Attached to scbus0 >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense failed >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): got CAM status 0= x10 >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): fatal error, >> failed to attach to device >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): lost device >> Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense failed >> Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): removing device >> entry >> >> After the above, if I remove the USB connector and plug it back in, X >> freezes (the cursor moves with the mouse, but no response to clicks, >> or to keyboard gestures) until I remove the connector. >> >> Interestingly, if I plug the drive in prior to booting the system, the >> system recognizes it properly and I can mount it and display its root >> directory. So there is a workaround. But after all this time that I've >> been trying to use FreeBSD and all the effort that's gone into getting >> the USB layer right, it's discouraging to still be running into issues >> like this. Hopefully, one of you will have a bright (configuration?) >> idea that will allow me to use the USB drives as I do on other >> systems, without the need for the reboot workaround. >> >> Thanks -- >> > > Hi, > > Maybe your drive needs an USB quirk to work properly. See: > > usbconfig -h > > Look for "quirk". There are 48 supported quirks. Do you have suggestions as to which I might = try? I would add that I'm not sure if you are suggesting this as a solution to my problem, or as a step toward improving the USB driver. If the latter, I'm happy to help. If the former, I'd argue that's not sufficient. These drives (I have three identical ones) work flawlessly, with no user intervention, with Linux (Slackware), and OpenBSD. FreeBSD ought to do the same. And if a "quirk" is needed with FreeBSD, it seems odd that the drives work correctly and without added quirks with FreeBSD when plugged in at boot-time (as I said in the message to which you replied). but not when hot-plugged. This suggests to me that there's a bug, or, at the very least, a missing feature. I'm happy to work with you to try to understand this better, since I can reproduce it at will. Let me know what you'd like me to do. /Don > > --HPS > From owner-freebsd-usb@FreeBSD.ORG Thu Sep 23 16:00: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 28AAC106566C for ; Thu, 23 Sep 2010 16:00:04 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id B4A888FC15 for ; Thu, 23 Sep 2010 16:00:03 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o8NFxuKA006806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Sep 2010 17:59:57 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.4/8.14.4) with ESMTP id o8NFxmXY063948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Sep 2010 17:59:48 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o8NFxmil003833; Thu, 23 Sep 2010 17:59:48 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o8NFxm7Q003832; Thu, 23 Sep 2010 17:59:48 +0200 (CEST) (envelope-from ticso) Date: Thu, 23 Sep 2010 17:59:48 +0200 From: Bernd Walter To: Donald Allen Message-ID: <20100923155948.GC2846@cicely7.cicely.de> References: <201009230834.12501.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: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: freebsd-usb@freebsd.org Subject: Re: USB drives still don't work correctly X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 16:00:04 -0000 On Thu, Sep 23, 2010 at 11:07:59AM -0400, Donald Allen wrote: > On Thu, Sep 23, 2010 at 2:34 AM, Hans Petter Selasky wrote: > > On Wednesday 22 September 2010 18:03:11 Donald Allen wrote: > >> I have tried periodically to use FreeBSD -- a couple of the 7.x > >> releases, 8.0 and now 8.1. I do my backups on Seagate SATA drives in > >> USB shoeboxes with ext2 filesystems. These drives work fine with Linux > >> (Slackware) and OpenBSD. But with FreeBSD, absolutely no luck. The 7.x > >> releases would freeze or crash. The much-needed reimplementation of > >> the USB layer in 8.x gave me new hope, but I'm still experiencing > >> problems. > >> > >> I have 8.1 RELEASE installed on a Thinkpad G41, an old system I use > >> for experimenting. When I plug in one of the USB drives directly to > >> the machine, I get  the following in /var/log/messages: > >> > >> Sep 22 09:53:10 elektra kernel: ugen3.2: at > >> usbus3 Sep 22 09:53:10 elektra kernel: umass0: on > >> usbus3 Sep 22 09:53:10 elektra kernel: umass0:  SCSI over Bulk-Only; > >> quirks = 0x4000 Sep 22 09:53:10 elektra root: Unknown USB device: vendor > >> 0x04fc > >> product 0x0c15 bus uhub3 > >> Sep 22 09:53:12 elektra kernel: umass0:0:0:-1: Attached to scbus0 > >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense failed > >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): got CAM status 0x10 > >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): fatal error, > >> failed to attach to device > >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): lost device > >> Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense failed > >> Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): removing device > >> entry > >> > >> After the above, if I remove the USB connector and plug it back in, X > >> freezes (the cursor moves with the mouse, but no response to clicks, > >> or to keyboard gestures) until I remove the connector. > >> > >> Interestingly, if I plug the drive in prior to booting the system, the > >> system recognizes it properly and I can mount it and display its root > >> directory. So there is a workaround. But after all this time that I've > >> been trying to use FreeBSD and all the effort that's gone into getting > >> the USB layer right, it's discouraging to still be running into issues > >> like this. Hopefully, one of you will have a bright (configuration?) > >> idea that will allow me to use the USB drives as I do on other > >> systems, without the need for the reboot workaround. > >> > >> Thanks -- > >> > > > > Hi, > > > > Maybe your drive needs an USB quirk to work properly. See: > > > > usbconfig -h > > > > Look for "quirk". > > There are 48 supported quirks. Do you have suggestions as to which I might try? > > I would add that I'm not sure if you are suggesting this as a solution > to my problem, or as a step toward improving the USB driver. If the > latter, I'm happy to help. If the former, I'd argue that's not > sufficient. These drives (I have three identical ones) work > flawlessly, with no user intervention, with Linux (Slackware), and > OpenBSD. FreeBSD ought to do the same. And if a "quirk" is needed with > FreeBSD, it seems odd that the drives work correctly and without added > quirks with FreeBSD when plugged in at boot-time (as I said in the > message to which you replied). but not when hot-plugged. This suggests > to me that there's a bug, or, at the very least, a missing feature. Or FreeBSD tries to use a feature, which is broken with the drive, which often happens, since FreeBSD tries hard to be fast and correct. For example broken cache flushes won't hurt if your OS don't bother to even try a flush, broken tagged command queuing or pipelining won't hurt if your OS only does single transactions. Yes: FreeBSD is unusual in that it expects a device to work correctly and that announced features can be used. You also shouldn't ignore that fact that other OS are also use quirk tables to work aroung broken devices - of course Linux is more often used with crappy hardware than FreeBSD, so they likely have bigger quirk tables - with OpenBSD - well either it doesn't use the broken feature at all or they are already stumbled over the problem by luck. I've never seen a Sunplus USB mass storage device so far and I've seen a lot. The FreeBSD driver likely isn't at fault, since it works with so many non-broken devices. For me it looks like the device is just hanging on a command, which would be clearly against specification. I've seen so many creative firmware bugs in USB devices that I don't easily trust any of them. Fortunately most vendors have learned their lessons, so that more recent devices are less error prune. > I'm happy to work with you to try to understand this better, since I > can reproduce it at will. Let me know what you'd like me to do. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-usb@FreeBSD.ORG Thu Sep 23 17:15: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 2E47C1065672 for ; Thu, 23 Sep 2010 17:15:17 +0000 (UTC) (envelope-from donaldcallen@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id A4EDB8FC1C for ; Thu, 23 Sep 2010 17:15:16 +0000 (UTC) Received: by wyb33 with SMTP id 33so2402366wyb.13 for ; Thu, 23 Sep 2010 10:15:15 -0700 (PDT) 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 :content-transfer-encoding; bh=a5V+EQv4WTFu/6raF3pX4eMuQ7iaLSdXF6d9kHvKZcs=; b=PebjDoEg2AhuhFRaE+eSf04IRMhGnOpyGE4UGWGxR+w01oqynQoHSfW3KQQYVcjRXS RZAlH5q7+8VnAAY8oiq1j8QBGE0neUEfcObDDVlPHvX/ou1jFRptFko9CPV3NuFC9o8u h1j7PY+cHBEvByrZUcP5LMF54iu8d/yOKITM8= 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:content-transfer-encoding; b=ezI+3PICPVTTO96E34eYjODBFSlQRR5QQn33Y9lNE+SBrBQWNdI9ue6z4h2FXuCzWt L3yoALbW0nwsPaa/1euINOxvJ8YsXAQhPjafMXLb7U/MAXTMAHCXBDrOsPDQAmt6D9lZ Y1NYlbE8FscfKfXBWl2+jpceQI5IeTg/DwzHI= MIME-Version: 1.0 Received: by 10.216.1.17 with SMTP id 17mr1851884wec.99.1285262115483; Thu, 23 Sep 2010 10:15:15 -0700 (PDT) Received: by 10.216.82.69 with HTTP; Thu, 23 Sep 2010 10:15:15 -0700 (PDT) In-Reply-To: <20100923155948.GC2846@cicely7.cicely.de> References: <201009230834.12501.hselasky@c2i.net> <20100923155948.GC2846@cicely7.cicely.de> Date: Thu, 23 Sep 2010 13:15:15 -0400 Message-ID: From: Donald Allen To: ticso@cicely.de Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb@freebsd.org Subject: Re: USB drives still don't work correctly 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, 23 Sep 2010 17:15:17 -0000 On Thu, Sep 23, 2010 at 11:59 AM, Bernd Walter wr= ote: > On Thu, Sep 23, 2010 at 11:07:59AM -0400, Donald Allen wrote: >> On Thu, Sep 23, 2010 at 2:34 AM, Hans Petter Selasky = wrote: >> > On Wednesday 22 September 2010 18:03:11 Donald Allen wrote: >> >> I have tried periodically to use FreeBSD -- a couple of the 7.x >> >> releases, 8.0 and now 8.1. I do my backups on Seagate SATA drives in >> >> USB shoeboxes with ext2 filesystems. These drives work fine with Linu= x >> >> (Slackware) and OpenBSD. But with FreeBSD, absolutely no luck. The 7.= x >> >> releases would freeze or crash. The much-needed reimplementation of >> >> the USB layer in 8.x gave me new hope, but I'm still experiencing >> >> problems. >> >> >> >> I have 8.1 RELEASE installed on a Thinkpad G41, an old system I use >> >> for experimenting. When I plug in one of the USB drives directly to >> >> the machine, I get =A0the following in /var/log/messages: >> >> >> >> Sep 22 09:53:10 elektra kernel: ugen3.2: at >> >> usbus3 Sep 22 09:53:10 elektra kernel: umass0: = on >> >> usbus3 Sep 22 09:53:10 elektra kernel: umass0: =A0SCSI over Bulk-Only= ; >> >> quirks =3D 0x4000 Sep 22 09:53:10 elektra root: Unknown USB device: v= endor >> >> 0x04fc >> >> product 0x0c15 bus uhub3 >> >> Sep 22 09:53:12 elektra kernel: umass0:0:0:-1: Attached to scbus0 >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense fai= led >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): got CAM statu= s 0x10 >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): fatal error, >> >> failed to attach to device >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): lost device >> >> Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense fai= led >> >> Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): removing devi= ce >> >> entry >> >> >> >> After the above, if I remove the USB connector and plug it back in, X >> >> freezes (the cursor moves with the mouse, but no response to clicks, >> >> or to keyboard gestures) until I remove the connector. >> >> >> >> Interestingly, if I plug the drive in prior to booting the system, th= e >> >> system recognizes it properly and I can mount it and display its root >> >> directory. So there is a workaround. But after all this time that I'v= e >> >> been trying to use FreeBSD and all the effort that's gone into gettin= g >> >> the USB layer right, it's discouraging to still be running into issue= s >> >> like this. Hopefully, one of you will have a bright (configuration?) >> >> idea that will allow me to use the USB drives as I do on other >> >> systems, without the need for the reboot workaround. >> >> >> >> Thanks -- >> >> >> > >> > Hi, >> > >> > Maybe your drive needs an USB quirk to work properly. See: >> > >> > usbconfig -h >> > >> > Look for "quirk". >> >> There are 48 supported quirks. Do you have suggestions as to which I mig= ht try? >> >> I would add that I'm not sure if you are suggesting this as a solution >> to my problem, or as a step toward improving the USB driver. If the >> latter, I'm happy to help. If the former, I'd argue that's not >> sufficient. These drives (I have three identical ones) work >> flawlessly, with no user intervention, with Linux (Slackware), and >> OpenBSD. FreeBSD ought to do the same. And if a "quirk" is needed with >> FreeBSD, it seems odd that the drives work correctly and without added >> quirks with FreeBSD when plugged in at boot-time (as I said in the >> message to which you replied). but not when hot-plugged. This suggests >> to me that there's a bug, or, at the very least, a missing feature. > > Or FreeBSD tries to use a feature, which is broken with the drive, > which often happens, since FreeBSD tries hard to be fast and correct. > For example broken cache flushes won't hurt if your OS don't bother > to even try a flush, broken tagged command queuing or pipelining won't > hurt if your OS only does single transactions. > Yes: FreeBSD is unusual in that it expects a device to work correctly > and that announced features can be used. > You also shouldn't ignore that fact that other OS are also use quirk > tables to work aroung broken devices I'm not ignoring that at all. I've looked at the Linux driver and am aware of usb/core/quirks.c. I'm simply stating the undeniable fact that the other OSes don't require manual intervention in order to use these drives hot-plugged. If they are using heuristics behind the scenes to apply the right quirks, that's fine with me. - of course Linux is more often > used with crappy hardware than FreeBSD, We don't live in an ideal world and not every device implements the specs correctly. Apparently there are enough devices like mine out there that Linux and OpenBSD have found a way to make them work. It's sometimes not a winning strategy to insist on absolute adherence to a protocol -- Opera tried that with their browser and look at their share of the desktop market. It can be a bit like having "I had the right of way" on your tombstone. so they likely have bigger > quirk tables - with OpenBSD - well either it doesn't use the broken > feature at all or they are already stumbled over the problem by luck. > I've never seen a Sunplus USB mass storage device so far and I've seen > a lot. > The FreeBSD driver likely isn't at fault, since it works with so many > non-broken devices. > For me it looks like the device is just hanging on a command, which > would be clearly against specification. > I've seen so many creative firmware bugs in USB devices that I don't > easily trust any of them. > Fortunately most vendors have learned their lessons, so that more > recent devices are less error prune. Whether my hardware is "crappy" or not (and you may well be right about that -- these shoeboxes are a few years old), there's still the issue that the drives work correctly with FreeBSD when present at boot-time, but not when hot-plugged. I would think the handshake with the drive would be the same in either case, so either I'm wrong or there's a bug. If you think a command is hanging, can you suggest a quirk or subset of the 48 to try that might cure the problems in the hotplug case? /Don > >> I'm happy to work with you to try to understand this better, since I >> can reproduce it at will. Let me know what you'd like me to do. > > -- > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > From owner-freebsd-usb@FreeBSD.ORG Thu Sep 23 19:13:14 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 3168B106566C for ; Thu, 23 Sep 2010 19:13:14 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 981C78FC15 for ; Thu, 23 Sep 2010 19:13:13 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o8NJD64B020051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Sep 2010 21:13:08 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.4/8.14.4) with ESMTP id o8NJCwRX070498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Sep 2010 21:12:58 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o8NJCwW2004670; Thu, 23 Sep 2010 21:12:58 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o8NJCuce004669; Thu, 23 Sep 2010 21:12:56 +0200 (CEST) (envelope-from ticso) Date: Thu, 23 Sep 2010 21:12:56 +0200 From: Bernd Walter To: Donald Allen Message-ID: <20100923191256.GE2846@cicely7.cicely.de> References: <201009230834.12501.hselasky@c2i.net> <20100923155948.GC2846@cicely7.cicely.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 cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: ticso@cicely.de, freebsd-usb@freebsd.org Subject: Re: USB drives still don't work correctly X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 19:13:14 -0000 On Thu, Sep 23, 2010 at 01:15:15PM -0400, Donald Allen wrote: > On Thu, Sep 23, 2010 at 11:59 AM, Bernd Walter wrote: > > On Thu, Sep 23, 2010 at 11:07:59AM -0400, Donald Allen wrote: > >> On Thu, Sep 23, 2010 at 2:34 AM, Hans Petter Selasky wrote: > >> > On Wednesday 22 September 2010 18:03:11 Donald Allen wrote: > >> >> I have tried periodically to use FreeBSD -- a couple of the 7.x > >> >> releases, 8.0 and now 8.1. I do my backups on Seagate SATA drives in > >> >> USB shoeboxes with ext2 filesystems. These drives work fine with Linux > >> >> (Slackware) and OpenBSD. But with FreeBSD, absolutely no luck. The 7.x > >> >> releases would freeze or crash. The much-needed reimplementation of > >> >> the USB layer in 8.x gave me new hope, but I'm still experiencing > >> >> problems. > >> >> > >> >> I have 8.1 RELEASE installed on a Thinkpad G41, an old system I use > >> >> for experimenting. When I plug in one of the USB drives directly to > >> >> the machine, I get  the following in /var/log/messages: > >> >> > >> >> Sep 22 09:53:10 elektra kernel: ugen3.2: at > >> >> usbus3 Sep 22 09:53:10 elektra kernel: umass0: on > >> >> usbus3 Sep 22 09:53:10 elektra kernel: umass0:  SCSI over Bulk-Only; > >> >> quirks = 0x4000 Sep 22 09:53:10 elektra root: Unknown USB device: vendor > >> >> 0x04fc > >> >> product 0x0c15 bus uhub3 > >> >> Sep 22 09:53:12 elektra kernel: umass0:0:0:-1: Attached to scbus0 > >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense failed > >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): got CAM status 0x10 > >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): fatal error, > >> >> failed to attach to device > >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): lost device > >> >> Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense failed > >> >> Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): removing device > >> >> entry > >> >> > >> >> After the above, if I remove the USB connector and plug it back in, X > >> >> freezes (the cursor moves with the mouse, but no response to clicks, > >> >> or to keyboard gestures) until I remove the connector. > >> >> > >> >> Interestingly, if I plug the drive in prior to booting the system, the > >> >> system recognizes it properly and I can mount it and display its root > >> >> directory. So there is a workaround. But after all this time that I've > >> >> been trying to use FreeBSD and all the effort that's gone into getting > >> >> the USB layer right, it's discouraging to still be running into issues > >> >> like this. Hopefully, one of you will have a bright (configuration?) > >> >> idea that will allow me to use the USB drives as I do on other > >> >> systems, without the need for the reboot workaround. > >> >> > >> >> Thanks -- > >> >> > >> > > >> > Hi, > >> > > >> > Maybe your drive needs an USB quirk to work properly. See: > >> > > >> > usbconfig -h > >> > > >> > Look for "quirk". > >> > >> There are 48 supported quirks. Do you have suggestions as to which I might try? > >> > >> I would add that I'm not sure if you are suggesting this as a solution > >> to my problem, or as a step toward improving the USB driver. If the > >> latter, I'm happy to help. If the former, I'd argue that's not > >> sufficient. These drives (I have three identical ones) work > >> flawlessly, with no user intervention, with Linux (Slackware), and > >> OpenBSD. FreeBSD ought to do the same. And if a "quirk" is needed with > >> FreeBSD, it seems odd that the drives work correctly and without added > >> quirks with FreeBSD when plugged in at boot-time (as I said in the > >> message to which you replied). but not when hot-plugged. This suggests > >> to me that there's a bug, or, at the very least, a missing feature. > > > > Or FreeBSD tries to use a feature, which is broken with the drive, > > which often happens, since FreeBSD tries hard to be fast and correct. > > For example broken cache flushes won't hurt if your OS don't bother > > to even try a flush, broken tagged command queuing or pipelining won't > > hurt if your OS only does single transactions. > > Yes: FreeBSD is unusual in that it expects a device to work correctly > > and that announced features can be used. > > You also shouldn't ignore that fact that other OS are also use quirk > > tables to work aroung broken devices > > I'm not ignoring that at all. I've looked at the Linux driver and am > aware of usb/core/quirks.c. I'm simply stating the undeniable fact > that the other OSes don't require manual intervention in order to use > these drives hot-plugged. If they are using heuristics behind the > scenes to apply the right quirks, that's fine with me. In my opion FreeBSD has found more HDD firmware bugs than any other OS. Just think about FreeBSD3 when CAM was introduced and a large set of SCSI drives failed because they never expected tagged command queuing to be used that agressive. I'm aware of at least three major (at that time) vendors which had devices with problems. Sometimes it is simple to avoid bugs. Many USB devices fail to comply with specifications if asked anything before being addressed - this is a clear violation, but just changing the order helped without harm. It the tagged command queuing it is not that simple - an OS not using it agressive won't notice, but does it mean we can't every use that feature on all those device which are perfectly Ok? Whitelisting is also not an option because why should we punish the good vendors? > - of course Linux is more often > > used with crappy hardware than FreeBSD, > > We don't live in an ideal world and not every device implements the > specs correctly. Apparently there are enough devices like mine out > there that Linux and OpenBSD have found a way to make them work. It's > sometimes not a winning strategy to insist on absolute adherence to a > protocol -- Opera tried that with their browser and look at their > share of the desktop market. It can be a bit like having "I had the > right of way" on your tombstone. Yes - that point has something in common. People expect crappy webpages to work and people expect crappy hardware to work. But FreeBSD is not an OS which trades working with crappy hardware at the cost of not using important features with working devcies. Windows for example handles USB disks completely different than SATA just becasuse it assumes people might disconnect it at any time. They only do a cache flush in the device clicked for being disconnected and if the device hangs on that command - well - the user is about to disconnect it anyway. > so they likely have bigger > > quirk tables - with OpenBSD - well either it doesn't use the broken > > feature at all or they are already stumbled over the problem by luck. > > I've never seen a Sunplus USB mass storage device so far and I've seen > > a lot. > > The FreeBSD driver likely isn't at fault, since it works with so many > > non-broken devices. > > For me it looks like the device is just hanging on a command, which > > would be clearly against specification. > > I've seen so many creative firmware bugs in USB devices that I don't > > easily trust any of them. > > Fortunately most vendors have learned their lessons, so that more > > recent devices are less error prune. > > Whether my hardware is "crappy" or not (and you may well be right > about that -- these shoeboxes are a few years old), there's still the > issue that the drives work correctly with FreeBSD when present at > boot-time, but not when hot-plugged. I would think the handshake with > the drive would be the same in either case, so either I'm wrong or > there's a bug. Yes - the handshake should be the same, but the drive state is not. So it is just when hot-plugging the device and not when booting connected? Probably it just hangs if asked before the media has spun up, which is likely the case when it had power long time before. Or has the device an external power source and is already rotating before plugged in? > If you think a command is hanging, can you suggest a quirk or subset > of the 48 to try that might cure the problems in the hotplug case? Unfortunately not. Maybe you have a chance to find out via cam debug which command it has problems with, but I'm not familar with it's use, since I never needed it myself. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-usb@FreeBSD.ORG Thu Sep 23 23:01:41 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 39737106566B for ; Thu, 23 Sep 2010 23:01:41 +0000 (UTC) (envelope-from donaldcallen@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id B881D8FC13 for ; Thu, 23 Sep 2010 23:01:40 +0000 (UTC) Received: by wwc33 with SMTP id 33so2752123wwc.31 for ; Thu, 23 Sep 2010 16:01:39 -0700 (PDT) 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 :content-transfer-encoding; bh=g1fLtTY5KcwBqCVebS0dR9ZdfyUxz0l8tM2vCrhMVGQ=; b=n2qThtKhc8huAsQbLIJmgSPsV+DgGPoDlbkZK88vediL+H0A9UA1zD4TBdPT5PTkUQ rezHKDURRuYuIx81kSgeqdZVyzCV4jyO5i58h1Wh9oLcgONqpeMtD3VPWTralKFW649A JBwDq5fjnwCJwzEUUYLZIk/x5A7qeH+ST7rrc= 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:content-transfer-encoding; b=c5wIfODvk9PfbtGoLi2hqINiFxE6FHGT3VQ+JAV83EwPOKWaHLUvgJVBJyn9BfF0K2 y6Ting1nima5/jgQmaR9WTddatNia/dQB7MrdjZbeh9rVpFkhqls0ywwXAsSJJAOvcXE D4oZG7NgmbGjpfOqifE9VN6PJVcyOPKrn3T7I= MIME-Version: 1.0 Received: by 10.216.21.204 with SMTP id r54mr2031750wer.95.1285282898859; Thu, 23 Sep 2010 16:01:38 -0700 (PDT) Received: by 10.216.82.69 with HTTP; Thu, 23 Sep 2010 16:01:38 -0700 (PDT) In-Reply-To: <20100923191256.GE2846@cicely7.cicely.de> References: <201009230834.12501.hselasky@c2i.net> <20100923155948.GC2846@cicely7.cicely.de> <20100923191256.GE2846@cicely7.cicely.de> Date: Thu, 23 Sep 2010 19:01:38 -0400 Message-ID: From: Donald Allen To: ticso@cicely.de Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb@freebsd.org Subject: Re: USB drives still don't work correctly 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, 23 Sep 2010 23:01:41 -0000 On Thu, Sep 23, 2010 at 3:12 PM, Bernd Walter wro= te: > On Thu, Sep 23, 2010 at 01:15:15PM -0400, Donald Allen wrote: >> On Thu, Sep 23, 2010 at 11:59 AM, Bernd Walter = wrote: >> > On Thu, Sep 23, 2010 at 11:07:59AM -0400, Donald Allen wrote: >> >> On Thu, Sep 23, 2010 at 2:34 AM, Hans Petter Selasky wrote: >> >> > On Wednesday 22 September 2010 18:03:11 Donald Allen wrote: >> >> >> I have tried periodically to use FreeBSD -- a couple of the 7.x >> >> >> releases, 8.0 and now 8.1. I do my backups on Seagate SATA drives = in >> >> >> USB shoeboxes with ext2 filesystems. These drives work fine with L= inux >> >> >> (Slackware) and OpenBSD. But with FreeBSD, absolutely no luck. The= 7.x >> >> >> releases would freeze or crash. The much-needed reimplementation o= f >> >> >> the USB layer in 8.x gave me new hope, but I'm still experiencing >> >> >> problems. >> >> >> >> >> >> I have 8.1 RELEASE installed on a Thinkpad G41, an old system I us= e >> >> >> for experimenting. When I plug in one of the USB drives directly t= o >> >> >> the machine, I get =A0the following in /var/log/messages: >> >> >> >> >> >> Sep 22 09:53:10 elektra kernel: ugen3.2: = at >> >> >> usbus3 Sep 22 09:53:10 elektra kernel: umass0: on >> >> >> usbus3 Sep 22 09:53:10 elektra kernel: umass0: =A0SCSI over Bulk-O= nly; >> >> >> quirks =3D 0x4000 Sep 22 09:53:10 elektra root: Unknown USB device= : vendor >> >> >> 0x04fc >> >> >> product 0x0c15 bus uhub3 >> >> >> Sep 22 09:53:12 elektra kernel: umass0:0:0:-1: Attached to scbus0 >> >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense = failed >> >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): got CAM st= atus 0x10 >> >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): fatal erro= r, >> >> >> failed to attach to device >> >> >> Sep 22 09:53:37 elektra kernel: (da0:umass-sim0:0:0:0): lost devic= e >> >> >> Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): AutoSense = failed >> >> >> Sep 22 09:53:47 elektra kernel: (da0:umass-sim0:0:0:0): removing d= evice >> >> >> entry >> >> >> >> >> >> After the above, if I remove the USB connector and plug it back in= , X >> >> >> freezes (the cursor moves with the mouse, but no response to click= s, >> >> >> or to keyboard gestures) until I remove the connector. >> >> >> >> >> >> Interestingly, if I plug the drive in prior to booting the system,= the >> >> >> system recognizes it properly and I can mount it and display its r= oot >> >> >> directory. So there is a workaround. But after all this time that = I've >> >> >> been trying to use FreeBSD and all the effort that's gone into get= ting >> >> >> the USB layer right, it's discouraging to still be running into is= sues >> >> >> like this. Hopefully, one of you will have a bright (configuration= ?) >> >> >> idea that will allow me to use the USB drives as I do on other >> >> >> systems, without the need for the reboot workaround. >> >> >> >> >> >> Thanks -- >> >> >> >> >> > >> >> > Hi, >> >> > >> >> > Maybe your drive needs an USB quirk to work properly. See: >> >> > >> >> > usbconfig -h >> >> > >> >> > Look for "quirk". >> >> >> >> There are 48 supported quirks. Do you have suggestions as to which I = might try? >> >> >> >> I would add that I'm not sure if you are suggesting this as a solutio= n >> >> to my problem, or as a step toward improving the USB driver. If the >> >> latter, I'm happy to help. If the former, I'd argue that's not >> >> sufficient. These drives (I have three identical ones) work >> >> flawlessly, with no user intervention, with Linux (Slackware), and >> >> OpenBSD. FreeBSD ought to do the same. And if a "quirk" is needed wit= h >> >> FreeBSD, it seems odd that the drives work correctly and without adde= d >> >> quirks with FreeBSD when plugged in at boot-time (as I said in the >> >> message to which you replied). but not when hot-plugged. This suggest= s >> >> to me that there's a bug, or, at the very least, a missing feature. >> > >> > Or FreeBSD tries to use a feature, which is broken with the drive, >> > which often happens, since FreeBSD tries hard to be fast and correct. >> > For example broken cache flushes won't hurt if your OS don't bother >> > to even try a flush, broken tagged command queuing or pipelining won't >> > hurt if your OS only does single transactions. >> > Yes: FreeBSD is unusual in that it expects a device to work correctly >> > and that announced features can be used. >> > You also shouldn't ignore that fact that other OS are also use quirk >> > tables to work aroung broken devices >> >> I'm not ignoring that at all. I've looked at the Linux driver and am >> aware of usb/core/quirks.c. I'm simply stating the undeniable fact >> that the other OSes don't require manual intervention in order to use >> these drives hot-plugged. If they are using heuristics behind the >> scenes to apply the right quirks, that's fine with me. > > In my opion FreeBSD has found more HDD firmware bugs than any other OS. > Just think about FreeBSD3 when CAM was introduced and a large set > of SCSI drives failed because they never expected tagged command queuing > to be used that agressive. > I'm aware of at least three major (at that time) vendors which had > devices with problems. > Sometimes it is simple to avoid bugs. > Many USB devices fail to comply with specifications if asked anything > before being addressed - this is a clear violation, but just changing > the order helped without harm. > It the tagged command queuing it is not that simple - an OS not using it > agressive won't notice, but does it mean we can't every use that feature > on all those device which are perfectly Ok? > Whitelisting is also not an option because why should we punish the > good vendors? > >> =A0- of course Linux is more often >> > used with crappy hardware than FreeBSD, >> >> We don't live in an ideal world and not every device implements the >> specs correctly. Apparently there are enough devices like mine out >> there that Linux and OpenBSD have found a way to make them work. It's >> sometimes not a winning strategy to insist on absolute adherence to a >> protocol -- Opera tried that with their browser and look at their >> share of the desktop market. It can be a bit like having "I had the >> right of way" on your tombstone. > > Yes - that point has something in common. > People expect crappy webpages to work and people expect crappy hardware > to work. Yes, except that "people" don't know that the stuff is crappy. For example, Opera used to explode when pointed at wsj.com. They (the Opera apologists) claimed that wsj.com was violating whatever version of the html protocol was current at that point. I could not have cared less -- I just wanted to read the Wall St. Journal. So I used Firefox, which worked fine. > But FreeBSD is not an OS which trades working with crappy hardware at > the cost of not using important features with working devcies. > Windows for example handles USB disks completely different than SATA > just becasuse it assumes people might disconnect it at any time. > They only do a cache flush in the device clicked for being disconnected > and if the device hangs on that command - well - the user is about to > disconnect it anyway. That's a fair point. If you have to penalize using the good devices well in order to support the non-compliant ones, then I agree with you. But I would think that heuristics should be possible such that if a non-compliant device behaves oddly in response to an aggressive, but legal, command sequence, then the system could back off and try again, using a more conservative, lower performance approach that works, and note that it is doing so in the system log. > >> so they likely have bigger >> > quirk tables - with OpenBSD - well either it doesn't use the broken >> > feature at all or they are already stumbled over the problem by luck. >> > I've never seen a Sunplus USB mass storage device so far and I've seen >> > a lot. >> > The FreeBSD driver likely isn't at fault, since it works with so many >> > non-broken devices. >> > For me it looks like the device is just hanging on a command, which >> > would be clearly against specification. >> > I've seen so many creative firmware bugs in USB devices that I don't >> > easily trust any of them. >> > Fortunately most vendors have learned their lessons, so that more >> > recent devices are less error prune. >> >> Whether my hardware is "crappy" or not (and you may well be right >> about that -- these shoeboxes are a few years old), there's still the >> issue that the drives work correctly with FreeBSD when present at >> boot-time, but not when hot-plugged. I would think the handshake with >> the drive would be the same in either case, so either I'm wrong or >> there's a bug. > > Yes - the handshake should be the same, but the drive state is not. > So it is just when hot-plugging the device and not when booting connected= ? Yes. > Probably it just hangs if asked before the media has spun up, which is > likely the case when it had power long time before. > Or has the device an external power source and is already rotating before > plugged in? The device has its own power supply and the disk was up to speed and settled long before I hot-plugged it (also when I plugged it into the system prior to booting it, so in the same state in both cases, but very different outcomes). So your "in the process of spinning up" theory does not apply in my case. > >> If you think a command is hanging, can you suggest a quirk or subset >> of the 48 to try that might cure the problems in the hotplug case? > > Unfortunately not. > Maybe you have a chance to find out via cam debug which command it > has problems with, but I'm not familar with it's use, since I never > needed it myself. I probably will not bother with this on my own. Unless you guys are willing to work with me to understand what's going on here and whether it's fixable either on my end or in the driver, I will have to make my decision about use of FreeBSD knowing that I can't rely on hot-plugging these USB drives for backup. If I can reliably talk to the drives by having them connected at boot-time, that might be good enough. I'll have to get more experience with the rest of the system to see if it's worth this compromise. /Don > > -- > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > From owner-freebsd-usb@FreeBSD.ORG Thu Sep 23 23:50: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 D8BE4106564A for ; Thu, 23 Sep 2010 23:50:43 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 5A23C8FC1C for ; Thu, 23 Sep 2010 23:50:42 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o8NNoZlU033936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 24 Sep 2010 01:50:37 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.4/8.14.4) with ESMTP id o8NNoIH3088857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Sep 2010 01:50:18 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o8NNoIdi005856; Fri, 24 Sep 2010 01:50:18 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o8NNoHDY005855; Fri, 24 Sep 2010 01:50:17 +0200 (CEST) (envelope-from ticso) Date: Fri, 24 Sep 2010 01:50:16 +0200 From: Bernd Walter To: Donald Allen Message-ID: <20100923235016.GH2846@cicely7.cicely.de> References: <201009230834.12501.hselasky@c2i.net> <20100923155948.GC2846@cicely7.cicely.de> <20100923191256.GE2846@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: ticso@cicely.de, freebsd-usb@freebsd.org Subject: Re: USB drives still don't work correctly X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 23:50:43 -0000 On Thu, Sep 23, 2010 at 07:01:38PM -0400, Donald Allen wrote: > On Thu, Sep 23, 2010 at 3:12 PM, Bernd Walter wrote: > > On Thu, Sep 23, 2010 at 01:15:15PM -0400, Donald Allen wrote: > >> On Thu, Sep 23, 2010 at 11:59 AM, Bernd Walter wrote: > >> > On Thu, Sep 23, 2010 at 11:07:59AM -0400, Donald Allen wrote: > >> >> On Thu, Sep 23, 2010 at 2:34 AM, Hans Petter Selasky wrote: > >> >> > On Wednesday 22 September 2010 18:03:11 Donald Allen wrote: > >> We don't live in an ideal world and not every device implements the > >> specs correctly. Apparently there are enough devices like mine out > >> there that Linux and OpenBSD have found a way to make them work. It's > >> sometimes not a winning strategy to insist on absolute adherence to a > >> protocol -- Opera tried that with their browser and look at their > >> share of the desktop market. It can be a bit like having "I had the > >> right of way" on your tombstone. > > > > Yes - that point has something in common. > > People expect crappy webpages to work and people expect crappy hardware > > to work. > > Yes, except that "people" don't know that the stuff is crappy. For That;'s unfortunately true and that's the reason why vendors often don't care to fix that problem. > example, Opera used to explode when pointed at wsj.com. They (the > Opera apologists) claimed that wsj.com was violating whatever version > of the html protocol was current at that point. I could not have cared > less -- I just wanted to read the Wall St. Journal. So I used Firefox, > which worked fine. > > > But FreeBSD is not an OS which trades working with crappy hardware at > > the cost of not using important features with working devcies. > > Windows for example handles USB disks completely different than SATA > > just becasuse it assumes people might disconnect it at any time. > > They only do a cache flush in the device clicked for being disconnected > > and if the device hangs on that command - well - the user is about to > > disconnect it anyway. > > That's a fair point. If you have to penalize using the good devices > well in order to support the non-compliant ones, then I agree with > you. But I would think that heuristics should be possible such that if > a non-compliant device behaves oddly in response to an aggressive, but > legal, command sequence, then the system could back off and try again, > using a more conservative, lower performance approach that works, and > note that it is doing so in the system log. Sometimes it is possible, but with umass devices I've often seen that devices hang in a way where only a power cycle can get them back to business. > >> so they likely have bigger > >> > quirk tables - with OpenBSD - well either it doesn't use the broken > >> > feature at all or they are already stumbled over the problem by luck. > >> > I've never seen a Sunplus USB mass storage device so far and I've seen > >> > a lot. > >> > The FreeBSD driver likely isn't at fault, since it works with so many > >> > non-broken devices. > >> > For me it looks like the device is just hanging on a command, which > >> > would be clearly against specification. > >> > I've seen so many creative firmware bugs in USB devices that I don't > >> > easily trust any of them. > >> > Fortunately most vendors have learned their lessons, so that more > >> > recent devices are less error prune. > >> > >> Whether my hardware is "crappy" or not (and you may well be right > >> about that -- these shoeboxes are a few years old), there's still the > >> issue that the drives work correctly with FreeBSD when present at > >> boot-time, but not when hot-plugged. I would think the handshake with > >> the drive would be the same in either case, so either I'm wrong or > >> there's a bug. > > > > Yes - the handshake should be the same, but the drive state is not. > > So it is just when hot-plugging the device and not when booting connected? > > Yes. > > > Probably it just hangs if asked before the media has spun up, which is > > likely the case when it had power long time before. > > Or has the device an external power source and is already rotating before > > plugged in? > > The device has its own power supply and the disk was up to speed and > settled long before I hot-plugged it (also when I plugged it into the > system prior to booting it, so in the same state in both cases, but > very different outcomes). So your "in the process of spinning up" > theory does not apply in my case. Ok - it is not spinning up, but there is still another point. An USB device is required to follow bus power even it is self powered. The reason is that an USB device pushes current into the bus and if it is connected to a powered down host it is forbidden. A pullup resistor of 1.5k is used to notify the host about existence. Once a device sees USB power it is allowed to suck a certain low current for a short time. A self powered device usually only senses the buspower, but the chip in your device may be used for both modes, so it has to be strict on timing, although almost no host really cares about this. A device enables it's pull-up and this has to be done within a short time because it is not allowed to suck current from the bus for a long time. Once the pullup is enabled the host gets informed by the hub port that there is a new device and it can enable the hub port at any time to communicate with the device at address 0 under which - because many devices are buggy - it can only setup the final address. So the difference in timing is that in one case the device sees power, enables the interface and the host directly tries to get the device up within short time. In the other case the host takes a long time until it comes to the device. Another point is the regular framing signal a device sees. Once again the device has to settle down if framing signal is missing, which means a host is in suspend mode and the device has to go to suspend as well. Bus power can still be available for standby purpose or because the port can't disable the power at all, which is very common. I think the device won't see framing signals until the host enables the port, so this shouldn't influence any further. > >> If you think a command is hanging, can you suggest a quirk or subset > >> of the 48 to try that might cure the problems in the hotplug case? > > > > Unfortunately not. > > Maybe you have a chance to find out via cam debug which command it > > has problems with, but I'm not familar with it's use, since I never > > needed it myself. > > I probably will not bother with this on my own. Unless you guys are > willing to work with me to understand what's going on here and whether > it's fixable either on my end or in the driver, I will have to make my > decision about use of FreeBSD knowing that I can't rely on > hot-plugging these USB drives for backup. If I can reliably talk to > the drives by having them connected at boot-time, that might be good > enough. I'll have to get more experience with the rest of the system > to see if it's worth this compromise. Surely there is a way to get it working since it works with other OS and the device gets probed fine from the USB standpoint, so everything works to setup quirks - I'm just don't see anyexisting to fit my assumptions. As a test you can try to connect the device to an self powered USB hub and the last port. Then connect the whole hub to the host. In this case the device will see power before being connected as most hubs don't switch their power power output. If it doesn't work you can connect other devices to the other ports, then the host will take care about the other devices first. There is also another difference. If you boot with an USB device connected likely the BIOS already has spoken with the device. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-usb@FreeBSD.ORG Fri Sep 24 15:16: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 C90CA106566B for ; Fri, 24 Sep 2010 15:16:15 +0000 (UTC) (envelope-from donaldcallen@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5AC718FC1A for ; Fri, 24 Sep 2010 15:16:15 +0000 (UTC) Received: by wyb33 with SMTP id 33so3655113wyb.13 for ; Fri, 24 Sep 2010 08:16:14 -0700 (PDT) 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=kGYfpKAfAadZAMRhL8r7qoeuE49oDNdD7jlYvdtr0E0=; b=J7SxpZ/DQitR4DbV8ne2OA3yL8GdCmQp/G1xy3pHlp+odnTVAqS0FZJljTrB/6Va5J QW8BYgN+npD5lAkCfq4AtHs/DuOnB3gFPr9pZrWeCyUZPp/YDjJImv9ODQdjLlpmsvTl EoTwITdgirXTM2P5GUPsvwYlaKUiikIo8OAEs= 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=WC90CwpM54hmpN3YOyfvcfr6+bDSSGeMnp1ygw4D3ndDAackmnOw4KKUAQM1nSN3Y0 2PTgu60QLmVKbhGOFGnZeM60vFBhI52b/oNeVuJpKlw3TtVo0gc7qwhvOV+7MRJniq7r Sxbxn2uiavqiMsY+W7vYKPWgYRF//HvS4+r1w= MIME-Version: 1.0 Received: by 10.216.38.207 with SMTP id a57mr9591938web.40.1285341374425; Fri, 24 Sep 2010 08:16:14 -0700 (PDT) Received: by 10.216.82.69 with HTTP; Fri, 24 Sep 2010 08:16:14 -0700 (PDT) In-Reply-To: <20100923235016.GH2846@cicely7.cicely.de> References: <201009230834.12501.hselasky@c2i.net> <20100923155948.GC2846@cicely7.cicely.de> <20100923191256.GE2846@cicely7.cicely.de> <20100923235016.GH2846@cicely7.cicely.de> Date: Fri, 24 Sep 2010 11:16:14 -0400 Message-ID: From: Donald Allen To: ticso@cicely.de Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-usb@freebsd.org Subject: Re: USB drives still don't work correctly 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, 24 Sep 2010 15:16:15 -0000 A few more things on this issue: 1. I installed FreeBSD on another system, just on the off-chance that my problem might be caused by testing with an old machine (c. 2005). This machine is a relatively new HP desktop and it exhibits exactly the same symptoms w.r.t. the USB drives as I described earlier. 2. I booted the system with one of the drives connected and spinning, so I could get the device description with usbconfig: ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x04fc idProduct = 0x0c15 bcdDevice = 0xc683 iManufacturer = 0x0002 iProduct = 0x0003 iSerialNumber = 0x0001 bNumConfigurations = 0x0001 If you dump_device_quirks, you find this entry, matching my hardware: VID=0x04fc PID=0x0c15 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_MSC_NO_SYNC_CACHE So this device is known to the FreeBSD USB world. Unfortunately, the built-in quirks in the kernel don't completely do the job. If you google for 'freebsd sunplus', you turn up other people complaining about the same issues I have. One guy even discovered, as I did, that the drive works if it's present at boot-time. 3. Plugging the drive into a self-powered USB hub and then hot-plugging the hub into the computer doesn't help. /Don From owner-freebsd-usb@FreeBSD.ORG Fri Sep 24 15:35:45 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 1F40E106567A for ; Fri, 24 Sep 2010 15:35:45 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id BAB698FC12 for ; Fri, 24 Sep 2010 15:35:44 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o8OFZdbA090581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 24 Sep 2010 17:35:40 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.4/8.14.4) with ESMTP id o8OFZXZF026397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Sep 2010 17:35:33 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o8OFZXWP010377; Fri, 24 Sep 2010 17:35:33 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o8OFZXlR010376; Fri, 24 Sep 2010 17:35:33 +0200 (CEST) (envelope-from ticso) Date: Fri, 24 Sep 2010 17:35:33 +0200 From: Bernd Walter To: Donald Allen Message-ID: <20100924153532.GU2846@cicely7.cicely.de> References: <201009230834.12501.hselasky@c2i.net> <20100923155948.GC2846@cicely7.cicely.de> <20100923191256.GE2846@cicely7.cicely.de> <20100923235016.GH2846@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: ticso@cicely.de, freebsd-usb@freebsd.org Subject: Re: USB drives still don't work correctly X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 15:35:45 -0000 On Fri, Sep 24, 2010 at 11:16:14AM -0400, Donald Allen wrote: > A few more things on this issue: > > 1. I installed FreeBSD on another system, just on the off-chance that > my problem might be caused by testing with an old machine (c. 2005). > This machine is a relatively new HP desktop and it exhibits exactly > the same symptoms w.r.t. the USB drives as I described earlier. > > 2. I booted the system with one of the drives connected and spinning, > so I could get the device description with usbconfig: > > ugen1.2: at usbus1, > cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON You can't ask the hanging device? It is bulk only so the command channel should be used for identification only. > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x04fc > idProduct = 0x0c15 > bcdDevice = 0xc683 > iManufacturer = 0x0002 > iProduct = 0x0003 > iSerialNumber = 0x0001 > bNumConfigurations = 0x0001 > > If you dump_device_quirks, you find this entry, matching my hardware: > > VID=0x04fc PID=0x0c15 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_MSC_NO_SYNC_CACHE > > So this device is known to the FreeBSD USB world. Unfortunately, the > built-in quirks in the kernel don't completely do the job. If you > google for 'freebsd sunplus', you turn up other people complaining > about the same issues I have. One guy even discovered, as I did, that > the drive works if it's present at boot-time. I've found others as well when searching for the error message. > 3. Plugging the drive into a self-powered USB hub and then > hot-plugging the hub into the computer doesn't help. This is unexpected :( So probably it really is the BIOS making the difference. If you stop at the loader stage, plug the device in and then start the kernel - will it change something? This way the BIOS won't see the device, but the kernel does. Will it help if you try usbconfig reset on the device? The feature to reset ports wasn't available with the old stack. It is just wild guessing, since I'm a bit out of ideas, but you could try UQ_MSC_FORCE_WIRE_BBB and UQ_MSC_FORCE_PROTO_SCSI, although the point that it works when already plugged in makes it unlikely. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-usb@FreeBSD.ORG Sat Sep 25 09:41: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 30CFD106566B for ; Sat, 25 Sep 2010 09:41:29 +0000 (UTC) (envelope-from sanpei@sanpei.org) Received: from mail2.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.freebsd.org (Postfix) with ESMTP id F34AE8FC17 for ; Sat, 25 Sep 2010 09:41:28 +0000 (UTC) Received: from cherry2.sanpei.org (j069113.ppp.asahi-net.or.jp [61.213.69.113]) by mail2.asahi-net.or.jp (Postfix) with ESMTP id 10B0FB44C5 for ; Sat, 25 Sep 2010 18:21:43 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by cherry2.sanpei.org (8.14.4/8.14.3) with ESMTP id o8P9Lgu9081015; Sat, 25 Sep 2010 18:21:43 +0900 (JST) (envelope-from sanpei@sanpei.org) Date: Sat, 25 Sep 2010 18:21:42 +0900 (JST) Message-Id: <20100925.182142.75173118738901607.sanpei@sanpei.org> To: freebsd-usb@freebsd.org From: MIHIRA Sanpei Yoshiro X-Mailer: Mew version 6.2 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (cherry2.sanpei.org [127.0.0.1]); Sat, 25 Sep 2010 18:21:43 +0900 (JST) Subject: [axe] Gigabit USB NIC, Buffalo (Melco Inc.) LUA3-U2-AGT could not be often use with CardBus USB port. 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, 25 Sep 2010 09:41:29 -0000 Dear All, I have Gigabit USB NIC, Buffalo (Melco Inc.) LUA3-U2-AGT. That NIC use AX88178. I use that NIC with CardBus USB 2.0 port. http://www.avlab.com.tw/usb/1005_0004_000cx.htm But I often could not use that NIC with CardBus USB 2.0 port. With Another USB port(USB 1.1), I always use this NIC(but poor performance) Pleae let me know to how to fix this problem. [NG Steps] (with CardBus USB 2.0 port, about 9 times NG, 10 times tests) 1. Insert USB NIC. 2. This USB NIC was not probed USB 2.0, only USB 1.1[NG] # usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.2: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON <----- Why? 3. set IP address (ifconfig) [OK] 4. ping from another host, 9 of 10 packet was lost[NG]. [OK Steps](with CardBus USB 2.0 port, about 1 times OK, 10 times tests) 1. Insert USB NIC. 2. This USB NIC was probed **USB 2.0**[OK] # usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON 3. set IP address (ifconfig) [OK] 4. ping and ssh [OK] [OK Steps] onboard USB 1.1 port always OK 1. Insert USB NIC. 2. This USB NIC was probed **USB 1.1**[OK] # usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON 3. set IP address (ifconfig) [OK] 4. ping and ssh [OK] Best Regards, --- MIHIRA, Sanpei Yoshiro Tokyo, Japan.