From tmueko at kommunity.net  Tue Sep  1 07:50:32 2009
From: tmueko at kommunity.net (=?ISO-8859-1?Q?Tom_M=FCller-Kortkamp?=)
Date: Tue Sep  1 07:51:40 2009
Subject: usb/113672: [usb67] [ehci] [panic] Kernel panic with AEWIN
	CB6971
In-Reply-To: <200908311207.n7VC7Iq5036353@freefall.freebsd.org>
References: <200908311207.n7VC7Iq5036353@freefall.freebsd.org>
Message-ID: <9AEE706B-E4FC-434F-A181-C7BB47C1AE5F@kommunity.net>


Am 31.08.2009 um 14:07 schrieb gavin@FreeBSD.org:

> Old Synopsis: [ehci] [panic] Kernel panic with AEWIN CB6971
> New Synopsis: [usb67] [ehci] [panic] Kernel panic with AEWIN CB6971
>
> State-Changed-From-To: open->feedback
> State-Changed-By: gavin
> State-Changed-When: Mon Aug 31 12:03:58 UTC 2009
> State-Changed-Why:
> To submitter: Do you know if this problem still exists in newer  
> versions
> of FreeBSD, or if it has been fixed since the PR was submitted?  If  
> you
> are still able to test, it would be useful if you could establish if
> the problem still exists in 7.2, and 8.0.  Thanks!

Sorry, I don't have access to that Host any more and it was the only  
one I ever owned.

Tom

>
>
> Responsible-Changed-From-To: freebsd-usb->gavin
> Responsible-Changed-By: gavin
> Responsible-Changed-When: Mon Aug 31 12:03:58 UTC 2009
> Responsible-Changed-Why:
> Track
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=113672

--
kommunity GmbH & Co.KG - Goseriede 4, D-30159 Hannover
Telefon: +49 (0)5 11 - 80 72 58 - 0  Fax: +49 (0)5 11 - 80 72 58 - 10
Mail: mailto:tmueko@kommunity.net, Web: http://www.kommunity.net
------------
USt.-IDNr.: DE 813740826;
Handelsregister: Amtsgericht Hannover; Registernummer: HRA 26721;
Pers?nlich haftende Gesellschafterin: kommunity  
Verwaltungsgesellschaft mbH
vertreten durch den Gesch?ftsf?hrer Tom M?ller-Kortkamp;
Handelsregister: Amtsgericht Hannover; Registernummer: HRB 60200
------------
Teamviewer-Support-Link: http://www.kommunity.biz



From mike at sentex.net  Tue Sep  1 15:40:08 2009
From: mike at sentex.net (Mike Tancsa)
Date: Tue Sep  1 15:40:14 2009
Subject: usb/138172: Additional dev id for u3g (Option mini PCIe)
Message-ID: <200909011540.n81Fe7ai036952@freefall.freebsd.org>

The following reply was made to PR usb/138172; it has been noted by GNATS.

From: Mike Tancsa <mike@sentex.net>
To: bug-followup@FreeBSD.org, mike@sentex.ca
Cc:  
Subject: Re: usb/138172: Additional dev id for u3g (Option mini PCIe)
Date: Tue, 01 Sep 2009 10:52:00 -0400

 Here is an additional device ID for an Option 380 PCIe.  The U760 is 
 also in the diff below (http://www.freebsd.org/cgi/query-pr.cgi?pr=138138)
 
          ---Mike
 
 --- /tmp/usbdevs        2009-09-01 10:36:23.000000000 -0400
 +++ usbdevs     2009-09-01 10:25:53.000000000 -0400
 @@ -1917,6 +1917,8 @@
   product OPTION GTICON322       0xd033  GlobeTrotter Icon322 storage
   product OPTION GTMAX36         0x6701  GlobeTrotter Max 3.6 Modem
   product OPTION GTMAXHSUPA      0x7001  GlobeTrotter HSUPA
 +product OPTION GTMAXHSUPAE     0x6901  GlobeTrotter HSUPA PCIe
 +product OPTION GTMAX380HSUPAE  0x7211  GlobeTrotter 380HSUPA PCIe
 
   /* OQO */
   product OQO WIFI01             0x0002  model 01 WiFi interface
 
 
 
 --- /tmp/u3g-orig.c     2009-09-01 10:37:15.000000000 -0400
 +++ u3g.c       2009-09-01 10:38:24.000000000 -0400
 @@ -16,7 +16,7 @@
    * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
    * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
    *
 - * $FreeBSD: src/sys/dev/usb/u3g.c,v 1.24.2.5 2009/08/13 07:19:43 
 n_hibma Exp $
 + * $FreeBSD: src/sys/dev/usb/u3g.c,v 1.24.2.4 2009/07/09 15:29:26 
 n_hibma Exp $
    */
 
   /*
 @@ -134,6 +134,8 @@
          {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS 
 },            U3GSP_UMTS,     U3GINIT_NONE },
          {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 
 },             U3GSP_HSDPA,    U3GINIT_NONE },
          {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAXHSUPA 
 },          U3GSP_HSDPA,    U3GINIT_NONE },
 +       {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAXHSUPAE 
 },         U3GSP_HSDPA,    U3GINIT_NONE },
 +       {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX380HSUPAE 
 },      U3GSP_HSDPA,    U3GINIT_NONE },
          {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G 
 },        U3GSP_UMTS,     U3GINIT_NONE },
          /* OEM: Qualcomm, Inc. */
          {{ USB_VENDOR_QUALCOMMINC, USB_PRODUCT_QUALCOMMINC_ZTE_STOR 
 },  U3GSP_CDMA,     U3GINIT_ZTESTOR },
 @@ -144,6 +146,7 @@
          {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 
 },                U3GSP_HSPA,     U3GINIT_HUAWEI },
          /* OEM: Novatel */
          {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_CDMA_MODEM 
 },        U3GSP_CDMA,     U3GINIT_EJECT },
 +       {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U760 
 },      U3GSP_CDMA,     U3GINIT_EJECT },
          {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_ES620 
 },             U3GSP_UMTS,     U3GINIT_EJECT },        // XXX
          {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_MC950D 
 },            U3GSP_HSUPA,    U3GINIT_EJECT },
          {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U720 
 },              U3GSP_UMTS,     U3GINIT_EJECT },        // XXX
 
 
 # cu -l /dev/cuaU0.2
 Connected
 ati
 Manufacturer: Option N.V.
 Model: GTM380
 Revision: 2.12.0Hd (Date: May 27 2008, Time: 11:19:10)
 
 OK
 
 ucom0: <Option N.V. Globetrotter HSUPA Modem, class 255/255, rev 
 1.10/0.00, addr 2> on uhub0
 ucom0: Interface 0 of 3, not in use
 ucom0:  Endpoint 0 of 3
 ucom0:  Endpoint 1 of 3
 ucom0: port=0 iface=0 in=0x83 out=0x3
 ucom0:  Endpoint 2 of 3
 ucom0: Interface 1 of 3, not in use
 ucom0:  Endpoint 0 of 2
 ucom0:  Endpoint 1 of 2
 ucom0: port=1 iface=1 in=0x84 out=0x4
 ucom0: Interface 2 of 3, not in use
 ucom0:  Endpoint 0 of 3
 ucom0:  Endpoint 1 of 3
 ucom0:  Endpoint 2 of 3
 ucom0: port=2 iface=2 in=0x82 out=0x2
 ucom0: configured 3 serial ports (U0.%d)
 
 
 # usbdevs -v
 Controller /dev/usb0:
 addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), 
 AMD(0x0000), rev 1.00
   port 1 powered
   port 2 addr 2: full speed, power 500 mA, config 1, Globetrotter 
 HSUPA Modem(0x7211), Option N.V.(0x0af0), rev 0.00
   port 3 powered
   port 4 powered
 Controller /dev/usb1:
 addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), 
 AMD(0x0000), rev 1.00
   port 1 powered
   port 2 powered
   port 3 powered
   port 4 powered
 
 The only odd quirk of this one is that cuaU0.0, cuaU0.1 do not work. 
 Everything needs to be done through .2 ?
 
 
          ---Mike
 
 
 --------------------------------------------------------------------
 Mike Tancsa,                                      tel +1 519 651 3400
 Sentex Communications,                            mike@sentex.net
 Providing Internet since 1994                    www.sentex.net
 Cambridge, Ontario Canada                         www.sentex.net/mike
 
From hselasky at c2i.net  Tue Sep  1 15:55:34 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep  1 15:55:41 2009
Subject: usb/138172: Additional dev id for u3g (Option mini PCIe)
In-Reply-To: <200909011540.n81Fe7ai036952@freefall.freebsd.org>
References: <200909011540.n81Fe7ai036952@freefall.freebsd.org>
Message-ID: <200909011755.47148.hselasky@c2i.net>

On Tuesday 01 September 2009 17:40:07 Mike Tancsa wrote:
> The following reply was made to PR usb/138172; it has been noted by GNATS.
>
> From: Mike Tancsa <mike@sentex.net>
> To: bug-followup@FreeBSD.org, mike@sentex.ca
> Cc:
> Subject: Re: usb/138172: Additional dev id for u3g (Option mini PCIe)
> Date: Tue, 01 Sep 2009 10:52:00 -0400
>
>  Here is an additional device ID for an Option 380 PCIe.  The U760 is
>  also in the diff below (http://www.freebsd.org/cgi/query-pr.cgi?pr=138138)
>
>           ---Mike
>
>  --- /tmp/usbdevs        2009-09-01 10:36:23.000000000 -0400
>  +++ usbdevs     2009-09-01 10:25:53.000000000 -0400
>  @@ -1917,6 +1917,8 @@
>    product OPTION GTICON322       0xd033  GlobeTrotter Icon322 storage
>    product OPTION GTMAX36         0x6701  GlobeTrotter Max 3.6 Modem
>    product OPTION GTMAXHSUPA      0x7001  GlobeTrotter HSUPA
>  +product OPTION GTMAXHSUPAE     0x6901  GlobeTrotter HSUPA PCIe
>  +product OPTION GTMAX380HSUPAE  0x7211  GlobeTrotter 380HSUPA PCIe
>
>    /* OQO */
>    product OQO WIFI01             0x0002  model 01 WiFi interface
>
>
>
>  --- /tmp/u3g-orig.c     2009-09-01 10:37:15.000000000 -0400
>  +++ u3g.c       2009-09-01 10:38:24.000000000 -0400
>  @@ -16,7 +16,7 @@
>     * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
> OF * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. *
>  - * $FreeBSD: src/sys/dev/usb/u3g.c,v 1.24.2.5 2009/08/13 07:19:43
>  n_hibma Exp $
>  + * $FreeBSD: src/sys/dev/usb/u3g.c,v 1.24.2.4 2009/07/09 15:29:26
>  n_hibma Exp $
>     */
>
>    /*
>  @@ -134,6 +134,8 @@
>           {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS
>  },            U3GSP_UMTS,     U3GINIT_NONE },
>           {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36
>  },             U3GSP_HSDPA,    U3GINIT_NONE },
>           {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAXHSUPA
>  },          U3GSP_HSDPA,    U3GINIT_NONE },
>  +       {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAXHSUPAE
>  },         U3GSP_HSDPA,    U3GINIT_NONE },
>  +       {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX380HSUPAE
>  },      U3GSP_HSDPA,    U3GINIT_NONE },
>           {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G
>  },        U3GSP_UMTS,     U3GINIT_NONE },
>           /* OEM: Qualcomm, Inc. */
>           {{ USB_VENDOR_QUALCOMMINC, USB_PRODUCT_QUALCOMMINC_ZTE_STOR
>  },  U3GSP_CDMA,     U3GINIT_ZTESTOR },
>  @@ -144,6 +146,7 @@
>           {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220
>  },                U3GSP_HSPA,     U3GINIT_HUAWEI },
>           /* OEM: Novatel */
>           {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_CDMA_MODEM
>  },        U3GSP_CDMA,     U3GINIT_EJECT },
>  +       {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U760
>  },      U3GSP_CDMA,     U3GINIT_EJECT },
>           {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_ES620
>  },             U3GSP_UMTS,     U3GINIT_EJECT },        // XXX
>           {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_MC950D
>  },            U3GSP_HSUPA,    U3GINIT_EJECT },
>           {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U720
>  },              U3GSP_UMTS,     U3GINIT_EJECT },        // XXX
>
>
>  # cu -l /dev/cuaU0.2
>  Connected
>  ati
>  Manufacturer: Option N.V.
>  Model: GTM380
>  Revision: 2.12.0Hd (Date: May 27 2008, Time: 11:19:10)
>
>  OK
>
>  ucom0: <Option N.V. Globetrotter HSUPA Modem, class 255/255, rev
>  1.10/0.00, addr 2> on uhub0
>  ucom0: Interface 0 of 3, not in use
>  ucom0:  Endpoint 0 of 3
>  ucom0:  Endpoint 1 of 3
>  ucom0: port=0 iface=0 in=0x83 out=0x3
>  ucom0:  Endpoint 2 of 3
>  ucom0: Interface 1 of 3, not in use
>  ucom0:  Endpoint 0 of 2
>  ucom0:  Endpoint 1 of 2
>  ucom0: port=1 iface=1 in=0x84 out=0x4
>  ucom0: Interface 2 of 3, not in use
>  ucom0:  Endpoint 0 of 3
>  ucom0:  Endpoint 1 of 3
>  ucom0:  Endpoint 2 of 3
>  ucom0: port=2 iface=2 in=0x82 out=0x2
>  ucom0: configured 3 serial ports (U0.%d)
>
>
>  # usbdevs -v
>  Controller /dev/usb0:
>  addr 1: full speed, self powered, config 1, OHCI root hub(0x0000),
>  AMD(0x0000), rev 1.00
>    port 1 powered
>    port 2 addr 2: full speed, power 500 mA, config 1, Globetrotter
>  HSUPA Modem(0x7211), Option N.V.(0x0af0), rev 0.00
>    port 3 powered
>    port 4 powered
>  Controller /dev/usb1:
>  addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
>  AMD(0x0000), rev 1.00
>    port 1 powered
>    port 2 powered
>    port 3 powered
>    port 4 powered
>
>  The only odd quirk of this one is that cuaU0.0, cuaU0.1 do not work.
>  Everything needs to be done through .2 ?
>
>
>           ---Mike
>
>

Does your patch apply to 8+9-current ?

--HPS

From mike at sentex.net  Tue Sep  1 20:40:19 2009
From: mike at sentex.net (Mike Tancsa)
Date: Tue Sep  1 20:40:26 2009
Subject: usb/138172: Additional dev id for u3g (Option mini PCIe)
In-Reply-To: <200909011755.47148.hselasky@c2i.net>
References: <200909011540.n81Fe7ai036952@freefall.freebsd.org>
	<200909011755.47148.hselasky@c2i.net>
Message-ID: <200909012036.n81Kasgg015091@lava.sentex.ca>

At 11:55 AM 9/1/2009, Hans Petter Selasky wrote:
>On Tuesday 01 September 2009 17:40:07 Mike Tancsa wrote:
> >
>
>Does your patch apply to 8+9-current ?


Here are the diffs for 8+9-current

I tested the Option mini-pci-express units. I dont have the novatel 
handy right now, but it should work

--- usbdevs.orig        2009-09-01 15:39:55.000000000 -0400
+++ usbdevs     2009-09-01 15:40:32.000000000 -0400
@@ -1930,6 +1930,8 @@
  product OPTION GTMAX36         0x6701  GlobeTrotter Max 3.6 Modem
  product OPTION GTHSDPA         0x6971  GlobeTrotter HSDPA
  product OPTION GTMAXHSUPA      0x7001  GlobeTrotter HSUPA
+product OPTION GTMAXHSUPAE      0x6901  GlobeTrotter HSUPA PCIe
+product OPTION GTMAX380HSUPAE   0x7211  GlobeTrotter 380HSUPA PCIe

  /* OQO */
  product OQO WIFI01             0x0002  model 01 WiFi interface

--- u3g.c.prev  2009-08-13 08:44:26.000000000 -0400
+++ u3g.c       2009-09-01 16:16:45.000000000 -0400
@@ -180,6 +180,8 @@
         U3G_DEV(OPTION, GTMAX36, 0),
         U3G_DEV(OPTION, GTHSDPA, 0),
         U3G_DEV(OPTION, GTMAXHSUPA, 0),
+       U3G_DEV(OPTION, GTMAXHSUPAE, 0),
+       U3G_DEV(OPTION, GTMAX380HSUPAE, 0),
         U3G_DEV(OPTION, VODAFONEMC3G, 0),
         /* OEM: Qualcomm, Inc. */
         U3G_DEV(QUALCOMMINC, ZTE_STOR, U3GFL_SCSI_EJECT),
@@ -204,6 +206,7 @@
         U3G_DEV(NOVATEL, X950D, 0),
         U3G_DEV(NOVATEL, XU870, 0),
         U3G_DEV(NOVATEL, ZEROCD, U3GFL_SCSI_EJECT),
+       U3G_DEV(NOVATEL, U760, U3GFL_SCSI_EJECT),
         U3G_DEV(DELL, U740, 0),
         /* OEM: Merlin */
         U3G_DEV(MERLIN, V620, 0),



alix# usbconfig show_ifdrv
ugen0.1: <OHCI root HUB AMD> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.1.0: uhub0: <AMD OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1>
ugen1.1: <EHCI root HUB AMD> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
ugen1.1.0: uhub1: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1>
ugen0.2: <Globetrotter HSUPA Modem Option N.V.> at usbus0, cfg=0 
md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2.0: u3g0: <Data Interface>
alix#


ugen0.2: <Globetrotter HSUPA Modem Option N.V.> at usbus0, cfg=0 
md=HOST spd=FULL (12Mbps) pwr=ON

   bLength = 0x0012
   bDescriptorType = 0x0001
   bcdUSB = 0x0110
   bDeviceClass = 0x00ff
   bDeviceSubClass = 0x00ff
   bDeviceProtocol = 0x00ff
   bMaxPacketSize0 = 0x0040
   idVendor = 0x0af0
   idProduct = 0x7211
   bcdDevice = 0x0000
   iManufacturer = 0x0001  <Option N.V.>
   iProduct = 0x0002  <Globetrotter HSUPA Modem  >
   iSerialNumber = 0x0004  <Serial Number>
   bNumConfigurations = 0x0001




ugen0.2: <Globetrotter HSUPA Modem Option N.V.> at usbus0, cfg=0 
md=HOST spd=FULL (12Mbps) pwr=ON


  Configuration index 0

     bLength = 0x0009
     bDescriptorType = 0x0002
     wTotalLength = 0x005f
     bNumInterfaces = 0x0003
     bConfigurationValue = 0x0001
     iConfiguration = 0x0000  <no string>
     bmAttributes = 0x00a0
     bMaxPower = 0x00fa

     Interface 0
       bLength = 0x0009
       bDescriptorType = 0x0004
       bInterfaceNumber = 0x0000
       bAlternateSetting = 0x0000
       bNumEndpoints = 0x0003
       bInterfaceClass = 0x00ff
       bInterfaceSubClass = 0x00ff
       bInterfaceProtocol = 0x00ff
       iInterface = 0x0003  <Data Interface>

      Endpoint 0
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0083
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 1
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0003
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 2
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0085
         bmAttributes = 0x0003
         wMaxPacketSize = 0x0010
         bInterval = 0x0080
         bRefresh = 0x0000
         bSynchAddress = 0x0000

       Additional Descriptor

       bLength = 0x03
       bDescriptorType = 0x24
       bDescriptorSubType = 0x03
        RAW dump:
        0x00 | 0x03, 0x24, 0x03



     Interface 1
       bLength = 0x0009
       bDescriptorType = 0x0004
       bInterfaceNumber = 0x0001
       bAlternateSetting = 0x0000
       bNumEndpoints = 0x0002
       bInterfaceClass = 0x00ff
       bInterfaceSubClass = 0x00ff
       bInterfaceProtocol = 0x00ff
       iInterface = 0x0003  <Data Interface>

      Endpoint 0
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0084
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 1
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0004
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000


     Interface 2
       bLength = 0x0009
       bDescriptorType = 0x0004
       bInterfaceNumber = 0x0002
       bAlternateSetting = 0x0000
       bNumEndpoints = 0x0003
       bInterfaceClass = 0x00ff
       bInterfaceSubClass = 0x00ff
       bInterfaceProtocol = 0x00ff
       iInterface = 0x0003  <Data Interface>

      Endpoint 0
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0081
         bmAttributes = 0x0003
         wMaxPacketSize = 0x0010
         bInterval = 0x0080
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 1
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0082
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 2
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0002
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000


Used the same ppp.conf and all looks good with my provider.

tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500
         inet 10.141.132.86 --> 10.1.0.1 netmask 0xffffffff
         Opened by PID 1151

         ---Mike


>--HPS

--------------------------------------------------------------------
Mike Tancsa,                                      tel +1 519 651 3400
Sentex Communications,                            mike@sentex.net
Providing Internet since 1994                    www.sentex.net
Cambridge, Ontario Canada                         www.sentex.net/mike

From hselasky at c2i.net  Tue Sep  1 20:48:02 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep  1 20:48:09 2009
Subject: usb/138172: Additional dev id for u3g (Option mini PCIe)
In-Reply-To: <200909012036.n81Kasgg015091@lava.sentex.ca>
References: <200909011540.n81Fe7ai036952@freefall.freebsd.org>
	<200909011755.47148.hselasky@c2i.net>
	<200909012036.n81Kasgg015091@lava.sentex.ca>
Message-ID: <200909012248.17910.hselasky@c2i.net>

On Tuesday 01 September 2009 22:40:25 Mike Tancsa wrote:
> usb/138172

Here is the commit:

http://perforce.freebsd.org/chv.cgi?CH=168061

--HPS
From mike at sentex.net  Tue Sep  1 20:59:06 2009
From: mike at sentex.net (Mike Tancsa)
Date: Tue Sep  1 20:59:12 2009
Subject: usb/138172: Additional dev id for u3g (Option mini PCIe)
In-Reply-To: <200909012248.17910.hselasky@c2i.net>
References: <200909011540.n81Fe7ai036952@freefall.freebsd.org>
	<200909011755.47148.hselasky@c2i.net>
	<200909012036.n81Kasgg015091@lava.sentex.ca>
	<200909012248.17910.hselasky@c2i.net>
Message-ID: <200909012055.n81KtgF4015198@lava.sentex.ca>

At 04:48 PM 9/1/2009, Hans Petter Selasky wrote:
>On Tuesday 01 September 2009 22:40:25 Mike Tancsa wrote:
> > usb/138172
>
>Here is the commit:
>
>http://perforce.freebsd.org/chv.cgi?CH=168061

Thanks!  Any chance it will hit the 2 trees ?  (the RELENG_7 version) 
as well as whats in perforce to RELENG_8 and HEAD ?


>--HPS

--------------------------------------------------------------------
Mike Tancsa,                                      tel +1 519 651 3400
Sentex Communications,                            mike@sentex.net
Providing Internet since 1994                    www.sentex.net
Cambridge, Ontario Canada                         www.sentex.net/mike

From hselasky at c2i.net  Tue Sep  1 21:04:26 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep  1 21:04:33 2009
Subject: usb/138172: Additional dev id for u3g (Option mini PCIe)
In-Reply-To: <200909012055.n81KtgF4015198@lava.sentex.ca>
References: <200909011540.n81Fe7ai036952@freefall.freebsd.org>
	<200909012248.17910.hselasky@c2i.net>
	<200909012055.n81KtgF4015198@lava.sentex.ca>
Message-ID: <200909012304.45907.hselasky@c2i.net>

On Tuesday 01 September 2009 22:59:12 Mike Tancsa wrote:
> At 04:48 PM 9/1/2009, Hans Petter Selasky wrote:
> >On Tuesday 01 September 2009 22:40:25 Mike Tancsa wrote:
> > > usb/138172
> >
> >Here is the commit:
> >
> >http://perforce.freebsd.org/chv.cgi?CH=168061
>
> Thanks!  Any chance it will hit the 2 trees ?  (the RELENG_7 version)
> as well as whats in perforce to RELENG_8 and HEAD ?

Hi,

After 8.0 is released it will go into 8+9 HEAD at least.

--HPS

From hugme at hugme.org  Wed Sep  2 02:13:53 2009
From: hugme at hugme.org (Hug Me)
Date: Wed Sep  2 02:14:00 2009
Subject: huawei card
Message-ID: <f9876c510909011846r8a26261q760fca0123ab6c2d@mail.gmail.com>

I've been having all sorts of trouble with this card. I've tried it
several ways. umass in the kernel, umass loaded manually, umass not
loaded at all... u3g in loaded manually or in the kernel, ubsa loaded
manually or in the kernel. I can't seem to get it detected as anything
except a storage device. I've tried the camcontrol eject and when it
comes back I still don't see the device....

here is some of what I see:

significant lines from boot with device in place
...
umass0: <HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/0.00,
addr 2> on uhub0
umass1: <HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/0.00,
addr 2> on uhub0
...
(probe2:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe2:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(probe2:umass-sim0:0:0:0): SCSI Status: Check Condition
(probe2:umass-sim0:0:0:0): NOT READY asc:3a,0
(probe2:umass-sim0:0:0:0): Medium not present
(probe2:umass-sim0:0:0:0): Unretryable error
(probe3:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe3:umass-sim1:1:0:0): CAM Status: SCSI Status Error
(probe3:umass-sim1:1:0:0): SCSI Status: Check Condition
(probe3:umass-sim1:1:0:0): NOT READY asc:3a,0
(probe3:umass-sim1:1:0:0): Medium not present
(probe3:umass-sim1:1:0:0): Unretryable error
(probe0:mpt0:0:8:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:mpt0:0:8:0): CAM Status: SCSI Status Error
(probe0:mpt0:0:8:0): SCSI Status: Check Condition
(probe0:mpt0:0:8:0): UNIT ATTENTION asc:29,0
(probe0:mpt0:0:8:0): Power on, reset, or bus device reset occurred
(probe0:mpt0:0:8:0): Retrying Command (per Sense Data)
ses0 at mpt0 bus 0 target 8 lun 0
ses0: <IBM 25P3495a S320  1 1> Fixed Processor SCSI-2 device
ses0: 3.300MB/s transfers
ses0: SAF-TE Compliant Device
da0 at mpt0 bus 0 target 0 lun 0
da0: <LSILOGIC 1030 IM 1000> Fixed Direct Access SCSI-2 device
da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit)
da0: Command Queueing Enabled
da0: 34702MB (71071561 512 byte sectors: 255H 63S/T 4424C)
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
da1 at umass-sim1 bus 1 target 0 lun 0
da1: <HUAWEI MMC Storage 2.31> Removable Direct Access SCSI-2 device
da1: 1.000MB/s transfers
da1: Attempt to query device size failed: NOT READY, Medium not present
cd0 at umass-sim0 bus 0 target 0 lun 0
cd0: <HUAWEI Mass Storage 2.31> Removable CD-ROM SCSI-2 device
cd0: 1.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present


with umass not loaded:
Unknown USB device: vendor 0x12d1 product 0x1414 bus uhub0
ugen0: <HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/0.00,
addr 2> on uhub0

# usbdevs -v
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, OHCI root hub(0x0000),
(0x1166)(0x0000), rev 1.00
 port 1 powered
 port 2 addr 2: full speed, self powered, config 1, HUAWEI
Mobile(0x1414), HUAWEI Technology(0x12d1), rev 0.00
 port 3 powered
 port 4 powered


Thanks for your help!


-- 
        *******************************************************************
        Don't ever forget to
                -*HUGME*-

Yield to Temptation ... it may not pass your way again.
                -- Lazarus Long, "Time Enough for Love"
From hselasky at c2i.net  Wed Sep  2 06:29:52 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Sep  2 06:29:58 2009
Subject: huawei card
In-Reply-To: <f9876c510909011846r8a26261q760fca0123ab6c2d@mail.gmail.com>
References: <f9876c510909011846r8a26261q760fca0123ab6c2d@mail.gmail.com>
Message-ID: <200909020830.11183.hselasky@c2i.net>

On Wednesday 02 September 2009 03:46:01 Hug Me wrote:
> 0x1414

Your device seems not listed in dev/usb/u3g.c . That's probably why it doesn't 
work.

--HPS
From hugme at hugme.org  Wed Sep  2 11:31:37 2009
From: hugme at hugme.org (Hug Me)
Date: Wed Sep  2 11:31:42 2009
Subject: huawei card
In-Reply-To: <f9876c510909011846r8a26261q760fca0123ab6c2d@mail.gmail.com>
References: <f9876c510909011846r8a26261q760fca0123ab6c2d@mail.gmail.com>
Message-ID: <f9876c510909020431k57ff3153n2ab95f7ae97dd26c@mail.gmail.com>

Well, I'm one step closer. I changed the line in /sys/dev/usb/usbdevs from this:

 product HUAWEI MOBILE            0x1001  Huawei Mobile

to this:

product HUAWEI MOBILE              0x1414  Huawei Technology

recompiled and the devices now show up... however, there are 4 of them:

hugme@dragoncon# ls /dev/cuaU*
/dev/cuaU0.0            /dev/cuaU0.1            /dev/cuaU0.2
 /dev/cuaU0.3
/dev/cuaU0.0.init       /dev/cuaU0.1.init       /dev/cuaU0.2.init
 /dev/cuaU0.3.init
/dev/cuaU0.0.lock       /dev/cuaU0.1.lock       /dev/cuaU0.2.lock
 /dev/cuaU0.3.lock

is this a default? I haven't been able to get them to initilize yet...
tried minicom this morning, I'm going to configure remote to try tip
in just a bit....


On Tue, Sep 1, 2009 at 9:46 PM, Hug Me<hugme@hugme.org> wrote:
> I've been having all sorts of trouble with this card. I've tried it
> several ways. umass in the kernel, umass loaded manually, umass not
> loaded at all... u3g in loaded manually or in the kernel, ubsa loaded
> manually or in the kernel. I can't seem to get it detected as anything
> except a storage device. I've tried the camcontrol eject and when it
> comes back I still don't see the device....
>
> here is some of what I see:
>
> significant lines from boot with device in place
> ...
> umass0: <HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/0.00,
> addr 2> on uhub0
> umass1: <HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/0.00,
> addr 2> on uhub0
> ...
> (probe2:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
> (probe2:umass-sim0:0:0:0): CAM Status: SCSI Status Error
> (probe2:umass-sim0:0:0:0): SCSI Status: Check Condition
> (probe2:umass-sim0:0:0:0): NOT READY asc:3a,0
> (probe2:umass-sim0:0:0:0): Medium not present
> (probe2:umass-sim0:0:0:0): Unretryable error
> (probe3:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
> (probe3:umass-sim1:1:0:0): CAM Status: SCSI Status Error
> (probe3:umass-sim1:1:0:0): SCSI Status: Check Condition
> (probe3:umass-sim1:1:0:0): NOT READY asc:3a,0
> (probe3:umass-sim1:1:0:0): Medium not present
> (probe3:umass-sim1:1:0:0): Unretryable error
> (probe0:mpt0:0:8:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
> (probe0:mpt0:0:8:0): CAM Status: SCSI Status Error
> (probe0:mpt0:0:8:0): SCSI Status: Check Condition
> (probe0:mpt0:0:8:0): UNIT ATTENTION asc:29,0
> (probe0:mpt0:0:8:0): Power on, reset, or bus device reset occurred
> (probe0:mpt0:0:8:0): Retrying Command (per Sense Data)
> ses0 at mpt0 bus 0 target 8 lun 0
> ses0: <IBM 25P3495a S320 ?1 1> Fixed Processor SCSI-2 device
> ses0: 3.300MB/s transfers
> ses0: SAF-TE Compliant Device
> da0 at mpt0 bus 0 target 0 lun 0
> da0: <LSILOGIC 1030 IM 1000> Fixed Direct Access SCSI-2 device
> da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit)
> da0: Command Queueing Enabled
> da0: 34702MB (71071561 512 byte sectors: 255H 63S/T 4424C)
> SMP: AP CPU #2 Launched!
> SMP: AP CPU #1 Launched!
> SMP: AP CPU #3 Launched!
> da1 at umass-sim1 bus 1 target 0 lun 0
> da1: <HUAWEI MMC Storage 2.31> Removable Direct Access SCSI-2 device
> da1: 1.000MB/s transfers
> da1: Attempt to query device size failed: NOT READY, Medium not present
> cd0 at umass-sim0 bus 0 target 0 lun 0
> cd0: <HUAWEI Mass Storage 2.31> Removable CD-ROM SCSI-2 device
> cd0: 1.000MB/s transfers
> cd0: Attempt to query device size failed: NOT READY, Medium not present
>
>
> with umass not loaded:
> Unknown USB device: vendor 0x12d1 product 0x1414 bus uhub0
> ugen0: <HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/0.00,
> addr 2> on uhub0
>
> # usbdevs -v
> Controller /dev/usb0:
> addr 1: full speed, self powered, config 1, OHCI root hub(0x0000),
> (0x1166)(0x0000), rev 1.00
> ?port 1 powered
> ?port 2 addr 2: full speed, self powered, config 1, HUAWEI
> Mobile(0x1414), HUAWEI Technology(0x12d1), rev 0.00
> ?port 3 powered
> ?port 4 powered
>
>
> Thanks for your help!
>
>
> --
> ? ? ? ?*******************************************************************
> ? ? ? ?Don't ever forget to
> ? ? ? ? ? ? ? ?-*HUGME*-
>
> Yield to Temptation ... it may not pass your way again.
> ? ? ? ? ? ? ? ?-- Lazarus Long, "Time Enough for Love"
>



-- 
        *******************************************************************
        Don't ever forget to
                -*HUGME*-

Yield to Temptation ... it may not pass your way again.
                -- Lazarus Long, "Time Enough for Love"
From hugme at hugme.org  Wed Sep  2 11:40:15 2009
From: hugme at hugme.org (Hug Me)
Date: Wed Sep  2 11:40:21 2009
Subject: huawei card
In-Reply-To: <f9876c510909020431k57ff3153n2ab95f7ae97dd26c@mail.gmail.com>
References: <f9876c510909011846r8a26261q760fca0123ab6c2d@mail.gmail.com>
	<f9876c510909020431k57ff3153n2ab95f7ae97dd26c@mail.gmail.com>
Message-ID: <f9876c510909020440q7e463d01tc2763974b6ef44ed@mail.gmail.com>

Tip has worked, I'm not sure why minicom did not. Here is the line I
had to set up in /etc/remote:

tmobile:dv=/dev/cuaU0.0:br#1700000:pa=none:

this was the result:
-----
hugme@dragoncon# tip tmobile
connected
ati
Manufacturer: huawei
Model: UMG181
Revision: 11.100.10.00.420
IMEI: 355768022267564
+GCAP: +CGSM,+FCLASS,+DS

OK
-----

PPP is the next step....



On Wed, Sep 2, 2009 at 7:31 AM, Hug Me<hugme@hugme.org> wrote:
> Well, I'm one step closer. I changed the line in /sys/dev/usb/usbdevs from this:
>
> ?product HUAWEI MOBILE ? ? ? ? ? ?0x1001 ?Huawei Mobile
>
> to this:
>
> product HUAWEI MOBILE ? ? ? ? ? ? ?0x1414 ?Huawei Technology
>
> recompiled and the devices now show up... however, there are 4 of them:
>
> hugme@dragoncon# ls /dev/cuaU*
> /dev/cuaU0.0 ? ? ? ? ? ?/dev/cuaU0.1 ? ? ? ? ? ?/dev/cuaU0.2
> ?/dev/cuaU0.3
> /dev/cuaU0.0.init ? ? ? /dev/cuaU0.1.init ? ? ? /dev/cuaU0.2.init
> ?/dev/cuaU0.3.init
> /dev/cuaU0.0.lock ? ? ? /dev/cuaU0.1.lock ? ? ? /dev/cuaU0.2.lock
> ?/dev/cuaU0.3.lock
>
> is this a default? I haven't been able to get them to initilize yet...
> tried minicom this morning, I'm going to configure remote to try tip
> in just a bit....
>
>
> On Tue, Sep 1, 2009 at 9:46 PM, Hug Me<hugme@hugme.org> wrote:
>> I've been having all sorts of trouble with this card. I've tried it
>> several ways. umass in the kernel, umass loaded manually, umass not
>> loaded at all... u3g in loaded manually or in the kernel, ubsa loaded
>> manually or in the kernel. I can't seem to get it detected as anything
>> except a storage device. I've tried the camcontrol eject and when it
>> comes back I still don't see the device....
>>
>> here is some of what I see:
>>
>> significant lines from boot with device in place
>> ...
>> umass0: <HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/0.00,
>> addr 2> on uhub0
>> umass1: <HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/0.00,
>> addr 2> on uhub0
>> ...
>> (probe2:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
>> (probe2:umass-sim0:0:0:0): CAM Status: SCSI Status Error
>> (probe2:umass-sim0:0:0:0): SCSI Status: Check Condition
>> (probe2:umass-sim0:0:0:0): NOT READY asc:3a,0
>> (probe2:umass-sim0:0:0:0): Medium not present
>> (probe2:umass-sim0:0:0:0): Unretryable error
>> (probe3:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
>> (probe3:umass-sim1:1:0:0): CAM Status: SCSI Status Error
>> (probe3:umass-sim1:1:0:0): SCSI Status: Check Condition
>> (probe3:umass-sim1:1:0:0): NOT READY asc:3a,0
>> (probe3:umass-sim1:1:0:0): Medium not present
>> (probe3:umass-sim1:1:0:0): Unretryable error
>> (probe0:mpt0:0:8:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
>> (probe0:mpt0:0:8:0): CAM Status: SCSI Status Error
>> (probe0:mpt0:0:8:0): SCSI Status: Check Condition
>> (probe0:mpt0:0:8:0): UNIT ATTENTION asc:29,0
>> (probe0:mpt0:0:8:0): Power on, reset, or bus device reset occurred
>> (probe0:mpt0:0:8:0): Retrying Command (per Sense Data)
>> ses0 at mpt0 bus 0 target 8 lun 0
>> ses0: <IBM 25P3495a S320 ?1 1> Fixed Processor SCSI-2 device
>> ses0: 3.300MB/s transfers
>> ses0: SAF-TE Compliant Device
>> da0 at mpt0 bus 0 target 0 lun 0
>> da0: <LSILOGIC 1030 IM 1000> Fixed Direct Access SCSI-2 device
>> da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit)
>> da0: Command Queueing Enabled
>> da0: 34702MB (71071561 512 byte sectors: 255H 63S/T 4424C)
>> SMP: AP CPU #2 Launched!
>> SMP: AP CPU #1 Launched!
>> SMP: AP CPU #3 Launched!
>> da1 at umass-sim1 bus 1 target 0 lun 0
>> da1: <HUAWEI MMC Storage 2.31> Removable Direct Access SCSI-2 device
>> da1: 1.000MB/s transfers
>> da1: Attempt to query device size failed: NOT READY, Medium not present
>> cd0 at umass-sim0 bus 0 target 0 lun 0
>> cd0: <HUAWEI Mass Storage 2.31> Removable CD-ROM SCSI-2 device
>> cd0: 1.000MB/s transfers
>> cd0: Attempt to query device size failed: NOT READY, Medium not present
>>
>>
>> with umass not loaded:
>> Unknown USB device: vendor 0x12d1 product 0x1414 bus uhub0
>> ugen0: <HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/0.00,
>> addr 2> on uhub0
>>
>> # usbdevs -v
>> Controller /dev/usb0:
>> addr 1: full speed, self powered, config 1, OHCI root hub(0x0000),
>> (0x1166)(0x0000), rev 1.00
>> ?port 1 powered
>> ?port 2 addr 2: full speed, self powered, config 1, HUAWEI
>> Mobile(0x1414), HUAWEI Technology(0x12d1), rev 0.00
>> ?port 3 powered
>> ?port 4 powered
>>
>>
>> Thanks for your help!
>>
>>
>> --
>> ? ? ? ?*******************************************************************
>> ? ? ? ?Don't ever forget to
>> ? ? ? ? ? ? ? ?-*HUGME*-
>>
>> Yield to Temptation ... it may not pass your way again.
>> ? ? ? ? ? ? ? ?-- Lazarus Long, "Time Enough for Love"
>>
>
>
>
> --
> ? ? ? ?*******************************************************************
> ? ? ? ?Don't ever forget to
> ? ? ? ? ? ? ? ?-*HUGME*-
>
> Yield to Temptation ... it may not pass your way again.
> ? ? ? ? ? ? ? ?-- Lazarus Long, "Time Enough for Love"
>



-- 
        *******************************************************************
        Don't ever forget to
                -*HUGME*-

Yield to Temptation ... it may not pass your way again.
                -- Lazarus Long, "Time Enough for Love"
From mike at sentex.net  Fri Sep  4 19:21:30 2009
From: mike at sentex.net (Mike Tancsa)
Date: Fri Sep  4 19:21:36 2009
Subject: USB_ERR_IOERROR on cold boot, not warm boot
Message-ID: <200909041918.n84JI3S7040121@lava.sentex.ca>

Not sure if this is a faulty device or just a quirk as to how it 
works. But on cold boot (after a power cycle) it does not work. But 
if I do a soft reboot, it attaches no problem

Here is the diff on the boot verbose on the the cold boot vs warm boot

# diff -u bad.txt good.txt | egrep "^\+|^\-"
-usb_alloc_device:1586: set address 2 failed (USB_ERR_IOERROR, ignored)
-usb_alloc_device:1624: getting device descriptor at addr 2 failed, 
USB_ERR_IOERROR!
-usbd_req_re_enumerate:1539: addr=2, set address failed! 
(USB_ERR_IOERROR, ignored)
-usbd_req_re_enumerate:1553: getting device descriptor at addr 2 
failed, USB_ERR_IOERROR!
-usbd_req_re_enumerate:1539: addr=2, set address failed! 
(USB_ERR_IOERROR, ignored)
-usbd_req_re_enumerate:1553: getting device descriptor at addr 2 
failed, USB_ERR_IOERROR!
-ugen0.2: <(null)> at usbus0 (disconnected)
-uhub_reattach_port:435: could not allocate new device!
-ct_to_ts([2000-01-01 00:01:51]) = 946684911.000000000
-ct_to_ts([2000-01-01 00:01:51]) = 946684911.000000000
+ugen0.2: <HP> at usbus0
+u3g0: <Data Interface> on usbus0
+u3g0: Found 3 ports.
+ct_to_ts([2000-01-01 00:06:04]) = 946685164.000000000
+ct_to_ts([2000-01-01 00:06:04]) = 946685164.000000000


Is there something I can do to deal with this specific device 
differently in the driver ?  Its 8.0-BETA3 FreeBSD 8.0-BETA3 #2: Wed 
Sep  2  using the u3g driver.

alix# usbconfig dump_device_desc
ugen0.1: <OHCI root HUB AMD> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

   bLength = 0x0012
   bDescriptorType = 0x0001
   bcdUSB = 0x0100
   bDeviceClass = 0x0009
   bDeviceSubClass = 0x0000
   bDeviceProtocol = 0x0000
   bMaxPacketSize0 = 0x0040
   idVendor = 0x0000
   idProduct = 0x0000
   bcdDevice = 0x0100
   iManufacturer = 0x0001  <AMD>
   iProduct = 0x0002  <OHCI root HUB>
   iSerialNumber = 0x0000  <no string>
   bNumConfigurations = 0x0001

ugen1.1: <EHCI root HUB AMD> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON

   bLength = 0x0012
   bDescriptorType = 0x0001
   bcdUSB = 0x0200
   bDeviceClass = 0x0009
   bDeviceSubClass = 0x0000
   bDeviceProtocol = 0x0001
   bMaxPacketSize0 = 0x0040
   idVendor = 0x0000
   idProduct = 0x0000
   bcdDevice = 0x0100
   iManufacturer = 0x0001  <AMD>
   iProduct = 0x0002  <EHCI root HUB>
   iSerialNumber = 0x0000  <no string>
   bNumConfigurations = 0x0001

ugen0.2: <HP hs2300 HSDPA Broadband Wirel HP> at usbus0, cfg=0 
md=HOST spd=FULL (12Mbps) pwr=ON

   bLength = 0x0012
   bDescriptorType = 0x0001
   bcdUSB = 0x0110
   bDeviceClass = 0x0000
   bDeviceSubClass = 0x0000
   bDeviceProtocol = 0x0000
   bMaxPacketSize0 = 0x0040
   idVendor = 0x03f0
   idProduct = 0x1e1d
   bcdDevice = 0x0002
   iManufacturer = 0x0001  <HP>
   iProduct = 0x0002  <HP hs2300 HSDPA Broadband Wireless Module>
   iSerialNumber = 0x0000  <no string>
   bNumConfigurations = 0x0001


ugen0.2: <HP hs2300 HSDPA Broadband Wirel HP> at usbus0, cfg=0 
md=HOST spd=FULL (12Mbps) pwr=ON


  Configuration index 0

     bLength = 0x0009
     bDescriptorType = 0x0002
     wTotalLength = 0x0043
     bNumInterfaces = 0x0001
     bConfigurationValue = 0x0001
     iConfiguration = 0x0000  <no string>
     bmAttributes = 0x00e0
     bMaxPower = 0x0000

     Interface 0
       bLength = 0x0009
       bDescriptorType = 0x0004
       bInterfaceNumber = 0x0000
       bAlternateSetting = 0x0000
       bNumEndpoints = 0x0007
       bInterfaceClass = 0x00ff
       bInterfaceSubClass = 0x00ff
       bInterfaceProtocol = 0x00ff
       iInterface = 0x0003  <Data Interface>

      Endpoint 0
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0081
         bmAttributes = 0x0003
         wMaxPacketSize = 0x0010
         bInterval = 0x0080
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 1
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0082
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 2
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0002
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 3
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0084
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 4
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0004
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 5
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0085
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000

      Endpoint 6
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0005
         bmAttributes = 0x0002
         wMaxPacketSize = 0x0040
         bInterval = 0x0000
         bRefresh = 0x0000
         bSynchAddress = 0x0000



alix#


ati3
Manufacturer: Sierra Wireless, Inc.
Model: MC8775
Revision: H1_1_9_3MCAP C:/WS/FW/H1_1_9_3MCAP/MSM6280/SRC 2007/12/12 11:49:21
IMEI: xxxx
IMEI SV: 10
FSN: xxxx
3GPP Release 5
+GCAP: +CGSM,+DS,+ES



         ---Mike


--------------------------------------------------------------------
Mike Tancsa,                                      tel +1 519 651 3400
Sentex Communications,                            mike@sentex.net
Providing Internet since 1994                    www.sentex.net
Cambridge, Ontario Canada                         www.sentex.net/mike

From tavvva at seznam.cz  Sat Sep  5 00:33:11 2009
From: tavvva at seznam.cz (=?iso-8859-2?Q?Jarom=EDr=20C=E1p=EDk?=)
Date: Sat Sep  5 00:33:48 2009
Subject: kern/137806: USB keyboard doesn't work until it's unplugged
In-Reply-To: <200908152140.n7FLe7iN063575@freefall.freebsd.org>
Message-ID: <1858.4707-7260-1257771675-1252091184@seznam.cz>

Hello. 

Any news here?

Regards,
Jaromir.
From hselasky at c2i.net  Sat Sep  5 07:05:17 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Sep  5 07:05:53 2009
Subject: USB_ERR_IOERROR on cold boot, not warm boot
In-Reply-To: <200909041918.n84JI3S7040121@lava.sentex.ca>
References: <200909041918.n84JI3S7040121@lava.sentex.ca>
Message-ID: <200909050905.39112.hselasky@c2i.net>

On Friday 04 September 2009 21:21:41 Mike Tancsa wrote:
> Not sure if this is a faulty device or just a quirk as to how it
> works. But on cold boot (after a power cycle) it does not work. But
> if I do a soft reboot, it attaches no problem
>
> Here is the diff on the boot verbose on the the cold boot vs warm boot
>
> # diff -u bad.txt good.txt | egrep "^\+|^\-"
> -usb_alloc_device:1586: set address 2 failed (USB_ERR_IOERROR, ignored)
> -usb_alloc_device:1624: getting device descriptor at addr 2 failed,
> USB_ERR_IOERROR!
> -usbd_req_re_enumerate:1539: addr=2, set address failed!
> (USB_ERR_IOERROR, ignored)
> -usbd_req_re_enumerate:1553: getting device descriptor at addr 2
> failed, USB_ERR_IOERROR!
> -usbd_req_re_enumerate:1539: addr=2, set address failed!
> (USB_ERR_IOERROR, ignored)
> -usbd_req_re_enumerate:1553: getting device descriptor at addr 2
> failed, USB_ERR_IOERROR!
> -ugen0.2: <(null)> at usbus0 (disconnected)
> -uhub_reattach_port:435: could not allocate new device!
> -ct_to_ts([2000-01-01 00:01:51]) = 946684911.000000000
> -ct_to_ts([2000-01-01 00:01:51]) = 946684911.000000000
> +ugen0.2: <HP> at usbus0
> +u3g0: <Data Interface> on usbus0
> +u3g0: Found 3 ports.
> +ct_to_ts([2000-01-01 00:06:04]) = 946685164.000000000
> +ct_to_ts([2000-01-01 00:06:04]) = 946685164.000000000
>
>
> Is there something I can do to deal with this specific device
> differently in the driver ?  Its 8.0-BETA3 FreeBSD 8.0-BETA3 #2: Wed
> Sep  2  using the u3g driver.
>
> alix# usbconfig dump_device_desc
> ugen0.1: <OHCI root HUB AMD> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON
>
>    bLength = 0x0012
>    bDescriptorType = 0x0001
>    bcdUSB = 0x0100
>    bDeviceClass = 0x0009
>    bDeviceSubClass = 0x0000
>    bDeviceProtocol = 0x0000
>    bMaxPacketSize0 = 0x0040
>    idVendor = 0x0000
>    idProduct = 0x0000
>    bcdDevice = 0x0100
>    iManufacturer = 0x0001  <AMD>
>    iProduct = 0x0002  <OHCI root HUB>
>    iSerialNumber = 0x0000  <no string>
>    bNumConfigurations = 0x0001
>
> ugen1.1: <EHCI root HUB AMD> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
> pwr=ON
>
>    bLength = 0x0012
>    bDescriptorType = 0x0001
>    bcdUSB = 0x0200
>    bDeviceClass = 0x0009
>    bDeviceSubClass = 0x0000
>    bDeviceProtocol = 0x0001
>    bMaxPacketSize0 = 0x0040
>    idVendor = 0x0000
>    idProduct = 0x0000
>    bcdDevice = 0x0100
>    iManufacturer = 0x0001  <AMD>
>    iProduct = 0x0002  <EHCI root HUB>
>    iSerialNumber = 0x0000  <no string>
>    bNumConfigurations = 0x0001
>
> ugen0.2: <HP hs2300 HSDPA Broadband Wirel HP> at usbus0, cfg=0
> md=HOST spd=FULL (12Mbps) pwr=ON
>
>    bLength = 0x0012
>    bDescriptorType = 0x0001
>    bcdUSB = 0x0110
>    bDeviceClass = 0x0000
>    bDeviceSubClass = 0x0000
>    bDeviceProtocol = 0x0000
>    bMaxPacketSize0 = 0x0040
>    idVendor = 0x03f0
>    idProduct = 0x1e1d
>    bcdDevice = 0x0002
>    iManufacturer = 0x0001  <HP>
>    iProduct = 0x0002  <HP hs2300 HSDPA Broadband Wireless Module>
>    iSerialNumber = 0x0000  <no string>
>    bNumConfigurations = 0x0001
>
>
> ugen0.2: <HP hs2300 HSDPA Broadband Wirel HP> at usbus0, cfg=0
> md=HOST spd=FULL (12Mbps) pwr=ON
>
>
>   Configuration index 0
>
>      bLength = 0x0009
>      bDescriptorType = 0x0002
>      wTotalLength = 0x0043
>      bNumInterfaces = 0x0001
>      bConfigurationValue = 0x0001
>      iConfiguration = 0x0000  <no string>
>      bmAttributes = 0x00e0
>      bMaxPower = 0x0000
>
>      Interface 0
>        bLength = 0x0009
>        bDescriptorType = 0x0004
>        bInterfaceNumber = 0x0000
>        bAlternateSetting = 0x0000
>        bNumEndpoints = 0x0007
>        bInterfaceClass = 0x00ff
>        bInterfaceSubClass = 0x00ff
>        bInterfaceProtocol = 0x00ff
>        iInterface = 0x0003  <Data Interface>
>
>       Endpoint 0
>          bLength = 0x0007
>          bDescriptorType = 0x0005
>          bEndpointAddress = 0x0081
>          bmAttributes = 0x0003
>          wMaxPacketSize = 0x0010
>          bInterval = 0x0080
>          bRefresh = 0x0000
>          bSynchAddress = 0x0000
>
>       Endpoint 1
>          bLength = 0x0007
>          bDescriptorType = 0x0005
>          bEndpointAddress = 0x0082
>          bmAttributes = 0x0002
>          wMaxPacketSize = 0x0040
>          bInterval = 0x0000
>          bRefresh = 0x0000
>          bSynchAddress = 0x0000
>
>       Endpoint 2
>          bLength = 0x0007
>          bDescriptorType = 0x0005
>          bEndpointAddress = 0x0002
>          bmAttributes = 0x0002
>          wMaxPacketSize = 0x0040
>          bInterval = 0x0000
>          bRefresh = 0x0000
>          bSynchAddress = 0x0000
>
>       Endpoint 3
>          bLength = 0x0007
>          bDescriptorType = 0x0005
>          bEndpointAddress = 0x0084
>          bmAttributes = 0x0002
>          wMaxPacketSize = 0x0040
>          bInterval = 0x0000
>          bRefresh = 0x0000
>          bSynchAddress = 0x0000
>
>       Endpoint 4
>          bLength = 0x0007
>          bDescriptorType = 0x0005
>          bEndpointAddress = 0x0004
>          bmAttributes = 0x0002
>          wMaxPacketSize = 0x0040
>          bInterval = 0x0000
>          bRefresh = 0x0000
>          bSynchAddress = 0x0000
>
>       Endpoint 5
>          bLength = 0x0007
>          bDescriptorType = 0x0005
>          bEndpointAddress = 0x0085
>          bmAttributes = 0x0002
>          wMaxPacketSize = 0x0040
>          bInterval = 0x0000
>          bRefresh = 0x0000
>          bSynchAddress = 0x0000
>
>       Endpoint 6
>          bLength = 0x0007
>          bDescriptorType = 0x0005
>          bEndpointAddress = 0x0005
>          bmAttributes = 0x0002
>          wMaxPacketSize = 0x0040
>          bInterval = 0x0000
>          bRefresh = 0x0000
>          bSynchAddress = 0x0000
>
>
>
> alix#
>
>
> ati3
> Manufacturer: Sierra Wireless, Inc.
> Model: MC8775
> Revision: H1_1_9_3MCAP C:/WS/FW/H1_1_9_3MCAP/MSM6280/SRC 2007/12/12
> 11:49:21 IMEI: xxxx
> IMEI SV: 10
> FSN: xxxx
> 3GPP Release 5
> +GCAP: +CGSM,+DS,+ES
>

Does this device have a button to enable it? Does it help pressing that 
button?

One idea is to not power down the port which obviously gives the device power 
on failures.

--HPS
From citycat4 at ngs.ru  Sat Sep  5 12:35:30 2009
From: citycat4 at ngs.ru (Rashid N. Achilov)
Date: Sat Sep  5 12:36:03 2009
Subject: kern/137806: USB keyboard doesn't work until it's unplugged
In-Reply-To: <1858.4707-7260-1257771675-1252091184@seznam.cz>
References: <1858.4707-7260-1257771675-1252091184@seznam.cz>
Message-ID: <200909051905.21126.citycat4@ngs.ru>

On Saturday 05 September 2009, Jarom?r C?p?k wrote:
> Hello. 
> 
> Any news here?

On 7.x - none. HID devices still uninitalized, LPT OK (now I have USB printer 
Samsung ML-1640). I suspect, that team still wait for 8.0-RELEASE and, when 
it will occured, says "Upgrade your version to latest, 7.x won't support".

Personaly I'd like to try install USB2 - probably it wll solve this problem. 

Also usb/138175 - is anybody takes it? Or now I have "secret key" - to boot, 
insert USB or card in reader 

:ROFL:
-- 
   With Best Regards.
   Rashid N. Achilov (RNA1-RIPE), Web: http://openoffice.mirahost.ru
   E-Mail: shelton [???!] vmfree [???] askd [???] ru
   PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A
From mike at sentex.net  Sat Sep  5 12:53:29 2009
From: mike at sentex.net (Mike Tancsa)
Date: Sat Sep  5 12:53:41 2009
Subject: USB_ERR_IOERROR on cold boot, not warm boot
In-Reply-To: <200909050905.39112.hselasky@c2i.net>
References: <200909041918.n84JI3S7040121@lava.sentex.ca>
	<200909050905.39112.hselasky@c2i.net>
Message-ID: <200909051250.n85Co1Ve046513@lava.sentex.ca>

At 03:05 AM 9/5/2009, Hans Petter Selasky wrote:
>On Friday 04 September 2009 21:21:41 Mike Tancsa wrote:
> > Not sure if this is a faulty device or just a quirk as to how it
> > works. But on cold boot (after a power cycle) it does not work. But
> > if I do a soft reboot, it attaches no problem
> >
> > Here is the diff on the boot verbose on the the cold boot vs warm boot
> >
> > # diff -u bad.txt good.txt | egrep "^\+|^\-"
> > -usb_alloc_device:1586: set address 2 failed (USB_ERR_IOERROR, ignored)
> > -usb_alloc_device:1624: getting device descriptor at addr 2 failed,
> > USB_ERR_IOERROR!
> > -usbd_req_re_enumerate:1539: addr=2, set address failed!
> > (USB_ERR_IOERROR, ignored)
> > -usbd_req_re_enumerate:1553: getting device descriptor at addr 2
> > failed, USB_ERR_IOERROR!
> > -usbd_req_re_enumerate:1539: addr=2, set address failed!
> > (USB_ERR_IOERROR, ignored)
> > -usbd_req_re_enumerate:1553: getting device descriptor at addr 2
> > failed, USB_ERR_IOERROR!
> > -ugen0.2: <(null)> at usbus0 (disconnected)
> > -uhub_reattach_port:435: could not allocate new device!
> > -ct_to_ts([2000-01-01 00:01:51]) = 946684911.000000000
> > -ct_to_ts([2000-01-01 00:01:51]) = 946684911.000000000
> > +ugen0.2: <HP> at usbus0
> > +u3g0: <Data Interface> on usbus0
> > +u3g0: Found 3 ports.
> > +ct_to_ts([2000-01-01 00:06:04]) = 946685164.000000000
> > +ct_to_ts([2000-01-01 00:06:04]) = 946685164.000000000
> >
> >
> > Is there something I can do to deal with this specific device
> > differently in the driver ?  Its 8.0-BETA3 FreeBSD 8.0-BETA3 #2: Wed
> > Sep  2  using the u3g driver.
>
>Does this device have a button to enable it? Does it help pressing that
>button?
>
>One idea is to not power down the port which obviously gives the device power
>on failures.

Hi,
         Its a mini-pciExpress card that is designed to be inside a 
laptop, or in this case embedded device.  So no buttons.  The other 
similar devices I have dont exhibit this behaviour so it seems to be 
quirky to this particular model.

Here is the card and board

http://eastar4.com/ebay/SierraMC8775-2.jpg
http://www.pcengines.ch/alix6b2.htm

         ---Mike



--------------------------------------------------------------------
Mike Tancsa,                                      tel +1 519 651 3400
Sentex Communications,                            mike@sentex.net
Providing Internet since 1994                    www.sentex.net
Cambridge, Ontario Canada                         www.sentex.net/mike

From yerenkow at gmail.com  Sat Sep  5 13:30:07 2009
From: yerenkow at gmail.com (Alexander Yerenkow)
Date: Sat Sep  5 13:30:18 2009
Subject: usb/138548: usb devices periodically have unknown activity
Message-ID: <200909051328.n85DSGZV089449@www.freebsd.org>


>Number:         138548
>Category:       usb
>Synopsis:       usb devices periodically have unknown activity
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Sep 05 13:30:06 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Alexander Yerenkow
>Release:        7.2
>Organization:
>Environment:
FreeBSD pcbsd 7.2-STABLE FreeBSD 7.2-STABLE #6: Mon Jun 15 19:18:56 EDT 2009 root@build7x32.pcbsd.org:/usr/obj/pcbsd-build72/cvs/7.2-src/sys/PCBSD i386
>Description:
My usb devices have light indicators on them.
When I put usb flash/bluetooth adapter in PC with windows, it read it for a few seconds, and after that nothing, no actifity, no lights. Only If I copy/read something, then lights are seen.
In FreeBSD I see other behaviour, Bluetooth adapter blinks about every 2 seconds; Corsair Voyager GT (usb flash disk) - in about 1-1,1 seconds.
That's wrong, I think.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From hselasky at c2i.net  Sat Sep  5 15:22:55 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Sep  5 15:23:08 2009
Subject: kern/137806: USB keyboard doesn't work until it's unplugged
In-Reply-To: <200909051905.21126.citycat4@ngs.ru>
References: <1858.4707-7260-1257771675-1252091184@seznam.cz>
	<200909051905.21126.citycat4@ngs.ru>
Message-ID: <200909051723.16646.hselasky@c2i.net>

On Saturday 05 September 2009 14:05:20 Rashid N. Achilov wrote:
> On Saturday 05 September 2009, Jarom?r C?p?k wrote:
> > Hello.
> >
> > Any news here?
>
> On 7.x - none. HID devices still uninitalized, LPT OK (now I have USB
> printer Samsung ML-1640). I suspect, that team still wait for 8.0-RELEASE
> and, when it will occured, says "Upgrade your version to latest, 7.x won't
> support".
>
> Personaly I'd like to try install USB2 - probably it wll solve this
> problem.
>
> Also usb/138175 - is anybody takes it? Or now I have "secret key" - to
> boot, insert USB or card in reader
>

Is this the same for different branded USB keyboards?

--HPS
From citycat4 at ngs.ru  Sat Sep  5 15:50:31 2009
From: citycat4 at ngs.ru (Rashid N. Achilov)
Date: Sat Sep  5 15:50:38 2009
Subject: kern/137806: USB keyboard doesn't work until it's unplugged
In-Reply-To: <200909051723.16646.hselasky@c2i.net>
References: <1858.4707-7260-1257771675-1252091184@seznam.cz>
	<200909051905.21126.citycat4@ngs.ru>
	<200909051723.16646.hselasky@c2i.net>
Message-ID: <200909052245.55823.citycat4@ngs.ru>

On Saturday 05 September 2009, Hans Petter Selasky wrote:
> 
> Is this the same for different branded USB keyboards?

My hardware: m/b Gigabyte GA-P35-S3, Intel ICH9 P35-based chipset. Keyboard - 
Microsoft Wireless 5000 (of course completed mouse don't work), mouse - 
Logitech LX7. Any boot HID devices (kb and mouse) does not init, in spite of 
init all another devices (USB flash, USB printer). So I should any boot 
plug-unplug kb ad mouse, this is very uncomfortable.

When need any additional data, they will be sent.
-- 
   With Best Regards.
   Rashid N. Achilov (RNA1-RIPE), Web: http://openoffice.mirahost.ru
   E-Mail: shelton [???!] vmfree [???] askd [???] ru
   PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A
From hselasky at c2i.net  Sat Sep  5 15:57:58 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Sep  5 15:58:05 2009
Subject: kern/137806: USB keyboard doesn't work until it's unplugged
In-Reply-To: <200909052245.55823.citycat4@ngs.ru>
References: <1858.4707-7260-1257771675-1252091184@seznam.cz>
	<200909051723.16646.hselasky@c2i.net>
	<200909052245.55823.citycat4@ngs.ru>
Message-ID: <200909051758.20393.hselasky@c2i.net>

On Saturday 05 September 2009 17:45:55 Rashid N. Achilov wrote:
> On Saturday 05 September 2009, Hans Petter Selasky wrote:
> > Is this the same for different branded USB keyboards?
>
> My hardware: m/b Gigabyte GA-P35-S3, Intel ICH9 P35-based chipset. Keyboard
> - Microsoft Wireless 5000 (of course completed mouse don't work), mouse -
> Logitech LX7. Any boot HID devices (kb and mouse) does not init, in spite
> of init all another devices (USB flash, USB printer). So I should any boot
> plug-unplug kb ad mouse, this is very uncomfortable.
>
> When need any additional data, they will be sent.

Hi,

I looked at the error report and noticed this problem was reported on 7.2. I'm 
mostly working on issues reported on 8.x. Is this issue the same on 7.2 and 
8.0-BETA3, just for reference?

--HPS

From datastream.freecity at gmail.com  Sat Sep  5 17:06:08 2009
From: datastream.freecity at gmail.com (datastream)
Date: Sat Sep  5 17:06:40 2009
Subject: Problem with USB mass storage
Message-ID: <4AA296D2.4010503@gmail.com>

hi,
    my usb hdd does not work.it seems broken again.


#uname -a
FreeBSD datastream-laptop.people.163.org 9.0-CURRENT FreeBSD 9.0-CURRENT
#5 r196859: Sat Sep  5 21:27:55 CST 2009    
root@datastream-laptop.people.163.org:/usr/obj/usr/home/datastream/freebsd/sys/G8laptop 
amd64


usbd_set_config_index:523: could not read device status: USB_ERR_SHORT_XFER
ugen6.2: <JMicron> at usbus6
umass0: <MSC Bulk-Only Transfer> on usbus6
umass0:  SCSI over Bulk-Only; quirks = 0x0000
umass0:2:0:-1: Attached to scbus2
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Maxtor 7 Y250M0 11W0> Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C)
ugen6.2: <JMicron> at usbus6 (disconnected)
umass0: at uhub6, port 2, addr 2 (disconnected)
(da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x3f, scsi
status == 0x0
(da0:umass-sim0:0:0:0): lost device
(da0:umass-sim0:0:0:0): removing device entry



Thanks,
Kevin
From hselasky at c2i.net  Sat Sep  5 17:28:23 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Sep  5 17:28:29 2009
Subject: Problem with USB mass storage
In-Reply-To: <4AA296D2.4010503@gmail.com>
References: <4AA296D2.4010503@gmail.com>
Message-ID: <200909051928.44393.hselasky@c2i.net>

On Saturday 05 September 2009 18:50:26 datastream wrote:
> hi,
>     my usb hdd does not work.it seems broken again.
>
>
> #uname -a
> FreeBSD datastream-laptop.people.163.org 9.0-CURRENT FreeBSD 9.0-CURRENT
> #5 r196859: Sat Sep  5 21:27:55 CST 2009
> root@datastream-laptop.people.163.org:/usr/obj/usr/home/datastream/freebsd/
>sys/G8laptop amd64
>
>
> usbd_set_config_index:523: could not read device status: USB_ERR_SHORT_XFER
> ugen6.2: <JMicron> at usbus6
> umass0: <MSC Bulk-Only Transfer> on usbus6
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:2:0:-1: Attached to scbus2
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <Maxtor 7 Y250M0 11W0> Fixed Direct Access SCSI-2 device
> da0: 40.000MB/s transfers
> da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C)
> ugen6.2: <JMicron> at usbus6 (disconnected)
> umass0: at uhub6, port 2, addr 2 (disconnected)
> (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x3f, scsi
> status == 0x0
> (da0:umass-sim0:0:0:0): lost device
> (da0:umass-sim0:0:0:0): removing device entry
>

Try adding a quirk to sys/dev/usb/storage/umass.c

--HPS

From citycat4 at ngs.ru  Sat Sep  5 17:40:20 2009
From: citycat4 at ngs.ru (Rashid N. Achilov)
Date: Sat Sep  5 17:40:27 2009
Subject: kern/137806: USB keyboard doesn't work until it's unplugged
In-Reply-To: <200909051758.20393.hselasky@c2i.net>
References: <1858.4707-7260-1257771675-1252091184@seznam.cz>
	<200909052245.55823.citycat4@ngs.ru>
	<200909051758.20393.hselasky@c2i.net>
Message-ID: <200909060035.48886.citycat4@ngs.ru>

On Saturday 05 September 2009, Hans Petter Selasky wrote:

> I looked at the error report and noticed this problem was reported on 7.2. 
I'm 
> mostly working on issues reported on 8.x. Is this issue the same on 7.2 and 
> 8.0-BETA3, just for reference?

I don't know, I haven't any 8.x installations. On my side I'll install 8.x 
only after 8.1 releasing - after installing 4.0 I have hard belief, 
that "dot-zero release" is only another name "widely testing public beta".
-- 
   With Best Regards.
   Rashid N. Achilov (RNA1-RIPE), Web: http://openoffice.mirahost.ru
   E-Mail: shelton [???!] vmfree [???] askd [???] ru
   PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A
From ralph at imada.sdu.dk  Sat Sep  5 18:18:08 2009
From: ralph at imada.sdu.dk (Ralph Zitz)
Date: Sat Sep  5 18:18:15 2009
Subject: USB quirks
Message-ID: <4AA2A5EF.7090100@imada.sdu.dk>

Hello,
How does one know which quirks to add? At the moment I'm getting the 
following messages when attaching my device:

ugen4.2: <vendor 0x0781> at 
usbus4                                                                                                

umass0: <vendor 0x0781 product 0x5406, class 0/0, rev 2.00/2.00, addr 2> 
on usbus4
umass0:  SCSI over Bulk-Only; quirks = 0x0000
umass0:3:0:-1: Attached to scbus3
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:3a,0
(probe0:umass-sim0:0:0:0): Medium not present
(probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <SanDisk Cruzer 7.01> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 15286MB (31306239 512 byte sectors: 255H 63S/T 1948C)
xptioctl: pass driver is not in the kernel
xptioctl: put "device pass" in your kernel config file
(probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
(probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:1): UNIT ATTENTION asc:29,0
(probe0:umass-sim0:0:0:1): Power on, reset, or bus device reset occurred
(probe0:umass-sim0:0:0:1): Retrying Command (per Sense Data)
(probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
(probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:1): NOT READY asc:3a,0
(probe0:umass-sim0:0:0:1): Medium not present
(probe0:umass-sim0:0:0:1): Unretryable error
cd1 at umass-sim0 bus 0 target 0 lun 1
cd1: <SanDisk Cruzer 7.01> Removable CD-ROM SCSI-0 device
cd1: 40.000MB/s transfers
cd1: cd present [49151 x 2048 byte records]
GEOM: da0: media size does not match label.

The usbstick was formatted with fat32. In /dev I have da0 and da0a 
listed, yet neither can be mounted:

sudo mount_msdosfs /dev/da0a /home/ralph/mnt
mount_msdosfs: /dev/da0a: Invalid argument

sudo mount_msdosfs /dev/da0 /home/ralph/mnt
mount_msdosfs: /dev/da0: Invalid argument

I also don't understand the message about the pass device not being in 
the kernel conf - it is.

Any help would be greatly appreciated.

Regards,
Ralph.
From ralph at imada.sdu.dk  Sat Sep  5 18:21:18 2009
From: ralph at imada.sdu.dk (Ralph Zitz)
Date: Sat Sep  5 18:21:24 2009
Subject: USB quirks
In-Reply-To: <4AA2A5EF.7090100@imada.sdu.dk>
References: <4AA2A5EF.7090100@imada.sdu.dk>
Message-ID: <4AA2AC17.8040802@imada.sdu.dk>

Ralph Zitz wrote:
> Hello,
> How does one know which quirks to add? At the moment I'm getting the 
> following messages when attaching my device:
>
> ugen4.2: <vendor 0x0781> at 
> usbus4                                                                                                
>
> umass0: <vendor 0x0781 product 0x5406, class 0/0, rev 2.00/2.00, addr 
> 2> on usbus4
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:3:0:-1: Attached to scbus3
> (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
> (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
> (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
> (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:3a,0
> (probe0:umass-sim0:0:0:0): Medium not present
> (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <SanDisk Cruzer 7.01> Removable Direct Access SCSI-0 device
> da0: 40.000MB/s transfers
> da0: 15286MB (31306239 512 byte sectors: 255H 63S/T 1948C)
> xptioctl: pass driver is not in the kernel
> xptioctl: put "device pass" in your kernel config file
> (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
> (probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
> (probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
> (probe0:umass-sim0:0:0:1): UNIT ATTENTION asc:29,0
> (probe0:umass-sim0:0:0:1): Power on, reset, or bus device reset occurred
> (probe0:umass-sim0:0:0:1): Retrying Command (per Sense Data)
> (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
> (probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
> (probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
> (probe0:umass-sim0:0:0:1): NOT READY asc:3a,0
> (probe0:umass-sim0:0:0:1): Medium not present
> (probe0:umass-sim0:0:0:1): Unretryable error
> cd1 at umass-sim0 bus 0 target 0 lun 1
> cd1: <SanDisk Cruzer 7.01> Removable CD-ROM SCSI-0 device
> cd1: 40.000MB/s transfers
> cd1: cd present [49151 x 2048 byte records]
> GEOM: da0: media size does not match label.
>
> The usbstick was formatted with fat32. In /dev I have da0 and da0a 
> listed, yet neither can be mounted:
>
> sudo mount_msdosfs /dev/da0a /home/ralph/mnt
> mount_msdosfs: /dev/da0a: Invalid argument
>
> sudo mount_msdosfs /dev/da0 /home/ralph/mnt
> mount_msdosfs: /dev/da0: Invalid argument
>
> I also don't understand the message about the pass device not being in 
> the kernel conf - it is.
>
> Any help would be greatly appreciated.
>
> Regards,
> Ralph.
> _______________________________________________
> 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"
I forgot to mention:
uname -a:
FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #17 r196849: Sat Sep  5 09:35:27 
CEST 2009  amd64
From bruce at cran.org.uk  Sat Sep  5 22:20:04 2009
From: bruce at cran.org.uk (Bruce Cran)
Date: Sat Sep  5 22:20:10 2009
Subject: usb/138559: [usb8] uether sysctl handler doesn't NUL-terminate the
	string
Message-ID: <200909052214.n85ME42B047658@www.freebsd.org>


>Number:         138559
>Category:       usb
>Synopsis:       [usb8] uether sysctl handler doesn't NUL-terminate the string
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Sep 05 22:20:03 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Bruce Cran
>Release:        8.0-BETA3
>Organization:
>Environment:
FreeBSD gluon.draftnet 8.0-BETA3 FreeBSD 8.0-BETA3 #1: Fri Sep  4 09:20:32 BST 2009     brucec@gluon.draftnet:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
The sysctl handler in sys/dev/usb/net/usb_ethernet.c line 143 doesn't NUL-terminate the sysctl string returned to the user because it passes the length as "strlen(name)" instead of "strlen(name)+1".
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- usb_ethernet.c.orig	2009-09-05 21:35:09.000000000 +0100
+++ usb_ethernet.c	2009-09-05 21:36:18.000000000 +0100
@@ -146,7 +146,7 @@
 	const char *name;
 
 	name = device_get_nameunit(ue->ue_dev);
-	return SYSCTL_OUT(req, name, strlen(name));
+	return SYSCTL_OUT(req, name, strlen(name) + 1);
 }
 
 int


>Release-Note:
>Audit-Trail:
>Unformatted:
From bruce at cran.org.uk  Sun Sep  6 05:40:01 2009
From: bruce at cran.org.uk (Bruce Cran)
Date: Sun Sep  6 05:40:07 2009
Subject: usb/138563: [usb8] [patch] Increase buffer sizes to accomodate
	longer USB strings
Message-ID: <200909060537.n865bJeL043791@www.freebsd.org>


>Number:         138563
>Category:       usb
>Synopsis:       [usb8] [patch] Increase buffer sizes to accomodate longer USB strings
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 06 05:40:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Bruce Cran
>Release:        8.0-BETA4
>Organization:
>Environment:
FreeBSD gluon.draftnet 8.0-BETA4 FreeBSD 8.0-BETA4 #1: Sun Sep  6 06:09:25 BST 2009     brucec@gluon.draftnet:/usr/obj/usr/src/sys/MYKERNEL  i386
>Description:
My USB mouse is detected as:

ums0: <Microsoft Microsoft 3-Button Mouse with I, class 0/0, rev 1.10/3.00, addr 3> on usbus3

The product name stored in the device is "Microsoft 3-Button Mouse with IntelliEye(TM)"

The string gets truncated because the 'temp' buffer in sys/dev/usb/usb_device.c line 2154 only has enough space for 32 wide characters; according to http://msdn.microsoft.com/en-us/library/ms790920.aspx USB allows strings to be up to 126 wide characters.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- usb_device.c.orig	2009-09-06 06:14:44.000000000 +0100
+++ usb_device.c	2009-09-06 06:15:06.000000000 +0100
@@ -2151,7 +2151,7 @@
 #ifdef USB_VERBOSE
 	const struct usb_knowndev *kdp;
 #endif
-	char temp[64];
+	char temp[255];
 	uint16_t vendor_id;
 	uint16_t product_id;
 
--- usb_bus.h.orig	2009-09-06 06:15:12.000000000 +0100
+++ usb_bus.h	2009-09-06 06:15:20.000000000 +0100
@@ -101,7 +101,7 @@
 	union {
 		struct usb_hw_ep_scratch hw_ep_scratch[1];
 		struct usb_temp_setup temp_setup[1];
-		uint8_t	data[128];
+		uint8_t	data[255];
 	}	scratch[1];
 };
 


>Release-Note:
>Audit-Trail:
>Unformatted:
From hselasky at c2i.net  Sun Sep  6 06:07:37 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Sep  6 06:07:44 2009
Subject: usb/138559: [usb8] uether sysctl handler doesn't NUL-terminate
	the string
In-Reply-To: <200909052214.n85ME42B047658@www.freebsd.org>
References: <200909052214.n85ME42B047658@www.freebsd.org>
Message-ID: <200909060807.59357.hselasky@c2i.net>

On Sunday 06 September 2009 00:14:04 Bruce Cran wrote:
> >Number:         138559
> >Category:       usb
> >Synopsis:       [usb8] uether sysctl handler doesn't NUL-terminate the
> > string Confidential:   no
> >Severity:       non-critical
> >Priority:       low
> >Responsible:    freebsd-usb
> >State:          open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Sat Sep 05 22:20:03 UTC 2009
> >Closed-Date:
> >Last-Modified:
> >Originator:     Bruce Cran
> >Release:        8.0-BETA3
> >Organization:
> >Environment:
>
> FreeBSD gluon.draftnet 8.0-BETA3 FreeBSD 8.0-BETA3 #1: Fri Sep  4 09:20:32
> BST 2009     brucec@gluon.draftnet:/usr/obj/usr/src/sys/GENERIC  i386
>
> >Description:
>
> The sysctl handler in sys/dev/usb/net/usb_ethernet.c line 143 doesn't
> NUL-terminate the sysctl string returned to the user because it passes the
> length as "strlen(name)" instead of "strlen(name)+1".
>
> >How-To-Repeat:
> >
> >Fix:
>
> Patch attached with submission follows:
>
> --- usb_ethernet.c.orig	2009-09-05 21:35:09.000000000 +0100
> +++ usb_ethernet.c	2009-09-05 21:36:18.000000000 +0100
> @@ -146,7 +146,7 @@
>  	const char *name;
>
>  	name = device_get_nameunit(ue->ue_dev);
> -	return SYSCTL_OUT(req, name, strlen(name));
> +	return SYSCTL_OUT(req, name, strlen(name) + 1);
>  }
>
>  int
>
> >Release-Note:
> >Audit-Trail:
> >Unformatted:

Hi,

When plugging an USB ethernet adapter and printing out all sysctls, the parent 
string does not look corrupt. Are you sure that the terminating zero is not 
inserted somewhere else?

--HPS
From hselasky at c2i.net  Sun Sep  6 06:10:03 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Sep  6 06:10:09 2009
Subject: usb/138559: [usb8] uether sysctl handler doesn't NUL-terminate
	the string
Message-ID: <200909060610.n866A3ic081257@freefall.freebsd.org>

The following reply was made to PR usb/138559; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Bruce Cran <bruce@cran.org.uk>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/138559: [usb8] uether sysctl handler doesn't NUL-terminate the string
Date: Sun, 6 Sep 2009 08:07:58 +0200

 On Sunday 06 September 2009 00:14:04 Bruce Cran wrote:
 > >Number:         138559
 > >Category:       usb
 > >Synopsis:       [usb8] uether sysctl handler doesn't NUL-terminate the
 > > string Confidential:   no
 > >Severity:       non-critical
 > >Priority:       low
 > >Responsible:    freebsd-usb
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Sat Sep 05 22:20:03 UTC 2009
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Bruce Cran
 > >Release:        8.0-BETA3
 > >Organization:
 > >Environment:
 >
 > FreeBSD gluon.draftnet 8.0-BETA3 FreeBSD 8.0-BETA3 #1: Fri Sep  4 09:20:32
 > BST 2009     brucec@gluon.draftnet:/usr/obj/usr/src/sys/GENERIC  i386
 >
 > >Description:
 >
 > The sysctl handler in sys/dev/usb/net/usb_ethernet.c line 143 doesn't
 > NUL-terminate the sysctl string returned to the user because it passes the
 > length as "strlen(name)" instead of "strlen(name)+1".
 >
 > >How-To-Repeat:
 > >
 > >Fix:
 >
 > Patch attached with submission follows:
 >
 > --- usb_ethernet.c.orig	2009-09-05 21:35:09.000000000 +0100
 > +++ usb_ethernet.c	2009-09-05 21:36:18.000000000 +0100
 > @@ -146,7 +146,7 @@
 >  	const char *name;
 >
 >  	name = device_get_nameunit(ue->ue_dev);
 > -	return SYSCTL_OUT(req, name, strlen(name));
 > +	return SYSCTL_OUT(req, name, strlen(name) + 1);
 >  }
 >
 >  int
 >
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 
 Hi,
 
 When plugging an USB ethernet adapter and printing out all sysctls, the parent 
 string does not look corrupt. Are you sure that the terminating zero is not 
 inserted somewhere else?
 
 --HPS
From hselasky at c2i.net  Sun Sep  6 06:57:06 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Sep  6 06:57:12 2009
Subject: usb/138563: [usb8] [patch] Increase buffer sizes to accomodate
	longer USB strings
In-Reply-To: <200909060537.n865bJeL043791@www.freebsd.org>
References: <200909060537.n865bJeL043791@www.freebsd.org>
Message-ID: <200909060857.28707.hselasky@c2i.net>

On Sunday 06 September 2009 07:37:20 Bruce Cran wrote:
> Bruce Cran

Can you try the following patch and report back?

http://perforce.freebsd.org/chv.cgi?CH=168223

--HPS
From hselasky at c2i.net  Sun Sep  6 07:00:17 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Sep  6 07:00:27 2009
Subject: usb/138563: [usb8] [patch] Increase buffer sizes to accomodate
	longer USB strings
Message-ID: <200909060700.n8670Gsp035328@freefall.freebsd.org>

The following reply was made to PR usb/138563; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Bruce Cran <bruce@cran.org.uk>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/138563: [usb8] [patch] Increase buffer sizes to accomodate longer USB strings
Date: Sun, 6 Sep 2009 08:57:27 +0200

 On Sunday 06 September 2009 07:37:20 Bruce Cran wrote:
 > Bruce Cran
 
 Can you try the following patch and report back?
 
 http://perforce.freebsd.org/chv.cgi?CH=168223
 
 --HPS
From dorian.buettner at gmx.de  Sun Sep  6 08:09:54 2009
From: dorian.buettner at gmx.de (=?ISO-8859-1?Q?Dorian_B=FCttner?=)
Date: Sun Sep  6 08:10:01 2009
Subject: USB quirks
In-Reply-To: <4AA2AC17.8040802@imada.sdu.dk>
References: <4AA2A5EF.7090100@imada.sdu.dk> <4AA2AC17.8040802@imada.sdu.dk>
Message-ID: <4AA3680E.6030400@gmx.de>

Ralph Zitz schrieb:
> Ralph Zitz wrote:
>> Hello,
>> How does one know which quirks to add? At the moment I'm getting the 
>> following messages when attaching my device:
>>
>> ugen4.2: <vendor 0x0781> at 
>> usbus4                                                                                                
>>
>> umass0: <vendor 0x0781 product 0x5406, class 0/0, rev 2.00/2.00, addr 
>> 2> on usbus4
>> umass0:  SCSI over Bulk-Only; quirks = 0x0000
>> umass0:3:0:-1: Attached to scbus3
>> (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
>> (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
>> (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
>> (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:3a,0
>> (probe0:umass-sim0:0:0:0): Medium not present
>> (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
>> da0 at umass-sim0 bus 0 target 0 lun 0
>> da0: <SanDisk Cruzer 7.01> Removable Direct Access SCSI-0 device
>> da0: 40.000MB/s transfers
>> da0: 15286MB (31306239 512 byte sectors: 255H 63S/T 1948C)
>> xptioctl: pass driver is not in the kernel
>> xptioctl: put "device pass" in your kernel config file
>> (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
>> (probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
>> (probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
>> (probe0:umass-sim0:0:0:1): UNIT ATTENTION asc:29,0
>> (probe0:umass-sim0:0:0:1): Power on, reset, or bus device reset occurred
>> (probe0:umass-sim0:0:0:1): Retrying Command (per Sense Data)
>> (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
>> (probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
>> (probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
>> (probe0:umass-sim0:0:0:1): NOT READY asc:3a,0
>> (probe0:umass-sim0:0:0:1): Medium not present
>> (probe0:umass-sim0:0:0:1): Unretryable error
>> cd1 at umass-sim0 bus 0 target 0 lun 1
>> cd1: <SanDisk Cruzer 7.01> Removable CD-ROM SCSI-0 device
>> cd1: 40.000MB/s transfers
>> cd1: cd present [49151 x 2048 byte records]
>> GEOM: da0: media size does not match label.
>>
>> The usbstick was formatted with fat32. In /dev I have da0 and da0a 
>> listed, yet neither can be mounted:
>>
>> sudo mount_msdosfs /dev/da0a /home/ralph/mnt
>> mount_msdosfs: /dev/da0a: Invalid argument
>>
>> sudo mount_msdosfs /dev/da0 /home/ralph/mnt
>> mount_msdosfs: /dev/da0: Invalid argument
>>
>> I also don't understand the message about the pass device not being 
>> in the kernel conf - it is.
>>
>> Any help would be greatly appreciated.
>>
>> Regards,
>> Ralph.
>> _______________________________________________
>> 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"
> I forgot to mention:
> uname -a:
> FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #17 r196849: Sat Sep  5 
> 09:35:27 CEST 2009  amd64
> _______________________________________________
> 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"
How about that part:
xptioctl: pass driver is not in the kernel
xptioctl: put "device pass" in your kernel config file

Don't know how this is handled on neither 9-current nor on amd64, but I 
guess this should be solved first.
From bruce at cran.org.uk  Sun Sep  6 11:05:31 2009
From: bruce at cran.org.uk (Bruce Cran)
Date: Sun Sep  6 11:05:36 2009
Subject: usb/138563: [usb8] [patch] Increase buffer sizes to accomodate
 longer USB strings
In-Reply-To: <200909060857.28707.hselasky@c2i.net>
References: <200909060537.n865bJeL043791@www.freebsd.org>
	<200909060857.28707.hselasky@c2i.net>
Message-ID: <20090906120525.193d86e7@gluon.draftnet>

The new versions of usb_device.c and usb_bus.h fixed the problem.

-- 
Bruce
From bruce at cran.org.uk  Sun Sep  6 11:30:05 2009
From: bruce at cran.org.uk (Bruce Cran)
Date: Sun Sep  6 11:30:11 2009
Subject: usb/138563: [usb8] [patch] Increase buffer sizes to accomodate
 longer USB strings
Message-ID: <200909061130.n86BU5J1037694@freefall.freebsd.org>

The following reply was made to PR usb/138563; it has been noted by GNATS.

From: Bruce Cran <bruce@cran.org.uk>
To: Hans Petter Selasky <hselasky@c2i.net>
Cc: freebsd-usb@freebsd.org, freebsd-gnats-submit@freebsd.org
Subject: Re: usb/138563: [usb8] [patch] Increase buffer sizes to accomodate
 longer USB strings
Date: Sun, 6 Sep 2009 12:05:25 +0100

 The new versions of usb_device.c and usb_bus.h fixed the problem.
 
 -- 
 Bruce
From brucec at FreeBSD.org  Sun Sep  6 11:41:23 2009
From: brucec at FreeBSD.org (brucec@FreeBSD.org)
Date: Sun Sep  6 11:41:30 2009
Subject: usb/138559: [usb8] [patch] uether sysctl handler doesn't
	NUL-terminate the string
Message-ID: <200909061141.n86BfNs8060305@freefall.freebsd.org>

Synopsis: [usb8] [patch] uether sysctl handler doesn't NUL-terminate the string

State-Changed-From-To: open->closed 
State-Changed-By: brucec
State-Changed-When: Sun Sep 6 11:34:49 UTC 2009
State-Changed-Why: 
It appears it's not a bug in usb_ethernet.c because the sysctl node isn't 
created with the CTLTYPE_STRING flag, which requires that strings be
nul-terminated instead of relying on the length parameter. The string 
therefore gets nul-terminated elsewhere.

http://www.freebsd.org/cgi/query-pr.cgi?pr=138559
From dorian.buettner at gmx.de  Sun Sep  6 21:14:57 2009
From: dorian.buettner at gmx.de (Dorian =?iso-8859-1?q?B=FCttner?=)
Date: Sun Sep  6 21:15:03 2009
Subject: Asus M2A-VP, SB600 usb chip and keyboard attached during boot
Message-ID: <200909062314.54270.dorian.buettner@gmx.de>

Hi usb list,

am actually running 8-Beta4 and experience uncomfortability during system 
boot. If I already have a keyboard attached to usb during boot, it will fail 
like this:
Sep  5 19:02:55 zock kernel: usb_alloc_device:1586: set address 2 failed 
(USB_ER
R_TIMEOUT, ignored)
Sep  5 19:02:55 zock kernel: usb_alloc_device:1624: getting device descriptor 
at
 addr 2 failed, USB_ERR_TIMEOUT!
Sep  5 19:02:55 zock kernel: usbd_req_re_enumerate:1539: addr=2, set address 
fai
led! (USB_ERR_TIMEOUT, ignored)
Sep  5 19:02:56 zock kernel: usbd_req_re_enumerate:1553: getting device 
descript
or at addr 2 failed, USB_ERR_TIMEOUT!
Sep  5 19:02:58 zock kernel: usbd_req_re_enumerate:1539: addr=2, set address 
fai
led! (USB_ERR_TIMEOUT, ignored)
Sep  5 19:02:59 zock kernel: usbd_req_re_enumerate:1553: getting device 
descript
or at addr 2 failed, USB_ERR_TIMEOUT!
Sep  5 19:02:59 zock kernel: ugen2.2: <(null)> at usbus2 (disconnected)
Sep  5 19:02:59 zock kernel: uhub_reattach_port:435: could not allocate new 
devi
ce!

It is however possible to make it 'awake' by attaching to one of the other usb 
socket blocks at the rear. How do you call the blocks, the board has 2x2 usb 
sockets mounted, others availabe via pci slot extensions.

When attaching after boot has run, it would read like this:

Sep  6 22:45:15 zock kernel: ugen0.2: <vendor 0x046d> at usbus0
Sep  6 22:45:15 zock kernel: uhub6: <vendor 0x046d product 0xc223, class 9/0, 
re
v 1.10/1.03, addr 2> on usbus0
Sep  6 22:45:16 zock kernel: uhub6: 4 ports with 2 removable, bus powered
Sep  6 22:45:17 zock root: Unknown USB device: vendor 0x046d product 0xc221 
bus
uhub6
Sep  6 22:45:17 zock kernel: ugen0.3: <vendor 0x046d> at usbus0
Sep  6 22:45:17 zock kernel: ukbd0: <vendor 0x046d Gaming Keyboard, class 0/0, 
r
ev 2.00/1.90, addr 3> on usbus0
Sep  6 22:45:17 zock kernel: kbd2 at ukbd0
Sep  6 22:45:17 zock kernel: uhid0: <vendor 0x046d Gaming Keyboard, class 0/0, 
r
ev 2.00/1.90, addr 3> on usbus0
Sep  6 22:45:18 zock kernel: ugen0.4: <Razer> at usbus0
Sep  6 22:45:19 zock kernel: ums0: <Razer Razer Copperhead Laser Mouse, class 
0/
0, rev 1.10/21.00, addr 4> on usbus0
Sep  6 22:45:19 zock kernel: ums0: 7 buttons and [XYZ] coordinates ID=0
Sep  6 22:45:19 zock kernel: ukbd1: <Razer Razer Copperhead Laser Mouse, class 
0
/0, rev 1.10/21.00, addr 4> on usbus0
Sep  6 22:45:19 zock kernel: kbd3 at ukbd1
Sep  6 22:45:19 zock kernel: ukbd_set_leds_callback:696: error=USB_ERR_STALLED
Sep  6 22:45:19 zock root: Unknown USB device: vendor 0x046d product 0xc222 
bus
uhub6
Sep  6 22:45:19 zock kernel: ugen0.5: <vendor 0x046d> at usbus0
Sep  6 22:45:19 zock kernel: hid_get_item:364: Number of items truncated to 
255
Sep  6 22:45:19 zock last message repeated 2 times
Sep  6 22:45:19 zock kernel: uhid1: <vendor 0x046d product 0xc222, class 0/0, 
re
v 2.00/1.03, addr 5> on usbus0
Sep  6 22:45:20 zock kernel: hid_get_item:364: Number of items truncated to 
255
Sep  6 22:45:20 zock last message repeated 2 times
Sep  6 22:45:23 zock ntpd[861]: ntpd 4.2.4p5-a (1)
Sep  6 22:45:29 zock login: ROOT LOGIN (root) ON ttyv0
Sep  6 22:45:30 zock ntpd[862]: time reset +0.413423 s
Sep  6 22:45:30 zock ntpd[862]: kernel time sync status change 2001
Sep  6 22:45:44 zock kernel: ukbd_set_leds_callback:696: error=USB_ERR_STALLED
Sep  6 22:45:45 zock last message repeated 2 times

(It's a gaming keyboard with a mouse attached to it, but the error would be 
the same with a dumb cherry kb attached).

It is, however, way better then in 7.2 http://www.freebsd.org/cgi/query-
pr.cgi?pr=usb/107827

Not sure if this patch originated at the netbsd would be related to it? 
http://marc.info/?l=openbsd-tech&m=124574838020563&w=2

Anything to test or similar welcome, but not within the next 2 days, I won't 
have access to the machine then. By the way, there seems to be some problem 
with the kbd leds, kde4 will hang when num lock is active during start phase.

Here is complete dmesg:
Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.             
FreeBSD 8.0-BETA4 #11: Sat Sep  5 13:51:35 CEST 2009                     
    root@zock.doris.net:/usr/obj/usr/src/sys/GENERIC                     
WARNING: WITNESS option enabled, expect reduced performance.             
Timecounter "i8254" frequency 1193182 Hz quality 0                       
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (2999.91-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x40f33  Stepping = 3                         
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>                                    
  Features2=0x2001<SSE3,CX16>                                                   
  AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>       
  AMD Features2=0x1f<LAHF,CMP,SVM,ExtAPIC,CR8>                                  
real memory  = 6442450944 (6144 MB)                                             
avail memory = 6178377728 (5892 MB)                                             
ACPI APIC Table: <ATI    ASUSACPI>                                              
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs                             
FreeBSD/SMP: 1 package(s) x 2 core(s)                                           
 cpu0 (BSP): APIC ID:  0                                                        
 cpu1 (AP): APIC ID:  1                                                         
ioapic0: Changing APIC ID to 4                                                  
ioapic0 <Version 2.1> irqs 0-23 on motherboard                                  
kbd1 at kbdmux0                                                                 
acpi0: <ATI ASUSACPI> on motherboard                                            
acpi0: [ITHREAD]                                                                
acpi0: Power Button (fixed)                                                     
acpi0: reservation of 0, a0000 (3) failed                                       
acpi0: reservation of 100000, cfde0000 (3) failed                               
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000                       
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0          
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0   
device_attach: acpi_hpet0 attach returned 12                                    
acpi_button0: <Power Button> on acpi0                                           
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0                         
pci0: <ACPI PCI bus> on pcib0                                                   
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0                              
pci1: <ACPI PCI bus> on pcib1                                                   
vgapci0: <VGA-compatible display> port 0xdf00-0xdf7f mem 
0xfa000000-0xfaffffff,0xd0000000-0xdfffffff,0xf8000000-0xf9ffffff irq 18 at 
device 0.0 on pci1         
pcib2: <ACPI PCI-PCI bridge> at device 7.0 on pci0                              
pci2: <ACPI PCI bus> on pcib2                                                   
re0: <RealTek 8168/8168B/8168C/8168CP/8168D/8168DP/8111B/8111C/8111CP/8111DP 
PCIe Gigabit Ethernet> port 0xee00-0xeeff mem 0xfddff000-0xfddfffff irq 19 at 
device 0.0 on pci2                                                                   
re0: Using 1 MSI messages                                                       
re0: Chip rev. 0x38000000                                                       
re0: MAC rev. 0x00000000                                                        
miibus0: <MII bus> on re0                                                       
rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0                
rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto                                                                        
re0: Ethernet address: 00:1b:fc:73:9e:b8                                        
re0: [FILTER]                                                                   
atapci0: <ATI IXP600 SATA300 controller> port 
0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 
0xfe02f000-0xfe02f3ff irq 22 at device 18.0 on pci0                                                                     
atapci0: [ITHREAD]                                                              
atapci0: AHCI v1.10 controller with 4 3Gbps ports, PM supported                 
ata2: <ATA channel 0> on atapci0                                                
ata2: port is not ready (timeout 0ms) tfd = 000001d0                            
ata2: software reset clear timeout                                              
ata2: [ITHREAD]                                                                 
ata3: <ATA channel 1> on atapci0                                                
ata3: [ITHREAD]                                                                 
ata4: <ATA channel 2> on atapci0                                                
ata4: [ITHREAD]                                                                 
ata5: <ATA channel 3> on atapci0                                                
ata5: [ITHREAD]                                                                 
ohci0: <OHCI (generic) USB controller> mem 0xfe02e000-0xfe02efff irq 16 at 
device 19.0 on pci0                                                                  
ohci0: [ITHREAD]                                                                
usbus0: <OHCI (generic) USB controller> on ohci0                                
ohci1: <OHCI (generic) USB controller> mem 0xfe02d000-0xfe02dfff irq 17 at 
device 19.1 on pci0                                                                  
ohci1: [ITHREAD]                                                                
usbus1: <OHCI (generic) USB controller> on ohci1                                
ohci2: <OHCI (generic) USB controller> mem 0xfe02c000-0xfe02cfff irq 18 at 
device 19.2 on pci0                                                                  
ohci2: [ITHREAD]                                                                
usbus2: <OHCI (generic) USB controller> on ohci2                                
ohci3: <OHCI (generic) USB controller> mem 0xfe02b000-0xfe02bfff irq 17 at 
device 19.3 on pci0                                                                  
ohci3: [ITHREAD]                                                                
usbus3: <OHCI (generic) USB controller> on ohci3                                
ohci4: <OHCI (generic) USB controller> mem 0xfe02a000-0xfe02afff irq 18 at 
device 19.4 on pci0                                                                  
ohci4: [ITHREAD]                                                                
usbus4: <OHCI (generic) USB controller> on ohci4                                
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfe029000-0xfe0290ff irq 19 at 
device 19.5 on pci0                                                              
ehci0: [ITHREAD]                                                                
usbus5: EHCI version 1.0                                                        
usbus5: <EHCI (generic) USB 2.0 controller> on ehci0                            
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)                   
atapci1: <ATI IXP600 UDMA133 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf900-0xf90f at device 20.1 on pci0                                          
ata0: <ATA channel 0> on atapci1                                                
ata0: [ITHREAD]                                                                 
isab0: <PCI-ISA bridge> at device 20.3 on pci0                                  
isa0: <ISA bus> on isab0                                                        
pcib3: <ACPI PCI-PCI bridge> at device 20.4 on pci0                             
pci3: <ACPI PCI bus> on pcib3                                                   
pcm0: <Creative EMU10K1> port 0xcf00-0xcf1f irq 21 at device 6.0 on pci3        
pcm0: <SigmaTel STAC9721/23 AC97 Codec>                                         
pcm0: [ITHREAD]                                                                 
acpi_tz0: <Thermal Zone> on acpi0                                               
ACPI Warning: \\_TZ_.THRM._PSL: Return Package type mismatch at index 0 - 
found [NULL Object Descriptor], expected Reference 20090521 nspredef-1058             
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0     
fdc0: [FILTER]                                                                  
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0         
uart0: [FILTER]                                                                 
ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0                           
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode                           
ppc0: [ITHREAD]                                                                 
ppbus0: <Parallel port bus> on ppc0                                             
plip0: <PLIP network interface> on ppbus0                                       
plip0: [ITHREAD]                                                                
lpt0: <Printer> on ppbus0                                                       
lpt0: [ITHREAD]                                                                 
lpt0: Interrupt-driven port                                                     
ppi0: <Parallel I/O> on ppbus0                                                  
atrtc0: <AT realtime clock> port 0x70-0x73 on acpi0                             
cpu0: <ACPI CPU> on acpi0                                                       
powernow0: <PowerNow! K8> on cpu0                                               
cpu1: <ACPI CPU> on acpi0                                                       
powernow1: <PowerNow! K8> on cpu1                                               
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0   
device_attach: acpi_hpet0 attach returned 12                                    
sc0: <System console> at flags 0x100 on isa0                                    
sc0: VGA <16 virtual consoles, flags=0x300>                                     
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0       
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0                
atkbd0: <AT Keyboard> irq 1 on atkbdc0                                          
kbd0 at atkbd0                                                                  
atkbd0: [GIANT-LOCKED]                                                          
atkbd0: [ITHREAD]                                                               
Timecounters tick every 1.000 msec                                              
usbus0: 12Mbps Full Speed USB v1.0                                              
usbus1: 12Mbps Full Speed USB v1.0                                              
usbus2: 12Mbps Full Speed USB v1.0                                              
usbus3: 12Mbps Full Speed USB v1.0                                              
usbus4: 12Mbps Full Speed USB v1.0                                              
usbus5: 480Mbps High Speed USB v2.0                                             
ugen0.1: <ATI> at usbus0                                                        
uhub0: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0          
ugen1.1: <ATI> at usbus1                                                        
uhub1: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1          
ugen2.1: <ATI> at usbus2                                                        
uhub2: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2          
ugen3.1: <ATI> at usbus3                                                        
uhub3: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3          
ugen4.1: <ATI> at usbus4                                                        
uhub4: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4          
ugen5.1: <ATI> at usbus5                                                        
uhub5: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus5          
acd0: DVDR <DVDR PX-750A/1.03> at ata0-master UDMA66                            
ad4: 305245MB <SAMSUNG HD320KJ CP100-11> at ata2-master SATA300                 
SMP: AP CPU #1 Launched!                                                        
WARNING: WITNESS option enabled, expect reduced performance.                    
GEOM: ad4s2: geometry does not match label (255h,63s != 16h,63s).               
GEOM: ad4s3: geometry does not match label (255h,63s != 16h,63s).               
uhub0: 2 ports with 2 removable, self powered                                   
uhub1: 2 ports with 2 removable, self powered                                   
uhub2: 2 ports with 2 removable, self powered                                   
uhub3: 2 ports with 2 removable, self powered                                   
uhub4: 2 ports with 2 removable, self powered                                   
Root mount waiting for: usbus5                                                  
Root mount waiting for: usbus5                                                  
Root mount waiting for: usbus5                                                  
uhub5: 10 ports with 10 removable, self powered                                 
Trying to mount root from ufs:/dev/ad4s3a                                       
re0: link state changed to UP                                                   
re0: link state changed to DOWN                                                 
re0: link state changed to UP                                                   
re0: link state changed to DOWN                                                 
re0: link state changed to UP                                                   
ugen0.2: <vendor 0x046d> at usbus0                                              
uhub6: <vendor 0x046d product 0xc223, class 9/0, rev 1.10/1.03, addr 2> on 
usbus0                                                                               
uhub6: 4 ports with 2 removable, bus powered                                    
ugen0.3: <vendor 0x046d> at usbus0                                              
ukbd0: <vendor 0x046d Gaming Keyboard, class 0/0, rev 2.00/1.90, addr 3> on 
usbus0                                                                              
kbd2 at ukbd0                                                                   
uhid0: <vendor 0x046d Gaming Keyboard, class 0/0, rev 2.00/1.90, addr 3> on 
usbus0                                                                              
ugen0.4: <Razer> at usbus0                                                      
ums0: <Razer Razer Copperhead Laser Mouse, class 0/0, rev 1.10/21.00, addr 4> 
on usbus0                                                                         
ums0: 7 buttons and [XYZ] coordinates ID=0                                      
ukbd1: <Razer Razer Copperhead Laser Mouse, class 0/0, rev 1.10/21.00, addr 4> 
on usbus0                                                                        
kbd3 at ukbd1                                                                   
ukbd_set_leds_callback:696: error=USB_ERR_STALLED                               
ugen0.5: <vendor 0x046d> at usbus0                                              
hid_get_item:364: Number of items truncated to 255                              
hid_get_item:364: Number of items truncated to 255
hid_get_item:364: Number of items truncated to 255
uhid1: <vendor 0x046d product 0xc222, class 0/0, rev 2.00/1.03, addr 5> on 
usbus0
hid_get_item:364: Number of items truncated to 255
hid_get_item:364: Number of items truncated to 255
hid_get_item:364: Number of items truncated to 255
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
lock order reversal:
 1st 0xffffff807bad1f68 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559
 2nd 0xffffff003d1e7000 dirhash (dirhash) @ 
/usr/src/sys/ufs/ufs/ufs_dirhash.c:285
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_witness_debugger() at _witness_debugger+0x2e
witness_checkorder() at witness_checkorder+0x81e
_sx_xlock() at _sx_xlock+0x55
ufsdirhash_acquire() at ufsdirhash_acquire+0x33
ufsdirhash_add() at ufsdirhash_add+0x19
ufs_direnter() at ufs_direnter+0x88b
ufs_makeinode() at ufs_makeinode+0x2a7
VOP_CREATE_APV() at VOP_CREATE_APV+0x8d
vn_open_cred() at vn_open_cred+0x468
kern_openat() at kern_openat+0x179
syscall() at syscall+0x1af
Xfast_syscall() at Xfast_syscall+0xe1
--- syscall (5, FreeBSD ELF64, open), rip = 0x80336ee0c, rsp = 0x7fffffffc7c8, 
rbp = 0x8068021c0 ---
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ukbd_set_leds_callback:696: error=USB_ERR_STALLED


From alfred at freebsd.org  Mon Sep  7 03:25:12 2009
From: alfred at freebsd.org (Alfred Perlstein)
Date: Mon Sep  7 03:25:18 2009
Subject: kern/137806: USB keyboard doesn't work until it's unplugged
In-Reply-To: <200909060035.48886.citycat4@ngs.ru>
References: <1858.4707-7260-1257771675-1252091184@seznam.cz>
	<200909052245.55823.citycat4@ngs.ru>
	<200909051758.20393.hselasky@c2i.net>
	<200909060035.48886.citycat4@ngs.ru>
Message-ID: <20090907030541.GQ21946@elvis.mu.org>

* Rashid N. Achilov <citycat4@ngs.ru> [090905 10:40] wrote:
> On Saturday 05 September 2009, Hans Petter Selasky wrote:
> 
> > I looked at the error report and noticed this problem was reported on 7.2. 
> I'm 
> > mostly working on issues reported on 8.x. Is this issue the same on 7.2 and 
> > 8.0-BETA3, just for reference?
> 
> I don't know, I haven't any 8.x installations. On my side I'll install 8.x 
> only after 8.1 releasing - after installing 4.0 I have hard belief, 
> that "dot-zero release" is only another name "widely testing public beta".

When you factor in the combination of hardware platforms and usage
patterns it really makes sense to try a .0 release or even -current
every so often to report bugs.

This is so that when that .1 release comes out, your bugs are addressed.

I agree it wouldn't make sense to deploy a .0 release en-masse without
testing/qualifying, but refusing to look at it just doesn't make sense.

-- 
- Alfred Perlstein
.- AMA, VMOA #5191, 03 vmax, 92 gs500, 85 ch250
.- FreeBSD committer
From hselasky at c2i.net  Mon Sep  7 07:03:59 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Sep  7 07:04:32 2009
Subject: Asus M2A-VP, SB600 usb chip and keyboard attached during boot
In-Reply-To: <200909062314.54270.dorian.buettner@gmx.de>
References: <200909062314.54270.dorian.buettner@gmx.de>
Message-ID: <200909070904.21708.hselasky@c2i.net>

On Sunday 06 September 2009 23:14:54 Dorian B?ttner wrote:
> ATI

Hi,

I will try to port that patch you referred to over to FreeBSD. Maybe I will 
have it ready later today.

--HPS
From bugmaster at FreeBSD.org  Mon Sep  7 11:07:10 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Sep  7 11:09:56 2009
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200909071107.n87B7AIl010416@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o usb/138563   usb        [usb8] [patch] Increase buffer sizes to accomodate lon
o usb/138548   usb        usb devices periodically have unknown activity
o usb/138389   usb        [usb8] [patch] NULL pointer dereference in usb_endpoin
o usb/138175   usb        [usb67] [boot] System cannot boot, when USB reader wit
o usb/138172   usb        Additional dev id for u3g (Option mini PCIe)
o usb/138138   usb        Novatel U760 for u3g (Verizon and Bell Canada)
o usb/138124   usb        [usb8] Axed uaudio functionality in the usbng (alterna
o usb/138119   usb        MultiBay CDROM (propably on USB bus) is not recognized
o usb/137872   usb        slow booting on usb flash drive
f usb/137848   usb        Page fault when using an USB bluetooth adapter
o usb/137806   usb        [ukbd] USB keyboard doesn't work until it's unplugged
o usb/137789   usb        Add quirks for EeePC 901 SD card reader
o usb/137763   usb        Logitech wireless keyboard media keys not working
o usb/137616   usb        [usbdevs] [patch]: usbdevs update: Please add JMicron'
o usb/137377   usb        Support for Huawei E180
o usb/137341   usb        driver if_rum doesn't work at all and throws panics
o usb/137226   usb        [patch] quirk for Philips extern USB disk
o usb/137191   usb        [usb][patch] export ums(4) output report parser data t
o usb/137190   usb        [usb][patch] inhibit spurious button releases for some
o usb/137189   usb        [usb][patch] create and use sysctl nodes for HID repor
p usb/137188   usb        [usb][patch] correctly handle USB report descriptors w
o usb/137138   usb        [umass] [patch] QUIRK: ASUS PDA Flash disk emulation
o usb/137129   usb        SteelSeries Ikari USB laser mouse not attaching
o usb/137035   usb        Sony cyber-shot DSC-P72 not accessible - cam quirks
p usb/136761   usb        [usbdevs] [patch] Teach usbdevs / u3g(4) about Huawei 
o usb/135938   usb        [aue] aue driver only passes traffic in promisc mode
f usb/135857   usb        RTL8187 Wireless Adapter
o usb/135575   usb        [usbdevs] [patch] Add HTC Wizard phone vid/pid informa
o usb/135542   usb        [keyboard] boot loader does not work with a usb keyboa
o usb/135372   usb        Quirk report for Teclast TL-C300 usb media player
o usb/135348   usb        [umass] USB Drive Hangs with ZFS (JMicron USB2/eSata)
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/134633   usb        Add support for WILLCOM03(SHARP smart phone)
o usb/134631   usb        [usbdevs] [patch] WiSPY DBx support requires usb tweak
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/134117   usb        [Patch] Add support for 'Option GlobeTrotter HSDPA Mod
o usb/134085   usb        [umass] Adding usb quirk for Sony USB flash drive
o usb/133989   usb        [newusb] [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
p usb/132799   usb        [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CA
o usb/132785   usb        [usb] [patch] Gemtech remote powersocket is classed as
o usb/132594   usb        USB subsystem causes page fault and crashes
o usb/132312   usb        Xorg 7.4 halts USB controller
o usb/132080   usb        [patch] [usb] Kernel panic after NOMEM caused by rum 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/131912   usb        [uslcom] [patch] New devices using Silicon Labs chips 
o usb/131900   usb        [usbdevs] [patch] Additional product identification co
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
o usb/131123   usb        [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk
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/130325   usb        [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh
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        [newusb] DVD drive detects as 'da' device
o usb/129945   usb        [usbdevs] [patch] add u3g support for Longcheer WM66 U
o usb/129766   usb        [usb] plugging in usb modem HUAWEI E226 panics system
o usb/129758   usb        [uftdi] [patch] add Pyramid LCD usb support
o usb/129673   usb        [uhci] uhci (uhub) confused on replugging USB 1.1 scan
o usb/129522   usb        [ubsa] [patch] add support for ZTE AC8700 modem
o usb/129500   usb        [umass] [panic] FreeBSD Crashes when connecting SanDis
o usb/129311   usb        [usb] [panic] Instant crash with an USB card reader
o usb/129251   usb        [usbdevs] [patch] Liebert UPS being assigned uhid and 
o usb/129173   usb        [uplcom] [patch] Add support for Corega CG-USBRS232R a
s usb/128990   usb        [usb] u3g does not handle RTS/CTS available on for exa
o usb/128977   usb        [usb] [patch] uaudio is not full duplex
o 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/128324   usb        [uplcom] [patch] remove baud rate restriction for PL23
o usb/127980   usb        [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an
o usb/127926   usb        [boot] USB Timeout during bootup
s usb/127549   usb        [umass] [patch] Meizu MiniPlayer M6 (SL) requires some
s usb/127453   usb        [request] ubsa, uark, ubser, uftdi, and friends should
o usb/127423   usb        [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr
o usb/127342   usb        [boot] [panic] enabling usb keyboard and mouse support
o usb/127248   usb        [ucom] panic while uplcom devices attaach 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/125736   usb        [ukbd] [hang] system hangs after AT keyboard detect if
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
p usb/125264   usb        [patch] sysctl for set usb mouse rate (very useful for
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
o 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/123352   usb        [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom
o usb/123351   usb        [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2
o usb/122992   usb        [umass] [patch] MotoROKR Z6 Phone not recognised by um
o usb/122956   usb        [ubsa] [patch] add support for Novatel Wireless XU870 
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/122621   usb        [new driver] [patch] New driver for Sierra Wireless 3G
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/122025   usb        [uscanner] [patch] uscanner does not attach to Epson R
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/121426   usb        [patch] [uscanner] add HP ScanJet 3570C
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        [umass] [patch] quirk to support ASUS P535 as umass (a
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/118485   usb        [usbdevs] [patch] Logitech Headset Workaround
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        [uaudio] [patch] Not possible to record with Plantroni
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
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/107935   usb        [usb67] [uplcom] [panic] panic while accessing /dev/cu
o usb/107924   usb        [usb67] usbd(8) does not call detach
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/107243   usb        [usb67] [cam] [quirk] [patch] Apacer USB Flash Drive q
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/99538    usb        [keyboard] while using USB keyboard default params of 
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/93155    usb        [ulpt] /dev/ulpt0: device busy, USB printer does not w
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/91629    usb        [usb] usbd_abort_pipe() may result in infinite loop
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
f usb/84750    usb        [hang] 6-BETA2 reboot/shutdown with root_fs on externa
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/80862    usb        [patch] USB locking issues: missing some Giant calls
o usb/80854    usb        [patch] [request] suggestion for new iface-no-probe me
o usb/80829    usb        [modules] [panic] possible panic when loading USB-modu
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 "
o usb/80361    usb        [umass] [patch] mounting of Dell usb-stick fails
o 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/79722    usb        [ehci] wrong alignments in ehci.h
a usb/79656    usb        [ehci] RHSC interrupts lost
o usb/79524    usb        [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa
o usb/79287    usb        [uhci] [hang] UHCI hang after interrupt transfer
o usb/79269    usb        [ohci] USB ohci da0 plug/unplug causes crashes and loc
o usb/78984    usb        [umass] [patch] Creative MUVO umass failure
o usb/77294    usb        [ucom] [panic] ucom + ulpcom panic
o usb/77184    usb        [umass] [panic] kernel panic on USB device disconnect,
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
o 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
o 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 
o usb/75705    usb        [umass] [panic] da0 attach / Optio S4 (with backtrace)
o 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 i386/46371   usb        USB controller cannot be initialized on IBM Netfinity 
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

305 problems total.

From avg at icyb.net.ua  Mon Sep  7 16:35:28 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Mon Sep  7 16:35:36 2009
Subject: Asus M2A-VP, SB600 usb chip and keyboard attached during boot
In-Reply-To: <200909070904.21708.hselasky@c2i.net>
References: <200909062314.54270.dorian.buettner@gmx.de>
	<200909070904.21708.hselasky@c2i.net>
Message-ID: <4AA53271.70907@icyb.net.ua>

on 07/09/2009 10:04 Hans Petter Selasky said the following:
> On Sunday 06 September 2009 23:14:54 Dorian B?ttner wrote:
>> ATI
> 
> Hi,
> 
> I will try to port that patch you referred to over to FreeBSD. Maybe I will 
> have it ready later today.

BTW, the patch as present verbatim in the posted link
(http://marc.info/?l=openbsd-tech&m=124574838020563&w=2) seems to be incorrect.
Either the register should be 0x53 and should be accessed via byte access.
Or the bit should be 27.

And, BTW, that bit of that register is not documented in AMD SB700/710/750
Register Reference Guide -- bits 24:27 of EHCI Misc Control register are said to
be reserved.

It's interesting to understand what this bit actually does, maybe someone has
contacts at AMD.


-- 
Andriy Gapon
From hselasky at c2i.net  Mon Sep  7 17:50:01 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Sep  7 17:50:07 2009
Subject: Asus M2A-VP, SB600 usb chip and keyboard attached during boot
In-Reply-To: <4AA53271.70907@icyb.net.ua>
References: <200909062314.54270.dorian.buettner@gmx.de>
	<200909070904.21708.hselasky@c2i.net> <4AA53271.70907@icyb.net.ua>
Message-ID: <200909071950.23865.hselasky@c2i.net>

On Monday 07 September 2009 18:18:57 Andriy Gapon wrote:
> BTW, the patch as present verbatim in the posted link
> (http://marc.info/?l=openbsd-tech&m=124574838020563&w=2) 
seems to be
> incorrect. Either the register should be 0x53 and should 
be accessed via
> byte access. Or the bit should be 27.
>
> And, BTW, that bit of that register is not documented in 
AMD SB700/710/750
> Register Reference Guide -- bits 24:27 of EHCI Misc 
Control register are
> said to be reserved.
>
> It's interesting to understand what this bit actually 
does, maybe someone
> has contacts at AMD.

Hi,

Can you try the following patch, and check that you get 
dmesg output according to the quirks.

http://perforce.freebsd.org/chv.cgi?CH=168288

--HPS
From ganael.laplanche at martymac.com  Tue Sep  8 11:59:46 2009
From: ganael.laplanche at martymac.com (Ganael LAPLANCHE)
Date: Tue Sep  8 11:59:53 2009
Subject: FreeBSD Siano (sms1xxx) driver updated
Message-ID: <20090908111415.M76691@martymac.com>

Hi,

Here is a new update of the sms1xxx USB DVB-T driver for FreeBSD (>= 8.x).

It now has initial support for another USB stick : the 'Hauppauge WinTV
MiniStick'. Other (siano-based) sticks should work, but you may need to add
VIDs/PIDs as necessary (and send me your patches ;-)).

As usual, the new version of the driver is available here :

http://contribs.martymac.com

Here is a direct link to the README file :

http://contribs.martymac.com/FreeBSD-siano/README

And another one to the CHANGELOG file :

http://contribs.martymac.com/FreeBSD-siano/CHANGELOG

Happy streaming,
Best regards,

Gana?l LAPLANCHE
ganael.laplanche@martymac.com
http://www.martymac.com
From dorian.buettner at gmx.de  Tue Sep  8 19:33:14 2009
From: dorian.buettner at gmx.de (Dorian =?iso-8859-1?q?B=FCttner?=)
Date: Tue Sep  8 19:33:21 2009
Subject: Asus M2A-VP, SB600 usb chip and keyboard attached during boot
In-Reply-To: <200909071950.23865.hselasky@c2i.net>
References: <200909062314.54270.dorian.buettner@gmx.de>
	<4AA53271.70907@icyb.net.ua> <200909071950.23865.hselasky@c2i.net>
Message-ID: <200909082133.08714.dorian.buettner@gmx.de>

On Monday 07 September 2009 19:50:22 Hans Petter Selasky wrote:
> On Monday 07 September 2009 18:18:57 Andriy Gapon wrote:
> > BTW, the patch as present verbatim in the posted link
> > (http://marc.info/?l=openbsd-tech&m=124574838020563&w=2)
> 
> seems to be
> 
> > incorrect. Either the register should be 0x53 and should
> 
> be accessed via
> 
> > byte access. Or the bit should be 27.
> >
> > And, BTW, that bit of that register is not documented in
> 
> AMD SB700/710/750
> 
> > Register Reference Guide -- bits 24:27 of EHCI Misc
> 
> Control register are
> 
> > said to be reserved.
> >
> > It's interesting to understand what this bit actually
> 
> does, maybe someone
> 
> > has contacts at AMD.
> 
> Hi,
> 
> Can you try the following patch, and check that you get
> dmesg output according to the quirks.
> 
> http://perforce.freebsd.org/chv.cgi?CH=168288
> 
> --HPS
> 

Just finished compiling, dmesg following. It Doesn't seem to have any impact 
concerning my problem, propably some sb700 owners might want to test also.
Don't know in how far this will give any hint but in 7.2 I worked around the 
crash on boot by compiling the kernel w/o any usb support, then adviced 
/etc/rc to load the necessary modules. That way I had everything working 
without too much effort unplugging devices during boot.


Copyright (c) 1992-2009 The FreeBSD Project.                                    
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994        
        The Regents of the University of California. All rights reserved.       
FreeBSD is a registered trademark of The FreeBSD Foundation.                    
FreeBSD 8.0-BETA4 #12: Tue Sep  8 21:06:47 CEST 2009                            
    root@zock.doris.net:/usr/obj/usr/src/sys/GENERIC                            
WARNING: WITNESS option enabled, expect reduced performance.                    
Timecounter "i8254" frequency 1193182 Hz quality 0                              
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (2999.91-MHz K8-class CPU)  
  Origin = "AuthenticAMD"  Id = 0x40f33  Stepping = 3                           
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>                                    
  Features2=0x2001<SSE3,CX16>                                                   
  AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>       
  AMD Features2=0x1f<LAHF,CMP,SVM,ExtAPIC,CR8>                                  
real memory  = 6442450944 (6144 MB)                                             
avail memory = 6178373632 (5892 MB)                                             
ACPI APIC Table: <ATI    ASUSACPI>                                              
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs                             
FreeBSD/SMP: 1 package(s) x 2 core(s)                                           
 cpu0 (BSP): APIC ID:  0                                                        
 cpu1 (AP): APIC ID:  1                                                         
ioapic0: Changing APIC ID to 4                                                  
ioapic0 <Version 2.1> irqs 0-23 on motherboard                                  
kbd1 at kbdmux0                                                                 
acpi0: <ATI ASUSACPI> on motherboard                                            
acpi0: [ITHREAD]                                                                
acpi0: Power Button (fixed)                                                     
acpi0: reservation of 0, a0000 (3) failed                                       
acpi0: reservation of 100000, cfde0000 (3) failed                               
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000                       
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0          
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0   
device_attach: acpi_hpet0 attach returned 12                                    
acpi_button0: <Power Button> on acpi0                                           
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0                         
pci0: <ACPI PCI bus> on pcib0                                                   
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0                              
pci1: <ACPI PCI bus> on pcib1                                                   
vgapci0: <VGA-compatible display> port 0xdf00-0xdf7f mem 
0xfa000000-0xfaffffff,0xd0000000-0xdfffffff,0xf8000000-0xf9ffffff irq 18 at 
device 0.0 on pci1         
pcib2: <ACPI PCI-PCI bridge> at device 7.0 on pci0                              
pci2: <ACPI PCI bus> on pcib2                                                   
re0: <RealTek 8168/8168B/8168C/8168CP/8168D/8168DP/8111B/8111C/8111CP/8111DP 
PCIe Gigabit Ethernet> port 0xee00-0xeeff mem 0xfddff000-0xfddfffff irq 19 at 
device 0.0 on pci2                                                                   
re0: Using 1 MSI messages                                                       
re0: Chip rev. 0x38000000                                                       
re0: MAC rev. 0x00000000                                                        
miibus0: <MII bus> on re0                                                       
rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0                
rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto                                                                        
re0: Ethernet address: 00:1b:fc:73:9e:b8                                        
re0: [FILTER]                                                                   
atapci0: <ATI IXP600 SATA300 controller> port 
0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 
0xfe02f000-0xfe02f3ff irq 22 at device 18.0 on pci0                                                                     
atapci0: [ITHREAD]                                                              
atapci0: AHCI v1.10 controller with 4 3Gbps ports, PM supported                 
ata2: <ATA channel 0> on atapci0                                                
ata2: port is not ready (timeout 0ms) tfd = 000001d0                            
ata2: software reset clear timeout                                              
ata2: [ITHREAD]                                                                 
ata3: <ATA channel 1> on atapci0                                                
ata3: [ITHREAD]                                                                 
ata4: <ATA channel 2> on atapci0                                                
ata4: [ITHREAD]                                                                 
ata5: <ATA channel 3> on atapci0                                                
ata5: [ITHREAD]                                                                 
ohci0: <OHCI (generic) USB controller> mem 0xfe02e000-0xfe02efff irq 16 at 
device 19.0 on pci0                                                                  
ohci0: [ITHREAD]                                                                
usbus0: <OHCI (generic) USB controller> on ohci0                                
ohci1: <OHCI (generic) USB controller> mem 0xfe02d000-0xfe02dfff irq 17 at 
device 19.1 on pci0                                                                  
ohci1: [ITHREAD]                                                                
usbus1: <OHCI (generic) USB controller> on ohci1                                
ohci2: <OHCI (generic) USB controller> mem 0xfe02c000-0xfe02cfff irq 18 at 
device 19.2 on pci0                                                                  
ohci2: [ITHREAD]                                                                
usbus2: <OHCI (generic) USB controller> on ohci2                                
ohci3: <OHCI (generic) USB controller> mem 0xfe02b000-0xfe02bfff irq 17 at 
device 19.3 on pci0                                                                  
ohci3: [ITHREAD]                                                                
usbus3: <OHCI (generic) USB controller> on ohci3                                
ohci4: <OHCI (generic) USB controller> mem 0xfe02a000-0xfe02afff irq 18 at 
device 19.4 on pci0                                                                  
ohci4: [ITHREAD]                                                                
usbus4: <OHCI (generic) USB controller> on ohci4                                
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfe029000-0xfe0290ff irq 19 at 
device 19.5 on pci0                                                              
ehci0: [ITHREAD]                                                                
usbus5: EHCI version 1.0                                                        
usbus5: <EHCI (generic) USB 2.0 controller> on ehci0                            
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)                   
atapci1: <ATI IXP600 UDMA133 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf900-0xf90f at device 20.1 on pci0                                          
ata0: <ATA channel 0> on atapci1                                                
ata0: [ITHREAD]                                                                 
isab0: <PCI-ISA bridge> at device 20.3 on pci0                                  
isa0: <ISA bus> on isab0                                                        
pcib3: <ACPI PCI-PCI bridge> at device 20.4 on pci0                             
pci3: <ACPI PCI bus> on pcib3                                                   
pcm0: <Creative EMU10K1> port 0xcf00-0xcf1f irq 21 at device 6.0 on pci3        
pcm0: <SigmaTel STAC9721/23 AC97 Codec>                                         
pcm0: [ITHREAD]                                                                 
acpi_tz0: <Thermal Zone> on acpi0                                               
ACPI Warning: \\_TZ_.THRM._PSL: Return Package type mismatch at index 0 - 
found [NULL Object Descriptor], expected Reference 20090521 nspredef-1058             
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0     
fdc0: [FILTER]                                                                  
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0         
uart0: [FILTER]                                                                 
ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0                           
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode                           
ppc0: [ITHREAD]                                                                 
ppbus0: <Parallel port bus> on ppc0                                             
plip0: <PLIP network interface> on ppbus0                                       
plip0: [ITHREAD]                                                                
lpt0: <Printer> on ppbus0                                                       
lpt0: [ITHREAD]                                                                 
lpt0: Interrupt-driven port                                                     
ppi0: <Parallel I/O> on ppbus0                                                  
atrtc0: <AT realtime clock> port 0x70-0x73 on acpi0                             
cpu0: <ACPI CPU> on acpi0                                                       
powernow0: <PowerNow! K8> on cpu0                                               
cpu1: <ACPI CPU> on acpi0                                                       
powernow1: <PowerNow! K8> on cpu1                                               
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0   
device_attach: acpi_hpet0 attach returned 12                                    
sc0: <System console> at flags 0x100 on isa0                                    
sc0: VGA <16 virtual consoles, flags=0x300>                                     
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0       
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0                
atkbd0: <AT Keyboard> irq 1 on atkbdc0                                          
kbd0 at atkbd0                                                                  
atkbd0: [GIANT-LOCKED]                                                          
atkbd0: [ITHREAD]                                                               
Timecounters tick every 1.000 msec                                              
usbus0: 12Mbps Full Speed USB v1.0                                              
usbus1: 12Mbps Full Speed USB v1.0                                              
usbus2: 12Mbps Full Speed USB v1.0                                              
usbus3: 12Mbps Full Speed USB v1.0                                              
usbus4: 12Mbps Full Speed USB v1.0                                              
usbus5: 480Mbps High Speed USB v2.0                                             
ugen0.1: <ATI> at usbus0                                                        
uhub0: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0          
ugen1.1: <ATI> at usbus1                                                        
uhub1: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1          
ugen2.1: <ATI> at usbus2                                                        
uhub2: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2          
ugen3.1: <ATI> at usbus3                                                        
uhub3: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3          
ugen4.1: <ATI> at usbus4                                                        
uhub4: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4          
ugen5.1: <ATI> at usbus5                                                        
uhub5: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus5          
acd0: DVDR <DVDR PX-750A/1.03> at ata0-master UDMA66                            
ad4: 305245MB <SAMSUNG HD320KJ CP100-11> at ata2-master SATA300                 
SMP: AP CPU #1 Launched!                                                        
WARNING: WITNESS option enabled, expect reduced performance.                    
GEOM: ad4s2: geometry does not match label (255h,63s != 16h,63s).               
GEOM: ad4s3: geometry does not match label (255h,63s != 16h,63s).               
uhub0: 2 ports with 2 removable, self powered                                   
uhub1: 2 ports with 2 removable, self powered                                   
uhub2: 2 ports with 2 removable, self powered                                   
uhub3: 2 ports with 2 removable, self powered                                   
uhub4: 2 ports with 2 removable, self powered                                   
Root mount waiting for: usbus5                                                  
Root mount waiting for: usbus5                                                  
Root mount waiting for: usbus5                                                  
uhub5: 10 ports with 10 removable, self powered                                 
Root mount waiting for: usbus5                                                  
Trying to mount root from ufs:/dev/ad4s3a                                       
usb_alloc_device:1586: set address 2 failed (USB_ERR_TIMEOUT, ignored)          
usb_alloc_device:1624: getting device descriptor at addr 2 failed, 
USB_ERR_TIMEOUT!                                                                             
usbd_req_re_enumerate:1539: addr=2, set address failed! (USB_ERR_TIMEOUT, 
ignored)                                                                              
lock order reversal:                                                            
 1st 0xffffff0004305620 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2083           
 2nd 0xffffff807ba69850 bufwait (bufwait) @ 
/usr/src/sys/ufs/ffs/ffs_softdep.c:6177                                                                             
 3rd 0xffffff00044d8ba8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2083           
KDB: stack backtrace:                                                           
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a                           
_witness_debugger() at _witness_debugger+0x2e                                   
witness_checkorder() at witness_checkorder+0x81e                                
__lockmgr_args() at __lockmgr_args+0xcf3                                        
ffs_lock() at ffs_lock+0x8c                                                     
VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b                                           
_vn_lock() at _vn_lock+0x47                                                     
vget() at vget+0x7b                                                             
vfs_hash_get() at vfs_hash_get+0xd5                                             
ffs_vgetf() at ffs_vgetf+0x48                                                   
softdep_sync_metadata() at softdep_sync_metadata+0x456                          
ffs_syncvnode() at ffs_syncvnode+0x210                                          
ffs_truncate() at ffs_truncate+0x4ab                                            
ufs_direnter() at ufs_direnter+0x6ae                                            
ufs_mkdir() at ufs_mkdir+0x623                                                  
VOP_MKDIR_APV() at VOP_MKDIR_APV+0x93                                           
kern_mkdirat() at kern_mkdirat+0x270                                            
syscall() at syscall+0x1af                                                      
Xfast_syscall() at Xfast_syscall+0xe1                                           
--- syscall (136, FreeBSD ELF64, mkdir), rip = 0x800729dcc, rsp = 
0x7fffffffec88, rbp = 0x7fffffffef66 ---                                                      
usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed, 
USB_ERR_TIMEOUT!                                                                        
usbd_req_re_enumerate:1539: addr=2, set address failed! (USB_ERR_TIMEOUT, 
ignored)                                                                              
usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed, 
USB_ERR_TIMEOUT!                                                                        
ugen0.2: <(null)> at usbus0 (disconnected)                                      
uhub_reattach_port:435: could not allocate new device!                          
re0: link state changed to UP                                                   
re0: link state changed to DOWN                                                 
re0: link state changed to UP                                                   
re0: link state changed to DOWN                                                 
re0: link state changed to UP                                                   
ugen1.2: <vendor 0x046d> at usbus1                                              
uhub6: <vendor 0x046d product 0xc223, class 9/0, rev 1.10/1.03, addr 2> on 
usbus1                                                                               
uhub6: 4 ports with 2 removable, bus powered                                    
ugen1.3: <vendor 0x046d> at usbus1                                              
ukbd0: <vendor 0x046d Gaming Keyboard, class 0/0, rev 2.00/1.90, addr 3> on 
usbus1                                                                              
kbd2 at ukbd0                                                                   
uhid0: <vendor 0x046d Gaming Keyboard, class 0/0, rev 2.00/1.90, addr 3> on 
usbus1                                                                              
ugen1.4: <USBest Technology> at usbus1                                          
umass0: <USBest Technology USB Mass Storage Device, class 0/0, rev 2.00/1.00, 
addr 4> on usbus1                                                                 
umass0:  SCSI over Bulk-Only; quirks = 0x0000                                   
umass0:0:0:-1: Attached to scbus0                                               
da0 at umass-sim0 bus 0 target 0 lun 0                                          
da0: <Ut163 USB2FlashStorage 0.00> Removable Direct Access SCSI-2 device        
da0: 1.000MB/s transfers                                                        
da0: 250MB (512000 512 byte sectors: 64H 32S/T 250C)                            
GEOM: da0: partition 1 does not start on a track boundary.                      
GEOM: da0: partition 1 does not end on a track boundary.                        
ugen1.5: <Razer> at usbus1                                                      
ums0: <Razer Razer Copperhead Laser Mouse, class 0/0, rev 1.10/21.00, addr 5> 
on usbus1                                                                         
ums0: 7 buttons and [XYZ] coordinates ID=0                                      
ukbd1: <Razer Razer Copperhead Laser Mouse, class 0/0, rev 1.10/21.00, addr 5> 
on usbus1                                                                        
kbd3 at ukbd1                                                                   
ukbd_set_leds_callback:696: error=USB_ERR_STALLED                               
ugen1.6: <vendor 0x046d> at usbus1                                              
hid_get_item:364: Number of items truncated to 255                              
hid_get_item:364: Number of items truncated to 255                              
hid_get_item:364: Number of items truncated to 255                              
uhid1: <vendor 0x046d product 0xc222, class 0/0, rev 2.00/1.03, addr 6> on 
usbus1                                                                               
hid_get_item:364: Number of items truncated to 255                              
hid_get_item:364: Number of items truncated to 255                              
hid_get_item:364: Number of items truncated to 255                              
ukbd_set_leds_callback:696: error=USB_ERR_STALLED                               
ukbd_set_leds_callback:696: error=USB_ERR_STALLED                               
ukbd_set_leds_callback:696: error=USB_ERR_STALLED                               
ukbd_set_leds_callback:696: error=USB_ERR_STALLED                               
ugen1.4: <USBest Technology> at usbus1 (disconnected)                           
umass0: at uhub6, port 2, addr 4 (disconnected)                                 
(da0:umass-sim0:0:0:0): lost device                                             
(da0:umass-sim0:0:0:0): removing device entry                                   
lock order reversal:                                                            
 1st 0xffffff807bad21c0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559    
 2nd 0xffffff00192fca00 dirhash (dirhash) @ 
/usr/src/sys/ufs/ufs/ufs_dirhash.c:285
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_witness_debugger() at _witness_debugger+0x2e
witness_checkorder() at witness_checkorder+0x81e
_sx_xlock() at _sx_xlock+0x55
ufsdirhash_acquire() at ufsdirhash_acquire+0x33
ufsdirhash_add() at ufsdirhash_add+0x19
ufs_direnter() at ufs_direnter+0x88b
ufs_makeinode() at ufs_makeinode+0x2a7
VOP_CREATE_APV() at VOP_CREATE_APV+0x8d
vn_open_cred() at vn_open_cred+0x468
kern_openat() at kern_openat+0x179
syscall() at syscall+0x1af
Xfast_syscall() at Xfast_syscall+0xe1
--- syscall (5, FreeBSD ELF64, open), rip = 0x80336ee0c, rsp = 0x7fffffffc7c8, 
rbp = 0x8068021c0 ---
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ukbd_set_leds_callback:696: error=USB_ERR_STALLED
ugen1.4: <USBest Technology> at usbus1
umass0: <USBest Technology USB Mass Storage Device, class 0/0, rev 2.00/1.00, 
addr 4> on usbus1
umass0:  SCSI over Bulk-Only; quirks = 0x0000
umass0:0:0:-1: Attached to scbus0
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Ut163 USB2FlashStorage 0.00> Removable Direct Access SCSI-2 device
da0: 1.000MB/s transfers
da0: 250MB (512000 512 byte sectors: 64H 32S/T 250C)
GEOM: da0: partition 1 does not start on a track boundary.
GEOM: da0: partition 1 does not end on a track boundary.
GEOM: da0: partition 1 does not start on a track boundary.
GEOM: da0: partition 1 does not end on a track boundary.

From tomas at megalogika.lt  Wed Sep  9 12:40:01 2009
From: tomas at megalogika.lt (Tomas Verbaitis)
Date: Wed Sep  9 12:40:08 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
Message-ID: <200909091232.n89CWMvK033580@www.freebsd.org>


>Number:         138659
>Category:       usb
>Synopsis:       uftdi driver broken in RELENG_8/CURRENT
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Sep 09 12:40:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Tomas Verbaitis
>Release:        8-BETA4 9-CURRENT
>Organization:
Megalogika Ltd
>Environment:
8.0-BETA4 FreeBSD 8.0-BETA4 #19: Wed Sep  9 12:41:06 EEST 2009
 8.0-BETA2 FreeBSD 8.0-BETA2 #13: Wed Aug 19 11:40:46 EEST 2009
 9.0-CURRENT FreeBSD 9.0-CURRENT #73: Tue Sep  1 16:54:15 EEST 2009
>Description:
www/kannel use to run perfectly with two, three or four Teltonika ModemUSB/G10 USB modems connected. uftdi(4) driver was attaching to these modems.

after i upgraded one of the machines to then 8-CURRENT on Aug 19 2009, i noticed the following problems:
 - only single device appears to be responsive right after start of kannel
 - even that device is answering requests slower and slower until it stalls completely within 1 hour
>How-To-Repeat:
run www/kannel with 1 or 2 Teltonika ModemUSB/G10 attached to a machine running FreeBSD RELENG_8 or CURRENT
>Fix:
no idea :(

7.x still worked ok, so i suspect, that it must be related to USB2

>Release-Note:
>Audit-Trail:
>Unformatted:
From hselasky at c2i.net  Wed Sep  9 14:33:36 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Sep  9 14:33:42 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909091232.n89CWMvK033580@www.freebsd.org>
References: <200909091232.n89CWMvK033580@www.freebsd.org>
Message-ID: <200909091634.01263.hselasky@c2i.net>

On Wednesday 09 September 2009 14:32:22 Tomas Verbaitis wrote:
>  - even that device is answering requests slower and slower until it stalls
> completely within 1 hour

What is printed in dmesg?

Try enabling uftdi debugging:

sysctl hw.usb.uftdi.debug=15

Any errors?

--HPS
From hselasky at c2i.net  Wed Sep  9 15:40:03 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Sep  9 15:40:10 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
Message-ID: <200909091540.n89Fe3aZ086985@freefall.freebsd.org>

The following reply was made to PR usb/138659; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Tomas Verbaitis <tomas@megalogika.lt>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/138659: uftdi driver broken in RELENG_8/CURRENT
Date: Wed, 9 Sep 2009 16:34:00 +0200

 On Wednesday 09 September 2009 14:32:22 Tomas Verbaitis wrote:
 >  - even that device is answering requests slower and slower until it stalls
 > completely within 1 hour
 
 What is printed in dmesg?
 
 Try enabling uftdi debugging:
 
 sysctl hw.usb.uftdi.debug=15
 
 Any errors?
 
 --HPS
From linimon at FreeBSD.org  Wed Sep  9 19:15:09 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Sep  9 19:15:22 2009
Subject: usb/138675: [usb8] [panic] page fault, perhaps in USB
Message-ID: <200909091915.n89JF9Lu005594@freefall.freebsd.org>

Old Synopsis: [panic] page fault, perhaps in USB
New Synopsis: [usb8] [panic] page fault, perhaps in USB

Responsible-Changed-From-To: freebsd-bugs->freebsd-usb
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Sep 9 19:14:41 UTC 2009
Responsible-Changed-Why: 
reassign.

http://www.freebsd.org/cgi/query-pr.cgi?pr=138675
From alexbestms at math.uni-muenster.de  Wed Sep  9 20:20:03 2009
From: alexbestms at math.uni-muenster.de (Alexander Best)
Date: Wed Sep  9 20:20:10 2009
Subject: usb/130325: [usb] [patch] fix
 tools/tools/usb/print-usb-if-vids.sh
Message-ID: <200909092020.n89KK38H065403@freefall.freebsd.org>

The following reply was made to PR usb/130325; it has been noted by GNATS.

From: Alexander Best <alexbestms@math.uni-muenster.de>
To: <bug-followup@FreeBSD.org>
Cc:  
Subject: Re: usb/130325: [usb] [patch] fix
 tools/tools/usb/print-usb-if-vids.sh
Date: Wed, 09 Sep 2009 22:13:55 +0200 (CEST)

 since this is a script the file should have it's executable bit set (755).
 
 alex
From hselasky at c2i.net  Wed Sep  9 23:27:09 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Sep  9 23:27:16 2009
Subject: usb/138675: [usb8] [panic] page fault, perhaps in USB
In-Reply-To: <200909091915.n89JF9Lu005594@freefall.freebsd.org>
References: <200909091915.n89JF9Lu005594@freefall.freebsd.org>
Message-ID: <200909100127.30703.hselasky@c2i.net>

On Wednesday 09 September 2009 21:15:09 linimon@freebsd.org wrote:
> Old Synopsis: [panic] page fault, perhaps in USB
> New Synopsis: [usb8] [panic] page fault, perhaps in USB
>
> Responsible-Changed-From-To: freebsd-bugs->freebsd-usb
> Responsible-Changed-By: linimon
> Responsible-Changed-When: Wed Sep 9 19:14:41 UTC 2009
> Responsible-Changed-Why:
> reassign.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=138675

Hi,

There seems to be some unresolved problems when using multiple HUBs in series.

Try the following patches:

http://perforce.freebsd.org/chv.cgi?CH=168387

Simply download the complete files using the download link.

--HPS

From tomasv at megalogika.lt  Thu Sep 10 13:00:09 2009
From: tomasv at megalogika.lt (Tomas Verbaitis)
Date: Thu Sep 10 13:00:16 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
Message-ID: <200909101300.n8AD09qn018286@freefall.freebsd.org>

The following reply was made to PR usb/138659; it has been noted by GNATS.

From: Tomas Verbaitis <tomasv@megalogika.lt>
To: Hans Petter Selasky <hselasky@c2i.net>
Cc: freebsd-usb@freebsd.org, freebsd-gnats-submit@freebsd.org
Subject: Re: usb/138659: uftdi driver broken in RELENG_8/CURRENT
Date: Thu, 10 Sep 2009 15:52:54 +0300

 On Wed, Sep 09, 2009 at 04:34:00PM +0200, Hans Petter Selasky wrote:
 > On Wednesday 09 September 2009 14:32:22 Tomas Verbaitis wrote:
 > >  - even that device is answering requests slower and slower until it stalls
 > > completely within 1 hour
 > What is printed in dmesg?
 
 Without enabling uftdi debugging, the dmesg only notes device
 connections and removals (btw, the old usb stack would crash the system,
 if attached uftdi deviced was removed and the cuaU* was accessed, so,
 yes, there is an improvement ,))
 
 Sep  9 15:49:46 sklepas kernel: ugen0.2: <Teltonika> at usbus0
 Sep  9 15:49:46 sklepas kernel: uftdi0: <Teltonika ModemUSB/G10> on usbus0
 Sep  9 15:56:08 sklepas kernel: ugen0.2: <Teltonika> at usbus0 (disconnected)
 Sep  9 15:56:08 sklepas kernel: uftdi0: at uhub0, port 1, addr 2 (disconnected)
 Sep  9 15:56:25 sklepas kernel: ugen0.2: <Teltonika> at usbus0
 Sep  9 15:56:26 sklepas kernel: uftdi0: <Teltonika ModemUSB/G10> on usbus0
 Sep  9 15:56:33 sklepas kernel: ugen0.2: <Teltonika> at usbus0 (disconnected)
 Sep  9 15:56:33 sklepas kernel: uftdi0: at uhub0, port 1, addr 2 (disconnected)
 Sep  9 15:56:41 sklepas kernel: ugen0.2: <Teltonika> at usbus0
 Sep  9 15:56:41 sklepas kernel: uftdi0: <Teltonika ModemUSB/G10> on usbus0
 
 > Try enabling uftdi debugging:
 > sysctl hw.usb.uftdi.debug=15
 
 after enabling debug it went like this:
 
 * modem attached
 
 Sep 10 15:38:30 sklepas kernel: ugen0.2: <Teltonika> at usbus0
 Sep 10 15:38:30 sklepas kernel: uftdi0: <Teltonika ModemUSB/G10> on usbus0
 Sep 10 15:38:30 sklepas kernel: uftdi_attach:284:
 
 * kannel started -- it initialized the modem ok and tried to send an sms
 
 Sep 10 15:40:25 sklepas kernel: uftdi_pre_param:653: 
 Sep 10 15:40:25 sklepas kernel: uftdi_cfg_open:354: uftdi_pre_param:653: 
 Sep 10 15:40:25 sklepas kernel: uftdi_pre_param:653: 
 Sep 10 15:40:25 sklepas kernel: uftdi_read_callback:459: status change msr=0x90 (0x00) lsr=0x60 (0x00)
 Sep 10 15:40:25 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
 Sep 10 15:40:25 sklepas kernel: uftdi_cfg_param:672: 
 Sep 10 15:40:26 sklepas kernel: uftdi_cfg_param:672: 
 Sep 10 15:40:26 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
 Sep 10 15:40:28 sklepas kernel: uftdi_pre_param:653: 
 Sep 10 15:40:28 sklepas kernel: uftdi_cfg_open:354: uftdi_pre_param:653: 
 Sep 10 15:40:28 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
 Sep 10 15:40:28 sklepas kernel: uftdi_cfg_param:672: 
 Sep 10 15:40:28 sklepas kernel: uftdi_cfg_param:672: 
 Sep 10 15:40:28 sklepas kernel: uftdi_pre_param:653: 
 Sep 10 15:40:28 sklepas kernel: uftdi_cfg_param:672: 
 Sep 10 15:40:29 sklepas kernel: uftdi_read_callback:459: status change msr=0x10 (0x90) lsr=0x60 (0x60)
 Sep 10 15:40:29 sklepas kernel: uftdi_cfg_get_status:705: msr=0x10 lsr=0x60
 Sep 10 15:40:31 sklepas kernel: uftdi_read_callback:459: status change msr=0x30 (0x10) lsr=0x60 (0x60)
 Sep 10 15:40:31 sklepas kernel: uftdi_cfg_get_status:705: msr=0x30 lsr=0x60
 Sep 10 15:40:31 sklepas kernel: uftdi_read_callback:459: status change msr=0x10 (0x30) lsr=0x00 (0x60)
 Sep 10 15:40:31 sklepas kernel: uftdi_cfg_get_status:705: msr=0x10 lsr=0x00
 
 * the sms did not get sent, at least the modem did not acknowledge that
 as the communication with it stalled for ca. 4 minutes
 
 * i disconnected the modem and stopped kannel
 
 Sep 10 15:44:06 sklepas kernel: ugen0.2: <Teltonika> at usbus0 (disconnected)
 Sep 10 15:44:06 sklepas kernel: uftdi0: at uhub0, port 2, addr 2 (disconnected)
 
 * kannel stopped only after modem removal, as, apparently it was still
 trying to say at least an ATZ to the modem
 
 * repeated the same again:
 
 Sep 10 15:44:28 sklepas kernel: ugen0.2: <Teltonika> at usbus0
 Sep 10 15:44:28 sklepas kernel: uftdi0: <Teltonika ModemUSB/G10> on usbus0
 Sep 10 15:44:28 sklepas kernel: uftdi_attach:284: 
 Sep 10 15:44:39 sklepas kernel: uftdi_pre_param:653: 
 Sep 10 15:44:39 sklepas kernel: uftdi_cfg_open:354: uftdi_pre_param:653: 
 Sep 10 15:44:39 sklepas kernel: uftdi_pre_param:653: 
 Sep 10 15:44:39 sklepas kernel: uftdi_read_callback:459: status change msr=0x90 (0x00) lsr=0x60 (0x00)
 Sep 10 15:44:39 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
 Sep 10 15:44:39 sklepas kernel: uftdi_cfg_param:672: 
 Sep 10 15:44:39 sklepas kernel: uftdi_cfg_param:672: 
 Sep 10 15:44:40 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
 Sep 10 15:44:41 sklepas kernel: uftdi_pre_param:653: 
 Sep 10 15:44:41 sklepas kernel: uftdi_cfg_open:354: uftdi_pre_param:653: 
 Sep 10 15:44:41 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
 Sep 10 15:44:41 sklepas kernel: uftdi_cfg_param:672: 
 Sep 10 15:44:41 sklepas kernel: uftdi_cfg_param:672: 
 Sep 10 15:44:41 sklepas kernel: uftdi_pre_param:653: 
 Sep 10 15:44:41 sklepas kernel: uftdi_cfg_param:672: 
 Sep 10 15:44:42 sklepas kernel: uftdi_read_callback:459: status change msr=0x10 (0x90) lsr=0x60 (0x60)
 Sep 10 15:44:42 sklepas kernel: uftdi_cfg_get_status:705: msr=0x10 lsr=0x60
 Sep 10 15:44:44 sklepas kernel: uftdi_read_callback:459: status change msr=0x30 (0x10) lsr=0x60 (0x60)
 Sep 10 15:44:44 sklepas kernel: uftdi_cfg_get_status:705: msr=0x30 lsr=0x60
 Sep 10 15:44:44 sklepas kernel: uftdi_read_callback:459: status change msr=0x10 (0x30) lsr=0x00 (0x60)
 Sep 10 15:44:44 sklepas kernel: uftdi_cfg_get_status:705: msr=0x10 lsr=0x00
 Sep 10 15:45:15 sklepas kernel: ugen0.2: <Teltonika> at usbus0 (disconnected)
 Sep 10 15:45:15 sklepas kernel: uftdi0: at uhub0, port 2, addr 2 (disconnected)
 
 
 hope this helps. thank you for quick reaction!
 
 
 -- 
 Tomas "Verbaitis" Verbaitis ** http://megalogika.lt
From tomasv at megalogika.lt  Thu Sep 10 13:08:51 2009
From: tomasv at megalogika.lt (Tomas Verbaitis)
Date: Thu Sep 10 13:08:58 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909091634.01263.hselasky@c2i.net>
References: <200909091232.n89CWMvK033580@www.freebsd.org>
	<200909091634.01263.hselasky@c2i.net>
Message-ID: <20090910125254.GK3287@megalogika.lt>

On Wed, Sep 09, 2009 at 04:34:00PM +0200, Hans Petter Selasky wrote:
> On Wednesday 09 September 2009 14:32:22 Tomas Verbaitis wrote:
> >  - even that device is answering requests slower and slower until it stalls
> > completely within 1 hour
> What is printed in dmesg?

Without enabling uftdi debugging, the dmesg only notes device
connections and removals (btw, the old usb stack would crash the system,
if attached uftdi deviced was removed and the cuaU* was accessed, so,
yes, there is an improvement ,))

Sep  9 15:49:46 sklepas kernel: ugen0.2: <Teltonika> at usbus0
Sep  9 15:49:46 sklepas kernel: uftdi0: <Teltonika ModemUSB/G10> on usbus0
Sep  9 15:56:08 sklepas kernel: ugen0.2: <Teltonika> at usbus0 (disconnected)
Sep  9 15:56:08 sklepas kernel: uftdi0: at uhub0, port 1, addr 2 (disconnected)
Sep  9 15:56:25 sklepas kernel: ugen0.2: <Teltonika> at usbus0
Sep  9 15:56:26 sklepas kernel: uftdi0: <Teltonika ModemUSB/G10> on usbus0
Sep  9 15:56:33 sklepas kernel: ugen0.2: <Teltonika> at usbus0 (disconnected)
Sep  9 15:56:33 sklepas kernel: uftdi0: at uhub0, port 1, addr 2 (disconnected)
Sep  9 15:56:41 sklepas kernel: ugen0.2: <Teltonika> at usbus0
Sep  9 15:56:41 sklepas kernel: uftdi0: <Teltonika ModemUSB/G10> on usbus0

> Try enabling uftdi debugging:
> sysctl hw.usb.uftdi.debug=15

after enabling debug it went like this:

* modem attached

Sep 10 15:38:30 sklepas kernel: ugen0.2: <Teltonika> at usbus0
Sep 10 15:38:30 sklepas kernel: uftdi0: <Teltonika ModemUSB/G10> on usbus0
Sep 10 15:38:30 sklepas kernel: uftdi_attach:284:

* kannel started -- it initialized the modem ok and tried to send an sms

Sep 10 15:40:25 sklepas kernel: uftdi_pre_param:653: 
Sep 10 15:40:25 sklepas kernel: uftdi_cfg_open:354: uftdi_pre_param:653: 
Sep 10 15:40:25 sklepas kernel: uftdi_pre_param:653: 
Sep 10 15:40:25 sklepas kernel: uftdi_read_callback:459: status change msr=0x90 (0x00) lsr=0x60 (0x00)
Sep 10 15:40:25 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
Sep 10 15:40:25 sklepas kernel: uftdi_cfg_param:672: 
Sep 10 15:40:26 sklepas kernel: uftdi_cfg_param:672: 
Sep 10 15:40:26 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
Sep 10 15:40:28 sklepas kernel: uftdi_pre_param:653: 
Sep 10 15:40:28 sklepas kernel: uftdi_cfg_open:354: uftdi_pre_param:653: 
Sep 10 15:40:28 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
Sep 10 15:40:28 sklepas kernel: uftdi_cfg_param:672: 
Sep 10 15:40:28 sklepas kernel: uftdi_cfg_param:672: 
Sep 10 15:40:28 sklepas kernel: uftdi_pre_param:653: 
Sep 10 15:40:28 sklepas kernel: uftdi_cfg_param:672: 
Sep 10 15:40:29 sklepas kernel: uftdi_read_callback:459: status change msr=0x10 (0x90) lsr=0x60 (0x60)
Sep 10 15:40:29 sklepas kernel: uftdi_cfg_get_status:705: msr=0x10 lsr=0x60
Sep 10 15:40:31 sklepas kernel: uftdi_read_callback:459: status change msr=0x30 (0x10) lsr=0x60 (0x60)
Sep 10 15:40:31 sklepas kernel: uftdi_cfg_get_status:705: msr=0x30 lsr=0x60
Sep 10 15:40:31 sklepas kernel: uftdi_read_callback:459: status change msr=0x10 (0x30) lsr=0x00 (0x60)
Sep 10 15:40:31 sklepas kernel: uftdi_cfg_get_status:705: msr=0x10 lsr=0x00

* the sms did not get sent, at least the modem did not acknowledge that
as the communication with it stalled for ca. 4 minutes

* i disconnected the modem and stopped kannel

Sep 10 15:44:06 sklepas kernel: ugen0.2: <Teltonika> at usbus0 (disconnected)
Sep 10 15:44:06 sklepas kernel: uftdi0: at uhub0, port 2, addr 2 (disconnected)

* kannel stopped only after modem removal, as, apparently it was still
trying to say at least an ATZ to the modem

* repeated the same again:

Sep 10 15:44:28 sklepas kernel: ugen0.2: <Teltonika> at usbus0
Sep 10 15:44:28 sklepas kernel: uftdi0: <Teltonika ModemUSB/G10> on usbus0
Sep 10 15:44:28 sklepas kernel: uftdi_attach:284: 
Sep 10 15:44:39 sklepas kernel: uftdi_pre_param:653: 
Sep 10 15:44:39 sklepas kernel: uftdi_cfg_open:354: uftdi_pre_param:653: 
Sep 10 15:44:39 sklepas kernel: uftdi_pre_param:653: 
Sep 10 15:44:39 sklepas kernel: uftdi_read_callback:459: status change msr=0x90 (0x00) lsr=0x60 (0x00)
Sep 10 15:44:39 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
Sep 10 15:44:39 sklepas kernel: uftdi_cfg_param:672: 
Sep 10 15:44:39 sklepas kernel: uftdi_cfg_param:672: 
Sep 10 15:44:40 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
Sep 10 15:44:41 sklepas kernel: uftdi_pre_param:653: 
Sep 10 15:44:41 sklepas kernel: uftdi_cfg_open:354: uftdi_pre_param:653: 
Sep 10 15:44:41 sklepas kernel: uftdi_cfg_get_status:705: msr=0x90 lsr=0x60
Sep 10 15:44:41 sklepas kernel: uftdi_cfg_param:672: 
Sep 10 15:44:41 sklepas kernel: uftdi_cfg_param:672: 
Sep 10 15:44:41 sklepas kernel: uftdi_pre_param:653: 
Sep 10 15:44:41 sklepas kernel: uftdi_cfg_param:672: 
Sep 10 15:44:42 sklepas kernel: uftdi_read_callback:459: status change msr=0x10 (0x90) lsr=0x60 (0x60)
Sep 10 15:44:42 sklepas kernel: uftdi_cfg_get_status:705: msr=0x10 lsr=0x60
Sep 10 15:44:44 sklepas kernel: uftdi_read_callback:459: status change msr=0x30 (0x10) lsr=0x60 (0x60)
Sep 10 15:44:44 sklepas kernel: uftdi_cfg_get_status:705: msr=0x30 lsr=0x60
Sep 10 15:44:44 sklepas kernel: uftdi_read_callback:459: status change msr=0x10 (0x30) lsr=0x00 (0x60)
Sep 10 15:44:44 sklepas kernel: uftdi_cfg_get_status:705: msr=0x10 lsr=0x00
Sep 10 15:45:15 sklepas kernel: ugen0.2: <Teltonika> at usbus0 (disconnected)
Sep 10 15:45:15 sklepas kernel: uftdi0: at uhub0, port 2, addr 2 (disconnected)


hope this helps. thank you for quick reaction!


-- 
Tomas "Verbaitis" Verbaitis ** http://megalogika.lt
From mailing at ekomedya.com  Thu Sep 10 15:18:29 2009
From: mailing at ekomedya.com (=?utf-8?Q?Eko_Bilgisayar_ve_=C4=B0leti=C5=9Fim_Hizmetleri_Ltd=2E_=C5=9Eti?=)
Date: Thu Sep 10 15:18:58 2009
Subject: Turkey Calling You To Visit - The Trade SHOW- In Las Vegas
Message-ID: <874ac7d6661f30feef603473661919d8@localhost.localdomain>

[http://www.turkeycalling.us]

[http://www.turkeycalling.us]

[http://www.turkeycalling.us]

[http://www.turkeycalling.us/turkey-fam/turkeyfam.htm]

Global Access Travel invites you to the Tradeshow in Las Vegas on September 13-15, 2009. Please visit us to get more information about our organization and services at our booth. If you fill the registration form or leave the business card when you visit us at our booth, you might be lucky visitor who is going to win our daily draw prize; Free inspection trip to Turkey. 

Yasal Uyar?;
Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini
hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir,
yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n
olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya
kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj
tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve
sisteminizden siliniz. Global Access Travel bu mesajin icerigi ile ilgili
olarak hicbir hukuksal sorumlulugu kabul etmez

Disclaimer
This e-mail communication is intended only for the use of the individual
or entity to which it is addressed, and may contain information that is
privileged, confidential and that may not be made public by law or
agreement. If the recipient of this message is not the intended recipient
or entity, you are hereby notified that any further dissemination,
distribution or copying of this information is strictly prohibited. If you
have received this message in error, please immediately notify the sender
and delete it from your system. The Global Access Traveldoes not accept
legal responsibility for the contents of this message. Yasal Uyar?;
Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini
hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir,
yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n
olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya
kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj
tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve
sisteminizden siliniz. Global Access Travel bu mesajin icerigi ile ilgili
olarak hicbir hukuksal sorumlulugu kabul etmez

Disclaimer
This e-mail communication is intended only for the use of the individual
or entity to which it is addressed, and may contain information that is
privileged, confidential and that may not be made public by law or
agreement. If the recipient of this message is not the intended recipient
or entity, you are hereby notified that any further dissemination,
distribution or copying of this information is strictly prohibited. If you
have received this message in error, please immediately notify the sender
and delete it from your system. The Global Access Traveldoes not accept
legal responsibility for the contents of this message. Yasal Uyar?;
Bu e-posta, sadece adreste belirtilen kisi veya kurulusun kullanimini
hedeflemekte olup,mesajda yer alan bilgiler kisiye ozel ve gizli olabilir,
yasalar ya da anlasmalar geregi ?c?nc? kisiler ile paylasilmasi m?mk?n
olmayabilir.Mesaji alan kisi, mesajin g?nderilmek istendigi kisi veya
kurulus degilse,bu mesaji yaymak,dagitmak veya kopyalamak yasaktir Mesaj
tarafiniza yanlislikla ulasmissa l?tfen mesaji geri g?nderiniz ve
sisteminizden siliniz. Global Access Travel bu mesajin icerigi ile ilgili
olarak hicbir hukuksal sorumlulugu kabul etmez

Disclaimer
This e-mail communication is intended only for the use of the individual
or entity to which it is addressed, and may contain information that is
privileged, confidential and that may not be made public by law or
agreement. If the recipient of this message is not the intended recipient
or entity, you are hereby notified that any further dissemination,
distribution or copying of this information is strictly prohibited. If you
have received this message in error, please immediately notify the sender
and delete it from your system. The Global Access Traveldoes not accept
legal responsibility for the contents of this message.
This message was sent by: TURKEY CALLING YOU TO VISIT "THE TRADE SHOW"  IN LAS VEGAS, N?zhetiye Cad, istanbul, Besiktas 34357, Turkey

Manage your subscription:
http://app.icontact.com/icp/mmail-mprofile.pl?r=47622560&l=82253&s=HWWN&m=587775&c=305227


From hselasky at c2i.net  Thu Sep 10 17:11:25 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Sep 10 17:11:33 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909101300.n8AD09qn018286@freefall.freebsd.org>
References: <200909101300.n8AD09qn018286@freefall.freebsd.org>
Message-ID: <200909101911.48970.hselasky@c2i.net>

On Thursday 10 September 2009 15:00:09 Tomas Verbaitis wrote:
> The following reply was made to PR usb/138659; it has been noted by GNATS.
>

Hi,

The UFTDI driver does not have any printouts for data write.

Try setting 

sysctl hw.usb.ucom.debug=15

If you don't see any "ucom_get_data" printouts, then there is something wrong.

--HPS

From gavin at FreeBSD.org  Fri Sep 11 09:37:09 2009
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Fri Sep 11 09:37:15 2009
Subject: usb/137226: [usb67][patch] quirk for Philips extern USB disk
Message-ID: <200909110937.n8B9b85W080946@freefall.freebsd.org>

Old Synopsis: [patch] quirk for Philips extern USB disk
New Synopsis: [usb67][patch] quirk for Philips extern USB disk

State-Changed-From-To: open->patched
State-Changed-By: gavin
State-Changed-When: Fri Sep 11 09:36:21 UTC 2009
State-Changed-Why: 
Fixed in -HEAD

http://www.freebsd.org/cgi/query-pr.cgi?pr=137226
From gavin at FreeBSD.org  Fri Sep 11 09:49:29 2009
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Fri Sep 11 09:49:36 2009
Subject: usb/137138: [umass][usb67][patch] QUIRK: ASUS PDA Flash disk
	emulation
Message-ID: <200909110949.n8B9nSNY090615@freefall.freebsd.org>

Old Synopsis: [umass] [patch] QUIRK: ASUS PDA Flash disk emulation
New Synopsis: [umass][usb67][patch] QUIRK: ASUS PDA Flash disk emulation

State-Changed-From-To: open->feedback
State-Changed-By: gavin
State-Changed-When: Fri Sep 11 09:47:58 UTC 2009
State-Changed-Why: 
To submitter: This has been fixed in HEAD so will be in 8.0 when it is released.
Do you know if it is also an issue in 7.x?  Thanks!


Responsible-Changed-From-To: freebsd-usb->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Fri Sep 11 09:47:58 UTC 2009
Responsible-Changed-Why: 
Track

http://www.freebsd.org/cgi/query-pr.cgi?pr=137138
From gavin at FreeBSD.org  Fri Sep 11 09:50:31 2009
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Fri Sep 11 09:50:37 2009
Subject: usb/137789: [patch][usb67]Add quirks for EeePC 901 SD card
	reader
Message-ID: <200909110950.n8B9oUvD094669@freefall.freebsd.org>

Old Synopsis: Add quirks for EeePC 901 SD card reader
New Synopsis: [patch][usb67]Add quirks for EeePC 901 SD card reader

State-Changed-From-To: open->feedback
State-Changed-By: gavin
State-Changed-When: Fri Sep 11 09:49:30 UTC 2009
State-Changed-Why: 
To submitter: This has been fixed in HEAD so will be in 8.0 when it is released.
Do you know if it is also an issue in 7.x?  Thanks!


Responsible-Changed-From-To: freebsd-usb->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Fri Sep 11 09:49:30 UTC 2009
Responsible-Changed-Why: 
Track

http://www.freebsd.org/cgi/query-pr.cgi?pr=137789
From gavin at FreeBSD.org  Fri Sep 11 09:51:12 2009
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Fri Sep 11 09:51:19 2009
Subject: usb/135372: [usb67][umass] Quirk report for Teclast TL-C300 usb
	media player
Message-ID: <200909110951.n8B9pB9G099951@freefall.freebsd.org>

Old Synopsis: Quirk report for Teclast TL-C300 usb media player
New Synopsis: [usb67][umass] Quirk report for Teclast TL-C300 usb media player

State-Changed-From-To: open->patched
State-Changed-By: gavin
State-Changed-When: Fri Sep 11 09:50:33 UTC 2009
State-Changed-Why: 
Fixed in HEAD.

http://www.freebsd.org/cgi/query-pr.cgi?pr=135372
From gavin at FreeBSD.org  Fri Sep 11 11:01:07 2009
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Fri Sep 11 11:01:13 2009
Subject: usb/138548: usb devices periodically have unknown activity
Message-ID: <200909111101.n8BB16C7072441@freefall.freebsd.org>

Synopsis: usb devices periodically have unknown activity

State-Changed-From-To: open->feedback
State-Changed-By: gavin
State-Changed-When: Fri Sep 11 10:46:47 UTC 2009
State-Changed-Why: 
To submitter:  Other than the LEDs flashing, do these devices work correctly?
Can you please provide the output of "usbdevs -v" when these devices are plugged
in?


Responsible-Changed-From-To: freebsd-usb->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Fri Sep 11 10:46:47 UTC 2009
Responsible-Changed-Why: 
Track

http://www.freebsd.org/cgi/query-pr.cgi?pr=138548
From yerenkow at gmail.com  Sat Sep 12 23:10:00 2009
From: yerenkow at gmail.com (Alexander Yerenkow)
Date: Sat Sep 12 23:10:33 2009
Subject: usb/138548: usb devices periodically have unknown activity
In-Reply-To: <200909111101.n8BB16C7072441@freefall.freebsd.org>
References: <200909111101.n8BB16C7072441@freefall.freebsd.org>
Message-ID: <a61b04150909121544g845ce62kf0ba7a3e4966d4e8@mail.gmail.com>

2009/9/11 <gavin@freebsd.org>

> Synopsis: usb devices periodically have unknown activity
>
> State-Changed-From-To: open->feedback
> State-Changed-By: gavin
> State-Changed-When: Fri Sep 11 10:46:47 UTC 2009
> State-Changed-Why:
> To submitter:  Other than the LEDs flashing, do these devices work
> correctly?
> Can you please provide the output of "usbdevs -v" when these devices are
> plugged
> in?
>
> Hi!
I currently have 8..0-BETA3 here, but still blinking.
Don't know exactly which info I should provide, but here something in
attach.
If this isn't sufficient, tell me what other info I should provide.



>
> Responsible-Changed-From-To: freebsd-usb->gavin
> Responsible-Changed-By: gavin
> Responsible-Changed-When: Fri Sep 11 10:46:47 UTC 2009
> Responsible-Changed-Why:
> Track
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=138548
>



-- 
Regards,
Alexander Yerenkow
-------------- next part --------------
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON


 Configuration index 0

    bLength = 0x0009 
    bDescriptorType = 0x0002 
    wTotalLength = 0x0019 
    bNumInterfaces = 0x0001 
    bConfigurationValue = 0x0001 
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x0040 
    bMaxPower = 0x0000 

    Interface 0
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0000 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0001 
      bInterfaceClass = 0x0009 
      bInterfaceSubClass = 0x0000 
      bInterfaceProtocol = 0x0000 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0081 
        bmAttributes = 0x0003 
        wMaxPacketSize = 0x0008 
        bInterval = 0x00ff 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 



ugen1.1: <UHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON


 Configuration index 0

    bLength = 0x0009 
    bDescriptorType = 0x0002 
    wTotalLength = 0x0019 
    bNumInterfaces = 0x0001 
    bConfigurationValue = 0x0001 
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x0040 
    bMaxPower = 0x0000 

    Interface 0
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0000 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0001 
      bInterfaceClass = 0x0009 
      bInterfaceSubClass = 0x0000 
      bInterfaceProtocol = 0x0000 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0081 
        bmAttributes = 0x0003 
        wMaxPacketSize = 0x0008 
        bInterval = 0x00ff 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 



ugen2.1: <UHCI root HUB Intel> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON


 Configuration index 0

    bLength = 0x0009 
    bDescriptorType = 0x0002 
    wTotalLength = 0x0019 
    bNumInterfaces = 0x0001 
    bConfigurationValue = 0x0001 
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x0040 
    bMaxPower = 0x0000 

    Interface 0
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0000 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0001 
      bInterfaceClass = 0x0009 
      bInterfaceSubClass = 0x0000 
      bInterfaceProtocol = 0x0000 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0081 
        bmAttributes = 0x0003 
        wMaxPacketSize = 0x0008 
        bInterval = 0x00ff 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 



ugen3.1: <UHCI root HUB Intel> at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON


 Configuration index 0

    bLength = 0x0009 
    bDescriptorType = 0x0002 
    wTotalLength = 0x0019 
    bNumInterfaces = 0x0001 
    bConfigurationValue = 0x0001 
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x0040 
    bMaxPower = 0x0000 

    Interface 0
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0000 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0001 
      bInterfaceClass = 0x0009 
      bInterfaceSubClass = 0x0000 
      bInterfaceProtocol = 0x0000 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0081 
        bmAttributes = 0x0003 
        wMaxPacketSize = 0x0008 
        bInterval = 0x00ff 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 



ugen4.1: <EHCI root HUB Intel> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON


 Configuration index 0

    bLength = 0x0009 
    bDescriptorType = 0x0002 
    wTotalLength = 0x0019 
    bNumInterfaces = 0x0001 
    bConfigurationValue = 0x0001 
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x0040 
    bMaxPower = 0x0000 

    Interface 0
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0000 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0001 
      bInterfaceClass = 0x0009 
      bInterfaceSubClass = 0x0000 
      bInterfaceProtocol = 0x0000 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0081 
        bmAttributes = 0x0003 
        wMaxPacketSize = 0x0008 
        bInterval = 0x00ff 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 



ugen1.2: <USB-PS/2 Optical Mouse Logitech> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON


 Configuration index 0

    bLength = 0x0009 
    bDescriptorType = 0x0002 
    wTotalLength = 0x0022 
    bNumInterfaces = 0x0001 
    bConfigurationValue = 0x0001 
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x00a0 
    bMaxPower = 0x0031 

    Interface 0
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0000 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0001 
      bInterfaceClass = 0x0003 
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0002 
      iInterface = 0x0000  <no string>

      Additional Descriptor

      bLength = 0x09
      bDescriptorType = 0x21
      bDescriptorSubType = 0x10
       RAW dump: 
       0x00 | 0x09, 0x21, 0x10, 0x01, 0x00, 0x01, 0x22, 0x3b, 
       0x08 | 0x00

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0081 
        bmAttributes = 0x0003 
        wMaxPacketSize = 0x0005 
        bInterval = 0x000a 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 



ugen4.2: <Voyager GT Corsair> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON


 Configuration index 0

    bLength = 0x0009 
    bDescriptorType = 0x0002 
    wTotalLength = 0x0020 
    bNumInterfaces = 0x0001 
    bConfigurationValue = 0x0001 
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x0080 
    bMaxPower = 0x0032 

    Interface 0
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0000 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0002 
      bInterfaceClass = 0x0008 
      bInterfaceSubClass = 0x0006 
      bInterfaceProtocol = 0x0050 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0081 
        bmAttributes = 0x0002 
        wMaxPacketSize = 0x0200 
        bInterval = 0x00ff 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 

     Endpoint 1
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0002 
        bmAttributes = 0x0002 
        wMaxPacketSize = 0x0200 
        bInterval = 0x00ff 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 



ugen1.3: <ISSCEDRBTA ISSC> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON


 Configuration index 0

    bLength = 0x0009 
    bDescriptorType = 0x0002 
    wTotalLength = 0x00ba 
    bNumInterfaces = 0x0003 
    bConfigurationValue = 0x0001 
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x00c0 
    bMaxPower = 0x0000 

    Interface 0
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0000 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0003 
      bInterfaceClass = 0x00e0 
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0001 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0081 
        bmAttributes = 0x0003 
        wMaxPacketSize = 0x0010 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 

     Endpoint 1
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0002 
        bmAttributes = 0x0002 
        wMaxPacketSize = 0x0040 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 

     Endpoint 2
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0082 
        bmAttributes = 0x0002 
        wMaxPacketSize = 0x0040 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 


    Interface 1
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0001 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0002 
      bInterfaceClass = 0x00e0 
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0001 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0003 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0000 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 

     Endpoint 1
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0083 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0000 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 


    Interface 1 Alt 1
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0001 
      bAlternateSetting = 0x0001 
      bNumEndpoints = 0x0002 
      bInterfaceClass = 0x00e0 
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0001 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0003 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0009 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 

     Endpoint 1
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0083 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0009 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 


    Interface 1 Alt 2
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0001 
      bAlternateSetting = 0x0002 
      bNumEndpoints = 0x0002 
      bInterfaceClass = 0x00e0 
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0001 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0003 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0011 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 

     Endpoint 1
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0083 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0011 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 


    Interface 1 Alt 3
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0001 
      bAlternateSetting = 0x0003 
      bNumEndpoints = 0x0002 
      bInterfaceClass = 0x00e0 
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0001 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0003 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0019 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 

     Endpoint 1
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0083 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0019 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 


    Interface 1 Alt 4
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0001 
      bAlternateSetting = 0x0004 
      bNumEndpoints = 0x0002 
      bInterfaceClass = 0x00e0 
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0001 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0003 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0021 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 

     Endpoint 1
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0083 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0021 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 


    Interface 1 Alt 5
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0001 
      bAlternateSetting = 0x0005 
      bNumEndpoints = 0x0002 
      bInterfaceClass = 0x00e0 
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0001 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0003 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0031 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 

     Endpoint 1
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0083 
        bmAttributes = 0x0001 
        wMaxPacketSize = 0x0031 
        bInterval = 0x0001 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 


    Interface 2
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0002 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0000 
      bInterfaceClass = 0x00fe 
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0000 
      iInterface = 0x0000  <no string>


-------------- next part --------------
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0100 
  bDeviceClass = 0x0009 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x0000 
  idProduct = 0x0000 
  bcdDevice = 0x0100 
  iManufacturer = 0x0001  <Intel>
  iProduct = 0x0002  <UHCI root HUB>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001 

ugen1.1: <UHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0100 
  bDeviceClass = 0x0009 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x0000 
  idProduct = 0x0000 
  bcdDevice = 0x0100 
  iManufacturer = 0x0001  <Intel>
  iProduct = 0x0002  <UHCI root HUB>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001 

ugen2.1: <UHCI root HUB Intel> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0100 
  bDeviceClass = 0x0009 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x0000 
  idProduct = 0x0000 
  bcdDevice = 0x0100 
  iManufacturer = 0x0001  <Intel>
  iProduct = 0x0002  <UHCI root HUB>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001 

ugen3.1: <UHCI root HUB Intel> at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0100 
  bDeviceClass = 0x0009 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x0000 
  idProduct = 0x0000 
  bcdDevice = 0x0100 
  iManufacturer = 0x0001  <Intel>
  iProduct = 0x0002  <UHCI root HUB>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001 

ugen4.1: <EHCI root HUB Intel> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x0009 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0001 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x0000 
  idProduct = 0x0000 
  bcdDevice = 0x0100 
  iManufacturer = 0x0001  <Intel>
  iProduct = 0x0002  <EHCI root HUB>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001 

ugen1.2: <USB-PS/2 Optical Mouse Logitech> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x0000 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0008 
  idVendor = 0x046d 
  idProduct = 0xc050 
  bcdDevice = 0x2720 
  iManufacturer = 0x0001  <Logitech>
  iProduct = 0x0002  <USB-PS/2 Optical Mouse>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001 

ugen4.2: <Voyager GT Corsair> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x0000 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x1b1c 
  idProduct = 0x1a90 
  bcdDevice = 0x1100 
  iManufacturer = 0x0001  <Corsair>
  iProduct = 0x0002  <Voyager GT>
  iSerialNumber = 0x0003  <A704012700015835>
  bNumConfigurations = 0x0001 

ugen1.3: <ISSCEDRBTA ISSC> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x00e0 
  bDeviceSubClass = 0x0001 
  bDeviceProtocol = 0x0001 
  bMaxPacketSize0 = 0x0010 
  idVendor = 0x1131 
  idProduct = 0x1004 
  bcdDevice = 0x0373 
  iManufacturer = 0x0001  <ISSC>
  iProduct = 0x0002  <ISSCEDRBTA>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001 
From hselasky at c2i.net  Sun Sep 13 10:43:38 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Sep 13 10:43:45 2009
Subject: usb/127980: [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x
	and 8.x
In-Reply-To: <20090912202054.GH21096@elmar.spoerlein.net>
References: <20090824115440.GA30195@elmar.spoerlein.net>
	<20090912202054.GH21096@elmar.spoerlein.net>
Message-ID: <200909131244.00946.hselasky@c2i.net>

On Saturday 12 September 2009 22:20:54 Ulrich Sp?rlein wrote:
> Greetings Hans,
>
> may I turn your attention to this regression on 7.x, 8.x and HEAD? The
> following quirk breaks this Samsung device, but is still required on 6.x
>
> Weird, isn't it? Anyway, could you please see that the PR is committed
> in time for 8.0 Release?
>

Maybe not for 8.0 Release.

It is now removed from USB P4:

http://perforce.freebsd.org/chv.cgi?CH=168490

--HPS

From vinnix.bsd at gmail.com  Sun Sep 13 12:43:57 2009
From: vinnix.bsd at gmail.com (Vinicius Abrahao)
Date: Sun Sep 13 12:44:03 2009
Subject: CFH: fix multimedia/pwcbsd with usb2
In-Reply-To: <a01628140909121905g2c0eb578kbc105fab5b1ca388@mail.gmail.com>
References: <20090908201713.GD41185@e.0x20.net>
	<20090909104528.20b28e65@ernst.jennejohn.org>
	<20090909181620.GA19090@e.0x20.net>
	<1e31c7980909121438p6389820fte3923b4c9c9729e8@mail.gmail.com>
	<a01628140909121905g2c0eb578kbc105fab5b1ca388@mail.gmail.com>
Message-ID: <1e31c7980909130516g1b3cb9fn5df77c23ec072413@mail.gmail.com>

Thanks Florent,

That's it for sure. I recompile my kernel yesterday and now pwcbsd is
loading normally.
Therefore, now I see that pwc is the wrong driver for me. My webcam is
a Philips SPC500NC.
ID 093a:2603 Pixart Imaging, Inc.

At Google I found that linux-gspca-kmod is the right driver for me.
But this seen broken as
pwcbsd was in the past.

In file included from
/usr/local/share/linux-kmod-compat/linux_compat/ldev_stub.c:44:
/usr/local/share/linux-kmod-compat/linux_compat/ldev_stub.h:69:30:
error: dev/usb/usb_port.h: No such file or directory
In file included from
/usr/local/share/linux-kmod-compat/linux_compat/linux_compat.c:44:
/usr/local/share/linux-kmod-compat/linux_compat/ldev_stub.h:69:30:
error: dev/usb/usb_port.h: No such file or directory
mkdep: compile failed
*** Error code 1

I'm using linux_base-f10-10_2 / linux-kmod-compat-20080408 with the
9.0 (-current).


Thanks in advance,
Vinicius



search related:
[1] http://forums.freebsd.org/showthread.php?t=2163
[2] http://www.freebsd.org/cgi/cvsweb.cgi/ports/multimedia/linux-gspca-kmod/



On Sat, Sep 12, 2009 at 11:05 PM, Florent Thoumie <flz@xbsd.org> wrote:
> On Sat, Sep 12, 2009 at 10:38 PM, Vinicius Abrahao <vinnix.bsd@gmail.com>
> wrote:
>>
>> Hi Guys,
>>
>> Thanks for hard work with pwcbsd. Now the port is compile here ?at
>> 9.0-current, but
>> I'm have some trouble to load the module:
>>
>> KLD pwc.ko: depends on kernel - not available or version mismatch
>> linker_load_file: Unsupported file type
>>
>> using the 9.0-CURRENT #16: Sun Sep ?6 10:40:56 BRT 2009 .
>>
>> Any ideas?
>
> You've compiled pwcbsd against kernel sources that aren't in sync with the
> kernel you're running.
>
> --
> Florent Thoumie
> flz@FreeBSD.org
> FreeBSD Committer
>
From hselasky at c2i.net  Sun Sep 13 13:07:41 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Sep 13 13:07:48 2009
Subject: CFH: fix multimedia/pwcbsd with usb2
In-Reply-To: <1e31c7980909130516g1b3cb9fn5df77c23ec072413@mail.gmail.com>
References: <20090908201713.GD41185@e.0x20.net>
	<a01628140909121905g2c0eb578kbc105fab5b1ca388@mail.gmail.com>
	<1e31c7980909130516g1b3cb9fn5df77c23ec072413@mail.gmail.com>
Message-ID: <200909131508.05025.hselasky@c2i.net>

On Sunday 13 September 2009 14:16:10 Vinicius Abrahao wrote:
> Thanks Florent,
>
> That's it for sure. I recompile my kernel yesterday and now pwcbsd is
> loading normally.
> Therefore, now I see that pwc is the wrong driver for me. My webcam is
> a Philips SPC500NC.
> ID 093a:2603 Pixart Imaging, Inc.
>
> At Google I found that linux-gspca-kmod is the right driver for me.
> But this seen broken as
> pwcbsd was in the past.

Hi,

The closes you will currently get is:

svn --username anonsvn --password anonsvn \
      checkout svn://svn.turbocat.net/i4b/trunk/usbcam/ulinux

As root:

make fetch
make patch
make

You manually have to patch:

ee libv4l/v4l2-apps/libv4l/libv4lconvert/control/libv4lcontrol.c

control/libv4lcontrol.c: In function 'v4lcontrol_vidioc_queryctrl':
control/libv4lcontrol.c:586: error: '__u32' undeclared (first use in this 
function)
control/libv4lcontrol.c:586: error: (Each undeclared identifier is reported 
only once
control/libv4lcontrol.c:586: error: for each function it appears in.)
control/libv4lcontrol.c:586: error: expected ';' before 'orig_id'
control/libv4lcontrol.c:600: error: 'orig_id' undeclared (first use in this 
function)

__u32 to uint32_t

In the end:

cd pwcview

./pwcview


Should bring your webcam right up in userland though.

--HPS

From sweetnavelorange at gmail.com  Mon Sep 14 03:20:03 2009
From: sweetnavelorange at gmail.com (James Butler)
Date: Mon Sep 14 03:20:10 2009
Subject: usb/138798: 8.0-BETA4 can't boot from USB flash drive
Message-ID: <200909140311.n8E3Bd4Y078459@www.freebsd.org>


>Number:         138798
>Category:       usb
>Synopsis:       8.0-BETA4 can't boot from USB flash drive
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 14 03:20:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     James Butler
>Release:        8.0-BETA4 (amd64)
>Organization:
>Environment:
n/a (can't boot)
>Description:
On FreeBSD 8 with certain USB flash drives and/or USB controllers, when booting from a USB drive the device does not become available until after the system has tried (and failed) to mount / from it. After this has occurred, the user is prompted to manually enter the device name at the mountroot> prompt; for me, even this doesn't work, and the device is not listed in the output from the ? command.

This machine boots 7.2 without problems from the same device.

Trying an 8-STABLE kernel from 5 September (identifies as 8.0-BETA4), here is the last bit of the kernel messages (typed):

root mount waiting for: usbus2 usbus1 usbus0
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
root mount waiting for: usbus2
uhub2: 2 ports with 2 removable, self powered
root mount waiting for: usbus2
ugen2.2: <TOSHIBA> at usbus2
umass0: <Toshiba TransMemory, class 0/0, rev 2.00/1.00, addr 2> on usbus2
umass0:  SCSI over Bulk-Only; quirks = 0x0000
root mount waiting for: usbus2
umass0:0:0:-1: Attached to scbus0
Trying to mount root from ufs:/dev/da0s1a
ROOT MOUNT ERROR:
If you have invalid mount options, reboot, and da0 at umass-sim0 bus 0
target 0 lun 0
da0: <TOSHIBA TransMemory PMAP> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 3875MB (7936000 512 byte sectors: 255H 63S/T 493C)
first try the following from
the loader prompt:

etc. This clearly shows the device being detected after mounting has failed.
>How-To-Repeat:
Install FreeBSD-8.0-BETA4 to a USB flash drive, and attempt to boot from it.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From freebsd at sopwith.solgatos.com  Mon Sep 14 04:44:55 2009
From: freebsd at sopwith.solgatos.com (Dieter)
Date: Mon Sep 14 04:45:01 2009
Subject: usb/113977: [request] Need a way to set mode of USB disk's
	write cache 
In-Reply-To: Your message of "Mon, 31 Aug 2009 12:14:11 GMT."
	<200908311214.n7VCEBJ2046645@freefall.freebsd.org> 
Message-ID: <200909132345.XAA21847@sopwith.solgatos.com>

In message <200908311214.n7VCEBJ2046645@freefall.freebsd.org>, gavin@FreeBSD.org writes:
> Synopsis: [request] Need a way to set mode of USB disk's write cache
> 
> State-Changed-From-To: suspended->feedback
> State-Changed-By: gavin
> State-Changed-When: Mon Aug 31 12:07:21 UTC 2009
> State-Changed-Why: 
> To submitter: Sorry that this PR has not been looked at since
> submission.  If your external device supports changing write
> cache, I think it should be visible with "camcontrol modepage da0 -m 8".
> If that doesn't work, I don't know if there is any way you can
> achieve what you want to do.
> 
> 
> Responsible-Changed-From-To: freebsd-usb->gavin
> Responsible-Changed-By: gavin
> Responsible-Changed-When: Mon Aug 31 12:07:21 UTC 2009
> Responsible-Changed-Why: 
> Track
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=113977

With:  umass0: <Prolific Technology Inc. ATAPI-6 Bridge Controller, class 0/0, rev 2.00/0.01, addr 2> on uhub4

# camcontrol modepage da0 -l
0x2f

# camcontrol modepage da0 -m 8
IC:  0
ABPF:  0
CAP:  0
DISC:  0
SIZE:  0
WCE:  0
MF:  0
RCD:  0
Demand Retention Priority:  0
Write Retention Priority:  0
Disable Pre-fetch Transfer Length:  0
Minimum Pre-fetch:  0
Maximum Pre-fetch:  0
Maximum Pre-fetch Ceiling:  0

# camcontrol modepage da0 -m 0x8 -e
camcontrol: no editable entries


With:  umass0: <JMicron USB to ATA/ATAPI Bridge, class 0/0, rev 2.00/1.00, addr 2> on uhub1

# camcontrol modepage da0 -l

gives no response (just a new shell prompt)

# camcontrol modepage da0 -m 0x8
camcontrol: error sending mode sense command

I tried several other values for -m with the same results.
From bugmaster at FreeBSD.org  Mon Sep 14 11:07:11 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Sep 14 11:09:50 2009
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200909141107.n8EB7AVt072517@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o usb/138798   usb        8.0-BETA4 can't boot from USB flash drive
o usb/138675   usb        [usb8] [panic] page fault, perhaps in USB
o usb/138659   usb        [usb8][uftdi] driver broken in RELENG_8/CURRENT
o usb/138563   usb        [usb8] [patch] Increase buffer sizes to accomodate lon
o usb/138389   usb        [usb8] [patch] NULL pointer dereference in usb_endpoin
o usb/138175   usb        [usb67] [boot] System cannot boot, when USB reader wit
o usb/138172   usb        Additional dev id for u3g (Option mini PCIe)
o usb/138138   usb        Novatel U760 for u3g (Verizon and Bell Canada)
o usb/138124   usb        [usb8] Axed uaudio functionality in the usbng (alterna
o usb/138119   usb        MultiBay CDROM (propably on USB bus) is not recognized
o usb/137872   usb        slow booting on usb flash drive
f usb/137848   usb        Page fault when using an USB bluetooth adapter
o usb/137806   usb        [ukbd] USB keyboard doesn't work until it's unplugged
o usb/137763   usb        [usb67][ukbd] Logitech wireless keyboard media keys no
o usb/137616   usb        [usb67][usb8][usbdevs] [patch]: usbdevs update: Please
o usb/137377   usb        [usb8] Support for Huawei E180
o usb/137341   usb        [usb8][rum] driver if_rum doesn't work at all and thro
p usb/137226   usb        [usb67][patch] quirk for Philips extern USB disk
o usb/137191   usb        [usb8][patch] export ums(4) output report parser data 
o 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        SteelSeries Ikari USB laser mouse not attaching
o usb/137035   usb        Sony cyber-shot DSC-P72 not accessible - cam quirks
p usb/136761   usb        [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H
o usb/135938   usb        [aue] aue driver only passes traffic in promisc mode
f usb/135857   usb        RTL8187 Wireless Adapter
o usb/135575   usb        [usbdevs] [patch] Add HTC Wizard phone vid/pid informa
o usb/135542   usb        [keyboard] boot loader does not work with a usb keyboa
p usb/135372   usb        [usb67][umass] Quirk report for Teclast TL-C300 usb me
o usb/135348   usb        [umass] USB Drive Hangs with ZFS (JMicron USB2/eSata)
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/134633   usb        Add support for WILLCOM03(SHARP smart phone)
o usb/134631   usb        [usbdevs] [patch] WiSPY DBx support requires usb tweak
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/134117   usb        [Patch] Add support for 'Option GlobeTrotter HSDPA Mod
o usb/134085   usb        [umass] Adding usb quirk for Sony USB flash drive
o usb/133989   usb        [newusb] [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
p usb/132799   usb        [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CA
o usb/132785   usb        [usb] [patch] Gemtech remote powersocket is classed as
o usb/132594   usb        USB subsystem causes page fault and crashes
o usb/132312   usb        Xorg 7.4 halts USB controller
o usb/132080   usb        [patch] [usb] Kernel panic after NOMEM caused by rum 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/131912   usb        [uslcom] [patch] New devices using Silicon Labs chips 
o usb/131900   usb        [usbdevs] [patch] Additional product identification co
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
o usb/131123   usb        [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk
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/130325   usb        [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh
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        [newusb] DVD drive detects as 'da' device
o usb/129945   usb        [usbdevs] [patch] add u3g support for Longcheer WM66 U
o usb/129766   usb        [usb] plugging in usb modem HUAWEI E226 panics system
o usb/129758   usb        [uftdi] [patch] add Pyramid LCD usb support
o usb/129673   usb        [uhci] uhci (uhub) confused on replugging USB 1.1 scan
o usb/129522   usb        [ubsa] [patch] add support for ZTE AC8700 modem
o usb/129500   usb        [umass] [panic] FreeBSD Crashes when connecting SanDis
o usb/129311   usb        [usb] [panic] Instant crash with an USB card reader
o usb/129251   usb        [usbdevs] [patch] Liebert UPS being assigned uhid and 
o usb/129173   usb        [uplcom] [patch] Add support for Corega CG-USBRS232R a
s usb/128990   usb        [usb] u3g does not handle RTS/CTS available on for exa
o usb/128977   usb        [usb] [patch] uaudio is not full duplex
o 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/128324   usb        [uplcom] [patch] remove baud rate restriction for PL23
o usb/127980   usb        [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an
o usb/127926   usb        [boot] USB Timeout during bootup
s usb/127549   usb        [umass] [patch] Meizu MiniPlayer M6 (SL) requires some
s usb/127453   usb        [request] ubsa, uark, ubser, uftdi, and friends should
o usb/127423   usb        [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr
o usb/127342   usb        [boot] [panic] enabling usb keyboard and mouse support
o usb/127248   usb        [ucom] panic while uplcom devices attaach 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/125736   usb        [ukbd] [hang] system hangs after AT keyboard detect if
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
p usb/125264   usb        [patch] sysctl for set usb mouse rate (very useful for
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
o 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/123352   usb        [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom
o usb/123351   usb        [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2
o usb/122992   usb        [umass] [patch] MotoROKR Z6 Phone not recognised by um
o usb/122956   usb        [ubsa] [patch] add support for Novatel Wireless XU870 
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/122621   usb        [new driver] [patch] New driver for Sierra Wireless 3G
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/122025   usb        [uscanner] [patch] uscanner does not attach to Epson R
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/121426   usb        [patch] [uscanner] add HP ScanJet 3570C
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        [umass] [patch] quirk to support ASUS P535 as umass (a
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/118485   usb        [usbdevs] [patch] Logitech Headset Workaround
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        [uaudio] [patch] Not possible to record with Plantroni
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
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/107935   usb        [usb67] [uplcom] [panic] panic while accessing /dev/cu
o usb/107924   usb        [usb67] usbd(8) does not call detach
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/107243   usb        [usb67] [cam] [quirk] [patch] Apacer USB Flash Drive q
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/99538    usb        [keyboard] while using USB keyboard default params of 
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/93155    usb        [ulpt] /dev/ulpt0: device busy, USB printer does not w
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/91629    usb        [usb] usbd_abort_pipe() may result in infinite loop
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
f usb/84750    usb        [hang] 6-BETA2 reboot/shutdown with root_fs on externa
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/80862    usb        [patch] USB locking issues: missing some Giant calls
o usb/80854    usb        [patch] [request] suggestion for new iface-no-probe me
o usb/80829    usb        [modules] [panic] possible panic when loading USB-modu
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 "
o usb/80361    usb        [umass] [patch] mounting of Dell usb-stick fails
o 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/79722    usb        [ehci] wrong alignments in ehci.h
a usb/79656    usb        [ehci] RHSC interrupts lost
o usb/79524    usb        [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa
o usb/79287    usb        [uhci] [hang] UHCI hang after interrupt transfer
o usb/79269    usb        [ohci] USB ohci da0 plug/unplug causes crashes and loc
o usb/78984    usb        [umass] [patch] Creative MUVO umass failure
o usb/77294    usb        [ucom] [panic] ucom + ulpcom panic
o usb/77184    usb        [umass] [panic] kernel panic on USB device disconnect,
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
o 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
o 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 
o usb/75705    usb        [umass] [panic] da0 attach / Optio S4 (with backtrace)
o 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 i386/46371   usb        USB controller cannot be initialized on IBM Netfinity 
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

305 problems total.

From pyunyh at gmail.com  Mon Sep 14 20:01:36 2009
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Mon Sep 14 20:01:43 2009
Subject: CFT: axe(4) performance patch
Message-ID: <20090914193722.GD1155@michelle.cdnetworks.com>

Hi,

I submitted axe(4) performance patch to Hans and he committed the
patch to P4.
http://perforce.freebsd.org/chv.cgi?CH=168457

The patch fixes two issues, lots of Rx errors seen under high
network load and poor Rx performance. The Rx error was introduced
in new USB stack conversion and it was not spotted until this time.
For better Rx performance, the patch increases Rx maximum burst
size to 16384 from 2048 for AX88178 and AX88772. Now I can see
dramatic Rx performance boost from 50Mbps to 220Mbps on AX88178.
AX88178 data sheet clearly indicates the default burst size is
16384 for maximum performance. But I don't know whether it breaks
AX88772 fast ethernet controller. Now vendor's site requires valid
account to download AX88772 data sheet so I can't verify that. If
you have AX88772 or AX88178 please give it try and let us know how
it goes.

Since all USB ethernet controllers are poorly designed to save
money and ASIX USB ether controller requires copy operation for
every received frames(actually it's much much worse than rl(4)
hardwares), you should have fast system to achieve maximum speed.
I see constant Rx 220Mbps for various packet sizes(from 64 bytes to
MTU sized bytes) on my 2.8GHz C2D. I don't know 220Mbps is the
maximum speed the controller can achieve but I never seen these
numbers on any USB ethernet drivers on FreeBSD.
From ardovm at yahoo.it  Wed Sep 16 13:30:06 2009
From: ardovm at yahoo.it (Arrigo Marchiori)
Date: Wed Sep 16 13:30:13 2009
Subject: usb/138879: [uftdi] [patch] Patch to add support for CTI USB-Mini
	485 and USB-Nano 485
Message-ID: <200909161321.n8GDLdu6053207@www.freebsd.org>


>Number:         138879
>Category:       usb
>Synopsis:       [uftdi] [patch] Patch to add support for CTI USB-Mini 485 and USB-Nano 485
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Sep 16 13:30:06 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Arrigo Marchiori
>Release:        7-STABLE
>Organization:
>Environment:
FreeBSD diavoletto 7.2-STABLE FreeBSD 7.2-STABLE #2: Wed Sep 16 12:31:09 CEST 2009     root@diavoletto:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
The attached patch adds support for the following USB-RS485 converters:
 - CTI USB-Nano 485
 - CTI USB-Mini 485

The patch simply adds them to the list of supported FTDI USB converters: the driver seems not to need other changes.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

diff -ru original/sys/dev/usb/uftdi.c patched/sys/dev/usb/uftdi.c
--- original/sys/dev/usb/uftdi.c	2009-09-16 15:05:16.000000000 +0200
+++ patched/sys/dev/usb/uftdi.c	2009-09-16 15:04:51.000000000 +0200
@@ -169,7 +169,9 @@
 	     uaa->product == USB_PRODUCT_FTDI_UOPTBR ||
 	     uaa->product == USB_PRODUCT_FTDI_EMCU2D ||
 	     uaa->product == USB_PRODUCT_FTDI_PCMSFU ||
-	     uaa->product == USB_PRODUCT_FTDI_EMCU2H ))
+	     uaa->product == USB_PRODUCT_FTDI_EMCU2H ||
+	     uaa->product == USB_PRODUCT_FTDI_CTI_USB_NANO_485 ||
+	     uaa->product == USB_PRODUCT_FTDI_CTI_USB_MINI_485 ))
 		return (UMATCH_VENDOR_PRODUCT);
 	if (uaa->vendor == USB_VENDOR_SIIG2 &&
 	    (uaa->product == USB_PRODUCT_SIIG2_US2308))
@@ -255,6 +257,8 @@
 		case USB_PRODUCT_FTDI_EMCU2D:
 		case USB_PRODUCT_FTDI_PCMSFU:
 		case USB_PRODUCT_FTDI_EMCU2H:
+		case USB_PRODUCT_FTDI_CTI_USB_NANO_485:
+		case USB_PRODUCT_FTDI_CTI_USB_MINI_485:
 			sc->sc_type = UFTDI_TYPE_8U232AM;
 			sc->sc_hdrlen = 0;
 			break;
diff -ru original/sys/dev/usb/usbdevs patched/sys/dev/usb/usbdevs
--- original/sys/dev/usb/usbdevs	2009-09-16 15:05:20.000000000 +0200
+++ patched/sys/dev/usb/usbdevs	2009-09-16 15:04:51.000000000 +0200
@@ -1310,6 +1310,10 @@
 product FTDI CFA_631		0xfc0c	Crystalfontz CFA-631 USB LCD
 product FTDI CFA_635		0xfc0d	Crystalfontz CFA-635 USB LCD
 product FTDI SEMC_DSS20		0xfc82	SEMC DSS-20 SyncStation
+/* Commerzielle und Technische Informationssysteme GmbH products also use
+   FTDI's id: */
+product FTDI CTI_USB_NANO_485	0xf60b	CTI USB-Nano 485
+product FTDI CTI_USB_MINI_485	0xf608	CTI USB-Mini 485
 
 /* Fuji photo products */
 product FUJIPHOTO MASS0100	0x0100	Mass Storage


>Release-Note:
>Audit-Trail:
>Unformatted:
From pyunyh at gmail.com  Wed Sep 16 18:53:51 2009
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Wed Sep 16 18:53:56 2009
Subject: CFT: axe(4) station address patch
Message-ID: <20090916185256.GI1155@michelle.cdnetworks.com>

Hi,

Traditionally axe(4) didn't support reprogramming station address
(node id) as datasheet does not mention the required command.
However AX88178 datasheet has the command and it seems the command
works as expected. I've attached patch which will enable changing
ethernet address of the controller for AX88178/AX88772/AX88172.
I couldn't test it on AX88772 and AX88172 controller. So if you
have these controllers would you give it try let me know how it
goes on your controller?

<testing>
Check the ethernet address and change it to other address with
ifconfig(8). The following command will change the ethernet address
to aa:bb:cc:dd:ee:ff.
#ifconfig ue0 down
#ifconfig ue0 ether aa:bb:cc:dd:ee:ff
#ifconfig ue0 up
After that check whether you can still use network.

Hans, would you review the patch?
From hselasky at c2i.net  Wed Sep 16 21:53:30 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Sep 16 21:53:36 2009
Subject: usb/138879: [uftdi] [patch] Patch to add support for CTI
	USB-Mini 485 and USB-Nano 485
In-Reply-To: <200909161321.n8GDLdu6053207@www.freebsd.org>
References: <200909161321.n8GDLdu6053207@www.freebsd.org>
Message-ID: <200909162353.59080.hselasky@c2i.net>

Hi,

Is this patched in 9-current?

--HPS

On Wednesday 16 September 2009 15:21:39 Arrigo Marchiori wrote:
> >Number:         138879
> >Category:       usb
> >Synopsis:       [uftdi] [patch] Patch to add support for CTI USB-Mini 485
> > and USB-Nano 485 Confidential:   no
> >Severity:       non-critical
> >Priority:       low
> >Responsible:    freebsd-usb
> >State:          open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class:          change-request
> >Submitter-Id:   current-users
> >Arrival-Date:   Wed Sep 16 13:30:06 UTC 2009
> >Closed-Date:
> >Last-Modified:
> >Originator:     Arrigo Marchiori
> >Release:        7-STABLE
> >Organization:
> >Environment:
>
> FreeBSD diavoletto 7.2-STABLE FreeBSD 7.2-STABLE #2: Wed Sep 16 12:31:09
> CEST 2009     root@diavoletto:/usr/obj/usr/src/sys/GENERIC  i386
>
> >Description:
>
> The attached patch adds support for the following USB-RS485 converters:
>  - CTI USB-Nano 485
>  - CTI USB-Mini 485
>
> The patch simply adds them to the list of supported FTDI USB converters:
> the driver seems not to need other changes.
>
> >How-To-Repeat:
> >
> >Fix:
>
> Patch attached with submission follows:
>
> diff -ru original/sys/dev/usb/uftdi.c patched/sys/dev/usb/uftdi.c
> --- original/sys/dev/usb/uftdi.c	2009-09-16 15:05:16.000000000 +0200
> +++ patched/sys/dev/usb/uftdi.c	2009-09-16 15:04:51.000000000 +0200
> @@ -169,7 +169,9 @@
>  	     uaa->product == USB_PRODUCT_FTDI_UOPTBR ||
>  	     uaa->product == USB_PRODUCT_FTDI_EMCU2D ||
>  	     uaa->product == USB_PRODUCT_FTDI_PCMSFU ||
> -	     uaa->product == USB_PRODUCT_FTDI_EMCU2H ))
> +	     uaa->product == USB_PRODUCT_FTDI_EMCU2H ||
> +	     uaa->product == USB_PRODUCT_FTDI_CTI_USB_NANO_485 ||
> +	     uaa->product == USB_PRODUCT_FTDI_CTI_USB_MINI_485 ))
>  		return (UMATCH_VENDOR_PRODUCT);
>  	if (uaa->vendor == USB_VENDOR_SIIG2 &&
>  	    (uaa->product == USB_PRODUCT_SIIG2_US2308))
> @@ -255,6 +257,8 @@
>  		case USB_PRODUCT_FTDI_EMCU2D:
>  		case USB_PRODUCT_FTDI_PCMSFU:
>  		case USB_PRODUCT_FTDI_EMCU2H:
> +		case USB_PRODUCT_FTDI_CTI_USB_NANO_485:
> +		case USB_PRODUCT_FTDI_CTI_USB_MINI_485:
>  			sc->sc_type = UFTDI_TYPE_8U232AM;
>  			sc->sc_hdrlen = 0;
>  			break;
> diff -ru original/sys/dev/usb/usbdevs patched/sys/dev/usb/usbdevs
> --- original/sys/dev/usb/usbdevs	2009-09-16 15:05:20.000000000 +0200
> +++ patched/sys/dev/usb/usbdevs	2009-09-16 15:04:51.000000000 +0200
> @@ -1310,6 +1310,10 @@
>  product FTDI CFA_631		0xfc0c	Crystalfontz CFA-631 USB LCD
>  product FTDI CFA_635		0xfc0d	Crystalfontz CFA-635 USB LCD
>  product FTDI SEMC_DSS20		0xfc82	SEMC DSS-20 SyncStation
> +/* Commerzielle und Technische Informationssysteme GmbH products also use
> +   FTDI's id: */
> +product FTDI CTI_USB_NANO_485	0xf60b	CTI USB-Nano 485
> +product FTDI CTI_USB_MINI_485	0xf608	CTI USB-Mini 485
>
>  /* Fuji photo products */
>  product FUJIPHOTO MASS0100	0x0100	Mass Storage
>
> >Release-Note:
> >Audit-Trail:
> >Unformatted:
>
> _______________________________________________
> 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 hselasky at c2i.net  Wed Sep 16 21:54:37 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Sep 16 21:54:43 2009
Subject: CFT: axe(4) station address patch
In-Reply-To: <20090916185256.GI1155@michelle.cdnetworks.com>
References: <20090916185256.GI1155@michelle.cdnetworks.com>
Message-ID: <200909162355.05395.hselasky@c2i.net>

Hi,

Can you send me the patch.

Seems like the list software stripped it off.

--HPS

On Wednesday 16 September 2009 20:52:56 Pyun YongHyeon wrote:
> Hi,
>
> Traditionally axe(4) didn't support reprogramming station address
> (node id) as datasheet does not mention the required command.
> However AX88178 datasheet has the command and it seems the command
> works as expected. I've attached patch which will enable changing
> ethernet address of the controller for AX88178/AX88772/AX88172.
> I couldn't test it on AX88772 and AX88172 controller. So if you
> have these controllers would you give it try let me know how it
> goes on your controller?
>
> <testing>
> Check the ethernet address and change it to other address with
> ifconfig(8). The following command will change the ethernet address
> to aa:bb:cc:dd:ee:ff.
> #ifconfig ue0 down
> #ifconfig ue0 ether aa:bb:cc:dd:ee:ff
> #ifconfig ue0 up
> After that check whether you can still use network.
>
> Hans, would you review the patch?

From hselasky at c2i.net  Wed Sep 16 22:00:13 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Sep 16 22:00:20 2009
Subject: usb/138879: [uftdi] [patch] Patch to add support for CTI
	USB-Mini 485 and USB-Nano 485
Message-ID: <200909162200.n8GM0Dbg006716@freefall.freebsd.org>

The following reply was made to PR usb/138879; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Arrigo Marchiori <ardovm@yahoo.it>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/138879: [uftdi] [patch] Patch to add support for CTI USB-Mini 485 and USB-Nano 485
Date: Wed, 16 Sep 2009 23:53:58 +0200

 Hi,
 
 Is this patched in 9-current?
 
 --HPS
 
 On Wednesday 16 September 2009 15:21:39 Arrigo Marchiori wrote:
 > >Number:         138879
 > >Category:       usb
 > >Synopsis:       [uftdi] [patch] Patch to add support for CTI USB-Mini 485
 > > and USB-Nano 485 Confidential:   no
 > >Severity:       non-critical
 > >Priority:       low
 > >Responsible:    freebsd-usb
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          change-request
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Wed Sep 16 13:30:06 UTC 2009
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Arrigo Marchiori
 > >Release:        7-STABLE
 > >Organization:
 > >Environment:
 >
 > FreeBSD diavoletto 7.2-STABLE FreeBSD 7.2-STABLE #2: Wed Sep 16 12:31:09
 > CEST 2009     root@diavoletto:/usr/obj/usr/src/sys/GENERIC  i386
 >
 > >Description:
 >
 > The attached patch adds support for the following USB-RS485 converters:
 >  - CTI USB-Nano 485
 >  - CTI USB-Mini 485
 >
 > The patch simply adds them to the list of supported FTDI USB converters:
 > the driver seems not to need other changes.
 >
 > >How-To-Repeat:
 > >
 > >Fix:
 >
 > Patch attached with submission follows:
 >
 > diff -ru original/sys/dev/usb/uftdi.c patched/sys/dev/usb/uftdi.c
 > --- original/sys/dev/usb/uftdi.c	2009-09-16 15:05:16.000000000 +0200
 > +++ patched/sys/dev/usb/uftdi.c	2009-09-16 15:04:51.000000000 +0200
 > @@ -169,7 +169,9 @@
 >  	     uaa->product == USB_PRODUCT_FTDI_UOPTBR ||
 >  	     uaa->product == USB_PRODUCT_FTDI_EMCU2D ||
 >  	     uaa->product == USB_PRODUCT_FTDI_PCMSFU ||
 > -	     uaa->product == USB_PRODUCT_FTDI_EMCU2H ))
 > +	     uaa->product == USB_PRODUCT_FTDI_EMCU2H ||
 > +	     uaa->product == USB_PRODUCT_FTDI_CTI_USB_NANO_485 ||
 > +	     uaa->product == USB_PRODUCT_FTDI_CTI_USB_MINI_485 ))
 >  		return (UMATCH_VENDOR_PRODUCT);
 >  	if (uaa->vendor == USB_VENDOR_SIIG2 &&
 >  	    (uaa->product == USB_PRODUCT_SIIG2_US2308))
 > @@ -255,6 +257,8 @@
 >  		case USB_PRODUCT_FTDI_EMCU2D:
 >  		case USB_PRODUCT_FTDI_PCMSFU:
 >  		case USB_PRODUCT_FTDI_EMCU2H:
 > +		case USB_PRODUCT_FTDI_CTI_USB_NANO_485:
 > +		case USB_PRODUCT_FTDI_CTI_USB_MINI_485:
 >  			sc->sc_type = UFTDI_TYPE_8U232AM;
 >  			sc->sc_hdrlen = 0;
 >  			break;
 > diff -ru original/sys/dev/usb/usbdevs patched/sys/dev/usb/usbdevs
 > --- original/sys/dev/usb/usbdevs	2009-09-16 15:05:20.000000000 +0200
 > +++ patched/sys/dev/usb/usbdevs	2009-09-16 15:04:51.000000000 +0200
 > @@ -1310,6 +1310,10 @@
 >  product FTDI CFA_631		0xfc0c	Crystalfontz CFA-631 USB LCD
 >  product FTDI CFA_635		0xfc0d	Crystalfontz CFA-635 USB LCD
 >  product FTDI SEMC_DSS20		0xfc82	SEMC DSS-20 SyncStation
 > +/* Commerzielle und Technische Informationssysteme GmbH products also use
 > +   FTDI's id: */
 > +product FTDI CTI_USB_NANO_485	0xf60b	CTI USB-Nano 485
 > +product FTDI CTI_USB_MINI_485	0xf608	CTI USB-Mini 485
 >
 >  /* Fuji photo products */
 >  product FUJIPHOTO MASS0100	0x0100	Mass Storage
 >
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 >
 > _______________________________________________
 > 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 pyunyh at gmail.com  Wed Sep 16 22:02:55 2009
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Wed Sep 16 22:03:02 2009
Subject: CFT: axe(4) station address patch
In-Reply-To: <200909162355.05395.hselasky@c2i.net>
References: <20090916185256.GI1155@michelle.cdnetworks.com>
	<200909162355.05395.hselasky@c2i.net>
Message-ID: <20090916220203.GJ1155@michelle.cdnetworks.com>

On Wed, Sep 16, 2009 at 11:55:04PM +0200, Hans Petter Selasky wrote:
> Hi,
> 
> Can you send me the patch.
> 

Sure.

> Seems like the list software stripped it off.
> 
> --HPS
> 
> On Wednesday 16 September 2009 20:52:56 Pyun YongHyeon wrote:
> > Hi,
> >
> > Traditionally axe(4) didn't support reprogramming station address
> > (node id) as datasheet does not mention the required command.
> > However AX88178 datasheet has the command and it seems the command
> > works as expected. I've attached patch which will enable changing
> > ethernet address of the controller for AX88178/AX88772/AX88172.
> > I couldn't test it on AX88772 and AX88172 controller. So if you
> > have these controllers would you give it try let me know how it
> > goes on your controller?
> >
> > <testing>
> > Check the ethernet address and change it to other address with
> > ifconfig(8). The following command will change the ethernet address
> > to aa:bb:cc:dd:ee:ff.
> > #ifconfig ue0 down
> > #ifconfig ue0 ether aa:bb:cc:dd:ee:ff
> > #ifconfig ue0 up
> > After that check whether you can still use network.
> >
> > Hans, would you review the patch?
> 
From hselasky at c2i.net  Thu Sep 17 06:42:43 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Sep 17 06:42:49 2009
Subject: CFT: axe(4) station address patch
In-Reply-To: <20090916220203.GJ1155@michelle.cdnetworks.com>
References: <20090916185256.GI1155@michelle.cdnetworks.com>
	<200909162355.05395.hselasky@c2i.net>
	<20090916220203.GJ1155@michelle.cdnetworks.com>
Message-ID: <200909170843.12350.hselasky@c2i.net>

On Thursday 17 September 2009 00:02:03 Pyun YongHyeon wrote:
> On Wed, Sep 16, 2009 at 11:55:04PM +0200, Hans Petter Selasky wrote:
> > Hi,
> >
> > Can you send me the patch.
>

Hi,

Your patch has been committed to USB P4:

http://perforce.freebsd.org/chv.cgi?CH=168602

--HPS

From balabharathi.d at gmail.com  Thu Sep 17 07:15:04 2009
From: balabharathi.d at gmail.com (balabharathi d)
Date: Thu Sep 17 07:15:11 2009
Subject: Porting USB stack into BlackFin
Message-ID: <c5dbd7c60909162350v8665b5dx4f1ef89708ca001b@mail.gmail.com>

Hi,

I am working on a project requiring a USB Host stack which will run on
anblackFin using VDK kernel. I would like to explore the possibility of
using the USB stack from FreeBSD. Please share the link for source files and
documentation.

Thanks
bala
From ardovm at yahoo.it  Thu Sep 17 08:57:35 2009
From: ardovm at yahoo.it (Arrigo Marchiori)
Date: Thu Sep 17 08:57:41 2009
Subject: usb/138879: [uftdi] [patch] Patch to add support for CTI
 USB-Mini 485 and USB-Nano 485
In-Reply-To: <200909162353.59080.hselasky@c2i.net>
References: <200909161321.n8GDLdu6053207@www.freebsd.org>
	<200909162353.59080.hselasky@c2i.net>
Message-ID: <20090917083046.GB10429@snail.casa>

On Wed, Sep 16, 2009 at 11:53:58PM +0200, Hans Petter Selasky wrote:

> Hi,
> 
> Is this patched in 9-current?

My patch is against the sources of 7-STABLE, cvsupp'ed on September
16, 2009. I don't know if it also fits the -CURRENT sources -- it
should be quite easy to adapt, though.

What the patch does, in fact, is just adding the product IDs to the
supported chips, treating them the same as (for instance)
USB_PRODUCT_FTDI_EMCU2H.

-- 
rigo

http://rigo.altervista.org
From ardovm at yahoo.it  Thu Sep 17 09:00:12 2009
From: ardovm at yahoo.it (Arrigo Marchiori)
Date: Thu Sep 17 09:00:19 2009
Subject: usb/138879: [uftdi] [patch] Patch to add support for CTI
 USB-Mini 485 and USB-Nano 485
Message-ID: <200909170900.n8H90CnM012557@freefall.freebsd.org>

The following reply was made to PR usb/138879; it has been noted by GNATS.

From: Arrigo Marchiori <ardovm@yahoo.it>
To: Hans Petter Selasky <hselasky@c2i.net>
Cc: freebsd-usb@freebsd.org, freebsd-gnats-submit@freebsd.org
Subject: Re: usb/138879: [uftdi] [patch] Patch to add support for CTI
 USB-Mini 485 and USB-Nano 485
Date: Thu, 17 Sep 2009 10:30:47 +0200

 On Wed, Sep 16, 2009 at 11:53:58PM +0200, Hans Petter Selasky wrote:
 
 > Hi,
 > 
 > Is this patched in 9-current?
 
 My patch is against the sources of 7-STABLE, cvsupp'ed on September
 16, 2009. I don't know if it also fits the -CURRENT sources -- it
 should be quite easy to adapt, though.
 
 What the patch does, in fact, is just adding the product IDs to the
 supported chips, treating them the same as (for instance)
 USB_PRODUCT_FTDI_EMCU2H.
 
 -- 
 rigo
 
 http://rigo.altervista.org
From hselasky at c2i.net  Thu Sep 17 10:47:52 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Sep 17 10:47:59 2009
Subject: usb/138879: [uftdi] [patch] Patch to add support for CTI
	USB-Mini 485 and USB-Nano 485
In-Reply-To: <200909161321.n8GDLdu6053207@www.freebsd.org>
References: <200909161321.n8GDLdu6053207@www.freebsd.org>
Message-ID: <200909171248.22066.hselasky@c2i.net>

Hi,

Your patch has been committed into FreeBSD's USB P4 repository for FreeBSD 9-
current.

http://perforce.freebsd.org/chv.cgi?CH=168603

--HPS @ Eurbsdcon2009
From hselasky at c2i.net  Thu Sep 17 10:50:07 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Sep 17 10:50:20 2009
Subject: usb/138879: [uftdi] [patch] Patch to add support for CTI
	USB-Mini 485 and USB-Nano 485
Message-ID: <200909171050.n8HAo6JQ024926@freefall.freebsd.org>

The following reply was made to PR usb/138879; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Arrigo Marchiori <ardovm@yahoo.it>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/138879: [uftdi] [patch] Patch to add support for CTI USB-Mini 485 and USB-Nano 485
Date: Thu, 17 Sep 2009 12:48:20 +0200

 Hi,
 
 Your patch has been committed into FreeBSD's USB P4 repository for FreeBSD 9-
 current.
 
 http://perforce.freebsd.org/chv.cgi?CH=168603
 
 --HPS @ Eurbsdcon2009
From hselasky at c2i.net  Thu Sep 17 14:41:15 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Sep 17 14:41:22 2009
Subject: Porting USB stack into BlackFin
In-Reply-To: <c5dbd7c60909162350v8665b5dx4f1ef89708ca001b@mail.gmail.com>
References: <c5dbd7c60909162350v8665b5dx4f1ef89708ca001b@mail.gmail.com>
Message-ID: <200909171253.08732.hselasky@c2i.net>

On Thursday 17 September 2009 08:50:18 balabharathi d wrote:
> Hi,
>
> I am working on a project requiring a USB Host stack which will run on
> anblackFin using VDK kernel. I would like to explore the possibility of
> using the USB stack from FreeBSD. Please share the link for source files
> and documentation.

src/sys/dev/usb

In FreeBSD 8 and 9-current.

--HPS

From nork at FreeBSD.org  Thu Sep 17 15:06:59 2009
From: nork at FreeBSD.org (Norikatsu Shigemura)
Date: Thu Sep 17 15:07:06 2009
Subject: CFT: axe(4) performance patch
In-Reply-To: <20090914193722.GD1155@michelle.cdnetworks.com>
References: <20090914193722.GD1155@michelle.cdnetworks.com>
Message-ID: <20090918000657.099df7c4.nork@FreeBSD.org>

Hi pyun!

On Mon, 14 Sep 2009 12:37:22 -0700
Pyun YongHyeon <pyunyh@gmail.com> wrote:
> I submitted axe(4) performance patch to Hans and he committed the
> patch to P4.
> http://perforce.freebsd.org/chv.cgi?CH=168457

	I tested following environments:

	AX88178(GbE), AX88172(100), AX88772(100), bge(GbE), re(GbE), rl(100)

		patched:	AX88178, AX88172, AX88772 <-> bge
		old:		AX88178, AX88172, AX88772 <-> bge
		patched:	AX88178, AX88172, AX88772 <-> rl
		old:		AX88178, AX88172, AX88772 <-> re

	My environment, there are 3 machines:
	+--+----+-------------+----+ (All port GbE L2SW)
	   |    |             |
	 bge  re          rl
	     (patched)   (old)

	 bge: FreeBSD 7.2-stable
	  re: FreeBSD 9-current
	  rl: FreeBSD 8.0-beta4


	For test environments:
	+--+----+---+---+---+     +--+-----+--+------+---+
	   |    |       |            |        |      |
	 bge  re  rl-axe        bge  re-axe    rl
	           (old)            (patched)


	According to netperf,

	patched:	AX88178, AX88172, AX88772 <-> bge
			 60Mbps,  60Mbps,  25Mbps
	patched:	AX88178, AX88172, AX88772 <-> rl
			 90Mbps,  60Mbps,  40Mbps

	old:		AX88178, AX88172, AX88772 <-> bge
			180Mbps,  90Mbps,  95Mbps
	old:		AX88178, AX88172, AX88772 <-> re
			180Mbps,  90Mbps,  95Mbps

	Ummmm, I'll try to update old(rl) machine to pached, and re-test.

	Thank you.
From jhs at berklix.com  Thu Sep 17 15:42:01 2009
From: jhs at berklix.com (Julian H. Stacey)
Date: Thu Sep 17 15:42:08 2009
Subject: How to get /dev/uscanner0 to use ehci at USB2 speed, not uhci ?
Message-ID: <200909171531.n8HFUtYw038501@fire.js.berklix.net>

Hi FreeBSD-USB@ people,
With 7.2-RELEASE, how should I get
/dev/uscanner0 to use ehci at USB2 speed, not uhci at USB1 ?
(Please feel free to reply RTFM ... URL= )

Logs & My config & what I've tried / looked at:

My USB scanner works, but its agoning slow in high res.

devd:
Processing event '+uscanner0 vendor=0x04b8 product=0x011d devclass=0xff
  devsubclass=0x00 release=0x0100 sernum="" intclass=0xff intsubclass=0x00
  at port=0 interface=0 vendor=0x04b8 product=0x011d devclass=0xff
  devsubclass=0x00 release=0x0100 sernum="" intclass=0xff intsubclass=0x00
  on uhub1'

dmesg extract:
  ------
  uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 21 at device 16.0 on pci0
  uhci0: [GIANT-LOCKED]
  uhci0: [ITHREAD]
  usb0: <VIA 83C572 USB controller> on uhci0
  usb0: USB revision 1.0
  uhub0: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
  uhub0: 2 ports with 2 removable, self powered
  
  uhci1: <VIA 83C572 USB controller> port 0xd800-0xd81f irq 21 at device 16.1 on pci0
  uhci1: [GIANT-LOCKED]
  uhci1: [ITHREAD]
  usb1: <VIA 83C572 USB controller> on uhci1
  usb1: USB revision 1.0
  uhub1: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
  uhub1: 2 ports with 2 removable, self powered
  
  uhci2: <VIA 83C572 USB controller> port 0xe000-0xe01f irq 21 at device 16.2 on pci0
  uhci2: [GIANT-LOCKED]
  uhci2: [ITHREAD]
  usb2: <VIA 83C572 USB controller> on uhci2
  usb2: USB revision 1.0
  uhub2: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
  uhub2: 2 ports with 2 removable, self powered
  
  uhci3: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 21 at device 16.3 on pci0
  uhci3: [GIANT-LOCKED]
  uhci3: [ITHREAD]
  usb3: <VIA 83C572 USB controller> on uhci3
  usb3: USB revision 1.0
  uhub3: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
  uhub3: 2 ports with 2 removable, self powered
  
  ehci0: <VIA VT6202 USB 2.0 controller> mem 0xfae00000-0xfae000ff irq 21 at device 16.4 on pci0
  ehci0: [GIANT-LOCKED]
  ehci0: [ITHREAD]
  usb4: EHCI version 1.0
  usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
  usb4: <VIA VT6202 USB 2.0 controller> on ehci0
  usb4: USB revision 2.0
  uhub4: <VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4
  uhub4: 8 ports with 8 removable, self powered
  
  uscanner0: <EPSON EPSON Scanner, class 255/0, rev 1.10/1.00, addr 2> on uhub1
  uscanner0: at uhub1 port 1 (addr 2) disconnected
  uscanner0: detached
  uscanner0: <EPSON EPSON Scanner, class 255/0, rev 1.10/1.00, addr 2> on uhub1
  uscanner0: at uhub1 port 1 (addr 2) disconnected
  uscanner0: detached
  uscanner0: <EPSON EPSON Scanner, class 255/0, rev 1.10/1.00, addr 2> on uhub1
  ------

config -x /boot/kernel/kernel 	# includes all of
	device  uhci
	device  ehci
	device  uscanner

uname -a
  FreeBSD john.js.berklix.net 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Tue May  5 00:41:36 CEST 2009     jhs@@@john.js.berklix.net:/usr1/src/sys/amd64/compile/JOHN64.small  amd64

sane-find-scanner -q
found USB scanner (vendor=0x04b8, product=0x011d) at /dev/uscanner0

PS I had a quick look at
	http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html
but nothing I noticed.

cd /usr/src ; find . -name \*devctl\*
./share/man/man4/devctl.4
# no binary just the manual.

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
  Mail ASCII plain text not HTML & Base64.      http://asciiribbon.org
  Virused Microsoft PCs cause spam.             http://berklix.com/free/ 
From hsn at sendmail.cz  Thu Sep 17 16:40:04 2009
From: hsn at sendmail.cz (Radim Kolar SF.NET)
Date: Thu Sep 17 16:40:10 2009
Subject: usb/138904: unpluging USB wifi card panics system
Message-ID: <E1MoJva-000DTQ-Ma@sanatana.dharma>


>Number:         138904
>Category:       usb
>Synopsis:       unpluging USB wifi card panics system
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Sep 17 16:40:03 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Radim Kolar
>Release:        FreeBSD 6.4-RELEASE-p4 i386
>Organization:
>Environment:
System: FreeBSD 7.2
        wifi Card is USB asus, freebsd identifies it as
        RT2573 rev 0x2573a RF RT2528 , using rum0
	
>Description:
        fatal trap 12, supervisor read page not presenT
        current process wpa_suppliciant
	
>How-To-Repeat:
	
        it can be repeated everytime, run wpa_sup to connect to wifi network,
        uplug card. system panics after few seconds

bt
#4  0xc0ae4180 in trap_pfault (frame=0xcdc0fa6c, usermode=0, eva=3264947216)
    at /usr/src/sys/i386/i386/trap.c:852
#5  0xc0ae4b2c in trap (frame=0xcdc0fa6c) at /usr/src/sys/i386/i386/trap.c:530
#6  0xc0ac923b in calltrap () at /usr/src/sys/i386/i386/exception.s:159
#7  0xc072ff97 in rum_write_multi (sc=0xc29b1000, reg=Variable "reg" is not avai
lable.
)
    at /usr/src/sys/dev/usb/if_rum.c:1581
#8  0xc072ffdb in rum_write (sc=Variable "sc" is not available.
) at /usr/src/sys/dev/usb/if_rum.c:1564
#9  0xc07305ce in rum_stop (priv=Variable "priv" is not available.
) at /usr/src/sys/dev/usb/if_rum.c:2229
#10 0xc0732049 in rum_init (priv=0xc29b1000)
    at /usr/src/sys/dev/usb/if_rum.c:2086
#11 0xc07331b8 in rum_ioctl (ifp=0xc2652000, cmd=2149607696,
    data=0xc2775300 "rum0") at /usr/src/sys/dev/usb/if_rum.c:1488
#12 0xc087b17e in ifhwioctl (cmd=2149607696, ifp=0xc2652000,
    data=0xc2775300 "rum0", td=0xc26308c0) at /usr/src/sys/net/if.c:1719
#13 0xc087dc3d in ifioctl (so=0xc299a680, cmd=2149607696,
    data=0xc2775300 "rum0", td=0xc26308c0) at /usr/src/sys/net/if.c:2009
#14 0xc082263a in soo_ioctl (fp=0xc2789000, cmd=2149607696, data=0xc2775300,
    active_cred=0xc29a2300, td=0xc26308c0)
    at /usr/src/sys/kern/sys_socket.c:191
#15 0xc081b3e5 in kern_ioctl (td=0xc26308c0, fd=3, com=2149607696,
    data=0xc2775300 "rum0") at file.h:269
#16 0xc081b544 in ioctl (td=0xc26308c0, uap=0xcdc0fcfc)
    at /usr/src/sys/kern/sys_generic.c:571
#17 0xc0ae44d5 in syscall (frame=0xcdc0fd38)
    at /usr/src/sys/i386/i386/trap.c:1090
#18 0xc0ac92a0 in Xint0x80_syscall ()
    at /usr/src/sys/i386/i386/exception.s:255
#19 0x00000033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
From pyunyh at gmail.com  Thu Sep 17 17:17:12 2009
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Thu Sep 17 17:17:20 2009
Subject: CFT: axe(4) performance patch
In-Reply-To: <20090918000657.099df7c4.nork@FreeBSD.org>
References: <20090914193722.GD1155@michelle.cdnetworks.com>
	<20090918000657.099df7c4.nork@FreeBSD.org>
Message-ID: <20090917170849.GL1155@michelle.cdnetworks.com>

On Fri, Sep 18, 2009 at 12:06:57AM +0900, Norikatsu Shigemura wrote:
> Hi pyun!
> 
> On Mon, 14 Sep 2009 12:37:22 -0700
> Pyun YongHyeon <pyunyh@gmail.com> wrote:
> > I submitted axe(4) performance patch to Hans and he committed the
> > patch to P4.
> > http://perforce.freebsd.org/chv.cgi?CH=168457
> 
> 	I tested following environments:
> 
Thanks a lot nork@ !

> 	AX88178(GbE), AX88172(100), AX88772(100), bge(GbE), re(GbE), rl(100)
> 
> 		patched:	AX88178, AX88172, AX88772 <-> bge
> 		old:		AX88178, AX88172, AX88772 <-> bge
> 		patched:	AX88178, AX88172, AX88772 <-> rl
> 		old:		AX88178, AX88172, AX88772 <-> re
> 
> 	My environment, there are 3 machines:
> 	+--+----+-------------+----+ (All port GbE L2SW)
> 	   |    |             |
> 	 bge  re          rl
> 	     (patched)   (old)
> 
> 	 bge: FreeBSD 7.2-stable
> 	  re: FreeBSD 9-current
> 	  rl: FreeBSD 8.0-beta4
> 
> 
> 	For test environments:
> 	+--+----+---+---+---+     +--+-----+--+------+---+
> 	   |    |       |            |        |      |
> 	 bge  re  rl-axe        bge  re-axe    rl
> 	           (old)            (patched)
> 
> 
> 	According to netperf,
> 
> 	patched:	AX88178, AX88172, AX88772 <-> bge
> 			 60Mbps,  60Mbps,  25Mbps
> 	patched:	AX88178, AX88172, AX88772 <-> rl
> 			 90Mbps,  60Mbps,  40Mbps
> 
> 	old:		AX88178, AX88172, AX88772 <-> bge
> 			180Mbps,  90Mbps,  95Mbps
> 	old:		AX88178, AX88172, AX88772 <-> re
> 			180Mbps,  90Mbps,  95Mbps
> 

I'm not sure I understood the test environment.
But it looks un-patched axe(4) performs better, right?
One odd thing is performance differences for AX88172. My patch does
not touch AX88172 controller but your benchmark shows big
differences for AX88172. Are you sure you didn't apply other
patches for axe(4)/USB stack? Ehh, I was wrong, there was a change
for AX88172. The bufsize was changed to 16KB from 2KB for AX88172,
that was not my intention. It seems new USB stack has no easy way
to configure this parameter in attach phase so I used 16KB. Would
you try changing the value to MCLBYTES(aorund line number 208 in
patched if_axe.c) and test it on AX88172?

Also please let me know what netperf parameters were used in the
test.

> 	Ummmm, I'll try to update old(rl) machine to pached, and re-test.
> 
> 	Thank you.

It seems you have all three variants that axe(4) supports, so would
you test "http://p4db.freebsd.org/chv.cgi?CH=168602"?
From maksverver at geocities.com  Thu Sep 17 21:20:01 2009
From: maksverver at geocities.com (Maks Verver)
Date: Thu Sep 17 21:20:08 2009
Subject: usb/138915: [patch] add support for SheevaPlug serial interface to
	uftdi driver
Message-ID: <200909172113.n8HLDieo096639@www.freebsd.org>


>Number:         138915
>Category:       usb
>Synopsis:       [patch] add support for SheevaPlug serial interface to uftdi driver
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Sep 17 21:20:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Maks Verver
>Release:        FreeBSD 9.0-CURRENT i386
>Organization:
>Environment:
>Description:
I have a Marvell SheevaPlug that I tried to interface with FreeBSD. It has an FTDI based USB-to-serial adapter for this purpose, and the existing uftdi driver seems to work fine, except that the USB device is currently not recognized by the driver.
>How-To-Repeat:

>Fix:
I've attached a patch to add the vendor and product id for the Marvell
SheevaPlug to the USB device list, add it to the uftdi source, and update the
uftdi man page accordingly.

Patch attached with submission follows:

diff -ur sys.bak/dev/usb/serial/uftdi.c sys/dev/usb/serial/uftdi.c
--- sys.bak/dev/usb/serial/uftdi.c	2009-09-17 22:36:04.000000000 +0200
+++ sys/dev/usb/serial/uftdi.c	2009-09-17 21:55:11.000000000 +0200
@@ -246,6 +246,7 @@
 	{USB_VPI(USB_VENDOR_INTREPIDCS, USB_PRODUCT_INTREPIDCS_NEOVI, UFTDI_TYPE_8U232AM)},
 	{USB_VPI(USB_VENDOR_BBELECTRONICS, USB_PRODUCT_BBELECTRONICS_USOTL4, UFTDI_TYPE_8U232AM)},
 	{USB_VPI(USB_VENDOR_MELCO, USB_PRODUCT_MELCO_PCOPRS1, UFTDI_TYPE_8U232AM)},
+	{USB_VPI(USB_VENDOR_MARVELL, USB_PRODUCT_MARVELL_SHEEVAPLUG, UFTDI_TYPE_8U232AM)},
 };
 
 static int
diff -ur sys.bak/dev/usb/usbdevs sys/dev/usb/usbdevs
--- sys.bak/dev/usb/usbdevs	2009-09-17 22:36:05.000000000 +0200
+++ sys/dev/usb/usbdevs	2009-09-17 21:54:03.000000000 +0200
@@ -659,6 +659,7 @@
 vendor INTEL		0x8086	Intel
 vendor SITECOM2		0x9016	Sitecom
 vendor MOSCHIP		0x9710	MosChip Semiconductor
+vendor MARVELL		0x9e88  Marvell Technology Group Ltd.
 vendor 3COM3		0xa727	3Com
 vendor HP2		0xf003	Hewlett Packard
 vendor USRP		0xfffe	GNU Radio USRP
@@ -1691,6 +1692,9 @@
 /* Macally products */
 product MACALLY MOUSE1		0x0101	mouse
 
+/* Marvell Technology Group, Ltd. products */
+product MARVELL SHEEVAPLUG	0x9e8f	SheevaPlug serial interface
+
 /* MCT Corp. */
 product MCT HUB0100		0x0100	Hub
 product MCT DU_H3SP_USB232	0x0200	D-Link DU-H3SP USB BAY Hub
diff -r share.bak/man/man4/uftdi.4 share/man/man4/uftdi.4
89a90,91
> .It
> Marvell SheevaPlug serial interface 


>Release-Note:
>Audit-Trail:
>Unformatted:
From nork at FreeBSD.org  Thu Sep 17 23:09:46 2009
From: nork at FreeBSD.org (Norikatsu Shigemura)
Date: Thu Sep 17 23:09:52 2009
Subject: CFT: axe(4) performance patch
In-Reply-To: <20090917170849.GL1155@michelle.cdnetworks.com>
References: <20090914193722.GD1155@michelle.cdnetworks.com>
	<20090918000657.099df7c4.nork@FreeBSD.org>
	<20090917170849.GL1155@michelle.cdnetworks.com>
Message-ID: <20090918080944.23532c80.nork@FreeBSD.org>

Hi pyun!

On Thu, 17 Sep 2009 10:08:49 -0700
Pyun YongHyeon <pyunyh@gmail.com> wrote:
> > 	patched:	AX88178, AX88172, AX88772 <-> bge
> > 			 60Mbps,  60Mbps,  25Mbps
> > 	patched:	AX88178, AX88172, AX88772 <-> rl
> > 			 90Mbps,  60Mbps,  40Mbps
> > 	old:		AX88178, AX88172, AX88772 <-> bge
> > 			180Mbps,  90Mbps,  95Mbps
> > 	old:		AX88178, AX88172, AX88772 <-> re
> > 			180Mbps,  90Mbps,  95Mbps
> I'm not sure I understood the test environment.
> But it looks un-patched axe(4) performs better, right?

	Yes.  I think that these are strange.

> One odd thing is performance differences for AX88172. My patch does
> not touch AX88172 controller but your benchmark shows big
> differences for AX88172. Are you sure you didn't apply other
> patches for axe(4)/USB stack? Ehh, I was wrong, there was a change

	No I don't apply any patch to axe/usb.

> for AX88172. The bufsize was changed to 16KB from 2KB for AX88172,
> that was not my intention. It seems new USB stack has no easy way
> to configure this parameter in attach phase so I used 16KB. Would
> you try changing the value to MCLBYTES(aorund line number 208 in
> patched if_axe.c) and test it on AX88172?

	I'll try, please wait a while.

> Also please let me know what netperf parameters were used in the
> test.

	Simple-fully, it's all default.

	Server:	netserver
	Client:	netperf -H Server

> > 	Ummmm, I'll try to update old(rl) machine to pached, and re-test.
> > 	Thank you.
> It seems you have all three variants that axe(4) supports, so would
> you test "http://p4db.freebsd.org/chv.cgi?CH=168602"?

	Yes, too!

	Thank you.
From tlb at tlb.org  Fri Sep 18 03:09:24 2009
From: tlb at tlb.org (Trevor Blackwell)
Date: Fri Sep 18 03:09:30 2009
Subject: Transfer size limits
Message-ID: <FB232B99-B12C-45F8-A9C8-91B5E0FB973A@tlb.org>


What's the largest practical bulk transfer size in the -8 USB stack?  
I'm currently transferring frames through a UE_BULK  pipe from a  
Mightex camera (it uses bulk, not isochronous.)

Currently, I'm setting usbd_xfer_max_len(xfer)==32768. If I could set  
it large enough for a complete frame (5 MB), it would simplify the  
logic of my driver. Large transfers didn't work reliably with the -7  
USB stack, because of some obscure problem with setting up DMA  
transfers in the ehci driver with more than a few separate physical  
regions.

--
Trevor Blackwell		650 776 7870	tlb@tlb.org





From hselasky at c2i.net  Fri Sep 18 10:58:07 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Sep 18 10:58:14 2009
Subject: Transfer size limits
In-Reply-To: <FB232B99-B12C-45F8-A9C8-91B5E0FB973A@tlb.org>
References: <FB232B99-B12C-45F8-A9C8-91B5E0FB973A@tlb.org>
Message-ID: <200909181258.35957.hselasky@c2i.net>

On Friday 18 September 2009 05:09:22 Trevor Blackwell wrote:
> What's the largest practical bulk transfer size in the -8 USB stack?
> I'm currently transferring frames through a UE_BULK  pipe from a
> Mightex camera (it uses bulk, not isochronous.)

You have to check what busdma supports. USB uses 32-bit transfer lenghts. 
Typically 64KByte blocks will give you a decent performance.

What is your performance requirement?

--HPS

From hsn at sendmail.cz  Fri Sep 18 11:00:11 2009
From: hsn at sendmail.cz (Radim Kolar)
Date: Fri Sep 18 11:00:20 2009
Subject: usb/138904: [rum] unpluging USB wifi card panics system
Message-ID: <200909181100.n8IB0ANK012763@freefall.freebsd.org>

The following reply was made to PR usb/138904; it has been noted by GNATS.

From: "Radim Kolar" <hsn@sendmail.cz>
To: bug-followup@freebsd.org, hsn@sendmail.cz
Cc:  
Subject: Re: usb/138904: [rum] unpluging USB wifi card panics system
Date: Fri, 18 Sep 2009 12:57:14 +0200

 It works correctly on 8.0 Beta4. No panic and if you plug device back and  
 run wpa_sup and dhclient it will
 even recover TCP sessions
 
 -- 
 Tato zpráva byla vytvoøena pøevratným po¹tovním klientem Opery:  
 http://www.opera.com/mail/
From gavin at FreeBSD.org  Fri Sep 18 13:51:09 2009
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Fri Sep 18 13:51:16 2009
Subject: usb/113060: [usb67] [ulpt] [patch] Samsung printer not working
	in bidirectional mode
Message-ID: <200909181351.n8IDp8Kq095980@freefall.freebsd.org>

Synopsis: [usb67] [ulpt] [patch] Samsung printer not working in bidirectional mode

State-Changed-From-To: feedback->open
State-Changed-By: gavin
State-Changed-When: Fri Sep 18 13:48:30 UTC 2009
State-Changed-Why: 
Feedback was provided, submitter is unable to test


Responsible-Changed-From-To: gavin->freebsd-usb
Responsible-Changed-By: gavin
Responsible-Changed-When: Fri Sep 18 13:48:30 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s)

http://www.freebsd.org/cgi/query-pr.cgi?pr=113060
From pldrouin at pldrouin.net  Sun Sep 20 20:42:20 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Sun Sep 20 20:42:27 2009
Subject: Are asynchronous transfers supported by uftdi?
Message-ID: <4AB68F11.2080202@pldrouin.net>

Hi,

Are asynchronous transfers supported by uftdi? I am trying to modify a 
linux tool (tbancontrol) to control a fan controller on FreeBSD and 
SIGIO behaviour seems to be a bit random on FreeBSD compared to linux. 
Here are the main lines of the tool related to initialization:

tban->port = open("/dev/ttyU0", O_RDWR | O_NOCTTY | O_NONBLOCK);
...
saio.sa_handler = tban_signal_handler_IO;
result = sigemptyset(&saio.sa_mask);
saio.sa_flags = 0;
result = sigaction(SIGIO, &saio, NULL);
result = fcntl(tban->port, F_SETFL, FASYNC);
...
tcgetattr(tban->port, &(tban->oldtio));
...
memcpy(&newtio,&tban->oldtio,sizeof(struct termios)); /*I added this 
line to avoid the error EINVAL when calling tcsetattr below. This is 
probably not enough to set all flags properly :S */
...

newtio.c_cflag = intToBaud(tban->baudrate)  /*baudrate is 19200*/
   | CRTSCTS
   | intToDataBits(tban->databits) /*databits is 8*/
   | intToStopBits(tban->stopBits) /*stopBits is 0*/
   | CLOCAL
   | CREAD;
 newtio.c_iflag     = IGNPAR;
 newtio.c_oflag     = 0;
 newtio.c_lflag     = 0;
 newtio.c_cc[VMIN]  = 1;
 newtio.c_cc[VTIME] = 0;
...
result = tcsetattr(tban->port, TCSANOW, &newtio);
*/*SIGIO is generated (?)*/ *
...
result = write(tban->port, sndBuf, cmdLen); /*request device status*/
...
/*Initialize data availability flag to false*/
/*Wait in a loop using sleep until availability flag is set to true by 
the callback function*/
/*SIGIO is generated */
bytesread = read(tban->port, local_buf, sizeof(local_buf));
*/*bytesread is -1, EINTR is generated*/

*Although this code works fine with Linux, is there something in it that 
is missing for FreeBSD? Or is it a bug/limitation of the uftdi driver?

Thanks a lot!

From pldrouin at pldrouin.net  Mon Sep 21 01:44:28 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Mon Sep 21 01:44:35 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
Message-ID: <4AB6DA79.7050209@pldrouin.net>

Hi,

I am also having troubles with the uftdi driver on 8.0-BETA4.
I am trying to use a fan controller (mCubed bigNG) that uses a FT232BL chip and it does not seem to be responding on FreeBSD 8.0 while the same code works perfectly on Linux (I have not tried the code on RELENG_7 yet but I could install it if necessary).

Here is the very simple code I am using for testing:
#include <termios.h>
#include <fcntl.h>
#include <string.h>
#include <unistd.h>
#include <stdio.h>

int main();

#define DEV "/dev/ttyU0"

#define TBAN_SER_SOURCE1        0x05 /* Primary source */
#define TBAN_SER_SOURCE2        0x06 /* Alternative source (miniNG...) */

#define TBAN_SER_REQUEST        0x36

int main()
{
  int fd;
  int result;
  struct termios oldtio, newtio;
  unsigned char buf[285];

  printf("Opening device\n");
  fd=open(DEV, O_RDWR | O_NOCTTY);

  if(fd<0) {
    perror(DEV);
    return 1;
  }

  result=tcgetattr(fd,&oldtio);
  if(result<0) {
    perror("tcgetattr");
    return 1;
  }

  memcpy(&newtio,&oldtio,sizeof(struct termios));
  newtio.c_cflag = B19200
    | CRTSCTS
    | CS8
    | CREAD;
  newtio.c_iflag     = IGNPAR;
  newtio.c_oflag     = 0;
  newtio.c_lflag     = 0;
  newtio.c_cc[VMIN]  = 1;
  newtio.c_cc[VTIME] = 0;

  result=tcflush(fd, TCIFLUSH);
  if(result<0) {
    perror("tcflush");
    return 1;
  }

  result=tcsetattr(fd,TCSANOW,&newtio);
  if(result<0) {
    perror("tcsetattr");
    return 1;
  }

  sleep(1);

  printf("Performing initial query\n");
  buf[0]=TBAN_SER_SOURCE1;
  buf[1]=TBAN_SER_REQUEST;

  printf("Requesting status\n");
  result=write(fd,buf,2);
  if(result<0) {
    perror("write");
    return 1;
  }

  sleep(1);

  printf("Reading status\n");
  result=read(fd,buf,32);
  if(result<0) {
    perror("read");
    return 1;
  }

  result=tcsetattr(fd,TCSANOW,&oldtio);
  if(result<0) {
    perror("tcsetattr");
    return 1;
  }

  result=close(fd);
  if(result<0) {
    perror("close");
    return 1;
  }
  return 0;
}

It hangs while reading independently of the number of bits I am reading.

Here is the output from dmesg when I load the uftdi module:
Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp = 0xffffff001f12b400, unit = 0
Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:346: ttycreate: U0
Sep 20 21:31:34 ldaemon root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub0

Here is the output in /var/log/messages when I enable the debug output for ucom and uftdi:
Sep 20 21:33:30 ldaemon kernel: ucom_open:554: tp = 0xffffff001f12b400
Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
Sep 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status change msr=0xf0 (0x00) lsr=0x60 (0x00)
Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
Sep 20 21:33:30 ldaemon kernel: ucom_cfg_status_change:887: DCD changed to 1
Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
Sep 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc = 0xffffff001f12ac58
Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=2
Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0

I really need to get this working so I am ready to test things as much as I can...

Thanks a lot!
Pierre-Luc Drouin

From linimon at FreeBSD.org  Mon Sep 21 04:29:23 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Mon Sep 21 04:29:29 2009
Subject: usb/138882: [ohci] [panic] Can't install FreeBSD 7.2 due to
	ohci panic
Message-ID: <200909210429.n8L4TM69088346@freefall.freebsd.org>

Old Synopsis: Can't install FreeBSD 7.2
New Synopsis: [ohci] [panic] Can't install FreeBSD 7.2 due to ohci panic

Responsible-Changed-From-To: freebsd-amd64->freebsd-usb
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Sep 21 04:28:05 UTC 2009
Responsible-Changed-Why: 
reclassify.

http://www.freebsd.org/cgi/query-pr.cgi?pr=138882
From linimon at FreeBSD.org  Mon Sep 21 04:29:37 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Mon Sep 21 04:29:48 2009
Subject: usb/138882: [ohci] [panic] Can't install FreeBSD 7.2 due to
	ohci panic
Message-ID: <200909210429.n8L4TaSA088393@freefall.freebsd.org>

Synopsis: [ohci] [panic] Can't install FreeBSD 7.2 due to ohci panic

State-Changed-From-To: open->feedback
State-Changed-By: linimon
State-Changed-When: Mon Sep 21 04:29:25 UTC 2009
State-Changed-Why: 
Note that feedback was requested.

http://www.freebsd.org/cgi/query-pr.cgi?pr=138882
From dorian.buettner at gmx.de  Mon Sep 21 08:10:04 2009
From: dorian.buettner at gmx.de (=?ISO-8859-15?Q?Dorian_B=FCttner?=)
Date: Mon Sep 21 08:10:11 2009
Subject: usb/138882: [ohci] [panic] Can't install FreeBSD 7.2 due to ohci
 panic
Message-ID: <200909210810.n8L8A3Le045326@freefall.freebsd.org>

The following reply was made to PR usb/138882; it has been noted by GNATS.

From: =?ISO-8859-15?Q?Dorian_B=FCttner?= <dorian.buettner@gmx.de>
To: bug-followup@FreeBSD.org, kazham@mail.ru
Cc:  
Subject: Re: usb/138882: [ohci] [panic] Can't install FreeBSD 7.2 due to ohci
 panic
Date: Mon, 21 Sep 2009 09:34:41 +0200

 1) dup, see here: http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/107827
 
 2) actually, I use a kernel with everything usb disabled, then load 
 related modules via kldload-instructions in /etc/rc. That is somewhat 
 working, or I can boot without keyboard attached, then once up reattach 
 everything.
From bugmaster at FreeBSD.org  Mon Sep 21 11:07:08 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Sep 21 11:09:46 2009
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200909211107.n8LB77M2030457@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o usb/138915   usb        [patch][usb8][usb67] add support for SheevaPlug serial
o usb/138904   usb        [rum] unpluging USB wifi card panics system
f usb/138882   usb        [ohci] [panic] Can't install FreeBSD 7.2 due to ohci p
o usb/138879   usb        [uftdi] [patch] Patch to add support for CTI USB-Mini 
o usb/138798   usb        8.0-BETA4 can't boot from USB flash drive
o usb/138675   usb        [usb8] [panic] page fault, perhaps in USB
o usb/138659   usb        [usb8][uftdi] driver broken in RELENG_8/CURRENT
o usb/138563   usb        [usb8] [patch] Increase buffer sizes to accomodate lon
o usb/138389   usb        [usb8] [patch] NULL pointer dereference in usb_endpoin
o usb/138175   usb        [usb67] [boot] System cannot boot, when USB reader wit
o usb/138172   usb        Additional dev id for u3g (Option mini PCIe)
o usb/138138   usb        Novatel U760 for u3g (Verizon and Bell Canada)
o usb/138124   usb        [usb8] Axed uaudio functionality in the usbng (alterna
o usb/138119   usb        MultiBay CDROM (propably on USB bus) is not recognized
o usb/137872   usb        slow booting on usb flash drive
f usb/137848   usb        Page fault when using an USB bluetooth adapter
o usb/137806   usb        [ukbd] USB keyboard doesn't work until it's unplugged
o usb/137763   usb        [usb67][ukbd] Logitech wireless keyboard media keys no
o usb/137616   usb        [usb67][usb8][usbdevs] [patch]: usbdevs update: Please
o usb/137377   usb        [usb8] Support for Huawei E180
o usb/137341   usb        [usb8][rum] driver if_rum doesn't work at all and thro
p usb/137226   usb        [usb67][patch] quirk for Philips extern USB disk
o usb/137191   usb        [usb8][patch] export ums(4) output report parser data 
o 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        SteelSeries Ikari USB laser mouse not attaching
o usb/137035   usb        Sony cyber-shot DSC-P72 not accessible - cam quirks
p usb/136761   usb        [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H
o usb/135938   usb        [aue] aue driver only passes traffic in promisc mode
f usb/135857   usb        RTL8187 Wireless Adapter
o usb/135575   usb        [usbdevs] [patch] Add HTC Wizard phone vid/pid informa
o usb/135542   usb        [keyboard] boot loader does not work with a usb keyboa
p usb/135372   usb        [usb67][umass] Quirk report for Teclast TL-C300 usb me
o usb/135348   usb        [umass] USB Drive Hangs with ZFS (JMicron USB2/eSata)
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/134633   usb        Add support for WILLCOM03(SHARP smart phone)
o usb/134631   usb        [usbdevs] [patch] WiSPY DBx support requires usb tweak
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/134117   usb        [Patch] Add support for 'Option GlobeTrotter HSDPA Mod
o usb/134085   usb        [umass] Adding usb quirk for Sony USB flash drive
o usb/133989   usb        [newusb] [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
p usb/132799   usb        [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CA
o usb/132785   usb        [usb] [patch] Gemtech remote powersocket is classed as
o usb/132594   usb        USB subsystem causes page fault and crashes
o usb/132312   usb        Xorg 7.4 halts USB controller
o usb/132080   usb        [patch] [usb] [rum] Kernel panic after NOMEM caused by
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/131912   usb        [uslcom] [patch] New devices using Silicon Labs chips 
o usb/131900   usb        [usbdevs] [patch] Additional product identification co
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
o usb/131123   usb        [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk
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/130325   usb        [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh
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        [newusb] DVD drive detects as 'da' device
o usb/129945   usb        [usbdevs] [patch] add u3g support for Longcheer WM66 U
o usb/129766   usb        [usb] plugging in usb modem HUAWEI E226 panics system
o usb/129758   usb        [uftdi] [patch] add Pyramid LCD usb support
o usb/129673   usb        [uhci] uhci (uhub) confused on replugging USB 1.1 scan
o usb/129522   usb        [ubsa] [patch] add support for ZTE AC8700 modem
o usb/129500   usb        [umass] [panic] FreeBSD Crashes when connecting SanDis
o usb/129311   usb        [usb] [panic] Instant crash with an USB card reader
o usb/129251   usb        [usbdevs] [patch] Liebert UPS being assigned uhid and 
o usb/129173   usb        [uplcom] [patch] Add support for Corega CG-USBRS232R a
s usb/128990   usb        [usb] u3g does not handle RTS/CTS available on for exa
o usb/128977   usb        [usb] [patch] uaudio is not full duplex
o 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/128324   usb        [uplcom] [patch] remove baud rate restriction for PL23
o usb/127980   usb        [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an
o usb/127926   usb        [boot] USB Timeout during bootup
s usb/127549   usb        [umass] [patch] Meizu MiniPlayer M6 (SL) requires some
s usb/127453   usb        [request] ubsa, uark, ubser, uftdi, and friends should
o usb/127423   usb        [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr
o usb/127342   usb        [boot] [panic] enabling usb keyboard and mouse support
o usb/127248   usb        [ucom] panic while uplcom devices attaach 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/125736   usb        [ukbd] [hang] system hangs after AT keyboard detect if
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
p usb/125264   usb        [patch] sysctl for set usb mouse rate (very useful for
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
o 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/123352   usb        [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom
o usb/123351   usb        [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2
o usb/122992   usb        [umass] [patch] MotoROKR Z6 Phone not recognised by um
o usb/122956   usb        [ubsa] [patch] add support for Novatel Wireless XU870 
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/122621   usb        [new driver] [patch] New driver for Sierra Wireless 3G
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/122025   usb        [uscanner] [patch] uscanner does not attach to Epson R
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/121426   usb        [patch] [uscanner] add HP ScanJet 3570C
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        [umass] [patch] quirk to support ASUS P535 as umass (a
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/118485   usb        [usbdevs] [patch] Logitech Headset Workaround
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        [uaudio] [patch] Not possible to record with Plantroni
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
o 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/107935   usb        [usb67] [uplcom] [panic] panic while accessing /dev/cu
o usb/107924   usb        [usb67] usbd(8) does not call detach
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/107243   usb        [usb67] [cam] [quirk] [patch] Apacer USB Flash Drive q
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/99538    usb        [keyboard] while using USB keyboard default params of 
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/93155    usb        [ulpt] /dev/ulpt0: device busy, USB printer does not w
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/91629    usb        [usb] usbd_abort_pipe() may result in infinite loop
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
f usb/84750    usb        [hang] 6-BETA2 reboot/shutdown with root_fs on externa
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/80862    usb        [patch] USB locking issues: missing some Giant calls
o usb/80854    usb        [patch] [request] suggestion for new iface-no-probe me
o usb/80829    usb        [modules] [panic] possible panic when loading USB-modu
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 "
o usb/80361    usb        [umass] [patch] mounting of Dell usb-stick fails
o 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/79722    usb        [ehci] wrong alignments in ehci.h
a usb/79656    usb        [ehci] RHSC interrupts lost
o usb/79524    usb        [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa
o usb/79287    usb        [uhci] [hang] UHCI hang after interrupt transfer
o usb/79269    usb        [ohci] USB ohci da0 plug/unplug causes crashes and loc
o usb/78984    usb        [umass] [patch] Creative MUVO umass failure
o usb/77294    usb        [ucom] [panic] ucom + ulpcom panic
o usb/77184    usb        [umass] [panic] kernel panic on USB device disconnect,
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
o 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
o 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 
o usb/75705    usb        [umass] [panic] da0 attach / Optio S4 (with backtrace)
o 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 i386/46371   usb        USB controller cannot be initialized on IBM Netfinity 
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

310 problems total.

From jhs at berklix.com  Mon Sep 21 12:10:31 2009
From: jhs at berklix.com (Julian H. Stacey)
Date: Mon Sep 21 12:10:38 2009
Subject: How to get /dev/uscanner0 to use ehci at USB2 speed, not uhci ? 
In-Reply-To: Your message "Thu, 17 Sep 2009 17:30:55 +0200."
	<200909171531.n8HFUtYw038501@fire.js.berklix.net> 
Message-ID: <200909211213.n8LCCtnl098153@fire.js.berklix.net>

Hi,
Reference:
> From:		"Julian H. Stacey" <jhs@berklix.com> 
> Date:		Thu, 17 Sep 2009 17:30:55 +0200 
> Message-id:	<200909171531.n8HFUtYw038501@fire.js.berklix.net> 

"Julian H. Stacey" wrote:
> Hi FreeBSD-USB@ people,
> With 7.2-RELEASE, how should I get
> /dev/uscanner0 to use ehci at USB2 speed, not uhci at USB1 ?
> (Please feel free to reply RTFM ... URL= )
> 
> Logs & My config & what I've tried / looked at:
> 
> My USB scanner works, but its agoning slow in high res.
> 
> devd:
> Processing event '+uscanner0 vendor=0x04b8 product=0x011d devclass=0xff
>   devsubclass=0x00 release=0x0100 sernum="" intclass=0xff intsubclass=0x00
>   at port=0 interface=0 vendor=0x04b8 product=0x011d devclass=0xff
>   devsubclass=0x00 release=0x0100 sernum="" intclass=0xff intsubclass=0x00
>   on uhub1'
> 
> dmesg extract:
>   ------
>   uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 21 at device 16.0 on pci0
>   uhci0: [GIANT-LOCKED]
>   uhci0: [ITHREAD]
>   usb0: <VIA 83C572 USB controller> on uhci0
>   usb0: USB revision 1.0
>   uhub0: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
>   uhub0: 2 ports with 2 removable, self powered
>   
>   uhci1: <VIA 83C572 USB controller> port 0xd800-0xd81f irq 21 at device 16.1 on pci0
>   uhci1: [GIANT-LOCKED]
>   uhci1: [ITHREAD]
>   usb1: <VIA 83C572 USB controller> on uhci1
>   usb1: USB revision 1.0
>   uhub1: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
>   uhub1: 2 ports with 2 removable, self powered
>   
>   uhci2: <VIA 83C572 USB controller> port 0xe000-0xe01f irq 21 at device 16.2 on pci0
>   uhci2: [GIANT-LOCKED]
>   uhci2: [ITHREAD]
>   usb2: <VIA 83C572 USB controller> on uhci2
>   usb2: USB revision 1.0
>   uhub2: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
>   uhub2: 2 ports with 2 removable, self powered
>   
>   uhci3: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 21 at device 16.3 on pci0
>   uhci3: [GIANT-LOCKED]
>   uhci3: [ITHREAD]
>   usb3: <VIA 83C572 USB controller> on uhci3
>   usb3: USB revision 1.0
>   uhub3: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
>   uhub3: 2 ports with 2 removable, self powered
>   
>   ehci0: <VIA VT6202 USB 2.0 controller> mem 0xfae00000-0xfae000ff irq 21 at device 16.4 on pci0
>   ehci0: [GIANT-LOCKED]
>   ehci0: [ITHREAD]
>   usb4: EHCI version 1.0
>   usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
>   usb4: <VIA VT6202 USB 2.0 controller> on ehci0
>   usb4: USB revision 2.0
>   uhub4: <VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4
>   uhub4: 8 ports with 8 removable, self powered
>   
>   uscanner0: <EPSON EPSON Scanner, class 255/0, rev 1.10/1.00, addr 2> on uhub1
>   uscanner0: at uhub1 port 1 (addr 2) disconnected
>   uscanner0: detached
>   uscanner0: <EPSON EPSON Scanner, class 255/0, rev 1.10/1.00, addr 2> on uhub1
>   uscanner0: at uhub1 port 1 (addr 2) disconnected
>   uscanner0: detached
>   uscanner0: <EPSON EPSON Scanner, class 255/0, rev 1.10/1.00, addr 2> on uhub1
>   ------
> 
> config -x /boot/kernel/kernel 	# includes all of
> 	device  uhci
> 	device  ehci
> 	device  uscanner
> 
> uname -a
>   FreeBSD john.js.berklix.net 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Tue May  5 00:41:36 CEST 2009     jhs@@@john.js.berklix.net:/usr1/src/sys/amd64/compile/JOHN64.small  amd64
> 
> sane-find-scanner -q
> found USB scanner (vendor=0x04b8, product=0x011d) at /dev/uscanner0
> 
> PS I had a quick look at
> 	http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html
> but nothing I noticed.

The scanner manufacturer documents hardware as USB-1 :-(
Idealy /var/log/messages might have issued a simple clear warning about that.

> cd /usr/src ; find . -name \*devctl\*
> /share/man/man4/devctl.4
> # no binary just the manual.

Cheers,
Julian
-- 
Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
  Mail ASCII plain text not HTML & Base64.      http://asciiribbon.org
  Virused Microsoft PCs cause spam.             http://berklix.com/free/
From hselasky at c2i.net  Mon Sep 21 16:27:17 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Sep 21 16:27:24 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB6DA79.7050209@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
Message-ID: <200909211827.53014.hselasky@c2i.net>

On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
> Hi,
>
> I am also having troubles with the uftdi driver on 8.0-BETA4.
> I am trying to use a fan controller (mCubed bigNG) that uses a FT232BL chip
> and it does not seem to be responding on FreeBSD 8.0 while the same code
> works perfectly on Linux (I have not tried the code on RELENG_7 yet but I
> could install it if necessary).
>
> Here is the very simple code I am using for testing:
> #include <termios.h>
> #include <fcntl.h>
> #include <string.h>
> #include <unistd.h>
> #include <stdio.h>
>
> int main();
>
> #define DEV "/dev/ttyU0"
>
> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
> #define TBAN_SER_SOURCE2        0x06 /* Alternative source (miniNG...) */
>
> #define TBAN_SER_REQUEST        0x36
>
> int main()
> {
>   int fd;
>   int result;
>   struct termios oldtio, newtio;
>   unsigned char buf[285];
>
>   printf("Opening device\n");
>   fd=open(DEV, O_RDWR | O_NOCTTY);
>
>   if(fd<0) {
>     perror(DEV);
>     return 1;
>   }
>
>   result=tcgetattr(fd,&oldtio);
>   if(result<0) {
>     perror("tcgetattr");
>     return 1;
>   }
>
>   memcpy(&newtio,&oldtio,sizeof(struct termios));
>   newtio.c_cflag = B19200
>
>     | CRTSCTS
>     | CS8
>     | CREAD;
>
>   newtio.c_iflag     = IGNPAR;
>   newtio.c_oflag     = 0;
>   newtio.c_lflag     = 0;
>   newtio.c_cc[VMIN]  = 1;
>   newtio.c_cc[VTIME] = 0;
>
>   result=tcflush(fd, TCIFLUSH);
>   if(result<0) {
>     perror("tcflush");
>     return 1;
>   }
>
>   result=tcsetattr(fd,TCSANOW,&newtio);
>   if(result<0) {
>     perror("tcsetattr");
>     return 1;
>   }
>
>   sleep(1);
>
>   printf("Performing initial query\n");
>   buf[0]=TBAN_SER_SOURCE1;
>   buf[1]=TBAN_SER_REQUEST;
>
>   printf("Requesting status\n");
>   result=write(fd,buf,2);
>   if(result<0) {
>     perror("write");
>     return 1;
>   }
>
>   sleep(1);
>
>   printf("Reading status\n");
>   result=read(fd,buf,32);
>   if(result<0) {
>     perror("read");
>     return 1;
>   }
>
>   result=tcsetattr(fd,TCSANOW,&oldtio);
>   if(result<0) {
>     perror("tcsetattr");
>     return 1;
>   }
>
>   result=close(fd);
>   if(result<0) {
>     perror("close");
>     return 1;
>   }
>   return 0;
> }
>
> It hangs while reading independently of the number of bits I am reading.
>
> Here is the output from dmesg when I load the uftdi module:
> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root: Unknown
> USB device: vendor 0x051d product 0x0002 bus uhub0
>
> Here is the output in /var/log/messages when I enable the debug output for
> ucom and uftdi: Sep 20 21:33:30 ldaemon kernel: ucom_open:554: tp =
> 0xffffff001f12b400 Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
> Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
> Sep 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status change
> msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon kernel:
> ucom_status_change:901:
> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
> Sep 20 21:33:30 ldaemon kernel: ucom_cfg_status_change:887: DCD changed to
> 1 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
> Sep 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
> Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
> Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc =
> 0xffffff001f12ac58 Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064:
> cnt=2
> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
>
> I really need to get this working so I am ready to test things as much as I
> can...

Hi,

You need to set raw mode for the TTY device I think. Maybe Ed can give you the 
function name you need to call to do that?

--HPS
From pldrouin at pldrouin.net  Mon Sep 21 17:29:12 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Mon Sep 21 17:29:19 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909211827.53014.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211827.53014.hselasky@c2i.net>
Message-ID: <4AB7B7E6.9070005@pldrouin.net>

Hans Petter Selasky wrote:
> On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
>   
>> Hi,
>>
>> I am also having troubles with the uftdi driver on 8.0-BETA4.
>> I am trying to use a fan controller (mCubed bigNG) that uses a FT232BL chip
>> and it does not seem to be responding on FreeBSD 8.0 while the same code
>> works perfectly on Linux (I have not tried the code on RELENG_7 yet but I
>> could install it if necessary).
>>
>> Here is the very simple code I am using for testing:
>> #include <termios.h>
>> #include <fcntl.h>
>> #include <string.h>
>> #include <unistd.h>
>> #include <stdio.h>
>>
>> int main();
>>
>> #define DEV "/dev/ttyU0"
>>
>> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
>> #define TBAN_SER_SOURCE2        0x06 /* Alternative source (miniNG...) */
>>
>> #define TBAN_SER_REQUEST        0x36
>>
>> int main()
>> {
>>   int fd;
>>   int result;
>>   struct termios oldtio, newtio;
>>   unsigned char buf[285];
>>
>>   printf("Opening device\n");
>>   fd=open(DEV, O_RDWR | O_NOCTTY);
>>
>>   if(fd<0) {
>>     perror(DEV);
>>     return 1;
>>   }
>>
>>   result=tcgetattr(fd,&oldtio);
>>   if(result<0) {
>>     perror("tcgetattr");
>>     return 1;
>>   }
>>
>>   memcpy(&newtio,&oldtio,sizeof(struct termios));
>>   newtio.c_cflag = B19200
>>
>>     | CRTSCTS
>>     | CS8
>>     | CREAD;
>>
>>   newtio.c_iflag     = IGNPAR;
>>   newtio.c_oflag     = 0;
>>   newtio.c_lflag     = 0;
>>   newtio.c_cc[VMIN]  = 1;
>>   newtio.c_cc[VTIME] = 0;
>>
>>   result=tcflush(fd, TCIFLUSH);
>>   if(result<0) {
>>     perror("tcflush");
>>     return 1;
>>   }
>>
>>   result=tcsetattr(fd,TCSANOW,&newtio);
>>   if(result<0) {
>>     perror("tcsetattr");
>>     return 1;
>>   }
>>
>>   sleep(1);
>>
>>   printf("Performing initial query\n");
>>   buf[0]=TBAN_SER_SOURCE1;
>>   buf[1]=TBAN_SER_REQUEST;
>>
>>   printf("Requesting status\n");
>>   result=write(fd,buf,2);
>>   if(result<0) {
>>     perror("write");
>>     return 1;
>>   }
>>
>>   sleep(1);
>>
>>   printf("Reading status\n");
>>   result=read(fd,buf,32);
>>   if(result<0) {
>>     perror("read");
>>     return 1;
>>   }
>>
>>   result=tcsetattr(fd,TCSANOW,&oldtio);
>>   if(result<0) {
>>     perror("tcsetattr");
>>     return 1;
>>   }
>>
>>   result=close(fd);
>>   if(result<0) {
>>     perror("close");
>>     return 1;
>>   }
>>   return 0;
>> }
>>
>> It hangs while reading independently of the number of bits I am reading.
>>
>> Here is the output from dmesg when I load the uftdi module:
>> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
>> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
>> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
>> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root: Unknown
>> USB device: vendor 0x051d product 0x0002 bus uhub0
>>
>> Here is the output in /var/log/messages when I enable the debug output for
>> ucom and uftdi: Sep 20 21:33:30 ldaemon kernel: ucom_open:554: tp =
>> 0xffffff001f12b400 Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>> Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>> Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
>> Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
>> Sep 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
>> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>> Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>> Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
>> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status change
>> msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon kernel:
>> ucom_status_change:901:
>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
>> Sep 20 21:33:30 ldaemon kernel: ucom_cfg_status_change:887: DCD changed to
>> 1 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
>> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
>> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
>> Sep 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
>> Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
>> Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>> Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc =
>> 0xffffff001f12ac58 Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064:
>> cnt=2
>> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
>>
>> I really need to get this working so I am ready to test things as much as I
>> can...
>>     
>
> Hi,
>
> You need to set raw mode for the TTY device I think. Maybe Ed can give you the 
> function name you need to call to do that?
>
> --HPS
>   
Do I need to do something like that?
ioctl(fileno(stdin), TIOCGETP, &tty_org);
tty = tty_org;

/* set terminal to raw mode ... */
tty.sg_flags |= CRMOD;
tty.sg_flags &= ~ECHO;
tty.sg_flags &= ~XTABS;
tty.sg_flags |= RAW;

Thanks!
Pierre-Luc Drouin
From hselasky at c2i.net  Mon Sep 21 17:32:03 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Sep 21 17:32:09 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB7B7E6.9070005@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211827.53014.hselasky@c2i.net>
	<4AB7B7E6.9070005@pldrouin.net>
Message-ID: <200909211932.37015.hselasky@c2i.net>

On Monday 21 September 2009 19:29:10 Pierre-Luc Drouin wrote:
> Hans Petter Selasky wrote:
> > On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
> >> Hi,
> >>
> >> I am also having troubles with the uftdi driver on 8.0-BETA4.
> >> I am trying to use a fan controller (mCubed bigNG) that uses a FT232BL
> >> chip and it does not seem to be responding on FreeBSD 8.0 while the same
> >> code works perfectly on Linux (I have not tried the code on RELENG_7 yet
> >> but I could install it if necessary).
> >>
> >> Here is the very simple code I am using for testing:
> >> #include <termios.h>
> >> #include <fcntl.h>
> >> #include <string.h>
> >> #include <unistd.h>
> >> #include <stdio.h>
> >>
> >> int main();
> >>
> >> #define DEV "/dev/ttyU0"
> >>
> >> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
> >> #define TBAN_SER_SOURCE2        0x06 /* Alternative source (miniNG...)
> >> */
> >>
> >> #define TBAN_SER_REQUEST        0x36
> >>
> >> int main()
> >> {
> >>   int fd;
> >>   int result;
> >>   struct termios oldtio, newtio;
> >>   unsigned char buf[285];
> >>
> >>   printf("Opening device\n");
> >>   fd=open(DEV, O_RDWR | O_NOCTTY);
> >>
> >>   if(fd<0) {
> >>     perror(DEV);
> >>     return 1;
> >>   }
> >>
> >>   result=tcgetattr(fd,&oldtio);
> >>   if(result<0) {
> >>     perror("tcgetattr");
> >>     return 1;
> >>   }
> >>
> >>   memcpy(&newtio,&oldtio,sizeof(struct termios));
> >>   newtio.c_cflag = B19200
> >>
> >>     | CRTSCTS
> >>     | CS8
> >>     | CREAD;
> >>
> >>   newtio.c_iflag     = IGNPAR;
> >>   newtio.c_oflag     = 0;
> >>   newtio.c_lflag     = 0;
> >>   newtio.c_cc[VMIN]  = 1;
> >>   newtio.c_cc[VTIME] = 0;
> >>
> >>   result=tcflush(fd, TCIFLUSH);
> >>   if(result<0) {
> >>     perror("tcflush");
> >>     return 1;
> >>   }
> >>
> >>   result=tcsetattr(fd,TCSANOW,&newtio);
> >>   if(result<0) {
> >>     perror("tcsetattr");
> >>     return 1;
> >>   }
> >>
> >>   sleep(1);
> >>
> >>   printf("Performing initial query\n");
> >>   buf[0]=TBAN_SER_SOURCE1;
> >>   buf[1]=TBAN_SER_REQUEST;
> >>
> >>   printf("Requesting status\n");
> >>   result=write(fd,buf,2);
> >>   if(result<0) {
> >>     perror("write");
> >>     return 1;
> >>   }
> >>
> >>   sleep(1);
> >>
> >>   printf("Reading status\n");
> >>   result=read(fd,buf,32);
> >>   if(result<0) {
> >>     perror("read");
> >>     return 1;
> >>   }
> >>
> >>   result=tcsetattr(fd,TCSANOW,&oldtio);
> >>   if(result<0) {
> >>     perror("tcsetattr");
> >>     return 1;
> >>   }
> >>
> >>   result=close(fd);
> >>   if(result<0) {
> >>     perror("close");
> >>     return 1;
> >>   }
> >>   return 0;
> >> }
> >>
> >> It hangs while reading independently of the number of bits I am reading.
> >>
> >> Here is the output from dmesg when I load the uftdi module:
> >> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
> >> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
> >> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
> >> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root: Unknown
> >> USB device: vendor 0x051d product 0x0002 bus uhub0
> >>
> >> Here is the output in /var/log/messages when I enable the debug output
> >> for ucom and uftdi: Sep 20 21:33:30 ldaemon kernel: ucom_open:554: tp =
> >> 0xffffff001f12b400 Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff =
> >> 1 Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> >> Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
> >> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> >> Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
> >> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
> >> Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
> >> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
> >> Sep 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
> >> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
> >> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> >> Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
> >> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> >> Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
> >> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
> >> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status change
> >> msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon kernel:
> >> ucom_status_change:901:
> >> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
> >> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_status_change:887: DCD
> >> changed to 1 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
> >> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
> >> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
> >> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
> >> Sep 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
> >> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
> >> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
> >> Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
> >> Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >> Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc =
> >> 0xffffff001f12ac58 Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064:
> >> cnt=2
> >> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>
> >> I really need to get this working so I am ready to test things as much
> >> as I can...
> >
> > Hi,
> >
> > You need to set raw mode for the TTY device I think. Maybe Ed can give
> > you the function name you need to call to do that?
> >
> > --HPS
>
> Do I need to do something like that?
> ioctl(fileno(stdin), TIOCGETP, &tty_org);
> tty = tty_org;
>
> /* set terminal to raw mode ... */
> tty.sg_flags |= CRMOD;
> tty.sg_flags &= ~ECHO;
> tty.sg_flags &= ~XTABS;
> tty.sg_flags |= RAW;
>
> Thanks!
> Pierre-Luc Drouin

Hi,

You need to call this function:

     void
     cfmakeraw(struct termios *t);

--HPS
From pldrouin at pldrouin.net  Mon Sep 21 17:52:13 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Mon Sep 21 17:52:20 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909211932.37015.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211827.53014.hselasky@c2i.net>
	<4AB7B7E6.9070005@pldrouin.net>
	<200909211932.37015.hselasky@c2i.net>
Message-ID: <4AB7BD4D.4020703@pldrouin.net>

Hans Petter Selasky wrote:
> On Monday 21 September 2009 19:29:10 Pierre-Luc Drouin wrote:
>   
>> Hans Petter Selasky wrote:
>>     
>>> On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
>>>       
>>>> Hi,
>>>>
>>>> I am also having troubles with the uftdi driver on 8.0-BETA4.
>>>> I am trying to use a fan controller (mCubed bigNG) that uses a FT232BL
>>>> chip and it does not seem to be responding on FreeBSD 8.0 while the same
>>>> code works perfectly on Linux (I have not tried the code on RELENG_7 yet
>>>> but I could install it if necessary).
>>>>
>>>> Here is the very simple code I am using for testing:
>>>> #include <termios.h>
>>>> #include <fcntl.h>
>>>> #include <string.h>
>>>> #include <unistd.h>
>>>> #include <stdio.h>
>>>>
>>>> int main();
>>>>
>>>> #define DEV "/dev/ttyU0"
>>>>
>>>> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
>>>> #define TBAN_SER_SOURCE2        0x06 /* Alternative source (miniNG...)
>>>> */
>>>>
>>>> #define TBAN_SER_REQUEST        0x36
>>>>
>>>> int main()
>>>> {
>>>>   int fd;
>>>>   int result;
>>>>   struct termios oldtio, newtio;
>>>>   unsigned char buf[285];
>>>>
>>>>   printf("Opening device\n");
>>>>   fd=open(DEV, O_RDWR | O_NOCTTY);
>>>>
>>>>   if(fd<0) {
>>>>     perror(DEV);
>>>>     return 1;
>>>>   }
>>>>
>>>>   result=tcgetattr(fd,&oldtio);
>>>>   if(result<0) {
>>>>     perror("tcgetattr");
>>>>     return 1;
>>>>   }
>>>>
>>>>   memcpy(&newtio,&oldtio,sizeof(struct termios));
>>>>   newtio.c_cflag = B19200
>>>>
>>>>     | CRTSCTS
>>>>     | CS8
>>>>     | CREAD;
>>>>
>>>>   newtio.c_iflag     = IGNPAR;
>>>>   newtio.c_oflag     = 0;
>>>>   newtio.c_lflag     = 0;
>>>>   newtio.c_cc[VMIN]  = 1;
>>>>   newtio.c_cc[VTIME] = 0;
>>>>
>>>>   result=tcflush(fd, TCIFLUSH);
>>>>   if(result<0) {
>>>>     perror("tcflush");
>>>>     return 1;
>>>>   }
>>>>
>>>>   result=tcsetattr(fd,TCSANOW,&newtio);
>>>>   if(result<0) {
>>>>     perror("tcsetattr");
>>>>     return 1;
>>>>   }
>>>>
>>>>   sleep(1);
>>>>
>>>>   printf("Performing initial query\n");
>>>>   buf[0]=TBAN_SER_SOURCE1;
>>>>   buf[1]=TBAN_SER_REQUEST;
>>>>
>>>>   printf("Requesting status\n");
>>>>   result=write(fd,buf,2);
>>>>   if(result<0) {
>>>>     perror("write");
>>>>     return 1;
>>>>   }
>>>>
>>>>   sleep(1);
>>>>
>>>>   printf("Reading status\n");
>>>>   result=read(fd,buf,32);
>>>>   if(result<0) {
>>>>     perror("read");
>>>>     return 1;
>>>>   }
>>>>
>>>>   result=tcsetattr(fd,TCSANOW,&oldtio);
>>>>   if(result<0) {
>>>>     perror("tcsetattr");
>>>>     return 1;
>>>>   }
>>>>
>>>>   result=close(fd);
>>>>   if(result<0) {
>>>>     perror("close");
>>>>     return 1;
>>>>   }
>>>>   return 0;
>>>> }
>>>>
>>>> It hangs while reading independently of the number of bits I am reading.
>>>>
>>>> Here is the output from dmesg when I load the uftdi module:
>>>> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
>>>> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
>>>> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
>>>> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root: Unknown
>>>> USB device: vendor 0x051d product 0x0002 bus uhub0
>>>>
>>>> Here is the output in /var/log/messages when I enable the debug output
>>>> for ucom and uftdi: Sep 20 21:33:30 ldaemon kernel: ucom_open:554: tp =
>>>> 0xffffff001f12b400 Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff =
>>>> 1 Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status change
>>>> msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon kernel:
>>>> ucom_status_change:901:
>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_status_change:887: DCD
>>>> changed to 1 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
>>>> Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>> Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>> Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc =
>>>> 0xffffff001f12ac58 Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064:
>>>> cnt=2
>>>> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>
>>>> I really need to get this working so I am ready to test things as much
>>>> as I can...
>>>>         
>>> Hi,
>>>
>>> You need to set raw mode for the TTY device I think. Maybe Ed can give
>>> you the function name you need to call to do that?
>>>
>>> --HPS
>>>       
>> Do I need to do something like that?
>> ioctl(fileno(stdin), TIOCGETP, &tty_org);
>> tty = tty_org;
>>
>> /* set terminal to raw mode ... */
>> tty.sg_flags |= CRMOD;
>> tty.sg_flags &= ~ECHO;
>> tty.sg_flags &= ~XTABS;
>> tty.sg_flags |= RAW;
>>
>> Thanks!
>> Pierre-Luc Drouin
>>     
>
> Hi,
>
> You need to call this function:
>
>      void
>      cfmakeraw(struct termios *t);
>
> --HPS
>   
Hi,

it still does not work. I have added the line
cfmakeraw(&newtio);

just before the call to tcflush and I get the following output in 
/var/log/messages:
Sep 21 13:38:46 ldaemon kernel: ucom_open:554: tp = 0xffffff001f12b400
Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
Sep 21 13:38:46 ldaemon kernel: ucom_break:816: onoff = 0
Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
Sep 21 13:38:46 ldaemon kernel: ucom_status_change:901:
Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
Sep 21 13:38:46 ldaemon kernel: uftdi_pre_param:653:
Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
Sep 21 13:38:46 ldaemon kernel: ucom_cfg_open:520:
Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_open:354: 
uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
Sep 21 13:38:46 ldaemon kernel: ucom_cfg_status_change:887: DCD changed to 1
Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
Sep 21 13:38:46 ldaemon kernel: uftdi_pre_param:653:
Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
Sep 21 13:38:46 ldaemon kernel: ucom_get_data:1064: cnt=0
Sep 21 13:38:47 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
Sep 21 13:38:48 ldaemon kernel: ucom_outwakeup:1009: sc = 0xffffff001f12ac58
Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064: cnt=2
Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064: cnt=0

Thanks!
Pierre-Luc
From hselasky at c2i.net  Mon Sep 21 18:14:02 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Sep 21 18:14:08 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB7BD4D.4020703@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211932.37015.hselasky@c2i.net>
	<4AB7BD4D.4020703@pldrouin.net>
Message-ID: <200909212014.36874.hselasky@c2i.net>

On Monday 21 September 2009 19:52:13 Pierre-Luc Drouin wrote:
> Hans Petter Selasky wrote:
> > On Monday 21 September 2009 19:29:10 Pierre-Luc Drouin wrote:
> >> Hans Petter Selasky wrote:
> >>> On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
> >>>> Hi,
> >>>>
> >>>> I am also having troubles with the uftdi driver on 8.0-BETA4.
> >>>> I am trying to use a fan controller (mCubed bigNG) that uses a FT232BL
> >>>> chip and it does not seem to be responding on FreeBSD 8.0 while the
> >>>> same code works perfectly on Linux (I have not tried the code on
> >>>> RELENG_7 yet but I could install it if necessary).
> >>>>
> >>>> Here is the very simple code I am using for testing:
> >>>> #include <termios.h>
> >>>> #include <fcntl.h>
> >>>> #include <string.h>
> >>>> #include <unistd.h>
> >>>> #include <stdio.h>
> >>>>
> >>>> int main();
> >>>>
> >>>> #define DEV "/dev/ttyU0"
> >>>>
> >>>> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
> >>>> #define TBAN_SER_SOURCE2        0x06 /* Alternative source (miniNG...)
> >>>> */
> >>>>
> >>>> #define TBAN_SER_REQUEST        0x36
> >>>>
> >>>> int main()
> >>>> {
> >>>>   int fd;
> >>>>   int result;
> >>>>   struct termios oldtio, newtio;
> >>>>   unsigned char buf[285];
> >>>>
> >>>>   printf("Opening device\n");
> >>>>   fd=open(DEV, O_RDWR | O_NOCTTY);
> >>>>
> >>>>   if(fd<0) {
> >>>>     perror(DEV);
> >>>>     return 1;
> >>>>   }
> >>>>
> >>>>   result=tcgetattr(fd,&oldtio);
> >>>>   if(result<0) {
> >>>>     perror("tcgetattr");
> >>>>     return 1;
> >>>>   }
> >>>>
> >>>>   memcpy(&newtio,&oldtio,sizeof(struct termios));
> >>>>   newtio.c_cflag = B19200
> >>>>
> >>>>     | CRTSCTS
> >>>>     | CS8
> >>>>     | CREAD;
> >>>>
> >>>>   newtio.c_iflag     = IGNPAR;
> >>>>   newtio.c_oflag     = 0;
> >>>>   newtio.c_lflag     = 0;
> >>>>   newtio.c_cc[VMIN]  = 1;
> >>>>   newtio.c_cc[VTIME] = 0;
> >>>>
> >>>>   result=tcflush(fd, TCIFLUSH);
> >>>>   if(result<0) {
> >>>>     perror("tcflush");
> >>>>     return 1;
> >>>>   }
> >>>>
> >>>>   result=tcsetattr(fd,TCSANOW,&newtio);
> >>>>   if(result<0) {
> >>>>     perror("tcsetattr");
> >>>>     return 1;
> >>>>   }
> >>>>
> >>>>   sleep(1);
> >>>>
> >>>>   printf("Performing initial query\n");
> >>>>   buf[0]=TBAN_SER_SOURCE1;
> >>>>   buf[1]=TBAN_SER_REQUEST;
> >>>>
> >>>>   printf("Requesting status\n");
> >>>>   result=write(fd,buf,2);
> >>>>   if(result<0) {
> >>>>     perror("write");
> >>>>     return 1;
> >>>>   }
> >>>>
> >>>>   sleep(1);
> >>>>
> >>>>   printf("Reading status\n");
> >>>>   result=read(fd,buf,32);
> >>>>   if(result<0) {
> >>>>     perror("read");
> >>>>     return 1;
> >>>>   }
> >>>>
> >>>>   result=tcsetattr(fd,TCSANOW,&oldtio);
> >>>>   if(result<0) {
> >>>>     perror("tcsetattr");
> >>>>     return 1;
> >>>>   }
> >>>>
> >>>>   result=close(fd);
> >>>>   if(result<0) {
> >>>>     perror("close");
> >>>>     return 1;
> >>>>   }
> >>>>   return 0;
> >>>> }
> >>>>
> >>>> It hangs while reading independently of the number of bits I am
> >>>> reading.
> >>>>
> >>>> Here is the output from dmesg when I load the uftdi module:
> >>>> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
> >>>> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
> >>>> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
> >>>> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root:
> >>>> Unknown USB device: vendor 0x051d product 0x0002 bus uhub0
> >>>>
> >>>> Here is the output in /var/log/messages when I enable the debug output
> >>>> for ucom and uftdi: Sep 20 21:33:30 ldaemon kernel: ucom_open:554: tp
> >>>> = 0xffffff001f12b400 Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827:
> >>>> onoff = 1 Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799:
> >>>> on=0x01, off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff
> >>>> = 1
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc =
> >>>> 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon kernel:
> >>>> uftdi_pre_param:653:
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
> >>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
> >>>> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status change
> >>>> msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon kernel:
> >>>> ucom_status_change:901:
> >>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
> >>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_status_change:887:
> >>>> DCD changed to 1 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413 Sep
> >>>> 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410 Sep 20
> >>>> 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414 Sep 20
> >>>> 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58 Sep
> >>>> 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
> >>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
> >>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
> >>>> Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>> Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >>>> Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc =
> >>>> 0xffffff001f12ac58 Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064:
> >>>> cnt=2
> >>>> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>>
> >>>> I really need to get this working so I am ready to test things as much
> >>>> as I can...
> >>>
> >>> Hi,
> >>>
> >>> You need to set raw mode for the TTY device I think. Maybe Ed can give
> >>> you the function name you need to call to do that?
> >>>
> >>> --HPS
> >>
> >> Do I need to do something like that?
> >> ioctl(fileno(stdin), TIOCGETP, &tty_org);
> >> tty = tty_org;
> >>
> >> /* set terminal to raw mode ... */
> >> tty.sg_flags |= CRMOD;
> >> tty.sg_flags &= ~ECHO;
> >> tty.sg_flags &= ~XTABS;
> >> tty.sg_flags |= RAW;
> >>
> >> Thanks!
> >> Pierre-Luc Drouin
> >
> > Hi,
> >
> > You need to call this function:
> >
> >      void
> >      cfmakeraw(struct termios *t);
> >
> > --HPS
>
> Hi,
>
> it still does not work. I have added the line
> cfmakeraw(&newtio);
>
> just before the call to tcflush and I get the following output in
> /var/log/messages:
> Sep 21 13:38:46 ldaemon kernel: ucom_open:554: tp = 0xffffff001f12b400
> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> Sep 21 13:38:46 ldaemon kernel: ucom_break:816: onoff = 0
> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
> Sep 21 13:38:46 ldaemon kernel: ucom_status_change:901:
> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
> Sep 21 13:38:46 ldaemon kernel: uftdi_pre_param:653:
> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_open:520:
> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_open:354:
> uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_status_change:887: DCD changed to
> 1 Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
> Sep 21 13:38:46 ldaemon kernel: uftdi_pre_param:653:
> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
> Sep 21 13:38:46 ldaemon kernel: ucom_get_data:1064: cnt=0
> Sep 21 13:38:47 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> Sep 21 13:38:48 ldaemon kernel: ucom_outwakeup:1009: sc =
> 0xffffff001f12ac58 Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064:
> cnt=2
> Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064: cnt=0
>

Can you try adding a delay after setting the baud rate?

--HPS
From pldrouin at pldrouin.net  Mon Sep 21 18:28:58 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Mon Sep 21 18:29:05 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909212014.36874.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211932.37015.hselasky@c2i.net>
	<4AB7BD4D.4020703@pldrouin.net>
	<200909212014.36874.hselasky@c2i.net>
Message-ID: <4AB7C5EA.5090008@pldrouin.net>

Hans Petter Selasky wrote:
> On Monday 21 September 2009 19:52:13 Pierre-Luc Drouin wrote:
>   
>> Hans Petter Selasky wrote:
>>     
>>> On Monday 21 September 2009 19:29:10 Pierre-Luc Drouin wrote:
>>>       
>>>> Hans Petter Selasky wrote:
>>>>         
>>>>> On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
>>>>>           
>>>>>> Hi,
>>>>>>
>>>>>> I am also having troubles with the uftdi driver on 8.0-BETA4.
>>>>>> I am trying to use a fan controller (mCubed bigNG) that uses a FT232BL
>>>>>> chip and it does not seem to be responding on FreeBSD 8.0 while the
>>>>>> same code works perfectly on Linux (I have not tried the code on
>>>>>> RELENG_7 yet but I could install it if necessary).
>>>>>>
>>>>>> Here is the very simple code I am using for testing:
>>>>>> #include <termios.h>
>>>>>> #include <fcntl.h>
>>>>>> #include <string.h>
>>>>>> #include <unistd.h>
>>>>>> #include <stdio.h>
>>>>>>
>>>>>> int main();
>>>>>>
>>>>>> #define DEV "/dev/ttyU0"
>>>>>>
>>>>>> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
>>>>>> #define TBAN_SER_SOURCE2        0x06 /* Alternative source (miniNG...)
>>>>>> */
>>>>>>
>>>>>> #define TBAN_SER_REQUEST        0x36
>>>>>>
>>>>>> int main()
>>>>>> {
>>>>>>   int fd;
>>>>>>   int result;
>>>>>>   struct termios oldtio, newtio;
>>>>>>   unsigned char buf[285];
>>>>>>
>>>>>>   printf("Opening device\n");
>>>>>>   fd=open(DEV, O_RDWR | O_NOCTTY);
>>>>>>
>>>>>>   if(fd<0) {
>>>>>>     perror(DEV);
>>>>>>     return 1;
>>>>>>   }
>>>>>>
>>>>>>   result=tcgetattr(fd,&oldtio);
>>>>>>   if(result<0) {
>>>>>>     perror("tcgetattr");
>>>>>>     return 1;
>>>>>>   }
>>>>>>
>>>>>>   memcpy(&newtio,&oldtio,sizeof(struct termios));
>>>>>>   newtio.c_cflag = B19200
>>>>>>
>>>>>>     | CRTSCTS
>>>>>>     | CS8
>>>>>>     | CREAD;
>>>>>>
>>>>>>   newtio.c_iflag     = IGNPAR;
>>>>>>   newtio.c_oflag     = 0;
>>>>>>   newtio.c_lflag     = 0;
>>>>>>   newtio.c_cc[VMIN]  = 1;
>>>>>>   newtio.c_cc[VTIME] = 0;
>>>>>>
>>>>>>   result=tcflush(fd, TCIFLUSH);
>>>>>>   if(result<0) {
>>>>>>     perror("tcflush");
>>>>>>     return 1;
>>>>>>   }
>>>>>>
>>>>>>   result=tcsetattr(fd,TCSANOW,&newtio);
>>>>>>   if(result<0) {
>>>>>>     perror("tcsetattr");
>>>>>>     return 1;
>>>>>>   }
>>>>>>
>>>>>>   sleep(1);
>>>>>>
>>>>>>   printf("Performing initial query\n");
>>>>>>   buf[0]=TBAN_SER_SOURCE1;
>>>>>>   buf[1]=TBAN_SER_REQUEST;
>>>>>>
>>>>>>   printf("Requesting status\n");
>>>>>>   result=write(fd,buf,2);
>>>>>>   if(result<0) {
>>>>>>     perror("write");
>>>>>>     return 1;
>>>>>>   }
>>>>>>
>>>>>>   sleep(1);
>>>>>>
>>>>>>   printf("Reading status\n");
>>>>>>   result=read(fd,buf,32);
>>>>>>   if(result<0) {
>>>>>>     perror("read");
>>>>>>     return 1;
>>>>>>   }
>>>>>>
>>>>>>   result=tcsetattr(fd,TCSANOW,&oldtio);
>>>>>>   if(result<0) {
>>>>>>     perror("tcsetattr");
>>>>>>     return 1;
>>>>>>   }
>>>>>>
>>>>>>   result=close(fd);
>>>>>>   if(result<0) {
>>>>>>     perror("close");
>>>>>>     return 1;
>>>>>>   }
>>>>>>   return 0;
>>>>>> }
>>>>>>
>>>>>> It hangs while reading independently of the number of bits I am
>>>>>> reading.
>>>>>>
>>>>>> Here is the output from dmesg when I load the uftdi module:
>>>>>> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
>>>>>> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
>>>>>> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
>>>>>> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root:
>>>>>> Unknown USB device: vendor 0x051d product 0x0002 bus uhub0
>>>>>>
>>>>>> Here is the output in /var/log/messages when I enable the debug output
>>>>>> for ucom and uftdi: Sep 20 21:33:30 ldaemon kernel: ucom_open:554: tp
>>>>>> = 0xffffff001f12b400 Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827:
>>>>>> onoff = 1 Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799:
>>>>>> on=0x01, off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff
>>>>>> = 1
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc =
>>>>>> 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon kernel:
>>>>>> uftdi_pre_param:653:
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status change
>>>>>> msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon kernel:
>>>>>> ucom_status_change:901:
>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
>>>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_status_change:887:
>>>>>> DCD changed to 1 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413 Sep
>>>>>> 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410 Sep 20
>>>>>> 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414 Sep 20
>>>>>> 21:33:30 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58 Sep
>>>>>> 20 21:33:30 ldaemon kernel: uftdi_pre_param:653:
>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
>>>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>> Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc =
>>>>>> 0xffffff001f12ac58 Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064:
>>>>>> cnt=2
>>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>>
>>>>>> I really need to get this working so I am ready to test things as much
>>>>>> as I can...
>>>>>>             
>>>>> Hi,
>>>>>
>>>>> You need to set raw mode for the TTY device I think. Maybe Ed can give
>>>>> you the function name you need to call to do that?
>>>>>
>>>>> --HPS
>>>>>           
>>>> Do I need to do something like that?
>>>> ioctl(fileno(stdin), TIOCGETP, &tty_org);
>>>> tty = tty_org;
>>>>
>>>> /* set terminal to raw mode ... */
>>>> tty.sg_flags |= CRMOD;
>>>> tty.sg_flags &= ~ECHO;
>>>> tty.sg_flags &= ~XTABS;
>>>> tty.sg_flags |= RAW;
>>>>
>>>> Thanks!
>>>> Pierre-Luc Drouin
>>>>         
>>> Hi,
>>>
>>> You need to call this function:
>>>
>>>      void
>>>      cfmakeraw(struct termios *t);
>>>
>>> --HPS
>>>       
>> Hi,
>>
>> it still does not work. I have added the line
>> cfmakeraw(&newtio);
>>
>> just before the call to tcflush and I get the following output in
>> /var/log/messages:
>> Sep 21 13:38:46 ldaemon kernel: ucom_open:554: tp = 0xffffff001f12b400
>> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>> Sep 21 13:38:46 ldaemon kernel: ucom_break:816: onoff = 0
>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
>> Sep 21 13:38:46 ldaemon kernel: ucom_status_change:901:
>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
>> Sep 21 13:38:46 ldaemon kernel: uftdi_pre_param:653:
>> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_open:520:
>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_open:354:
>> uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
>> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_status_change:887: DCD changed to
>> 1 Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
>> Sep 21 13:38:46 ldaemon kernel: uftdi_pre_param:653:
>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
>> Sep 21 13:38:46 ldaemon kernel: ucom_get_data:1064: cnt=0
>> Sep 21 13:38:47 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>> Sep 21 13:38:48 ldaemon kernel: ucom_outwakeup:1009: sc =
>> 0xffffff001f12ac58 Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064:
>> cnt=2
>> Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064: cnt=0
>>
>>     
>
> Can you try adding a delay after setting the baud rate?
>
> --HPS
>   
The code already sleeps for 1 second after I applying the baud rate (via 
tcsetattr(fd,TCSANOW,&newtio)). I am not sure to understand what you mean...

Thanks
From hselasky at c2i.net  Mon Sep 21 18:44:45 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Sep 21 18:44:52 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB7C5EA.5090008@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909212014.36874.hselasky@c2i.net>
	<4AB7C5EA.5090008@pldrouin.net>
Message-ID: <200909212045.20657.hselasky@c2i.net>

On Monday 21 September 2009 20:28:58 Pierre-Luc Drouin wrote:
> Hans Petter Selasky wrote:
> > On Monday 21 September 2009 19:52:13 Pierre-Luc Drouin wrote:
> >> Hans Petter Selasky wrote:
> >>> On Monday 21 September 2009 19:29:10 Pierre-Luc Drouin wrote:
> >>>> Hans Petter Selasky wrote:
> >>>>> On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
> >>>>>> Hi,
> >>>>>>
> >>>>>> I am also having troubles with the uftdi driver on 8.0-BETA4.
> >>>>>> I am trying to use a fan controller (mCubed bigNG) that uses a
> >>>>>> FT232BL chip and it does not seem to be responding on FreeBSD 8.0
> >>>>>> while the same code works perfectly on Linux (I have not tried the
> >>>>>> code on RELENG_7 yet but I could install it if necessary).
> >>>>>>
> >>>>>> Here is the very simple code I am using for testing:
> >>>>>> #include <termios.h>
> >>>>>> #include <fcntl.h>
> >>>>>> #include <string.h>
> >>>>>> #include <unistd.h>
> >>>>>> #include <stdio.h>
> >>>>>>
> >>>>>> int main();
> >>>>>>
> >>>>>> #define DEV "/dev/ttyU0"
> >>>>>>
> >>>>>> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
> >>>>>> #define TBAN_SER_SOURCE2        0x06 /* Alternative source
> >>>>>> (miniNG...) */
> >>>>>>
> >>>>>> #define TBAN_SER_REQUEST        0x36
> >>>>>>
> >>>>>> int main()
> >>>>>> {
> >>>>>>   int fd;
> >>>>>>   int result;
> >>>>>>   struct termios oldtio, newtio;
> >>>>>>   unsigned char buf[285];
> >>>>>>
> >>>>>>   printf("Opening device\n");
> >>>>>>   fd=open(DEV, O_RDWR | O_NOCTTY);
> >>>>>>
> >>>>>>   if(fd<0) {
> >>>>>>     perror(DEV);
> >>>>>>     return 1;
> >>>>>>   }
> >>>>>>
> >>>>>>   result=tcgetattr(fd,&oldtio);
> >>>>>>   if(result<0) {
> >>>>>>     perror("tcgetattr");
> >>>>>>     return 1;
> >>>>>>   }
> >>>>>>
> >>>>>>   memcpy(&newtio,&oldtio,sizeof(struct termios));
> >>>>>>   newtio.c_cflag = B19200
> >>>>>>
> >>>>>>     | CRTSCTS
> >>>>>>     | CS8
> >>>>>>     | CREAD;
> >>>>>>
> >>>>>>   newtio.c_iflag     = IGNPAR;
> >>>>>>   newtio.c_oflag     = 0;
> >>>>>>   newtio.c_lflag     = 0;
> >>>>>>   newtio.c_cc[VMIN]  = 1;
> >>>>>>   newtio.c_cc[VTIME] = 0;
> >>>>>>
> >>>>>>   result=tcflush(fd, TCIFLUSH);
> >>>>>>   if(result<0) {
> >>>>>>     perror("tcflush");
> >>>>>>     return 1;
> >>>>>>   }
> >>>>>>
> >>>>>>   result=tcsetattr(fd,TCSANOW,&newtio);
> >>>>>>   if(result<0) {
> >>>>>>     perror("tcsetattr");
> >>>>>>     return 1;
> >>>>>>   }
> >>>>>>
> >>>>>>   sleep(1);
> >>>>>>
> >>>>>>   printf("Performing initial query\n");
> >>>>>>   buf[0]=TBAN_SER_SOURCE1;
> >>>>>>   buf[1]=TBAN_SER_REQUEST;
> >>>>>>
> >>>>>>   printf("Requesting status\n");
> >>>>>>   result=write(fd,buf,2);
> >>>>>>   if(result<0) {
> >>>>>>     perror("write");
> >>>>>>     return 1;
> >>>>>>   }
> >>>>>>
> >>>>>>   sleep(1);
> >>>>>>
> >>>>>>   printf("Reading status\n");
> >>>>>>   result=read(fd,buf,32);
> >>>>>>   if(result<0) {
> >>>>>>     perror("read");
> >>>>>>     return 1;
> >>>>>>   }
> >>>>>>
> >>>>>>   result=tcsetattr(fd,TCSANOW,&oldtio);
> >>>>>>   if(result<0) {
> >>>>>>     perror("tcsetattr");
> >>>>>>     return 1;
> >>>>>>   }
> >>>>>>
> >>>>>>   result=close(fd);
> >>>>>>   if(result<0) {
> >>>>>>     perror("close");
> >>>>>>     return 1;
> >>>>>>   }
> >>>>>>   return 0;
> >>>>>> }
> >>>>>>
> >>>>>> It hangs while reading independently of the number of bits I am
> >>>>>> reading.
> >>>>>>
> >>>>>> Here is the output from dmesg when I load the uftdi module:
> >>>>>> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
> >>>>>> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
> >>>>>> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
> >>>>>> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root:
> >>>>>> Unknown USB device: vendor 0x051d product 0x0002 bus uhub0
> >>>>>>
> >>>>>> Here is the output in /var/log/messages when I enable the debug
> >>>>>> output for ucom and uftdi: Sep 20 21:33:30 ldaemon kernel:
> >>>>>> ucom_open:554: tp = 0xffffff001f12b400 Sep 20 21:33:30 ldaemon
> >>>>>> kernel: ucom_dtr:827: onoff = 1 Sep 20 21:33:30 ldaemon kernel:
> >>>>>> ucom_line_state:799: on=0x01, off=0x00 Sep 20 21:33:30 ldaemon
> >>>>>> kernel: ucom_rts:838: onoff = 1
> >>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
> >>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
> >>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00,
> >>>>>> off=0x04 Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
> >>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc =
> >>>>>> 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon kernel:
> >>>>>> uftdi_pre_param:653:
> >>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
> >>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01,
> >>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
> >>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
> >>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
> >>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
> >>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status
> >>>>>> change msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon
> >>>>>> kernel: ucom_status_change:901:
> >>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
> >>>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_status_change:887:
> >>>>>> DCD changed to 1 Sep 20 21:33:30 ldaemon kernel:
> >>>>>> uftdi_cfg_param:672: Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653:
> >>>>>> cmd = 0x402c7413 Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd
> >>>>>> = 0x80047410 Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd =
> >>>>>> 0x802c7414 Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc =
> >>>>>> 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon kernel:
> >>>>>> uftdi_pre_param:653:
> >>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
> >>>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
> >>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>>>> Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc =
> >>>>>> 0xffffff001f12ac58 Sep 20 21:33:32 ldaemon kernel:
> >>>>>> ucom_get_data:1064: cnt=2
> >>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>>>>
> >>>>>> I really need to get this working so I am ready to test things as
> >>>>>> much as I can...
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> You need to set raw mode for the TTY device I think. Maybe Ed can
> >>>>> give you the function name you need to call to do that?
> >>>>>
> >>>>> --HPS
> >>>>
> >>>> Do I need to do something like that?
> >>>> ioctl(fileno(stdin), TIOCGETP, &tty_org);
> >>>> tty = tty_org;
> >>>>
> >>>> /* set terminal to raw mode ... */
> >>>> tty.sg_flags |= CRMOD;
> >>>> tty.sg_flags &= ~ECHO;
> >>>> tty.sg_flags &= ~XTABS;
> >>>> tty.sg_flags |= RAW;
> >>>>
> >>>> Thanks!
> >>>> Pierre-Luc Drouin
> >>>
> >>> Hi,
> >>>
> >>> You need to call this function:
> >>>
> >>>      void
> >>>      cfmakeraw(struct termios *t);
> >>>
> >>> --HPS
> >>
> >> Hi,
> >>
> >> it still does not work. I have added the line
> >> cfmakeraw(&newtio);
> >>
> >> just before the call to tcflush and I get the following output in
> >> /var/log/messages:
> >> Sep 21 13:38:46 ldaemon kernel: ucom_open:554: tp = 0xffffff001f12b400
> >> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
> >> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> >> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
> >> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> >> Sep 21 13:38:46 ldaemon kernel: ucom_break:816: onoff = 0
> >> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
> >> Sep 21 13:38:46 ldaemon kernel: ucom_status_change:901:
> >> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
> >> Sep 21 13:38:46 ldaemon kernel: uftdi_pre_param:653:
> >> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
> >> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> >> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
> >> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> >> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_open:520:
> >> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_open:354:
> >> uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
> >> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_status_change:887: DCD changed
> >> to 1 Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
> >> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
> >> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
> >> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
> >> Sep 21 13:38:46 ldaemon kernel: uftdi_pre_param:653:
> >> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
> >> Sep 21 13:38:46 ldaemon kernel: ucom_get_data:1064: cnt=0
> >> Sep 21 13:38:47 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >> Sep 21 13:38:48 ldaemon kernel: ucom_outwakeup:1009: sc =
> >> 0xffffff001f12ac58 Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064:
> >> cnt=2
> >> Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064: cnt=0
> >
> > Can you try adding a delay after setting the baud rate?
> >
> > --HPS
>
> The code already sleeps for 1 second after I applying the baud rate (via
> tcsetattr(fd,TCSANOW,&newtio)). I am not sure to understand what you
> mean...

Hi,

I mean try adding some:

usleep(1000000);

To your code to see if that changes anything.

Also try reading one byte instead of 32.

Last, try adding a printout to:

src/sys/dev/usb/serial/uftdi.c

uftdi_read_callback()

and printout the actlen variable.

--HPS

From pldrouin at pldrouin.net  Mon Sep 21 18:58:43 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Mon Sep 21 18:58:55 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909212045.20657.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909212014.36874.hselasky@c2i.net>
	<4AB7C5EA.5090008@pldrouin.net>
	<200909212045.20657.hselasky@c2i.net>
Message-ID: <4AB7CCE0.2000703@pldrouin.net>

Hans Petter Selasky wrote:
> On Monday 21 September 2009 20:28:58 Pierre-Luc Drouin wrote:
>   
>> Hans Petter Selasky wrote:
>>     
>>> On Monday 21 September 2009 19:52:13 Pierre-Luc Drouin wrote:
>>>       
>>>> Hans Petter Selasky wrote:
>>>>         
>>>>> On Monday 21 September 2009 19:29:10 Pierre-Luc Drouin wrote:
>>>>>           
>>>>>> Hans Petter Selasky wrote:
>>>>>>             
>>>>>>> On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
>>>>>>>               
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I am also having troubles with the uftdi driver on 8.0-BETA4.
>>>>>>>> I am trying to use a fan controller (mCubed bigNG) that uses a
>>>>>>>> FT232BL chip and it does not seem to be responding on FreeBSD 8.0
>>>>>>>> while the same code works perfectly on Linux (I have not tried the
>>>>>>>> code on RELENG_7 yet but I could install it if necessary).
>>>>>>>>
>>>>>>>> Here is the very simple code I am using for testing:
>>>>>>>> #include <termios.h>
>>>>>>>> #include <fcntl.h>
>>>>>>>> #include <string.h>
>>>>>>>> #include <unistd.h>
>>>>>>>> #include <stdio.h>
>>>>>>>>
>>>>>>>> int main();
>>>>>>>>
>>>>>>>> #define DEV "/dev/ttyU0"
>>>>>>>>
>>>>>>>> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
>>>>>>>> #define TBAN_SER_SOURCE2        0x06 /* Alternative source
>>>>>>>> (miniNG...) */
>>>>>>>>
>>>>>>>> #define TBAN_SER_REQUEST        0x36
>>>>>>>>
>>>>>>>> int main()
>>>>>>>> {
>>>>>>>>   int fd;
>>>>>>>>   int result;
>>>>>>>>   struct termios oldtio, newtio;
>>>>>>>>   unsigned char buf[285];
>>>>>>>>
>>>>>>>>   printf("Opening device\n");
>>>>>>>>   fd=open(DEV, O_RDWR | O_NOCTTY);
>>>>>>>>
>>>>>>>>   if(fd<0) {
>>>>>>>>     perror(DEV);
>>>>>>>>     return 1;
>>>>>>>>   }
>>>>>>>>
>>>>>>>>   result=tcgetattr(fd,&oldtio);
>>>>>>>>   if(result<0) {
>>>>>>>>     perror("tcgetattr");
>>>>>>>>     return 1;
>>>>>>>>   }
>>>>>>>>
>>>>>>>>   memcpy(&newtio,&oldtio,sizeof(struct termios));
>>>>>>>>   newtio.c_cflag = B19200
>>>>>>>>
>>>>>>>>     | CRTSCTS
>>>>>>>>     | CS8
>>>>>>>>     | CREAD;
>>>>>>>>
>>>>>>>>   newtio.c_iflag     = IGNPAR;
>>>>>>>>   newtio.c_oflag     = 0;
>>>>>>>>   newtio.c_lflag     = 0;
>>>>>>>>   newtio.c_cc[VMIN]  = 1;
>>>>>>>>   newtio.c_cc[VTIME] = 0;
>>>>>>>>
>>>>>>>>   result=tcflush(fd, TCIFLUSH);
>>>>>>>>   if(result<0) {
>>>>>>>>     perror("tcflush");
>>>>>>>>     return 1;
>>>>>>>>   }
>>>>>>>>
>>>>>>>>   result=tcsetattr(fd,TCSANOW,&newtio);
>>>>>>>>   if(result<0) {
>>>>>>>>     perror("tcsetattr");
>>>>>>>>     return 1;
>>>>>>>>   }
>>>>>>>>
>>>>>>>>   sleep(1);
>>>>>>>>
>>>>>>>>   printf("Performing initial query\n");
>>>>>>>>   buf[0]=TBAN_SER_SOURCE1;
>>>>>>>>   buf[1]=TBAN_SER_REQUEST;
>>>>>>>>
>>>>>>>>   printf("Requesting status\n");
>>>>>>>>   result=write(fd,buf,2);
>>>>>>>>   if(result<0) {
>>>>>>>>     perror("write");
>>>>>>>>     return 1;
>>>>>>>>   }
>>>>>>>>
>>>>>>>>   sleep(1);
>>>>>>>>
>>>>>>>>   printf("Reading status\n");
>>>>>>>>   result=read(fd,buf,32);
>>>>>>>>   if(result<0) {
>>>>>>>>     perror("read");
>>>>>>>>     return 1;
>>>>>>>>   }
>>>>>>>>
>>>>>>>>   result=tcsetattr(fd,TCSANOW,&oldtio);
>>>>>>>>   if(result<0) {
>>>>>>>>     perror("tcsetattr");
>>>>>>>>     return 1;
>>>>>>>>   }
>>>>>>>>
>>>>>>>>   result=close(fd);
>>>>>>>>   if(result<0) {
>>>>>>>>     perror("close");
>>>>>>>>     return 1;
>>>>>>>>   }
>>>>>>>>   return 0;
>>>>>>>> }
>>>>>>>>
>>>>>>>> It hangs while reading independently of the number of bits I am
>>>>>>>> reading.
>>>>>>>>
>>>>>>>> Here is the output from dmesg when I load the uftdi module:
>>>>>>>> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
>>>>>>>> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
>>>>>>>> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
>>>>>>>> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root:
>>>>>>>> Unknown USB device: vendor 0x051d product 0x0002 bus uhub0
>>>>>>>>
>>>>>>>> Here is the output in /var/log/messages when I enable the debug
>>>>>>>> output for ucom and uftdi: Sep 20 21:33:30 ldaemon kernel:
>>>>>>>> ucom_open:554: tp = 0xffffff001f12b400 Sep 20 21:33:30 ldaemon
>>>>>>>> kernel: ucom_dtr:827: onoff = 1 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>> ucom_line_state:799: on=0x01, off=0x00 Sep 20 21:33:30 ldaemon
>>>>>>>> kernel: ucom_rts:838: onoff = 1
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00,
>>>>>>>> off=0x04 Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc =
>>>>>>>> 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>> uftdi_pre_param:653:
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01,
>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status
>>>>>>>> change msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon
>>>>>>>> kernel: ucom_status_change:901:
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
>>>>>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_status_change:887:
>>>>>>>> DCD changed to 1 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>> uftdi_cfg_param:672: Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653:
>>>>>>>> cmd = 0x402c7413 Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd
>>>>>>>> = 0x80047410 Sep 20 21:33:30 ldaemon kernel: ucom_ioctl:653: cmd =
>>>>>>>> 0x802c7414 Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc =
>>>>>>>> 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>> uftdi_pre_param:653:
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
>>>>>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>>>> Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc =
>>>>>>>> 0xffffff001f12ac58 Sep 20 21:33:32 ldaemon kernel:
>>>>>>>> ucom_get_data:1064: cnt=2
>>>>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>>>>
>>>>>>>> I really need to get this working so I am ready to test things as
>>>>>>>> much as I can...
>>>>>>>>                 
>>>>>>> Hi,
>>>>>>>
>>>>>>> You need to set raw mode for the TTY device I think. Maybe Ed can
>>>>>>> give you the function name you need to call to do that?
>>>>>>>
>>>>>>> --HPS
>>>>>>>               
>>>>>> Do I need to do something like that?
>>>>>> ioctl(fileno(stdin), TIOCGETP, &tty_org);
>>>>>> tty = tty_org;
>>>>>>
>>>>>> /* set terminal to raw mode ... */
>>>>>> tty.sg_flags |= CRMOD;
>>>>>> tty.sg_flags &= ~ECHO;
>>>>>> tty.sg_flags &= ~XTABS;
>>>>>> tty.sg_flags |= RAW;
>>>>>>
>>>>>> Thanks!
>>>>>> Pierre-Luc Drouin
>>>>>>             
>>>>> Hi,
>>>>>
>>>>> You need to call this function:
>>>>>
>>>>>      void
>>>>>      cfmakeraw(struct termios *t);
>>>>>
>>>>> --HPS
>>>>>           
>>>> Hi,
>>>>
>>>> it still does not work. I have added the line
>>>> cfmakeraw(&newtio);
>>>>
>>>> just before the call to tcflush and I get the following output in
>>>> /var/log/messages:
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_open:554: tp = 0xffffff001f12b400
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_break:816: onoff = 0
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_status_change:901:
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
>>>> Sep 21 13:38:46 ldaemon kernel: uftdi_pre_param:653:
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_open:520:
>>>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_open:354:
>>>> uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_status_change:887: DCD changed
>>>> to 1 Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc = 0xffffff001f12ac58
>>>> Sep 21 13:38:46 ldaemon kernel: uftdi_pre_param:653:
>>>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
>>>> Sep 21 13:38:46 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>> Sep 21 13:38:47 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>> Sep 21 13:38:48 ldaemon kernel: ucom_outwakeup:1009: sc =
>>>> 0xffffff001f12ac58 Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064:
>>>> cnt=2
>>>> Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>         
>>> Can you try adding a delay after setting the baud rate?
>>>
>>> --HPS
>>>       
>> The code already sleeps for 1 second after I applying the baud rate (via
>> tcsetattr(fd,TCSANOW,&newtio)). I am not sure to understand what you
>> mean...
>>     
>
> Hi,
>
> I mean try adding some:
>
> usleep(1000000);
>
> To your code to see if that changes anything.
>
> Also try reading one byte instead of 32.
>
> Last, try adding a printout to:
>
> src/sys/dev/usb/serial/uftdi.c
>
> uftdi_read_callback()
>
> and printout the actlen variable.
>
> --HPS
>
>   
ok, so I added the usleep statement right after the existing sleep 
statement. I also tried reading a single byte. It did not make any 
difference... I added a print statement to print the value of actlen 
right after it is set via
usbd_xfer_status(xfer, &actlen, NULL, NULL, NULL);

Here is the new output in /var/log/messages:
Sep 21 14:55:28 ldaemon kernel: ucom_open:554: tp = 0xffffff0139488800
Sep 21 14:55:28 ldaemon kernel: ucom_dtr:827: onoff = 1
Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
Sep 21 14:55:28 ldaemon kernel: ucom_rts:838: onoff = 1
Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
Sep 21 14:55:28 ldaemon kernel: ucom_break:816: onoff = 0
Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
Sep 21 14:55:28 ldaemon kernel: ucom_status_change:901:
Sep 21 14:55:28 ldaemon kernel: ucom_param:950: sc = 0xffffff013bcac458
Sep 21 14:55:28 ldaemon kernel: ucom_dtr:827: onoff = 1
Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
Sep 21 14:55:28 ldaemon kernel: ucom_rts:838: onoff = 1
Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
Sep 21 14:55:28 ldaemon kernel: ucom_cfg_open:520:
Sep 21 14:55:28 ldaemon kernel: actlen is 0
Sep 21 14:55:28 ldaemon kernel: actlen is 2
Sep 21 14:55:28 ldaemon kernel: actlen is 2
Sep 21 14:55:28 ldaemon kernel: ucom_cfg_status_change:887: DCD changed to 1
Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
Sep 21 14:55:28 ldaemon kernel: ucom_param:950: sc = 0xffffff013bcac458
Sep 21 14:55:28 ldaemon kernel: actlen is 2
Sep 21 14:55:28 ldaemon last message repeated 12 times
Sep 21 14:55:28 ldaemon kernel: ucom_get_data:1064: cnt=0
Sep 21 14:55:28 ldaemon kernel: actlen is 2
Sep 21 14:55:30 ldaemon last message repeated 111 times
Sep 21 14:55:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
Sep 21 14:55:30 ldaemon kernel: actlen is 2
Sep 21 14:55:31 ldaemon last message repeated 62 times
Sep 21 14:55:31 ldaemon kernel: ucom_outwakeup:1009: sc = 0xffffff013bcac458
Sep 21 14:55:31 ldaemon kernel: ucom_get_data:1064: cnt=2
Sep 21 14:55:31 ldaemon kernel: ucom_get_data:1064: cnt=0
Sep 21 14:55:31 ldaemon kernel: actlen is 2


From torfinn.ingolfsen at broadpark.no  Mon Sep 21 19:43:51 2009
From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen)
Date: Mon Sep 21 19:43:58 2009
Subject: PLease trim your quotes!
Message-ID: <20090921204347.8f26bd21.torfinn.ingolfsen@broadpark.no>

Everybody.
please, PLEASE trim your quotes to the bare minimum when replying to
any message.

Thank you.
-- 
Regards,
Torfinn Ingolfsen

From pldrouin at pldrouin.net  Mon Sep 21 19:48:51 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Mon Sep 21 19:48:58 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <20090921194342.GA95398@hoeg.nl>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211827.53014.hselasky@c2i.net>
	<20090921194342.GA95398@hoeg.nl>
Message-ID: <4AB7D8A3.3070809@pldrouin.net>

Hi,

In my case I cvsuped the sources on September 14th. I can cvsup them 
again and make buildworld with the latest sources if necessary.

Thank you
Pierre-Luc Drouin

Ed Schouten wrote:
> Hi,
>
> Sorry for being ignorant. I still have to catch up with the emails, but
> I just read this:
>
> 	after i upgraded one of the machines to then 8-CURRENT on Aug 19
> 	2009, i noticed the following problems:
>
> Keep in mind that MPSAFE TTY was imported on August 20.
>
> Will read the rest of the messages now.
>
>   

From pldrouin at pldrouin.net  Mon Sep 21 19:55:57 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Mon Sep 21 19:56:03 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <20090921194933.GB95398@hoeg.nl>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211827.53014.hselasky@c2i.net>
	<20090921194933.GB95398@hoeg.nl>
Message-ID: <4AB7DA4B.8050105@pldrouin.net>

Ed Schouten wrote:
> Hi Pierre-Luc, Hans,
>
> * Hans Petter Selasky <hselasky@c2i.net> wrote:
>   
>> You need to set raw mode for the TTY device I think. Maybe Ed can give you the 
>> function name you need to call to do that?
>>     
>
> Yes. You need cfmakeraw() to do that (or do everything yourself). See
> src/lib/libc/gen/termios.c to see what it does.
>
> So what I'm interested in, is the following:
>
> 	"even that device is answering requests slower and slower until
> 	it stalls completely within 1 hour"
>
> Could you run `pstat -t' to see what's going on when it stalls? This
> nifty tool just gives some random statistics on TTYs. Very useful to see
> what's going on. Where data is stuck, etc. etc.
>
>   
Here is what I get from pstat when I run my executable:

while ( 1 )
while? pstat -t ttyU0 | grep ttyU0
while? sleep 1
while? end
      LINE   INQ  CAN  LIN  LOW  OUTQ  USE  LOW   COL  SESS  PGID STATE
     ttyU0     0    0    0    0     0    0    0     4     0     0 ICl
     ttyU0     0    0    0    0     0    0    0     4     0     0 ICl
     ttyU0     0    0    0    0     0    0    0     4     0     0 ICl
     ttyU0     0    0    0    0     0    0    0     4     0     0 ICl
     ttyU0     0    0    0    0     0    0    0     4     0     0 ICl
     ttyU0     0    0    0    0     0    0    0     4     0     0 ICl
     ttyU0     0    0    0    0     0    0    0     4     0     0 ICl
     ttyU0     0    0    0    0     0    0    0     4     0     0 ICl
     ttyU0  1920    0    0  192  1984    0  199     4     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     4     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     4     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil

From ed at 80386.nl  Mon Sep 21 19:59:28 2009
From: ed at 80386.nl (Ed Schouten)
Date: Mon Sep 21 19:59:34 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909211827.53014.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211827.53014.hselasky@c2i.net>
Message-ID: <20090921194342.GA95398@hoeg.nl>

Hi,

Sorry for being ignorant. I still have to catch up with the emails, but
I just read this:

	after i upgraded one of the machines to then 8-CURRENT on Aug 19
	2009, i noticed the following problems:

Keep in mind that MPSAFE TTY was imported on August 20.

Will read the rest of the messages now.

-- 
 Ed Schouten <ed@80386.nl>
 WWW: http://80386.nl/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090921/a9ca624a/attachment.pgp
From ed at 80386.nl  Mon Sep 21 20:04:36 2009
From: ed at 80386.nl (Ed Schouten)
Date: Mon Sep 21 20:04:42 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB7DA4B.8050105@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211827.53014.hselasky@c2i.net>
	<20090921194933.GB95398@hoeg.nl> <4AB7DA4B.8050105@pldrouin.net>
Message-ID: <20090921195920.GE95398@hoeg.nl>

Hello Pierre-Luc,

* Pierre-Luc Drouin <pldrouin@pldrouin.net> wrote:
> Here is what I get from pstat when I run my executable:
> 
> while ( 1 )
> while? pstat -t ttyU0 | grep ttyU0
> while? sleep 1
> while? end
>      LINE   INQ  CAN  LIN  LOW  OUTQ  USE  LOW   COL  SESS  PGID STATE
>     ttyU0     0    0    0    0     0    0    0     4     0     0 ICl
<snip>
>     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil

That all makes sense. Just let me know what it looks like when things go
sour. If it still displays the above mentioned lines, then I suspect it
to be a more complex problem...

-- 
 Ed Schouten <ed@80386.nl>
 WWW: http://80386.nl/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090921/95a8f3d3/attachment.pgp
From ed at 80386.nl  Mon Sep 21 20:09:14 2009
From: ed at 80386.nl (Ed Schouten)
Date: Mon Sep 21 20:09:25 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909211827.53014.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211827.53014.hselasky@c2i.net>
Message-ID: <20090921194933.GB95398@hoeg.nl>

Hi Pierre-Luc, Hans,

* Hans Petter Selasky <hselasky@c2i.net> wrote:
> You need to set raw mode for the TTY device I think. Maybe Ed can give you the 
> function name you need to call to do that?

Yes. You need cfmakeraw() to do that (or do everything yourself). See
src/lib/libc/gen/termios.c to see what it does.

So what I'm interested in, is the following:

	"even that device is answering requests slower and slower until
	it stalls completely within 1 hour"

Could you run `pstat -t' to see what's going on when it stalls? This
nifty tool just gives some random statistics on TTYs. Very useful to see
what's going on. Where data is stuck, etc. etc.

-- 
 Ed Schouten <ed@80386.nl>
 WWW: http://80386.nl/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090921/3d6eefe9/attachment.pgp
From ed at 80386.nl  Mon Sep 21 20:09:14 2009
From: ed at 80386.nl (Ed Schouten)
Date: Mon Sep 21 20:09:25 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB7D8A3.3070809@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211827.53014.hselasky@c2i.net>
	<20090921194342.GA95398@hoeg.nl> <4AB7D8A3.3070809@pldrouin.net>
Message-ID: <20090921195032.GC95398@hoeg.nl>

* Pierre-Luc Drouin <pldrouin@pldrouin.net> wrote:
> In my case I cvsuped the sources on September 14th. I can cvsup them
> again and make buildworld with the latest sources if necessary.

Oh wait. Misread. It's already late. MPSAFE TTY got committed on August
19 2008, not 2009.

-- 
 Ed Schouten <ed@80386.nl>
 WWW: http://80386.nl/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090921/78b11b2f/attachment.pgp
From pldrouin at pldrouin.net  Mon Sep 21 20:10:03 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Mon Sep 21 20:10:09 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <20090921195920.GE95398@hoeg.nl>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909211827.53014.hselasky@c2i.net>
	<20090921194933.GB95398@hoeg.nl> <4AB7DA4B.8050105@pldrouin.net>
	<20090921195920.GE95398@hoeg.nl>
Message-ID: <4AB7DD9B.8070707@pldrouin.net>

Ed Schouten wrote:
> Hello Pierre-Luc,
>
> * Pierre-Luc Drouin <pldrouin@pldrouin.net> wrote:
>   
>> Here is what I get from pstat when I run my executable:
>>
>> while ( 1 )
>> while? pstat -t ttyU0 | grep ttyU0
>> while? sleep 1
>> while? end
>>      LINE   INQ  CAN  LIN  LOW  OUTQ  USE  LOW   COL  SESS  PGID STATE
>>     ttyU0     0    0    0    0     0    0    0     4     0     0 ICl
>>     
> <snip>
>   
>>     ttyU0  1920    0    0  192  1984    0  199     6     0     0 ICOil
>>     
>
> That all makes sense. Just let me know what it looks like when things go
> sour. If it still displays the above mentioned lines, then I suspect it
> to be a more complex problem...
>
>   
Well in my case (not to be confused with the starter of this thread), I 
simply cannot read any data. It hangs forever at the first read 
statement on FreeBSD in synchronous mode, or I get EINTR if I try 
reading in ASYNC mode after SIGIO is sent, independently of the number 
of bytes I try reading. All these tests run smoothly on Linux.

Pierre-Luc Drouin
From tlb at tlb.org  Mon Sep 21 22:38:48 2009
From: tlb at tlb.org (Trevor Blackwell)
Date: Mon Sep 21 22:38:55 2009
Subject: libusb20 api
Message-ID: <2C0D6269-1296-4D34-8029-828A0FE281CB@tlb.org>


This always fails:

       char devname[256];
       if (libusb20_dev_get_iface_desc(pdev, n, devname,  
sizeof(devname))) break;

while this works:

       char devname[128];
       if (libusb20_dev_get_iface_desc(pdev, n, devname,  
sizeof(devname))) break;

Because this function takes a uint8_t for length:

<libusb20_ugen20.c:851>:
static int
ugen20_dev_get_iface_desc(struct libusb20_device *pdev,
     uint8_t iface_index, char *buf, uint8_t len)

even though the kernel ioctl structure has a 16-bit length.

Hans, why not just use size_t for such arguments?

--
Trevor Blackwell		650 776 7870	tlb@tlb.org





From hselasky at c2i.net  Tue Sep 22 07:16:15 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep 22 07:16:22 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB7CCE0.2000703@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909212045.20657.hselasky@c2i.net>
	<4AB7CCE0.2000703@pldrouin.net>
Message-ID: <200909220916.46186.hselasky@c2i.net>

On Monday 21 September 2009 20:58:40 Pierre-Luc Drouin wrote:
> Hans Petter Selasky wrote:
> > On Monday 21 September 2009 20:28:58 Pierre-Luc Drouin wrote:
> >> Hans Petter Selasky wrote:
> >>> On Monday 21 September 2009 19:52:13 Pierre-Luc Drouin wrote:
> >>>> Hans Petter Selasky wrote:
> >>>>> On Monday 21 September 2009 19:29:10 Pierre-Luc Drouin wrote:
> >>>>>> Hans Petter Selasky wrote:
> >>>>>>> On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> I am also having troubles with the uftdi driver on 8.0-BETA4.
> >>>>>>>> I am trying to use a fan controller (mCubed bigNG) that uses a
> >>>>>>>> FT232BL chip and it does not seem to be responding on FreeBSD 8.0
> >>>>>>>> while the same code works perfectly on Linux (I have not tried the
> >>>>>>>> code on RELENG_7 yet but I could install it if necessary).
> >>>>>>>>
> >>>>>>>> Here is the very simple code I am using for testing:
> >>>>>>>> #include <termios.h>
> >>>>>>>> #include <fcntl.h>
> >>>>>>>> #include <string.h>
> >>>>>>>> #include <unistd.h>
> >>>>>>>> #include <stdio.h>
> >>>>>>>>
> >>>>>>>> int main();
> >>>>>>>>
> >>>>>>>> #define DEV "/dev/ttyU0"
> >>>>>>>>
> >>>>>>>> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
> >>>>>>>> #define TBAN_SER_SOURCE2        0x06 /* Alternative source
> >>>>>>>> (miniNG...) */
> >>>>>>>>
> >>>>>>>> #define TBAN_SER_REQUEST        0x36
> >>>>>>>>
> >>>>>>>> int main()
> >>>>>>>> {
> >>>>>>>>   int fd;
> >>>>>>>>   int result;
> >>>>>>>>   struct termios oldtio, newtio;
> >>>>>>>>   unsigned char buf[285];
> >>>>>>>>
> >>>>>>>>   printf("Opening device\n");
> >>>>>>>>   fd=open(DEV, O_RDWR | O_NOCTTY);
> >>>>>>>>
> >>>>>>>>   if(fd<0) {
> >>>>>>>>     perror(DEV);
> >>>>>>>>     return 1;
> >>>>>>>>   }
> >>>>>>>>
> >>>>>>>>   result=tcgetattr(fd,&oldtio);
> >>>>>>>>   if(result<0) {
> >>>>>>>>     perror("tcgetattr");
> >>>>>>>>     return 1;
> >>>>>>>>   }
> >>>>>>>>
> >>>>>>>>   memcpy(&newtio,&oldtio,sizeof(struct termios));
> >>>>>>>>   newtio.c_cflag = B19200
> >>>>>>>>
> >>>>>>>>     | CRTSCTS
> >>>>>>>>     | CS8
> >>>>>>>>     | CREAD;
> >>>>>>>>
> >>>>>>>>   newtio.c_iflag     = IGNPAR;
> >>>>>>>>   newtio.c_oflag     = 0;
> >>>>>>>>   newtio.c_lflag     = 0;
> >>>>>>>>   newtio.c_cc[VMIN]  = 1;
> >>>>>>>>   newtio.c_cc[VTIME] = 0;
> >>>>>>>>
> >>>>>>>>   result=tcflush(fd, TCIFLUSH);
> >>>>>>>>   if(result<0) {
> >>>>>>>>     perror("tcflush");
> >>>>>>>>     return 1;
> >>>>>>>>   }
> >>>>>>>>
> >>>>>>>>   result=tcsetattr(fd,TCSANOW,&newtio);
> >>>>>>>>   if(result<0) {
> >>>>>>>>     perror("tcsetattr");
> >>>>>>>>     return 1;
> >>>>>>>>   }
> >>>>>>>>
> >>>>>>>>   sleep(1);
> >>>>>>>>
> >>>>>>>>   printf("Performing initial query\n");
> >>>>>>>>   buf[0]=TBAN_SER_SOURCE1;
> >>>>>>>>   buf[1]=TBAN_SER_REQUEST;
> >>>>>>>>
> >>>>>>>>   printf("Requesting status\n");
> >>>>>>>>   result=write(fd,buf,2);
> >>>>>>>>   if(result<0) {
> >>>>>>>>     perror("write");
> >>>>>>>>     return 1;
> >>>>>>>>   }
> >>>>>>>>
> >>>>>>>>   sleep(1);
> >>>>>>>>
> >>>>>>>>   printf("Reading status\n");
> >>>>>>>>   result=read(fd,buf,32);
> >>>>>>>>   if(result<0) {
> >>>>>>>>     perror("read");
> >>>>>>>>     return 1;
> >>>>>>>>   }
> >>>>>>>>
> >>>>>>>>   result=tcsetattr(fd,TCSANOW,&oldtio);
> >>>>>>>>   if(result<0) {
> >>>>>>>>     perror("tcsetattr");
> >>>>>>>>     return 1;
> >>>>>>>>   }
> >>>>>>>>
> >>>>>>>>   result=close(fd);
> >>>>>>>>   if(result<0) {
> >>>>>>>>     perror("close");
> >>>>>>>>     return 1;
> >>>>>>>>   }
> >>>>>>>>   return 0;
> >>>>>>>> }
> >>>>>>>>
> >>>>>>>> It hangs while reading independently of the number of bits I am
> >>>>>>>> reading.
> >>>>>>>>
> >>>>>>>> Here is the output from dmesg when I load the uftdi module:
> >>>>>>>> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
> >>>>>>>> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
> >>>>>>>> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
> >>>>>>>> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root:
> >>>>>>>> Unknown USB device: vendor 0x051d product 0x0002 bus uhub0
> >>>>>>>>
> >>>>>>>> Here is the output in /var/log/messages when I enable the debug
> >>>>>>>> output for ucom and uftdi: Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>> ucom_open:554: tp = 0xffffff001f12b400 Sep 20 21:33:30 ldaemon
> >>>>>>>> kernel: ucom_dtr:827: onoff = 1 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>> ucom_line_state:799: on=0x01, off=0x00 Sep 20 21:33:30 ldaemon
> >>>>>>>> kernel: ucom_rts:838: onoff = 1
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
> >>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00,
> >>>>>>>> off=0x04 Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc =
> >>>>>>>> 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>> uftdi_pre_param:653:
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01,
> >>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
> >>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status
> >>>>>>>> change msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon
> >>>>>>>> kernel: ucom_status_change:901:
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
> >>>>>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>> ucom_cfg_status_change:887: DCD changed to 1 Sep 20 21:33:30
> >>>>>>>> ldaemon kernel:
> >>>>>>>> uftdi_cfg_param:672: Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>> ucom_ioctl:653: cmd = 0x402c7413 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>> ucom_ioctl:653: cmd = 0x80047410 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>> ucom_ioctl:653: cmd = 0x802c7414 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>> ucom_param:950: sc = 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon
> >>>>>>>> kernel:
> >>>>>>>> uftdi_pre_param:653:
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
> >>>>>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
> >>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>>>>>> Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >>>>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc =
> >>>>>>>> 0xffffff001f12ac58 Sep 20 21:33:32 ldaemon kernel:
> >>>>>>>> ucom_get_data:1064: cnt=2
> >>>>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>>>>>>
> >>>>>>>> I really need to get this working so I am ready to test things as
> >>>>>>>> much as I can...
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> You need to set raw mode for the TTY device I think. Maybe Ed can
> >>>>>>> give you the function name you need to call to do that?
> >>>>>>>
> >>>>>>> --HPS
> >>>>>>
> >>>>>> Do I need to do something like that?
> >>>>>> ioctl(fileno(stdin), TIOCGETP, &tty_org);
> >>>>>> tty = tty_org;
> >>>>>>
> >>>>>> /* set terminal to raw mode ... */
> >>>>>> tty.sg_flags |= CRMOD;
> >>>>>> tty.sg_flags &= ~ECHO;
> >>>>>> tty.sg_flags &= ~XTABS;
> >>>>>> tty.sg_flags |= RAW;
> >>>>>>
> >>>>>> Thanks!
> >>>>>> Pierre-Luc Drouin
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> You need to call this function:
> >>>>>
> >>>>>      void
> >>>>>      cfmakeraw(struct termios *t);
> >>>>>
> >>>>> --HPS
> >>>>
> >>>> Hi,
> >>>>
> >>>> it still does not work. I have added the line
> >>>> cfmakeraw(&newtio);
> >>>>
> >>>> just before the call to tcflush and I get the following output in
> >>>> /var/log/messages:
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_open:554: tp = 0xffffff001f12b400
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_break:816: onoff = 0
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_status_change:901:
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc =
> >>>> 0xffffff001f12ac58 Sep 21 13:38:46 ldaemon kernel:
> >>>> uftdi_pre_param:653:
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_open:520:
> >>>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_open:354:
> >>>> uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_status_change:887: DCD
> >>>> changed to 1 Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc =
> >>>> 0xffffff001f12ac58 Sep 21 13:38:46 ldaemon kernel:
> >>>> uftdi_pre_param:653:
> >>>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
> >>>> Sep 21 13:38:46 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>> Sep 21 13:38:47 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >>>> Sep 21 13:38:48 ldaemon kernel: ucom_outwakeup:1009: sc =
> >>>> 0xffffff001f12ac58 Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064:
> >>>> cnt=2
> >>>> Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>
> >>> Can you try adding a delay after setting the baud rate?
> >>>
> >>> --HPS
> >>
> >> The code already sleeps for 1 second after I applying the baud rate (via
> >> tcsetattr(fd,TCSANOW,&newtio)). I am not sure to understand what you
> >> mean...
> >
> > Hi,
> >
> > I mean try adding some:
> >
> > usleep(1000000);
> >
> > To your code to see if that changes anything.
> >
> > Also try reading one byte instead of 32.
> >
> > Last, try adding a printout to:
> >
> > src/sys/dev/usb/serial/uftdi.c
> >
> > uftdi_read_callback()
> >
> > and printout the actlen variable.
> >
> > --HPS
>
> ok, so I added the usleep statement right after the existing sleep
> statement. I also tried reading a single byte. It did not make any
> difference... I added a print statement to print the value of actlen
> right after it is set via
> usbd_xfer_status(xfer, &actlen, NULL, NULL, NULL);
>
> Here is the new output in /var/log/messages:
> Sep 21 14:55:28 ldaemon kernel: ucom_open:554: tp = 0xffffff0139488800
> Sep 21 14:55:28 ldaemon kernel: ucom_dtr:827: onoff = 1
> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> Sep 21 14:55:28 ldaemon kernel: ucom_rts:838: onoff = 1
> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> Sep 21 14:55:28 ldaemon kernel: ucom_break:816: onoff = 0
> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
> Sep 21 14:55:28 ldaemon kernel: ucom_status_change:901:
> Sep 21 14:55:28 ldaemon kernel: ucom_param:950: sc = 0xffffff013bcac458
> Sep 21 14:55:28 ldaemon kernel: ucom_dtr:827: onoff = 1
> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> Sep 21 14:55:28 ldaemon kernel: ucom_rts:838: onoff = 1
> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> Sep 21 14:55:28 ldaemon kernel: ucom_cfg_open:520:
> Sep 21 14:55:28 ldaemon kernel: actlen is 0
> Sep 21 14:55:28 ldaemon kernel: actlen is 2
> Sep 21 14:55:28 ldaemon kernel: actlen is 2
> Sep 21 14:55:28 ldaemon kernel: ucom_cfg_status_change:887: DCD changed to
> 1 Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
> Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
> Sep 21 14:55:28 ldaemon kernel: ucom_param:950: sc = 0xffffff013bcac458
> Sep 21 14:55:28 ldaemon kernel: actlen is 2
> Sep 21 14:55:28 ldaemon last message repeated 12 times
> Sep 21 14:55:28 ldaemon kernel: ucom_get_data:1064: cnt=0
> Sep 21 14:55:28 ldaemon kernel: actlen is 2
> Sep 21 14:55:30 ldaemon last message repeated 111 times
> Sep 21 14:55:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> Sep 21 14:55:30 ldaemon kernel: actlen is 2
> Sep 21 14:55:31 ldaemon last message repeated 62 times
> Sep 21 14:55:31 ldaemon kernel: ucom_outwakeup:1009: sc =
> 0xffffff013bcac458 Sep 21 14:55:31 ldaemon kernel: ucom_get_data:1064:
> cnt=2
> Sep 21 14:55:31 ldaemon kernel: ucom_get_data:1064: cnt=0
> Sep 21 14:55:31 ldaemon kernel: actlen is 2

If actlen is 2 then no modem data is transferred from the device.

--HPS
From pldrouin at pldrouin.net  Tue Sep 22 12:57:52 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Tue Sep 22 12:58:21 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909220916.46186.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909212045.20657.hselasky@c2i.net>
	<4AB7CCE0.2000703@pldrouin.net>
	<200909220916.46186.hselasky@c2i.net>
Message-ID: <4AB8C9CA.407@pldrouin.net>

Hans Petter Selasky wrote:
> On Monday 21 September 2009 20:58:40 Pierre-Luc Drouin wrote:
>   
>> Hans Petter Selasky wrote:
>>     
>>> On Monday 21 September 2009 20:28:58 Pierre-Luc Drouin wrote:
>>>       
>>>> Hans Petter Selasky wrote:
>>>>         
>>>>> On Monday 21 September 2009 19:52:13 Pierre-Luc Drouin wrote:
>>>>>           
>>>>>> Hans Petter Selasky wrote:
>>>>>>             
>>>>>>> On Monday 21 September 2009 19:29:10 Pierre-Luc Drouin wrote:
>>>>>>>               
>>>>>>>> Hans Petter Selasky wrote:
>>>>>>>>                 
>>>>>>>>> On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
>>>>>>>>>                   
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I am also having troubles with the uftdi driver on 8.0-BETA4.
>>>>>>>>>> I am trying to use a fan controller (mCubed bigNG) that uses a
>>>>>>>>>> FT232BL chip and it does not seem to be responding on FreeBSD 8.0
>>>>>>>>>> while the same code works perfectly on Linux (I have not tried the
>>>>>>>>>> code on RELENG_7 yet but I could install it if necessary).
>>>>>>>>>>
>>>>>>>>>> Here is the very simple code I am using for testing:
>>>>>>>>>> #include <termios.h>
>>>>>>>>>> #include <fcntl.h>
>>>>>>>>>> #include <string.h>
>>>>>>>>>> #include <unistd.h>
>>>>>>>>>> #include <stdio.h>
>>>>>>>>>>
>>>>>>>>>> int main();
>>>>>>>>>>
>>>>>>>>>> #define DEV "/dev/ttyU0"
>>>>>>>>>>
>>>>>>>>>> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
>>>>>>>>>> #define TBAN_SER_SOURCE2        0x06 /* Alternative source
>>>>>>>>>> (miniNG...) */
>>>>>>>>>>
>>>>>>>>>> #define TBAN_SER_REQUEST        0x36
>>>>>>>>>>
>>>>>>>>>> int main()
>>>>>>>>>> {
>>>>>>>>>>   int fd;
>>>>>>>>>>   int result;
>>>>>>>>>>   struct termios oldtio, newtio;
>>>>>>>>>>   unsigned char buf[285];
>>>>>>>>>>
>>>>>>>>>>   printf("Opening device\n");
>>>>>>>>>>   fd=open(DEV, O_RDWR | O_NOCTTY);
>>>>>>>>>>
>>>>>>>>>>   if(fd<0) {
>>>>>>>>>>     perror(DEV);
>>>>>>>>>>     return 1;
>>>>>>>>>>   }
>>>>>>>>>>
>>>>>>>>>>   result=tcgetattr(fd,&oldtio);
>>>>>>>>>>   if(result<0) {
>>>>>>>>>>     perror("tcgetattr");
>>>>>>>>>>     return 1;
>>>>>>>>>>   }
>>>>>>>>>>
>>>>>>>>>>   memcpy(&newtio,&oldtio,sizeof(struct termios));
>>>>>>>>>>   newtio.c_cflag = B19200
>>>>>>>>>>
>>>>>>>>>>     | CRTSCTS
>>>>>>>>>>     | CS8
>>>>>>>>>>     | CREAD;
>>>>>>>>>>
>>>>>>>>>>   newtio.c_iflag     = IGNPAR;
>>>>>>>>>>   newtio.c_oflag     = 0;
>>>>>>>>>>   newtio.c_lflag     = 0;
>>>>>>>>>>   newtio.c_cc[VMIN]  = 1;
>>>>>>>>>>   newtio.c_cc[VTIME] = 0;
>>>>>>>>>>
>>>>>>>>>>   result=tcflush(fd, TCIFLUSH);
>>>>>>>>>>   if(result<0) {
>>>>>>>>>>     perror("tcflush");
>>>>>>>>>>     return 1;
>>>>>>>>>>   }
>>>>>>>>>>
>>>>>>>>>>   result=tcsetattr(fd,TCSANOW,&newtio);
>>>>>>>>>>   if(result<0) {
>>>>>>>>>>     perror("tcsetattr");
>>>>>>>>>>     return 1;
>>>>>>>>>>   }
>>>>>>>>>>
>>>>>>>>>>   sleep(1);
>>>>>>>>>>
>>>>>>>>>>   printf("Performing initial query\n");
>>>>>>>>>>   buf[0]=TBAN_SER_SOURCE1;
>>>>>>>>>>   buf[1]=TBAN_SER_REQUEST;
>>>>>>>>>>
>>>>>>>>>>   printf("Requesting status\n");
>>>>>>>>>>   result=write(fd,buf,2);
>>>>>>>>>>   if(result<0) {
>>>>>>>>>>     perror("write");
>>>>>>>>>>     return 1;
>>>>>>>>>>   }
>>>>>>>>>>
>>>>>>>>>>   sleep(1);
>>>>>>>>>>
>>>>>>>>>>   printf("Reading status\n");
>>>>>>>>>>   result=read(fd,buf,32);
>>>>>>>>>>   if(result<0) {
>>>>>>>>>>     perror("read");
>>>>>>>>>>     return 1;
>>>>>>>>>>   }
>>>>>>>>>>
>>>>>>>>>>   result=tcsetattr(fd,TCSANOW,&oldtio);
>>>>>>>>>>   if(result<0) {
>>>>>>>>>>     perror("tcsetattr");
>>>>>>>>>>     return 1;
>>>>>>>>>>   }
>>>>>>>>>>
>>>>>>>>>>   result=close(fd);
>>>>>>>>>>   if(result<0) {
>>>>>>>>>>     perror("close");
>>>>>>>>>>     return 1;
>>>>>>>>>>   }
>>>>>>>>>>   return 0;
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>> It hangs while reading independently of the number of bits I am
>>>>>>>>>> reading.
>>>>>>>>>>
>>>>>>>>>> Here is the output from dmesg when I load the uftdi module:
>>>>>>>>>> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
>>>>>>>>>> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
>>>>>>>>>> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
>>>>>>>>>> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root:
>>>>>>>>>> Unknown USB device: vendor 0x051d product 0x0002 bus uhub0
>>>>>>>>>>
>>>>>>>>>> Here is the output in /var/log/messages when I enable the debug
>>>>>>>>>> output for ucom and uftdi: Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>> ucom_open:554: tp = 0xffffff001f12b400 Sep 20 21:33:30 ldaemon
>>>>>>>>>> kernel: ucom_dtr:827: onoff = 1 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>> ucom_line_state:799: on=0x01, off=0x00 Sep 20 21:33:30 ldaemon
>>>>>>>>>> kernel: ucom_rts:838: onoff = 1
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
>>>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff = 0
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00,
>>>>>>>>>> off=0x04 Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc =
>>>>>>>>>> 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>> uftdi_pre_param:653:
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01,
>>>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
>>>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status
>>>>>>>>>> change msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon
>>>>>>>>>> kernel: ucom_status_change:901:
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
>>>>>>>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>> ucom_cfg_status_change:887: DCD changed to 1 Sep 20 21:33:30
>>>>>>>>>> ldaemon kernel:
>>>>>>>>>> uftdi_cfg_param:672: Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>> ucom_ioctl:653: cmd = 0x402c7413 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>> ucom_ioctl:653: cmd = 0x80047410 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>> ucom_ioctl:653: cmd = 0x802c7414 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>> ucom_param:950: sc = 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon
>>>>>>>>>> kernel:
>>>>>>>>>> uftdi_pre_param:653:
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705: msr=0xf0
>>>>>>>>>> lsr=0x60 Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_param:672:
>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>>>>>> Sep 20 21:33:31 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>>>>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_outwakeup:1009: sc =
>>>>>>>>>> 0xffffff001f12ac58 Sep 20 21:33:32 ldaemon kernel:
>>>>>>>>>> ucom_get_data:1064: cnt=2
>>>>>>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>>>>>>
>>>>>>>>>> I really need to get this working so I am ready to test things as
>>>>>>>>>> much as I can...
>>>>>>>>>>                     
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> You need to set raw mode for the TTY device I think. Maybe Ed can
>>>>>>>>> give you the function name you need to call to do that?
>>>>>>>>>
>>>>>>>>> --HPS
>>>>>>>>>                   
>>>>>>>> Do I need to do something like that?
>>>>>>>> ioctl(fileno(stdin), TIOCGETP, &tty_org);
>>>>>>>> tty = tty_org;
>>>>>>>>
>>>>>>>> /* set terminal to raw mode ... */
>>>>>>>> tty.sg_flags |= CRMOD;
>>>>>>>> tty.sg_flags &= ~ECHO;
>>>>>>>> tty.sg_flags &= ~XTABS;
>>>>>>>> tty.sg_flags |= RAW;
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>> Pierre-Luc Drouin
>>>>>>>>                 
>>>>>>> Hi,
>>>>>>>
>>>>>>> You need to call this function:
>>>>>>>
>>>>>>>      void
>>>>>>>      cfmakeraw(struct termios *t);
>>>>>>>
>>>>>>> --HPS
>>>>>>>               
>>>>>> Hi,
>>>>>>
>>>>>> it still does not work. I have added the line
>>>>>> cfmakeraw(&newtio);
>>>>>>
>>>>>> just before the call to tcflush and I get the following output in
>>>>>> /var/log/messages:
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_open:554: tp = 0xffffff001f12b400
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_break:816: onoff = 0
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_status_change:901:
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc =
>>>>>> 0xffffff001f12ac58 Sep 21 13:38:46 ldaemon kernel:
>>>>>> uftdi_pre_param:653:
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_open:520:
>>>>>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_open:354:
>>>>>> uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_status_change:887: DCD
>>>>>> changed to 1 Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc =
>>>>>> 0xffffff001f12ac58 Sep 21 13:38:46 ldaemon kernel:
>>>>>> uftdi_pre_param:653:
>>>>>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>> Sep 21 13:38:47 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>>>> Sep 21 13:38:48 ldaemon kernel: ucom_outwakeup:1009: sc =
>>>>>> 0xffffff001f12ac58 Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064:
>>>>>> cnt=2
>>>>>> Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>>             
>>>>> Can you try adding a delay after setting the baud rate?
>>>>>
>>>>> --HPS
>>>>>           
>>>> The code already sleeps for 1 second after I applying the baud rate (via
>>>> tcsetattr(fd,TCSANOW,&newtio)). I am not sure to understand what you
>>>> mean...
>>>>         
>>> Hi,
>>>
>>> I mean try adding some:
>>>
>>> usleep(1000000);
>>>
>>> To your code to see if that changes anything.
>>>
>>> Also try reading one byte instead of 32.
>>>
>>> Last, try adding a printout to:
>>>
>>> src/sys/dev/usb/serial/uftdi.c
>>>
>>> uftdi_read_callback()
>>>
>>> and printout the actlen variable.
>>>
>>> --HPS
>>>       
>> ok, so I added the usleep statement right after the existing sleep
>> statement. I also tried reading a single byte. It did not make any
>> difference... I added a print statement to print the value of actlen
>> right after it is set via
>> usbd_xfer_status(xfer, &actlen, NULL, NULL, NULL);
>>
>> Here is the new output in /var/log/messages:
>> Sep 21 14:55:28 ldaemon kernel: ucom_open:554: tp = 0xffffff0139488800
>> Sep 21 14:55:28 ldaemon kernel: ucom_dtr:827: onoff = 1
>> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>> Sep 21 14:55:28 ldaemon kernel: ucom_rts:838: onoff = 1
>> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>> Sep 21 14:55:28 ldaemon kernel: ucom_break:816: onoff = 0
>> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
>> Sep 21 14:55:28 ldaemon kernel: ucom_status_change:901:
>> Sep 21 14:55:28 ldaemon kernel: ucom_param:950: sc = 0xffffff013bcac458
>> Sep 21 14:55:28 ldaemon kernel: ucom_dtr:827: onoff = 1
>> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>> Sep 21 14:55:28 ldaemon kernel: ucom_rts:838: onoff = 1
>> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>> Sep 21 14:55:28 ldaemon kernel: ucom_cfg_open:520:
>> Sep 21 14:55:28 ldaemon kernel: actlen is 0
>> Sep 21 14:55:28 ldaemon kernel: actlen is 2
>> Sep 21 14:55:28 ldaemon kernel: actlen is 2
>> Sep 21 14:55:28 ldaemon kernel: ucom_cfg_status_change:887: DCD changed to
>> 1 Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
>> Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>> Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
>> Sep 21 14:55:28 ldaemon kernel: ucom_param:950: sc = 0xffffff013bcac458
>> Sep 21 14:55:28 ldaemon kernel: actlen is 2
>> Sep 21 14:55:28 ldaemon last message repeated 12 times
>> Sep 21 14:55:28 ldaemon kernel: ucom_get_data:1064: cnt=0
>> Sep 21 14:55:28 ldaemon kernel: actlen is 2
>> Sep 21 14:55:30 ldaemon last message repeated 111 times
>> Sep 21 14:55:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>> Sep 21 14:55:30 ldaemon kernel: actlen is 2
>> Sep 21 14:55:31 ldaemon last message repeated 62 times
>> Sep 21 14:55:31 ldaemon kernel: ucom_outwakeup:1009: sc =
>> 0xffffff013bcac458 Sep 21 14:55:31 ldaemon kernel: ucom_get_data:1064:
>> cnt=2
>> Sep 21 14:55:31 ldaemon kernel: ucom_get_data:1064: cnt=0
>> Sep 21 14:55:31 ldaemon kernel: actlen is 2
>>     
>
> If actlen is 2 then no modem data is transferred from the device.
>
> --HPS
>   
Hmm, so does it indicate a bug in uftdi? In asynchronous mode, SIGIO is 
generated but when try reading I get error EINTR...

Thanks!
From hselasky at c2i.net  Tue Sep 22 14:38:14 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep 22 14:38:20 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB8C9CA.407@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909220916.46186.hselasky@c2i.net> <4AB8C9CA.407@pldrouin.net>
Message-ID: <200909221638.47642.hselasky@c2i.net>

On Tuesday 22 September 2009 14:57:46 Pierre-Luc Drouin wrote:
> Hans Petter Selasky wrote:
> > On Monday 21 September 2009 20:58:40 Pierre-Luc Drouin wrote:
> >> Hans Petter Selasky wrote:
> >>> On Monday 21 September 2009 20:28:58 Pierre-Luc Drouin wrote:
> >>>> Hans Petter Selasky wrote:
> >>>>> On Monday 21 September 2009 19:52:13 Pierre-Luc Drouin wrote:
> >>>>>> Hans Petter Selasky wrote:
> >>>>>>> On Monday 21 September 2009 19:29:10 Pierre-Luc Drouin wrote:
> >>>>>>>> Hans Petter Selasky wrote:
> >>>>>>>>> On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
> >>>>>>>>>> Hi,
> >>>>>>>>>>
> >>>>>>>>>> I am also having troubles with the uftdi driver on 8.0-BETA4.
> >>>>>>>>>> I am trying to use a fan controller (mCubed bigNG) that uses a
> >>>>>>>>>> FT232BL chip and it does not seem to be responding on FreeBSD
> >>>>>>>>>> 8.0 while the same code works perfectly on Linux (I have not
> >>>>>>>>>> tried the code on RELENG_7 yet but I could install it if
> >>>>>>>>>> necessary).
> >>>>>>>>>>
> >>>>>>>>>> Here is the very simple code I am using for testing:
> >>>>>>>>>> #include <termios.h>
> >>>>>>>>>> #include <fcntl.h>
> >>>>>>>>>> #include <string.h>
> >>>>>>>>>> #include <unistd.h>
> >>>>>>>>>> #include <stdio.h>
> >>>>>>>>>>
> >>>>>>>>>> int main();
> >>>>>>>>>>
> >>>>>>>>>> #define DEV "/dev/ttyU0"
> >>>>>>>>>>
> >>>>>>>>>> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
> >>>>>>>>>> #define TBAN_SER_SOURCE2        0x06 /* Alternative source
> >>>>>>>>>> (miniNG...) */
> >>>>>>>>>>
> >>>>>>>>>> #define TBAN_SER_REQUEST        0x36
> >>>>>>>>>>
> >>>>>>>>>> int main()
> >>>>>>>>>> {
> >>>>>>>>>>   int fd;
> >>>>>>>>>>   int result;
> >>>>>>>>>>   struct termios oldtio, newtio;
> >>>>>>>>>>   unsigned char buf[285];
> >>>>>>>>>>
> >>>>>>>>>>   printf("Opening device\n");
> >>>>>>>>>>   fd=open(DEV, O_RDWR | O_NOCTTY);
> >>>>>>>>>>
> >>>>>>>>>>   if(fd<0) {
> >>>>>>>>>>     perror(DEV);
> >>>>>>>>>>     return 1;
> >>>>>>>>>>   }
> >>>>>>>>>>
> >>>>>>>>>>   result=tcgetattr(fd,&oldtio);
> >>>>>>>>>>   if(result<0) {
> >>>>>>>>>>     perror("tcgetattr");
> >>>>>>>>>>     return 1;
> >>>>>>>>>>   }
> >>>>>>>>>>
> >>>>>>>>>>   memcpy(&newtio,&oldtio,sizeof(struct termios));
> >>>>>>>>>>   newtio.c_cflag = B19200
> >>>>>>>>>>
> >>>>>>>>>>     | CRTSCTS
> >>>>>>>>>>     | CS8
> >>>>>>>>>>     | CREAD;
> >>>>>>>>>>
> >>>>>>>>>>   newtio.c_iflag     = IGNPAR;
> >>>>>>>>>>   newtio.c_oflag     = 0;
> >>>>>>>>>>   newtio.c_lflag     = 0;
> >>>>>>>>>>   newtio.c_cc[VMIN]  = 1;
> >>>>>>>>>>   newtio.c_cc[VTIME] = 0;
> >>>>>>>>>>
> >>>>>>>>>>   result=tcflush(fd, TCIFLUSH);
> >>>>>>>>>>   if(result<0) {
> >>>>>>>>>>     perror("tcflush");
> >>>>>>>>>>     return 1;
> >>>>>>>>>>   }
> >>>>>>>>>>
> >>>>>>>>>>   result=tcsetattr(fd,TCSANOW,&newtio);
> >>>>>>>>>>   if(result<0) {
> >>>>>>>>>>     perror("tcsetattr");
> >>>>>>>>>>     return 1;
> >>>>>>>>>>   }
> >>>>>>>>>>
> >>>>>>>>>>   sleep(1);
> >>>>>>>>>>
> >>>>>>>>>>   printf("Performing initial query\n");
> >>>>>>>>>>   buf[0]=TBAN_SER_SOURCE1;
> >>>>>>>>>>   buf[1]=TBAN_SER_REQUEST;
> >>>>>>>>>>
> >>>>>>>>>>   printf("Requesting status\n");
> >>>>>>>>>>   result=write(fd,buf,2);
> >>>>>>>>>>   if(result<0) {
> >>>>>>>>>>     perror("write");
> >>>>>>>>>>     return 1;
> >>>>>>>>>>   }
> >>>>>>>>>>
> >>>>>>>>>>   sleep(1);
> >>>>>>>>>>
> >>>>>>>>>>   printf("Reading status\n");
> >>>>>>>>>>   result=read(fd,buf,32);
> >>>>>>>>>>   if(result<0) {
> >>>>>>>>>>     perror("read");
> >>>>>>>>>>     return 1;
> >>>>>>>>>>   }
> >>>>>>>>>>
> >>>>>>>>>>   result=tcsetattr(fd,TCSANOW,&oldtio);
> >>>>>>>>>>   if(result<0) {
> >>>>>>>>>>     perror("tcsetattr");
> >>>>>>>>>>     return 1;
> >>>>>>>>>>   }
> >>>>>>>>>>
> >>>>>>>>>>   result=close(fd);
> >>>>>>>>>>   if(result<0) {
> >>>>>>>>>>     perror("close");
> >>>>>>>>>>     return 1;
> >>>>>>>>>>   }
> >>>>>>>>>>   return 0;
> >>>>>>>>>> }
> >>>>>>>>>>
> >>>>>>>>>> It hangs while reading independently of the number of bits I am
> >>>>>>>>>> reading.
> >>>>>>>>>>
> >>>>>>>>>> Here is the output from dmesg when I load the uftdi module:
> >>>>>>>>>> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
> >>>>>>>>>> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
> >>>>>>>>>> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
> >>>>>>>>>> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root:
> >>>>>>>>>> Unknown USB device: vendor 0x051d product 0x0002 bus uhub0
> >>>>>>>>>>
> >>>>>>>>>> Here is the output in /var/log/messages when I enable the debug
> >>>>>>>>>> output for ucom and uftdi: Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>>>> ucom_open:554: tp = 0xffffff001f12b400 Sep 20 21:33:30 ldaemon
> >>>>>>>>>> kernel: ucom_dtr:827: onoff = 1 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>>>> ucom_line_state:799: on=0x01, off=0x00 Sep 20 21:33:30 ldaemon
> >>>>>>>>>> kernel: ucom_rts:838: onoff = 1
> >>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
> >>>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff =
> >>>>>>>>>> 0 Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00,
> >>>>>>>>>> off=0x04 Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
> >>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc =
> >>>>>>>>>> 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>>>> uftdi_pre_param:653:
> >>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
> >>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01,
> >>>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
> >>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
> >>>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
> >>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
> >>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status
> >>>>>>>>>> change msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon
> >>>>>>>>>> kernel: ucom_status_change:901:
> >>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705:
> >>>>>>>>>> msr=0xf0 lsr=0x60 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>>>> ucom_cfg_status_change:887: DCD changed to 1 Sep 20 21:33:30
> >>>>>>>>>> ldaemon kernel:
> >>>>>>>>>> uftdi_cfg_param:672: Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>>>> ucom_ioctl:653: cmd = 0x402c7413 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>>>> ucom_ioctl:653: cmd = 0x80047410 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>>>> ucom_ioctl:653: cmd = 0x802c7414 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>>>> ucom_param:950: sc = 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon
> >>>>>>>>>> kernel:
> >>>>>>>>>> uftdi_pre_param:653:
> >>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705:
> >>>>>>>>>> msr=0xf0 lsr=0x60 Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>>>> uftdi_cfg_param:672: Sep 20 21:33:30 ldaemon kernel:
> >>>>>>>>>> ucom_get_data:1064: cnt=0 Sep 20 21:33:31 ldaemon kernel:
> >>>>>>>>>> ucom_ioctl:653: cmd = 0x80047410 Sep 20 21:33:32 ldaemon kernel:
> >>>>>>>>>> ucom_outwakeup:1009: sc = 0xffffff001f12ac58 Sep 20 21:33:32
> >>>>>>>>>> ldaemon kernel:
> >>>>>>>>>> ucom_get_data:1064: cnt=2
> >>>>>>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>>>>>>>>
> >>>>>>>>>> I really need to get this working so I am ready to test things
> >>>>>>>>>> as much as I can...
> >>>>>>>>>
> >>>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>> You need to set raw mode for the TTY device I think. Maybe Ed can
> >>>>>>>>> give you the function name you need to call to do that?
> >>>>>>>>>
> >>>>>>>>> --HPS
> >>>>>>>>
> >>>>>>>> Do I need to do something like that?
> >>>>>>>> ioctl(fileno(stdin), TIOCGETP, &tty_org);
> >>>>>>>> tty = tty_org;
> >>>>>>>>
> >>>>>>>> /* set terminal to raw mode ... */
> >>>>>>>> tty.sg_flags |= CRMOD;
> >>>>>>>> tty.sg_flags &= ~ECHO;
> >>>>>>>> tty.sg_flags &= ~XTABS;
> >>>>>>>> tty.sg_flags |= RAW;
> >>>>>>>>
> >>>>>>>> Thanks!
> >>>>>>>> Pierre-Luc Drouin
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> You need to call this function:
> >>>>>>>
> >>>>>>>      void
> >>>>>>>      cfmakeraw(struct termios *t);
> >>>>>>>
> >>>>>>> --HPS
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> it still does not work. I have added the line
> >>>>>> cfmakeraw(&newtio);
> >>>>>>
> >>>>>> just before the call to tcflush and I get the following output in
> >>>>>> /var/log/messages:
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_open:554: tp =
> >>>>>> 0xffffff001f12b400 Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827:
> >>>>>> onoff = 1
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01,
> >>>>>> off=0x00 Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02,
> >>>>>> off=0x00 Sep 21 13:38:46 ldaemon kernel: ucom_break:816: onoff = 0
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x00,
> >>>>>> off=0x04 Sep 21 13:38:46 ldaemon kernel: ucom_status_change:901:
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc =
> >>>>>> 0xffffff001f12ac58 Sep 21 13:38:46 ldaemon kernel:
> >>>>>> uftdi_pre_param:653:
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01,
> >>>>>> off=0x00 Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02,
> >>>>>> off=0x00 Sep 21 13:38:46 ldaemon kernel: ucom_cfg_open:520:
> >>>>>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_open:354:
> >>>>>> uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_status_change:887: DCD
> >>>>>> changed to 1 Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc =
> >>>>>> 0xffffff001f12ac58 Sep 21 13:38:46 ldaemon kernel:
> >>>>>> uftdi_pre_param:653:
> >>>>>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
> >>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>>>> Sep 21 13:38:47 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >>>>>> Sep 21 13:38:48 ldaemon kernel: ucom_outwakeup:1009: sc =
> >>>>>> 0xffffff001f12ac58 Sep 21 13:38:48 ldaemon kernel:
> >>>>>> ucom_get_data:1064: cnt=2
> >>>>>> Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064: cnt=0
> >>>>>
> >>>>> Can you try adding a delay after setting the baud rate?
> >>>>>
> >>>>> --HPS
> >>>>
> >>>> The code already sleeps for 1 second after I applying the baud rate
> >>>> (via tcsetattr(fd,TCSANOW,&newtio)). I am not sure to understand what
> >>>> you mean...
> >>>
> >>> Hi,
> >>>
> >>> I mean try adding some:
> >>>
> >>> usleep(1000000);
> >>>
> >>> To your code to see if that changes anything.
> >>>
> >>> Also try reading one byte instead of 32.
> >>>
> >>> Last, try adding a printout to:
> >>>
> >>> src/sys/dev/usb/serial/uftdi.c
> >>>
> >>> uftdi_read_callback()
> >>>
> >>> and printout the actlen variable.
> >>>
> >>> --HPS
> >>
> >> ok, so I added the usleep statement right after the existing sleep
> >> statement. I also tried reading a single byte. It did not make any
> >> difference... I added a print statement to print the value of actlen
> >> right after it is set via
> >> usbd_xfer_status(xfer, &actlen, NULL, NULL, NULL);
> >>
> >> Here is the new output in /var/log/messages:
> >> Sep 21 14:55:28 ldaemon kernel: ucom_open:554: tp = 0xffffff0139488800
> >> Sep 21 14:55:28 ldaemon kernel: ucom_dtr:827: onoff = 1
> >> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> >> Sep 21 14:55:28 ldaemon kernel: ucom_rts:838: onoff = 1
> >> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> >> Sep 21 14:55:28 ldaemon kernel: ucom_break:816: onoff = 0
> >> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
> >> Sep 21 14:55:28 ldaemon kernel: ucom_status_change:901:
> >> Sep 21 14:55:28 ldaemon kernel: ucom_param:950: sc = 0xffffff013bcac458
> >> Sep 21 14:55:28 ldaemon kernel: ucom_dtr:827: onoff = 1
> >> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
> >> Sep 21 14:55:28 ldaemon kernel: ucom_rts:838: onoff = 1
> >> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
> >> Sep 21 14:55:28 ldaemon kernel: ucom_cfg_open:520:
> >> Sep 21 14:55:28 ldaemon kernel: actlen is 0
> >> Sep 21 14:55:28 ldaemon kernel: actlen is 2
> >> Sep 21 14:55:28 ldaemon kernel: actlen is 2
> >> Sep 21 14:55:28 ldaemon kernel: ucom_cfg_status_change:887: DCD changed
> >> to 1 Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
> >> Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410 Sep 21
> >> 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414 Sep 21
> >> 14:55:28 ldaemon kernel: ucom_param:950: sc = 0xffffff013bcac458 Sep 21
> >> 14:55:28 ldaemon kernel: actlen is 2
> >> Sep 21 14:55:28 ldaemon last message repeated 12 times
> >> Sep 21 14:55:28 ldaemon kernel: ucom_get_data:1064: cnt=0
> >> Sep 21 14:55:28 ldaemon kernel: actlen is 2
> >> Sep 21 14:55:30 ldaemon last message repeated 111 times
> >> Sep 21 14:55:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
> >> Sep 21 14:55:30 ldaemon kernel: actlen is 2
> >> Sep 21 14:55:31 ldaemon last message repeated 62 times
> >> Sep 21 14:55:31 ldaemon kernel: ucom_outwakeup:1009: sc =
> >> 0xffffff013bcac458 Sep 21 14:55:31 ldaemon kernel: ucom_get_data:1064:
> >> cnt=2
> >> Sep 21 14:55:31 ldaemon kernel: ucom_get_data:1064: cnt=0
> >> Sep 21 14:55:31 ldaemon kernel: actlen is 2
> >
> > If actlen is 2 then no modem data is transferred from the device.
> >
> > --HPS
>
> Hmm, so does it indicate a bug in uftdi? In asynchronous mode, SIGIO is
> generated but when try reading I get error EINTR...
>
> Thanks!

It indicates that your device is not sending any data.

--HPS

From pldrouin at pldrouin.net  Tue Sep 22 15:21:30 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Tue Sep 22 15:21:37 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909221638.47642.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909220916.46186.hselasky@c2i.net> <4AB8C9CA.407@pldrouin.net>
	<200909221638.47642.hselasky@c2i.net>
Message-ID: <4AB8EB78.2020809@pldrouin.net>

Hans Petter Selasky wrote:
> On Tuesday 22 September 2009 14:57:46 Pierre-Luc Drouin wrote:
>   
>> Hans Petter Selasky wrote:
>>     
>>> On Monday 21 September 2009 20:58:40 Pierre-Luc Drouin wrote:
>>>       
>>>> Hans Petter Selasky wrote:
>>>>         
>>>>> On Monday 21 September 2009 20:28:58 Pierre-Luc Drouin wrote:
>>>>>           
>>>>>> Hans Petter Selasky wrote:
>>>>>>             
>>>>>>> On Monday 21 September 2009 19:52:13 Pierre-Luc Drouin wrote:
>>>>>>>               
>>>>>>>> Hans Petter Selasky wrote:
>>>>>>>>                 
>>>>>>>>> On Monday 21 September 2009 19:29:10 Pierre-Luc Drouin wrote:
>>>>>>>>>                   
>>>>>>>>>> Hans Petter Selasky wrote:
>>>>>>>>>>                     
>>>>>>>>>>> On Monday 21 September 2009 03:44:25 Pierre-Luc Drouin wrote:
>>>>>>>>>>>                       
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I am also having troubles with the uftdi driver on 8.0-BETA4.
>>>>>>>>>>>> I am trying to use a fan controller (mCubed bigNG) that uses a
>>>>>>>>>>>> FT232BL chip and it does not seem to be responding on FreeBSD
>>>>>>>>>>>> 8.0 while the same code works perfectly on Linux (I have not
>>>>>>>>>>>> tried the code on RELENG_7 yet but I could install it if
>>>>>>>>>>>> necessary).
>>>>>>>>>>>>
>>>>>>>>>>>> Here is the very simple code I am using for testing:
>>>>>>>>>>>> #include <termios.h>
>>>>>>>>>>>> #include <fcntl.h>
>>>>>>>>>>>> #include <string.h>
>>>>>>>>>>>> #include <unistd.h>
>>>>>>>>>>>> #include <stdio.h>
>>>>>>>>>>>>
>>>>>>>>>>>> int main();
>>>>>>>>>>>>
>>>>>>>>>>>> #define DEV "/dev/ttyU0"
>>>>>>>>>>>>
>>>>>>>>>>>> #define TBAN_SER_SOURCE1        0x05 /* Primary source */
>>>>>>>>>>>> #define TBAN_SER_SOURCE2        0x06 /* Alternative source
>>>>>>>>>>>> (miniNG...) */
>>>>>>>>>>>>
>>>>>>>>>>>> #define TBAN_SER_REQUEST        0x36
>>>>>>>>>>>>
>>>>>>>>>>>> int main()
>>>>>>>>>>>> {
>>>>>>>>>>>>   int fd;
>>>>>>>>>>>>   int result;
>>>>>>>>>>>>   struct termios oldtio, newtio;
>>>>>>>>>>>>   unsigned char buf[285];
>>>>>>>>>>>>
>>>>>>>>>>>>   printf("Opening device\n");
>>>>>>>>>>>>   fd=open(DEV, O_RDWR | O_NOCTTY);
>>>>>>>>>>>>
>>>>>>>>>>>>   if(fd<0) {
>>>>>>>>>>>>     perror(DEV);
>>>>>>>>>>>>     return 1;
>>>>>>>>>>>>   }
>>>>>>>>>>>>
>>>>>>>>>>>>   result=tcgetattr(fd,&oldtio);
>>>>>>>>>>>>   if(result<0) {
>>>>>>>>>>>>     perror("tcgetattr");
>>>>>>>>>>>>     return 1;
>>>>>>>>>>>>   }
>>>>>>>>>>>>
>>>>>>>>>>>>   memcpy(&newtio,&oldtio,sizeof(struct termios));
>>>>>>>>>>>>   newtio.c_cflag = B19200
>>>>>>>>>>>>
>>>>>>>>>>>>     | CRTSCTS
>>>>>>>>>>>>     | CS8
>>>>>>>>>>>>     | CREAD;
>>>>>>>>>>>>
>>>>>>>>>>>>   newtio.c_iflag     = IGNPAR;
>>>>>>>>>>>>   newtio.c_oflag     = 0;
>>>>>>>>>>>>   newtio.c_lflag     = 0;
>>>>>>>>>>>>   newtio.c_cc[VMIN]  = 1;
>>>>>>>>>>>>   newtio.c_cc[VTIME] = 0;
>>>>>>>>>>>>
>>>>>>>>>>>>   result=tcflush(fd, TCIFLUSH);
>>>>>>>>>>>>   if(result<0) {
>>>>>>>>>>>>     perror("tcflush");
>>>>>>>>>>>>     return 1;
>>>>>>>>>>>>   }
>>>>>>>>>>>>
>>>>>>>>>>>>   result=tcsetattr(fd,TCSANOW,&newtio);
>>>>>>>>>>>>   if(result<0) {
>>>>>>>>>>>>     perror("tcsetattr");
>>>>>>>>>>>>     return 1;
>>>>>>>>>>>>   }
>>>>>>>>>>>>
>>>>>>>>>>>>   sleep(1);
>>>>>>>>>>>>
>>>>>>>>>>>>   printf("Performing initial query\n");
>>>>>>>>>>>>   buf[0]=TBAN_SER_SOURCE1;
>>>>>>>>>>>>   buf[1]=TBAN_SER_REQUEST;
>>>>>>>>>>>>
>>>>>>>>>>>>   printf("Requesting status\n");
>>>>>>>>>>>>   result=write(fd,buf,2);
>>>>>>>>>>>>   if(result<0) {
>>>>>>>>>>>>     perror("write");
>>>>>>>>>>>>     return 1;
>>>>>>>>>>>>   }
>>>>>>>>>>>>
>>>>>>>>>>>>   sleep(1);
>>>>>>>>>>>>
>>>>>>>>>>>>   printf("Reading status\n");
>>>>>>>>>>>>   result=read(fd,buf,32);
>>>>>>>>>>>>   if(result<0) {
>>>>>>>>>>>>     perror("read");
>>>>>>>>>>>>     return 1;
>>>>>>>>>>>>   }
>>>>>>>>>>>>
>>>>>>>>>>>>   result=tcsetattr(fd,TCSANOW,&oldtio);
>>>>>>>>>>>>   if(result<0) {
>>>>>>>>>>>>     perror("tcsetattr");
>>>>>>>>>>>>     return 1;
>>>>>>>>>>>>   }
>>>>>>>>>>>>
>>>>>>>>>>>>   result=close(fd);
>>>>>>>>>>>>   if(result<0) {
>>>>>>>>>>>>     perror("close");
>>>>>>>>>>>>     return 1;
>>>>>>>>>>>>   }
>>>>>>>>>>>>   return 0;
>>>>>>>>>>>> }
>>>>>>>>>>>>
>>>>>>>>>>>> It hangs while reading independently of the number of bits I am
>>>>>>>>>>>> reading.
>>>>>>>>>>>>
>>>>>>>>>>>> Here is the output from dmesg when I load the uftdi module:
>>>>>>>>>>>> Sep 20 21:31:31 ldaemon kernel: uftdi0: <USB - Serial> on usbus6
>>>>>>>>>>>> Sep 20 21:31:31 ldaemon kernel: ucom_attach_tty:317: tp =
>>>>>>>>>>>> 0xffffff001f12b400, unit = 0 Sep 20 21:31:31 ldaemon kernel:
>>>>>>>>>>>> ucom_attach_tty:346: ttycreate: U0 Sep 20 21:31:34 ldaemon root:
>>>>>>>>>>>> Unknown USB device: vendor 0x051d product 0x0002 bus uhub0
>>>>>>>>>>>>
>>>>>>>>>>>> Here is the output in /var/log/messages when I enable the debug
>>>>>>>>>>>> output for ucom and uftdi: Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>>>> ucom_open:554: tp = 0xffffff001f12b400 Sep 20 21:33:30 ldaemon
>>>>>>>>>>>> kernel: ucom_dtr:827: onoff = 1 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>>>> ucom_line_state:799: on=0x01, off=0x00 Sep 20 21:33:30 ldaemon
>>>>>>>>>>>> kernel: ucom_rts:838: onoff = 1
>>>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
>>>>>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_break:816: onoff =
>>>>>>>>>>>> 0 Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x00,
>>>>>>>>>>>> off=0x04 Sep 20 21:33:30 ldaemon kernel: ucom_status_change:901:
>>>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_param:950: sc =
>>>>>>>>>>>> 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>>>> uftdi_pre_param:653:
>>>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x01,
>>>>>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_rts:838: onoff = 1
>>>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: ucom_line_state:799: on=0x02,
>>>>>>>>>>>> off=0x00 Sep 20 21:33:30 ldaemon kernel: ucom_cfg_open:520:
>>>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_open:354:
>>>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_read_callback:459: status
>>>>>>>>>>>> change msr=0xf0 (0x00) lsr=0x60 (0x00) Sep 20 21:33:30 ldaemon
>>>>>>>>>>>> kernel: ucom_status_change:901:
>>>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705:
>>>>>>>>>>>> msr=0xf0 lsr=0x60 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>>>> ucom_cfg_status_change:887: DCD changed to 1 Sep 20 21:33:30
>>>>>>>>>>>> ldaemon kernel:
>>>>>>>>>>>> uftdi_cfg_param:672: Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>>>> ucom_ioctl:653: cmd = 0x402c7413 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>>>> ucom_ioctl:653: cmd = 0x80047410 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>>>> ucom_ioctl:653: cmd = 0x802c7414 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>>>> ucom_param:950: sc = 0xffffff001f12ac58 Sep 20 21:33:30 ldaemon
>>>>>>>>>>>> kernel:
>>>>>>>>>>>> uftdi_pre_param:653:
>>>>>>>>>>>> Sep 20 21:33:30 ldaemon kernel: uftdi_cfg_get_status:705:
>>>>>>>>>>>> msr=0xf0 lsr=0x60 Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>>>> uftdi_cfg_param:672: Sep 20 21:33:30 ldaemon kernel:
>>>>>>>>>>>> ucom_get_data:1064: cnt=0 Sep 20 21:33:31 ldaemon kernel:
>>>>>>>>>>>> ucom_ioctl:653: cmd = 0x80047410 Sep 20 21:33:32 ldaemon kernel:
>>>>>>>>>>>> ucom_outwakeup:1009: sc = 0xffffff001f12ac58 Sep 20 21:33:32
>>>>>>>>>>>> ldaemon kernel:
>>>>>>>>>>>> ucom_get_data:1064: cnt=2
>>>>>>>>>>>> Sep 20 21:33:32 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>>>>>>>>
>>>>>>>>>>>> I really need to get this working so I am ready to test things
>>>>>>>>>>>> as much as I can...
>>>>>>>>>>>>                         
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> You need to set raw mode for the TTY device I think. Maybe Ed can
>>>>>>>>>>> give you the function name you need to call to do that?
>>>>>>>>>>>
>>>>>>>>>>> --HPS
>>>>>>>>>>>                       
>>>>>>>>>> Do I need to do something like that?
>>>>>>>>>> ioctl(fileno(stdin), TIOCGETP, &tty_org);
>>>>>>>>>> tty = tty_org;
>>>>>>>>>>
>>>>>>>>>> /* set terminal to raw mode ... */
>>>>>>>>>> tty.sg_flags |= CRMOD;
>>>>>>>>>> tty.sg_flags &= ~ECHO;
>>>>>>>>>> tty.sg_flags &= ~XTABS;
>>>>>>>>>> tty.sg_flags |= RAW;
>>>>>>>>>>
>>>>>>>>>> Thanks!
>>>>>>>>>> Pierre-Luc Drouin
>>>>>>>>>>                     
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> You need to call this function:
>>>>>>>>>
>>>>>>>>>      void
>>>>>>>>>      cfmakeraw(struct termios *t);
>>>>>>>>>
>>>>>>>>> --HPS
>>>>>>>>>                   
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> it still does not work. I have added the line
>>>>>>>> cfmakeraw(&newtio);
>>>>>>>>
>>>>>>>> just before the call to tcflush and I get the following output in
>>>>>>>> /var/log/messages:
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_open:554: tp =
>>>>>>>> 0xffffff001f12b400 Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827:
>>>>>>>> onoff = 1
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01,
>>>>>>>> off=0x00 Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02,
>>>>>>>> off=0x00 Sep 21 13:38:46 ldaemon kernel: ucom_break:816: onoff = 0
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x00,
>>>>>>>> off=0x04 Sep 21 13:38:46 ldaemon kernel: ucom_status_change:901:
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc =
>>>>>>>> 0xffffff001f12ac58 Sep 21 13:38:46 ldaemon kernel:
>>>>>>>> uftdi_pre_param:653:
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x01,
>>>>>>>> off=0x00 Sep 21 13:38:46 ldaemon kernel: ucom_rts:838: onoff = 1
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_line_state:799: on=0x02,
>>>>>>>> off=0x00 Sep 21 13:38:46 ldaemon kernel: ucom_cfg_open:520:
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_open:354:
>>>>>>>> uftdi_cfg_get_status:705: msr=0xf0 lsr=0x60
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_cfg_status_change:887: DCD
>>>>>>>> changed to 1 Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_param:950: sc =
>>>>>>>> 0xffffff001f12ac58 Sep 21 13:38:46 ldaemon kernel:
>>>>>>>> uftdi_pre_param:653:
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: uftdi_cfg_param:672:
>>>>>>>> Sep 21 13:38:46 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>>>> Sep 21 13:38:47 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>>>>>> Sep 21 13:38:48 ldaemon kernel: ucom_outwakeup:1009: sc =
>>>>>>>> 0xffffff001f12ac58 Sep 21 13:38:48 ldaemon kernel:
>>>>>>>> ucom_get_data:1064: cnt=2
>>>>>>>> Sep 21 13:38:48 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>>>>>>                 
>>>>>>> Can you try adding a delay after setting the baud rate?
>>>>>>>
>>>>>>> --HPS
>>>>>>>               
>>>>>> The code already sleeps for 1 second after I applying the baud rate
>>>>>> (via tcsetattr(fd,TCSANOW,&newtio)). I am not sure to understand what
>>>>>> you mean...
>>>>>>             
>>>>> Hi,
>>>>>
>>>>> I mean try adding some:
>>>>>
>>>>> usleep(1000000);
>>>>>
>>>>> To your code to see if that changes anything.
>>>>>
>>>>> Also try reading one byte instead of 32.
>>>>>
>>>>> Last, try adding a printout to:
>>>>>
>>>>> src/sys/dev/usb/serial/uftdi.c
>>>>>
>>>>> uftdi_read_callback()
>>>>>
>>>>> and printout the actlen variable.
>>>>>
>>>>> --HPS
>>>>>           
>>>> ok, so I added the usleep statement right after the existing sleep
>>>> statement. I also tried reading a single byte. It did not make any
>>>> difference... I added a print statement to print the value of actlen
>>>> right after it is set via
>>>> usbd_xfer_status(xfer, &actlen, NULL, NULL, NULL);
>>>>
>>>> Here is the new output in /var/log/messages:
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_open:554: tp = 0xffffff0139488800
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_rts:838: onoff = 1
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_break:816: onoff = 0
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x00, off=0x04
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_status_change:901:
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_param:950: sc = 0xffffff013bcac458
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_dtr:827: onoff = 1
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x01, off=0x00
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_rts:838: onoff = 1
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_line_state:799: on=0x02, off=0x00
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_cfg_open:520:
>>>> Sep 21 14:55:28 ldaemon kernel: actlen is 0
>>>> Sep 21 14:55:28 ldaemon kernel: actlen is 2
>>>> Sep 21 14:55:28 ldaemon kernel: actlen is 2
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_cfg_status_change:887: DCD changed
>>>> to 1 Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x402c7413
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410 Sep 21
>>>> 14:55:28 ldaemon kernel: ucom_ioctl:653: cmd = 0x802c7414 Sep 21
>>>> 14:55:28 ldaemon kernel: ucom_param:950: sc = 0xffffff013bcac458 Sep 21
>>>> 14:55:28 ldaemon kernel: actlen is 2
>>>> Sep 21 14:55:28 ldaemon last message repeated 12 times
>>>> Sep 21 14:55:28 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>> Sep 21 14:55:28 ldaemon kernel: actlen is 2
>>>> Sep 21 14:55:30 ldaemon last message repeated 111 times
>>>> Sep 21 14:55:30 ldaemon kernel: ucom_ioctl:653: cmd = 0x80047410
>>>> Sep 21 14:55:30 ldaemon kernel: actlen is 2
>>>> Sep 21 14:55:31 ldaemon last message repeated 62 times
>>>> Sep 21 14:55:31 ldaemon kernel: ucom_outwakeup:1009: sc =
>>>> 0xffffff013bcac458 Sep 21 14:55:31 ldaemon kernel: ucom_get_data:1064:
>>>> cnt=2
>>>> Sep 21 14:55:31 ldaemon kernel: ucom_get_data:1064: cnt=0
>>>> Sep 21 14:55:31 ldaemon kernel: actlen is 2
>>>>         
>>> If actlen is 2 then no modem data is transferred from the device.
>>>
>>> --HPS
>>>       
>> Hmm, so does it indicate a bug in uftdi? In asynchronous mode, SIGIO is
>> generated but when try reading I get error EINTR...
>>
>> Thanks!
>>     
>
> It indicates that your device is not sending any data.
>
> --HPS
>
>   
So does it mean that the write statement (a status request) is not 
transmitted to the device either? Because this write statement should be 
followed by data sent from the device and it effectively does on Linux. 
And about SIGIO, shouldn't this signal be generated only when there is 
data available to read? Why is it generated in asynchronous mode and 
then the read statement returns EINTR?

Thanks!
Pierre-Luc
From hselasky at c2i.net  Tue Sep 22 15:35:23 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep 22 15:35:29 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB8EB78.2020809@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909221638.47642.hselasky@c2i.net>
	<4AB8EB78.2020809@pldrouin.net>
Message-ID: <200909221735.57680.hselasky@c2i.net>

On Tuesday 22 September 2009 17:21:28 Pierre-Luc Drouin wrote:

> >> Thanks!
> >
> > It indicates that your device is not sending any data.
> >
> > --HPS
>
> So does it mean that the write statement (a status request) is not
> transmitted to the device either?

No, the "xxx_get()" message means that the data you write is sent and 
transmitted.

BTW: I have a FTDI adapter here, and it works fine with loopback when the 
baudrate is set correctly.

> Because this write statement should be
> followed by data sent from the device and it effectively does on Linux.
> And about SIGIO, shouldn't this signal be generated only when there is
> data available to read? Why is it generated in asynchronous mode and
> then the read statement returns EINTR?

Ed has to answer these questions. This stuff is not handled in the USB stack 
for FTDI devices.

--HPS

From hselasky at c2i.net  Tue Sep 22 15:40:14 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep 22 15:40:20 2009
Subject: libusb20 api
In-Reply-To: <2C0D6269-1296-4D34-8029-828A0FE281CB@tlb.org>
References: <2C0D6269-1296-4D34-8029-828A0FE281CB@tlb.org>
Message-ID: <200909221740.49279.hselasky@c2i.net>

On Tuesday 22 September 2009 00:38:46 Trevor Blackwell wrote:
> This always fails:
>
>        char devname[256];
>        if (libusb20_dev_get_iface_desc(pdev, n, devname,
> sizeof(devname))) break;
>
> while this works:
>
>        char devname[128];
>        if (libusb20_dev_get_iface_desc(pdev, n, devname,
> sizeof(devname))) break;
>
> Because this function takes a uint8_t for length:
>
> <libusb20_ugen20.c:851>:
> static int
> ugen20_dev_get_iface_desc(struct libusb20_device *pdev,
>      uint8_t iface_index, char *buf, uint8_t len)
>
> even though the kernel ioctl structure has a 16-bit length.
>
> Hans, why not just use size_t for such arguments?

Your point is valid. Currently USB string descriptors are always limited to 
255 bytes. Setting up a larger buffer does not make sense.

I will see what I can do.

--HPS

From pldrouin at pldrouin.net  Tue Sep 22 16:15:17 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Tue Sep 22 16:15:23 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909221735.57680.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909221638.47642.hselasky@c2i.net>
	<4AB8EB78.2020809@pldrouin.net>
	<200909221735.57680.hselasky@c2i.net>
Message-ID: <4AB8F817.1040703@pldrouin.net>

Hans Petter Selasky wrote:
> On Tuesday 22 September 2009 17:21:28 Pierre-Luc Drouin wrote:
>
>   
>>>> Thanks!
>>>>         
>>> It indicates that your device is not sending any data.
>>>
>>> --HPS
>>>       
>> So does it mean that the write statement (a status request) is not
>> transmitted to the device either?
>>     
>
> No, the "xxx_get()" message means that the data you write is sent and 
> transmitted.
>
> BTW: I have a FTDI adapter here, and it works fine with loopback when the 
> baudrate is set correctly.
>
>   
>> Because this write statement should be
>> followed by data sent from the device and it effectively does on Linux.
>> And about SIGIO, shouldn't this signal be generated only when there is
>> data available to read? Why is it generated in asynchronous mode and
>> then the read statement returns EINTR?
>>     
>
> Ed has to answer these questions. This stuff is not handled in the USB stack 
> for FTDI devices.
>
> --HPS
>
>   
In the manual page for the uftdi driver, the chip I am using (FT232BL) 
is not listed. According to the FTDI website, it is based on FT8U232AM, 
but  it has extra functionalities. Have you had the chance to test an 
device that uses either a FT232BM, FT232BL or FT232BQ chip? I just 
tested the device on FreeBSD 7.2 and it does not work either...

Thanks
Pierre-Luc Drouin
From hselasky at c2i.net  Tue Sep 22 16:32:21 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep 22 16:32:28 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB8F817.1040703@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909221735.57680.hselasky@c2i.net>
	<4AB8F817.1040703@pldrouin.net>
Message-ID: <200909221832.56540.hselasky@c2i.net>

On Tuesday 22 September 2009 18:15:19 Pierre-Luc Drouin wrote:
> Hans Petter Selasky wrote:
> > On Tuesday 22 September 2009 17:21:28 Pierre-Luc Drouin wrote:
> >>>> Thanks!
> >>>
> >>> It indicates that your device is not sending any data.
> >>>
> >>> --HPS
> >>
> >> So does it mean that the write statement (a status request) is not
> >> transmitted to the device either?
> >
> > No, the "xxx_get()" message means that the data you write is sent and
> > transmitted.
> >
> > BTW: I have a FTDI adapter here, and it works fine with loopback when the
> > baudrate is set correctly.
> >
> >> Because this write statement should be
> >> followed by data sent from the device and it effectively does on Linux.
> >> And about SIGIO, shouldn't this signal be generated only when there is
> >> data available to read? Why is it generated in asynchronous mode and
> >> then the read statement returns EINTR?
> >
> > Ed has to answer these questions. This stuff is not handled in the USB
> > stack for FTDI devices.
> >
> > --HPS
>
> In the manual page for the uftdi driver, the chip I am using (FT232BL)
> is not listed. According to the FTDI website, it is based on FT8U232AM,
> but  it has extra functionalities. Have you had the chance to test an
> device that uses either a FT232BM, FT232BL or FT232BQ chip? I just
> tested the device on FreeBSD 7.2 and it does not work either...

No, I haven't.

--HPS

From hselasky at c2i.net  Tue Sep 22 16:38:06 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep 22 16:38:12 2009
Subject: libusb20 api
In-Reply-To: <200909221740.49279.hselasky@c2i.net>
References: <2C0D6269-1296-4D34-8029-828A0FE281CB@tlb.org>
	<200909221740.49279.hselasky@c2i.net>
Message-ID: <200909221838.42182.hselasky@c2i.net>

On Tuesday 22 September 2009 17:40:48 Hans Petter Selasky wrote:
> On Tuesday 22 September 2009 00:38:46 Trevor Blackwell wrote:
> > This always fails:
> >
> >        char devname[256];
> >        if (libusb20_dev_get_iface_desc(pdev, n, devname,
> > sizeof(devname))) break;
> >
> > while this works:
> >
> >        char devname[128];
> >        if (libusb20_dev_get_iface_desc(pdev, n, devname,
> > sizeof(devname))) break;
> >
> > Because this function takes a uint8_t for length:
> >
> > <libusb20_ugen20.c:851>:
> > static int
> > ugen20_dev_get_iface_desc(struct libusb20_device *pdev,
> >      uint8_t iface_index, char *buf, uint8_t len)
> >
> > even though the kernel ioctl structure has a 16-bit length.
> >
> > Hans, why not just use size_t for such arguments?
>
> Your point is valid. Currently USB string descriptors are always limited to
> 255 bytes. Setting up a larger buffer does not make sense.
>
> I will see what I can do.
>

s/string/interface/

> --HPS

From pldrouin at pldrouin.net  Tue Sep 22 16:40:40 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Tue Sep 22 16:40:47 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909221832.56540.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909221735.57680.hselasky@c2i.net>
	<4AB8F817.1040703@pldrouin.net>
	<200909221832.56540.hselasky@c2i.net>
Message-ID: <4AB8FE08.7040007@pldrouin.net>

Hans Petter Selasky wrote:
> On Tuesday 22 September 2009 18:15:19 Pierre-Luc Drouin wrote:
>   
>> Hans Petter Selasky wrote:
>>     
>>> On Tuesday 22 September 2009 17:21:28 Pierre-Luc Drouin wrote:
>>>       
>>>>>> Thanks!
>>>>>>             
>>>>> It indicates that your device is not sending any data.
>>>>>
>>>>> --HPS
>>>>>           
>>>> So does it mean that the write statement (a status request) is not
>>>> transmitted to the device either?
>>>>         
>>> No, the "xxx_get()" message means that the data you write is sent and
>>> transmitted.
>>>
>>> BTW: I have a FTDI adapter here, and it works fine with loopback when the
>>> baudrate is set correctly.
>>>
>>>       
>>>> Because this write statement should be
>>>> followed by data sent from the device and it effectively does on Linux.
>>>> And about SIGIO, shouldn't this signal be generated only when there is
>>>> data available to read? Why is it generated in asynchronous mode and
>>>> then the read statement returns EINTR?
>>>>         
>>> Ed has to answer these questions. This stuff is not handled in the USB
>>> stack for FTDI devices.
>>>
>>> --HPS
>>>       
>> In the manual page for the uftdi driver, the chip I am using (FT232BL)
>> is not listed. According to the FTDI website, it is based on FT8U232AM,
>> but  it has extra functionalities. Have you had the chance to test an
>> device that uses either a FT232BM, FT232BL or FT232BQ chip? I just
>> tested the device on FreeBSD 7.2 and it does not work either...
>>     
>
> No, I haven't.
>
> --HPS
>
>   
Are there additional tests I can do in synchronous mode to try pinning 
down the problem?

Thanks!
From hselasky at c2i.net  Tue Sep 22 16:41:58 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep 22 16:42:09 2009
Subject: libusb20 api
In-Reply-To: <200909221740.49279.hselasky@c2i.net>
References: <2C0D6269-1296-4D34-8029-828A0FE281CB@tlb.org>
	<200909221740.49279.hselasky@c2i.net>
Message-ID: <200909221842.36202.hselasky@c2i.net>

On Tuesday 22 September 2009 17:40:48 Hans Petter Selasky wrote:
> On Tuesday 22 September 2009 00:38:46 Trevor Blackwell wrote:
> > This always fails:
> >

Your comment could be applied to other functions being passed lengths aswell. 
However, if you compile your code with -Wall, you should be safe from such 
errors when passing too big constants.

I'm not sure if I will push an API change like this at the current moment.

--HPS

From hselasky at c2i.net  Tue Sep 22 16:46:49 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Sep 22 16:46:55 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4AB8FE08.7040007@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909221832.56540.hselasky@c2i.net>
	<4AB8FE08.7040007@pldrouin.net>
Message-ID: <200909221847.26679.hselasky@c2i.net>

On Tuesday 22 September 2009 18:40:40 Pierre-Luc Drouin wrote:
> Hans Petter Selasky wrote:
> > On Tuesday 22 September 2009 18:15:19 Pierre-Luc Drouin wrote:
> >> Hans Petter Selasky wrote:
> >>> On Tuesday 22 September 2009 17:21:28 Pierre-Luc Drouin wrote:
> >>>>>> Thanks!
> >>>>>
> >>>>> It indicates that your device is not sending any data.
> >>>>>
> >>>>> --HPS
> >>>>
> >>>> So does it mean that the write statement (a status request) is not
> >>>> transmitted to the device either?
> >>>
> >>> No, the "xxx_get()" message means that the data you write is sent and
> >>> transmitted.
> >>>
> >>> BTW: I have a FTDI adapter here, and it works fine with loopback when
> >>> the baudrate is set correctly.
> >>>
> >>>> Because this write statement should be
> >>>> followed by data sent from the device and it effectively does on
> >>>> Linux. And about SIGIO, shouldn't this signal be generated only when
> >>>> there is data available to read? Why is it generated in asynchronous
> >>>> mode and then the read statement returns EINTR?
> >>>
> >>> Ed has to answer these questions. This stuff is not handled in the USB
> >>> stack for FTDI devices.
> >>>
> >>> --HPS
> >>
> >> In the manual page for the uftdi driver, the chip I am using (FT232BL)
> >> is not listed. According to the FTDI website, it is based on FT8U232AM,
> >> but  it has extra functionalities. Have you had the chance to test an
> >> device that uses either a FT232BM, FT232BL or FT232BQ chip? I just
> >> tested the device on FreeBSD 7.2 and it does not work either...
> >
> > No, I haven't.
> >
> > --HPS
>
> Are there additional tests I can do in synchronous mode to try pinning
> down the problem?

Hi,

If the device doesn't work, then there are probably some FTDI USB registers 
which are not programmed correctly.

If you could debug that it would be great.

--HPS

From avg at icyb.net.ua  Wed Sep 23 14:54:44 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Wed Sep 23 14:54:50 2009
Subject: sb600/sb700 ohci experimental patch
Message-ID: <4ABA36B1.9070706@icyb.net.ua>


If you have a system with SB600, SB700, etc chipset and you have problems with low
speed USB devices attached during boot (keyboard, mouse), could you please try the
following experimental patch and report back?
I am primarily interested in the first several lines produced during boot with
printfs that are introduced by the patch. Preferably in the context of surrounding
USB-related dmesg messages. No need to report subsequent same-looking
ever-repeating messages (if any).

WARNING: this is an experimental patch, it is probably not even close to what a
real fix could be, it might not fix the problem (but perhaps it would), it might
introduce instabilities into OHCI driver and it is noisy (unconditional printf).
The primary purpose of this patch is to gather information necessary for a real fix.

Thank you!

diff --git a/sys/dev/usb/controller/ohci.c b/sys/dev/usb/controller/ohci.c
index 30592c1..fb6ba34 100644
--- a/sys/dev/usb/controller/ohci.c
+++ b/sys/dev/usb/controller/ohci.c
@@ -247,8 +249,8 @@ reset:
 	OWRITE4(sc, OHCI_INTERRUPT_ENABLE, sc->sc_eintrs | OHCI_MIE);
 	/* switch on desired functional features */
 	ctl = OREAD4(sc, OHCI_CONTROL);
-	ctl &= ~(OHCI_CBSR_MASK | OHCI_LES | OHCI_HCFS_MASK | OHCI_IR);
-	ctl |= OHCI_PLE | OHCI_IE | OHCI_CLE | OHCI_BLE |
+	ctl &= ~(OHCI_CBSR_MASK | OHCI_LES | OHCI_HCFS_MASK | OHCI_IR | OHCI_CLE |
OHCI_CLF);
+	ctl |= OHCI_PLE | OHCI_IE | /*OHCI_CLE |*/ OHCI_BLE |
 	    OHCI_RATIO_1_4 | OHCI_HCFS_OPERATIONAL;
 	/* And finally start it! */
 	OWRITE4(sc, OHCI_CONTROL, ctl);
@@ -2727,8 +2729,17 @@ ohci_set_hw_power(struct usb_bus *bus)
 	temp = OREAD4(sc, OHCI_CONTROL);
 	temp &= ~(OHCI_PLE | OHCI_IE | OHCI_CLE | OHCI_BLE);

-	if (flags & USB_HW_POWER_CONTROL)
+	if (flags & USB_HW_POWER_CONTROL) {
+		struct usb_page_search buf_res;
+
+		buf_res.physaddr = OREAD4(sc, OHCI_CONTROL_HEAD_ED);
+		printf("(hw power) control head <= %p\n", (void*)buf_res.physaddr);
+		usbd_get_page(&sc->sc_hw.ctrl_start_pc, 0, &buf_res);
+		printf("(hw power) control head => %p\n", (void*)buf_res.physaddr);
+		OWRITE4(sc, OHCI_CONTROL_HEAD_ED, buf_res.physaddr);
+
 		temp |= OHCI_CLE;
+	}

 	if (flags & USB_HW_POWER_BULK)
 		temp |= OHCI_BLE;

-- 
Andriy Gapon
From tom at tomjudge.com  Wed Sep 23 22:50:03 2009
From: tom at tomjudge.com (Tom Judge)
Date: Wed Sep 23 22:50:14 2009
Subject: usb/116947: [ukbd] [patch] [regression] enable boot protocol
 on the USB keyboards
Message-ID: <200909232250.n8NMo2UC037852@freefall.freebsd.org>

The following reply was made to PR usb/116947; it has been noted by GNATS.

From: Tom Judge <tom@tomjudge.com>
To: bug-followup@FreeBSD.org, rea-fbsd@codelabs.ru
Cc:  
Subject: Re: usb/116947: [ukbd] [patch] [regression] enable boot protocol
 on the USB keyboards
Date: Wed, 23 Sep 2009 22:22:16 +0000

 This is a multi-part message in MIME format.
 --------------070601060402040600080702
 Content-Type: text/plain; charset=ISO-8859-1; format=flowed
 Content-Transfer-Encoding: 7bit
 
 Here is a simple patch against 8.0 Beta 3  to make the Function keys work.
 
 This adds a quirk UQ_KBD_BOOTPROTO, than can be set to force the 
 keyboard to use the boot protocol.
 
 
 
 
 
 --------------070601060402040600080702
 Content-Type: text/plain;
  name="usb-natural4000.patch"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline;
  filename="usb-natural4000.patch"
 
 Index: quirk/usb_quirk.c
 ===================================================================
 --- quirk/usb_quirk.c	(revision 196574)
 +++ quirk/usb_quirk.c	(working copy)
 @@ -122,6 +122,7 @@
  	{USB_QUIRK_ENTRY(USB_VENDOR_METAGEEK, USB_PRODUCT_METAGEEK_WISPY1B, 0x0000, 0xFFFF, UQ_KBD_IGNORE, UQ_HID_IGNORE, UQ_NONE)},
  	{USB_QUIRK_ENTRY(USB_VENDOR_TENX, USB_PRODUCT_TENX_UAUDIO0, 0x0101, 0x0101, UQ_AUDIO_SWAP_LR, UQ_NONE)},
  	/* MS keyboards do weird things */
 +	{USB_QUIRK_ENTRY(USB_VENDOR_MICROSOFT, USB_PRODUCT_MICROSOFT_NATURAL4000, 0x0000, 0xFFFF, UQ_KBD_BOOTPROTO, UQ_NONE)},
  	{USB_QUIRK_ENTRY(USB_VENDOR_MICROSOFT, USB_PRODUCT_MICROSOFT_WLINTELLIMOUSE, 0x0000, 0xFFFF, UQ_MS_LEADING_BYTE, UQ_NONE)},
  	{USB_QUIRK_ENTRY(USB_VENDOR_METAGEEK, USB_PRODUCT_METAGEEK_WISPY24X, 0x0000, 0xFFFF, UQ_KBD_IGNORE, UQ_HID_IGNORE, UQ_NONE)},
  };
 @@ -138,6 +139,7 @@
  	[UQ_BUS_POWERED]	= "UQ_BUS_POWERED",
  	[UQ_HID_IGNORE]		= "UQ_HID_IGNORE",
  	[UQ_KBD_IGNORE]		= "UQ_KBD_IGNORE",
 +	[UQ_KBD_BOOTPROTO]	= "UQ_KBD_BOOTPROTO",
  	[UQ_MS_BAD_CLASS]	= "UQ_MS_BAD_CLASS",
  	[UQ_MS_LEADING_BYTE]	= "UQ_MS_LEADING_BYTE",
  	[UQ_MS_REVZ]		= "UQ_MS_REVZ",
 Index: quirk/usb_quirk.h
 ===================================================================
 --- quirk/usb_quirk.h	(revision 196574)
 +++ quirk/usb_quirk.h	(working copy)
 @@ -40,6 +40,7 @@
  	UQ_BUS_POWERED,		/* device is bus powered, despite claim */
  	UQ_HID_IGNORE,		/* device should be ignored by hid class */
  	UQ_KBD_IGNORE,		/* device should be ignored by kbd class */
 +	UQ_KBD_BOOTPROTO,	/* kbd should use the boot proto. */
  	UQ_MS_BAD_CLASS,	/* doesn't identify properly */
  	UQ_MS_LEADING_BYTE,	/* mouse sends an unknown leading byte */
  	UQ_MS_REVZ,		/* mouse has Z-axis reversed */
 Index: input/ukbd.c
 ===================================================================
 --- input/ukbd.c	(revision 196574)
 +++ input/ukbd.c	(working copy)
 @@ -789,6 +789,17 @@
  	 * according to the BIOS data?
  	 */
  	KBD_PROBE_DONE(kbd);
 +	/*
 +	 * Set boot protocol if we need the quirk.
 +	 */
 +	
 +	if (usb_test_quirk(uaa, UQ_KBD_BOOTPROTO)) {
 +		err = usbd_req_set_protocol(sc->sc_udev, &Giant, sc->sc_iface_index, 0);
 +		if (err != USB_ERR_NORMAL_COMPLETION) {
 +			DPRINTF("set protocol error=%s\n", usbd_errstr(err));
 +			goto detach;
 +		}
 +	}
  
  	/* figure out if there is an ID byte in the data */
  	err = usbd_req_get_hid_desc(uaa->device, NULL, &hid_ptr,
 Index: usbdevs
 ===================================================================
 --- usbdevs	(revision 196574)
 +++ usbdevs	(working copy)
 @@ -1751,6 +1751,7 @@
  product MICROSOFT WLNOTEBOOK3	0x00d2	Wireless Optical Mouse 3000 (Model 1049)
  product MICROSOFT WLUSBMOUSE	0x00b9	Wireless USB Mouse
  product MICROSOFT XBOX360	0x0292	XBOX 360 WLAN
 +product MICROSOFT NATURAL4000	0x00db  Natural Ergonomic Keyboard 4000
  
  /* Microtech products */
  product MICROTECH SCSIDB25	0x0004	USB-SCSI-DB25
 
 --------------070601060402040600080702--
From hinokind at gmail.com  Wed Sep 23 23:01:46 2009
From: hinokind at gmail.com (=?utf-8?B?QW5kcml1cyBNb3JrxatuYXM=?=)
Date: Wed Sep 23 23:02:19 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4ABA36B1.9070706@icyb.net.ua>
References: <4ABA36B1.9070706@icyb.net.ua>
Message-ID: <op.u0r8ufux43o42p@klevas>

On Wed, 23 Sep 2009 17:54:41 +0300, Andriy Gapon <avg@icyb.net.ua> wrote:
> If you have a system with SB600, SB700, etc chipset and you have problems with low
> speed USB devices attached during boot (keyboard, mouse), could you please try the
> following experimental patch and report back?
> I am primarily interested in the first several lines produced during boot with
> printfs that are introduced by the patch. Preferably in the context of surrounding
> USB-related dmesg messages. No need to report subsequent same-looking
> ever-repeating messages (if any).

I hope this helps:

Test box: FreeBSD 8.0-RC1 amd64 r197323M on Asus M2A-VM (SB600)

Without your patch, if mouse is plugged into one of the back USB ports and
umass device is present on any USB port, mouse won't work. It has to be
connected to front USB port to be friendly with other devices.

With your patch, mouse can be plugged anywhere, it won't complain about
umass devices connected to front USB port, but it still doesn't play nice
with devices on back ports during boot. If I connect storage device after
boot, both mouse and storage devices work fine.


Parts of dmesg with mouse connected to back and storage to front USB ports.
Everything works.

usbus0: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0xcfef1e30
(hw power) control head => 0x2329000
usbus1: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x4143000
(hw power) control head => 0x4143000
usbus2: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x4186000
(hw power) control head => 0x4186000
usbus3: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x41aa000
(hw power) control head => 0x41aa000
usbus4: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x4201000
(hw power) control head => 0x4201000
usbus5: 480Mbps High Speed USB v2.0

ugen0.1: <ATI> at usbus0
uhub0: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <ATI> at usbus1
uhub1: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen2.1: <ATI> at usbus2
uhub2: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
ugen3.1: <ATI> at usbus3
uhub3: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
ugen4.1: <ATI> at usbus4
uhub4: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
ugen5.1: <ATI> at usbus5
uhub5: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus5
Root mount waiting for: usbus5 usbus4 usbus3 usbus2 usbus1 usbus0
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
Root mount waiting for: usbus5
Root mount waiting for: usbus5
Root mount waiting for: usbus5
Root mount waiting for: usbus5
uhub5: 10 ports with 10 removable, self powered
Root mount waiting for: usbus5
(hw power) control head <= 0x2329000
(hw power) control head => 0x2329000
ugen0.2: <Logitech> at usbus0
ums0: <Logitech USB Gaming Mouse, class 0/0, rev 2.00/52.00, addr 2> on usbus0
ums0: 16 buttons and [XYZ] coordinates ID=0
uhid0: <Logitech USB Gaming Mouse, class 0/0, rev 2.00/52.00, addr 2> on usbus0
(hw power) control head <= 0x2329000
(hw power) control head => 0x2329000
ugen5.2: <PQI> at usbus5
umass0: <PQI PQI USB Flash Drive, class 0/0, rev 2.00/1.00, addr 2> on usbus5
umass0:  SCSI over Bulk-Only; quirks = 0x0000
Root mount waiting for: usbus5
(hw power) control head <= 0x2329000
(hw power) control head => 0x2329000
umass0:1:0:-1: Attached to scbus1
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Generic USB Flash Disk 0.00> Removable Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: 1967MB (4030463 512 byte sectors: 255H 63S/T 250C)


Connected another device to back USB port after booting was finished:

(hw power) control head <= 0x4143000
(hw power) control head => 0x4143000
ugen1.2: <CUSTT13> at usbus1
umass1: <Mass Storage Interface> on usbus1
umass1:  SCSI over Bulk-Only; quirks = 0x0000
umass1:2:1:-1: Attached to scbus2
(hw power) control head <= 0x4143000
(hw power) control head => 0x4143000
(hw power) control head <= 0x4143000
(hw power) control head => 0x4143000
(probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim1:1:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim1:1:0:0): SCSI Status: Check Condition
(probe0:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0
(probe0:umass-sim1:1:0:0): Not ready to ready change, medium may have changed
(probe0:umass-sim1:1:0:0): Retrying Command (per Sense Data)
da1 at umass-sim1 bus 1 target 0 lun 0
da1: <Agere MMCSD Storage 2.01> Removable Direct Access SCSI-0 device
da1: 1.000MB/s transfers
da1: 964MB (1974272 512 byte sectors: 64H 32S/T 964C)



Another dmesg, booting with storage device and mouse both connected to back
USB ports. Mouse works, storage doesn't.

usbus0: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0xcfef1e30
(hw power) control head => 0x2329000
usbus1: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0xcfef1e40
(hw power) control head => 0x4143000

<everything here is the same as in the dmesg above>

(hw power) control head <= 0x2329000
(hw power) control head => 0x2329000
ugen0.2: <Logitech> at usbus0
ums0: <Logitech USB Gaming Mouse, class 0/0, rev 2.00/52.00, addr 2> on usbus0
ums0: 16 buttons and [XYZ] coordinates ID=0
uhid0: <Logitech USB Gaming Mouse, class 0/0, rev 2.00/52.00, addr 2> on usbus0
(hw power) control head <= 0x2329000
(hw power) control head => 0x2329000
(hw power) control head <= 0x2329000
(hw power) control head => 0x2329000
(hw power) control head <= 0x4143000
(hw power) control head => 0x4143000
ugen1.2: <CUSTT13> at usbus1
umass0: <Mass Storage Interface> on usbus1
umass0:  SCSI over Bulk-Only; quirks = 0x0000
umass0:1:0:-1: Attached to scbus1
(hw power) control head <= 0x4143000
(hw power) control head => 0x4143000
<last two lines repeat 7 more times>


If you need anything else, let me know.

And thanks for the patch.

-- 
Andrius
From dorian.buettner at gmx.de  Thu Sep 24 06:22:31 2009
From: dorian.buettner at gmx.de (Dorian =?utf-8?q?B=C3=BCttner?=)
Date: Thu Sep 24 06:22:38 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <op.u0r8ufux43o42p@klevas>
References: <4ABA36B1.9070706@icyb.net.ua> <op.u0r8ufux43o42p@klevas>
Message-ID: <200909240822.28180.dorian.buettner@gmx.de>

On Friday 25 September 2009 00:31:17 Andrius Mork?nas wrote:
> On Wed, 23 Sep 2009 17:54:41 +0300, Andriy Gapon <avg@icyb.net.ua> wrote:
> > If you have a system with SB600, SB700, etc chipset and you have problems
> > with low speed USB devices attached during boot (keyboard, mouse), could
> > you please try the following experimental patch and report back?
> > I am primarily interested in the first several lines produced during boot
> > with printfs that are introduced by the patch. Preferably in the context
> > of surrounding USB-related dmesg messages. No need to report subsequent
> > same-looking ever-repeating messages (if any).
> 
> I hope this helps:
> 
> Test box: FreeBSD 8.0-RC1 amd64 r197323M on Asus M2A-VM (SB600)
> 
> Without your patch, if mouse is plugged into one of the back USB ports and
> umass device is present on any USB port, mouse won't work. It has to be
> connected to front USB port to be friendly with other devices.
> 
> With your patch, mouse can be plugged anywhere, it won't complain about
> umass devices connected to front USB port, but it still doesn't play nice
> with devices on back ports during boot. If I connect storage device after
> boot, both mouse and storage devices work fine.
> 
> 
> Parts of dmesg with mouse connected to back and storage to front USB ports.
> Everything works.
> 
> usbus0: 12Mbps Full Speed USB v1.0
> (hw power) control head <= 0xcfef1e30
> (hw power) control head => 0x2329000
> usbus1: 12Mbps Full Speed USB v1.0
> (hw power) control head <= 0x4143000
> (hw power) control head => 0x4143000
> usbus2: 12Mbps Full Speed USB v1.0
> (hw power) control head <= 0x4186000
> (hw power) control head => 0x4186000
> usbus3: 12Mbps Full Speed USB v1.0
> (hw power) control head <= 0x41aa000
> (hw power) control head => 0x41aa000
> usbus4: 12Mbps Full Speed USB v1.0
> (hw power) control head <= 0x4201000
> (hw power) control head => 0x4201000
> usbus5: 480Mbps High Speed USB v2.0
> 
> ugen0.1: <ATI> at usbus0
> uhub0: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
> ugen1.1: <ATI> at usbus1
> uhub1: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
> ugen2.1: <ATI> at usbus2
> uhub2: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
> ugen3.1: <ATI> at usbus3
> uhub3: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
> ugen4.1: <ATI> at usbus4
> uhub4: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
> ugen5.1: <ATI> at usbus5
> uhub5: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus5
> Root mount waiting for: usbus5 usbus4 usbus3 usbus2 usbus1 usbus0
> uhub2: 2 ports with 2 removable, self powered
> uhub3: 2 ports with 2 removable, self powered
> uhub0: 2 ports with 2 removable, self powered
> uhub4: 2 ports with 2 removable, self powered
> uhub1: 2 ports with 2 removable, self powered
> Root mount waiting for: usbus5
> Root mount waiting for: usbus5
> Root mount waiting for: usbus5
> Root mount waiting for: usbus5
> uhub5: 10 ports with 10 removable, self powered
> Root mount waiting for: usbus5
> (hw power) control head <= 0x2329000
> (hw power) control head => 0x2329000
> ugen0.2: <Logitech> at usbus0
> ums0: <Logitech USB Gaming Mouse, class 0/0, rev 2.00/52.00, addr 2> on
>  usbus0 ums0: 16 buttons and [XYZ] coordinates ID=0
> uhid0: <Logitech USB Gaming Mouse, class 0/0, rev 2.00/52.00, addr 2> on
>  usbus0 (hw power) control head <= 0x2329000
> (hw power) control head => 0x2329000
> ugen5.2: <PQI> at usbus5
> umass0: <PQI PQI USB Flash Drive, class 0/0, rev 2.00/1.00, addr 2> on
>  usbus5 umass0:  SCSI over Bulk-Only; quirks = 0x0000
> Root mount waiting for: usbus5
> (hw power) control head <= 0x2329000
> (hw power) control head => 0x2329000
> umass0:1:0:-1: Attached to scbus1
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <Generic USB Flash Disk 0.00> Removable Direct Access SCSI-2 device
> da0: 40.000MB/s transfers
> da0: 1967MB (4030463 512 byte sectors: 255H 63S/T 250C)
> 
> 
> Connected another device to back USB port after booting was finished:
> 
> (hw power) control head <= 0x4143000
> (hw power) control head => 0x4143000
> ugen1.2: <CUSTT13> at usbus1
> umass1: <Mass Storage Interface> on usbus1
> umass1:  SCSI over Bulk-Only; quirks = 0x0000
> umass1:2:1:-1: Attached to scbus2
> (hw power) control head <= 0x4143000
> (hw power) control head => 0x4143000
> (hw power) control head <= 0x4143000
> (hw power) control head => 0x4143000
> (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
> (probe0:umass-sim1:1:0:0): CAM Status: SCSI Status Error
> (probe0:umass-sim1:1:0:0): SCSI Status: Check Condition
> (probe0:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0
> (probe0:umass-sim1:1:0:0): Not ready to ready change, medium may have
>  changed (probe0:umass-sim1:1:0:0): Retrying Command (per Sense Data)
> da1 at umass-sim1 bus 1 target 0 lun 0
> da1: <Agere MMCSD Storage 2.01> Removable Direct Access SCSI-0 device
> da1: 1.000MB/s transfers
> da1: 964MB (1974272 512 byte sectors: 64H 32S/T 964C)
> 
> 
> 
> Another dmesg, booting with storage device and mouse both connected to back
> USB ports. Mouse works, storage doesn't.
> 
> usbus0: 12Mbps Full Speed USB v1.0
> (hw power) control head <= 0xcfef1e30
> (hw power) control head => 0x2329000
> usbus1: 12Mbps Full Speed USB v1.0
> (hw power) control head <= 0xcfef1e40
> (hw power) control head => 0x4143000
> 
> <everything here is the same as in the dmesg above>
> 
> (hw power) control head <= 0x2329000
> (hw power) control head => 0x2329000
> ugen0.2: <Logitech> at usbus0
> ums0: <Logitech USB Gaming Mouse, class 0/0, rev 2.00/52.00, addr 2> on
>  usbus0 ums0: 16 buttons and [XYZ] coordinates ID=0
> uhid0: <Logitech USB Gaming Mouse, class 0/0, rev 2.00/52.00, addr 2> on
>  usbus0 (hw power) control head <= 0x2329000
> (hw power) control head => 0x2329000
> (hw power) control head <= 0x2329000
> (hw power) control head => 0x2329000
> (hw power) control head <= 0x4143000
> (hw power) control head => 0x4143000
> ugen1.2: <CUSTT13> at usbus1
> umass0: <Mass Storage Interface> on usbus1
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:1:0:-1: Attached to scbus1
> (hw power) control head <= 0x4143000
> (hw power) control head => 0x4143000
> <last two lines repeat 7 more times>
> 
> 
> If you need anything else, let me know.
> 
> And thanks for the patch.
> 
That slightly reminds, back earlier I had the board in a different case where 
the fron port showed some other (better but also not  useful) weirdness, 
propably something to do with the pinout chart. I don't remember exactly.

Also, it appears that you are using 1MB capable usb flash on front, 40MB/s at 
the rear port? That brings me to the idea, do you have legacy usb enabled in 
bios or not? Cause, when I disable, I get other head power values than with 
legacy enabled.

Legacy disabled:
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x3ed8000
(hw power) control head => 0x3ed8000
usbus1: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x3f28000
(hw power) control head => 0x3f28000
usbus2: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x3f84000
(hw power) control head => 0x3f84000
usbus3: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x3fc3000
(hw power) control head => 0x3fc3000
usbus4: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x2e02000
(hw power) control head => 0x2e02000

Legacy enabled was:
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0xcfef1690
(hw power) control head => 0x3edf000
usbus1: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x3f27000
(hw power) control head => 0x3f27000
usbus2: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x3f6f000
(hw power) control head => 0x3f6f000
usbus3: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x403a000
(hw power) control head => 0x403a000
usbus4: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x4083000
(hw power) control head => 0x4083000
usbus5: 480Mbps High Speed USB v2.0
From avg at icyb.net.ua  Thu Sep 24 06:38:41 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Thu Sep 24 06:38:53 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <op.u0r8ufux43o42p@klevas>
References: <4ABA36B1.9070706@icyb.net.ua> <op.u0r8ufux43o42p@klevas>
Message-ID: <4ABB13EC.3020202@icyb.net.ua>

on 25/09/2009 01:31 Andrius Mork?nas said the following:
> usbus0: 12Mbps Full Speed USB v1.0
> (hw power) control head <= 0xcfef1e30
> (hw power) control head => 0x2329000
> usbus1: 12Mbps Full Speed USB v1.0
> (hw power) control head <= 0xcfef1e40
> (hw power) control head => 0x4143000 

These were the messages that I looked for the most.

> If you need anything else, let me know.
> 
> And thanks for the patch.

Thank you very much for the testing and the detailed report!
Unfortunately I have no clue about the umass issue.
>From comparing attach after boot and attach during boot messages it seems that
USB part worked almost identical, it's the CAM part that didn't happen in the
second case.

BTW, how many ports do you have at the back?
If more than 2, could you please try connecting the mouse to a port that is not
connected to uhub0 (this could be verified with usbconfig)?
And then see if you still get a mouse attachment problem during boot?
(No other devices during boot please :-) to simplify the testcase.)

-- 
Andriy Gapon
From hinokind at gmail.com  Thu Sep 24 08:30:47 2009
From: hinokind at gmail.com (=?utf-8?B?QW5kcml1cyBNb3JrxatuYXM=?=)
Date: Thu Sep 24 08:30:59 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4ABB13EC.3020202@icyb.net.ua>
References: <4ABA36B1.9070706@icyb.net.ua> <op.u0r8ufux43o42p@klevas>
	<4ABB13EC.3020202@icyb.net.ua>
Message-ID: <op.u0q5xcco43o42p@klevas>

On Thu, 24 Sep 2009 09:38:36 +0300, Andriy Gapon <avg@icyb.net.ua> wrote:
> BTW, how many ports do you have at the back?
> If more than 2, could you please try connecting the mouse to a port that is not
> connected to uhub0 (this could be verified with usbconfig)?
> And then see if you still get a mouse attachment problem during boot?
> (No other devices during boot please :-) to simplify the testcase.)

If I have USB Legacy disabled, mouse works in any port (with or without your
patch). When USB Legacy is enabled, without your patch mouse only works if I
unplug and plug it into a different port after boot. With your patch it works
in any port and doesn't care about USB legacy stuff.

On Thu, 24 Sep 2009 09:22:28 +0300, Dorian B?ttner <dorian.buettner@gmx.de> wrote:
> Also, it appears that you are using 1MB capable usb flash on front, 40MB/s at
> the rear port? That brings me to the idea, do you have legacy usb enabled in
> bios or not? Cause, when I disable, I get other head power values than with
> legacy enabled.

I forgot to mention that my tests were done with USB legacy disabled. Now I
looked at the values with it enabled, but unlike in your case, the values are
the same in both cases.

-- 
Andrius
From hselasky at c2i.net  Thu Sep 24 14:51:12 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Sep 24 14:51:24 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4ABA36B1.9070706@icyb.net.ua>
References: <4ABA36B1.9070706@icyb.net.ua>
Message-ID: <200909241651.47850.hselasky@c2i.net>

On Wednesday 23 September 2009 16:54:41 Andriy Gapon wrote:
> If you have a system with SB600, SB700, etc chipset and you have problems
> with low speed USB devices attached during boot (keyboard, mouse), could
> you please try the following experimental patch and report back?
> I am primarily interested in the first several lines produced during boot
> with printfs that are introduced by the patch. Preferably in the context of
> surrounding USB-related dmesg messages. No need to report subsequent
> same-looking ever-repeating messages (if any).
>
> WARNING: this is an experimental patch, it is probably not even close to
> what a real fix could be, it might not fix the problem (but perhaps it
> would), it might introduce instabilities into OHCI driver and it is noisy
> (unconditional printf). The primary purpose of this patch is to gather
> information necessary for a real fix.
>
> Thank you!
>
> diff --git a/sys/dev/usb/controller/ohci.c b/sys/dev/usb/controller/ohci.c
> index 30592c1..fb6ba34 100644
> --- a/sys/dev/usb/controller/ohci.c
> +++ b/sys/dev/usb/controller/ohci.c
> @@ -247,8 +249,8 @@ reset:
>  	OWRITE4(sc, OHCI_INTERRUPT_ENABLE, sc->sc_eintrs | OHCI_MIE);
>  	/* switch on desired functional features */
>  	ctl = OREAD4(sc, OHCI_CONTROL);
> -	ctl &= ~(OHCI_CBSR_MASK | OHCI_LES | OHCI_HCFS_MASK | OHCI_IR);
> -	ctl |= OHCI_PLE | OHCI_IE | OHCI_CLE | OHCI_BLE |
> +	ctl &= ~(OHCI_CBSR_MASK | OHCI_LES | OHCI_HCFS_MASK | OHCI_IR | OHCI_CLE
> | OHCI_CLF);
> +	ctl |= OHCI_PLE | OHCI_IE | /*OHCI_CLE |*/ OHCI_BLE |
>  	    OHCI_RATIO_1_4 | OHCI_HCFS_OPERATIONAL;
>  	/* And finally start it! */
>  	OWRITE4(sc, OHCI_CONTROL, ctl);
> @@ -2727,8 +2729,17 @@ ohci_set_hw_power(struct usb_bus *bus)
>  	temp = OREAD4(sc, OHCI_CONTROL);
>  	temp &= ~(OHCI_PLE | OHCI_IE | OHCI_CLE | OHCI_BLE);
>
> -	if (flags & USB_HW_POWER_CONTROL)
> +	if (flags & USB_HW_POWER_CONTROL) {
> +		struct usb_page_search buf_res;
> +
> +		buf_res.physaddr = OREAD4(sc, OHCI_CONTROL_HEAD_ED);
> +		printf("(hw power) control head <= %p\n", (void*)buf_res.physaddr);
> +		usbd_get_page(&sc->sc_hw.ctrl_start_pc, 0, &buf_res);
> +		printf("(hw power) control head => %p\n", (void*)buf_res.physaddr);
> +		OWRITE4(sc, OHCI_CONTROL_HEAD_ED, buf_res.physaddr);
> +
>  		temp |= OHCI_CLE;
> +	}
>
>  	if (flags & USB_HW_POWER_BULK)
>  		temp |= OHCI_BLE;

Hi,

Your patch looks good. Send me the final version when it is ready and testers 
report OK. I will then review and commit it.

I think that if you need to reload the control head, you will also need to 
reload the other head list pointers? Could you check that?

--HPS
From avg at icyb.net.ua  Fri Sep 25 06:34:27 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Fri Sep 25 06:34:40 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <200909241651.47850.hselasky@c2i.net>
References: <4ABA36B1.9070706@icyb.net.ua>
	<200909241651.47850.hselasky@c2i.net>
Message-ID: <4ABC646D.4070604@icyb.net.ua>

on 24/09/2009 17:51 Hans Petter Selasky said the following:
> 
> Your patch looks good. Send me the final version when it is ready and testers 
> report OK. I will then review and commit it.
> 
> I think that if you need to reload the control head, you will also need to 
> reload the other head list pointers? Could you check that?

I am just thinking that maybe there is a more clever / proper approach to fixing
this.

I did some additional debugging, maybe you'd find this interesting.
First debugging setup:

diff --git a/sys/dev/usb/controller/ohci.c b/sys/dev/usb/controller/ohci.c
index fb6ba34..83cb4bb 100644
--- a/sys/dev/usb/controller/ohci.c
+++ b/sys/dev/usb/controller/ohci.c
@@ -80,6 +80,8 @@ __FBSDID("$FreeBSD$");
 #ifdef USB_DEBUG
 static int ohcidebug = 0;

+extern devclass_t ohci_devclass; /* XXX */
+
 SYSCTL_NODE(_hw_usb, OID_AUTO, ohci, CTLFLAG_RW, 0, "USB ohci");
 SYSCTL_INT(_hw_usb_ohci, OID_AUTO, debug, CTLFLAG_RW,
     &ohcidebug, 0, "ohci debug level");
@@ -227,9 +229,9 @@ reset:
 		return (USB_ERR_IOERROR);
 	}
 #ifdef USB_DEBUG
-	if (ohcidebug > 15) {
+//	if (ohcidebug > 15) {
 		ohci_dumpregs(sc);
-	}
+//	}
 #endif

 	/* The controller is now in SUSPEND state, we have 2ms to finish. */
@@ -286,8 +289,15 @@ reset:
 	}

 #ifdef USB_DEBUG
-	if (ohcidebug > 5) {
+//	if (ohcidebug > 5) {
 		ohci_dumpregs(sc);
+//	}
+	int unit = device_get_unit(sc->sc_dev);
+	if (unit != 0) {
+		DPRINTFN(0, "dump of ohci0 regs:\n");
+		sc = devclass_get_softc(ohci_devclass, 0);
+		if (sc != NULL)
+			ohci_dumpregs(sc);
 	}
 #endif
 	return (USB_ERR_NORMAL_COMPLETION);
diff --git a/sys/dev/usb/controller/ohci_pci.c b/sys/dev/usb/controller/ohci_pci.c
index 3be6e42..755a90b 100644
--- a/sys/dev/usb/controller/ohci_pci.c
+++ b/sys/dev/usb/controller/ohci_pci.c
@@ -400,7 +400,7 @@ static driver_t ohci_driver =
 	.size = sizeof(struct ohci_softc),
 };

-static devclass_t ohci_devclass;
+devclass_t ohci_devclass; /* XXX */

 DRIVER_MODULE(ohci, pci, ohci_driver, ohci_devclass, 0, 0);
 MODULE_DEPEND(ohci, usb, 1, 1, 1);


The idea is to always dump all HW regs just after reset, after HW programming
and additionally dump HW regs of ohci0 after each of the subsequent controllers
gets programmed.

So, now the results:
ohci0: <OHCI (generic) USB controller> mem 0xfe02e000-0xfe02efff irq 16 at
device 18.0 on pci0
ohci0: [ITHREAD]
ohci_dumpregs:540: ohci_dumpregs: rev=0x00000110 control=0x000000c0
command=0x00000000
ohci_dumpregs:544:                intrstat=0x00000040 intre=0x00000000
intrd=0x00000000
ohci_dumpregs:548:                hcca=0x00000000 percur=0x00000000
ctrlhd=0x00000000
ohci_dumpregs:552:                ctrlcur=0x00000000 bulkhd=0x00000000
bulkcur=0x00000000
ohci_dumpregs:556:                done=0x00000000 fmival=0x00002edf fmrem=0x00000000
ohci_dumpregs:560:                fmnum=0x00000000 perst=0x00000000
lsthrs=0x00000628
ohci_dumpregs:564:                desca=0x02000b03 descb=0x00000000 stat=0x00000000
ohci_dumpregs:567:                port1=0x00010301 port2=0x00000100
ohci_dumpregs:573:          HCCA: frame_number=0x0000 done_head=0x00000000
ohci_dumpregs:540: ohci_dumpregs: rev=0x00000110 control=0x000000af
command=0x00000000
ohci_dumpregs:544:                intrstat=0x00000044 intre=0x8000005a
intrd=0x8000005a
ohci_dumpregs:548:                hcca=0x0304b000 percur=0x00000000
ctrlhd=0x03082000
ohci_dumpregs:552:                ctrlcur=0x00000000 bulkhd=0x03083000
bulkcur=0x00000000
ohci_dumpregs:556:                done=0x00000000 fmival=0xa7782edf fmrem=0x800013dd
ohci_dumpregs:560:                fmnum=0x0000000d perst=0x00002a2f
lsthrs=0x00000628
ohci_dumpregs:564:                desca=0x02000b03 descb=0x00000000 stat=0x00000000
ohci_dumpregs:567:                port1=0x00010301 port2=0x00000100
ohci_dumpregs:573:          HCCA: frame_number=0x000e done_head=0x00000000
usbus0: <OHCI (generic) USB controller> on ohci0
ohci1: <OHCI (generic) USB controller> mem 0xfe02d000-0xfe02dfff irq 16 at
device 18.1 on pci0
ohci1: [ITHREAD]
ohci_dumpregs:540: ohci_dumpregs: rev=0x00000110 control=0x000000c0
command=0x00000000
ohci_dumpregs:544:                intrstat=0x00000000 intre=0x00000000
intrd=0x00000000
ohci_dumpregs:548:                hcca=0x00000000 percur=0x00000000
ctrlhd=0x00000000
ohci_dumpregs:552:                ctrlcur=0x00000000 bulkhd=0x00000000
bulkcur=0x00000000
ohci_dumpregs:556:                done=0x00000000 fmival=0x00002edf fmrem=0x00000000
ohci_dumpregs:560:                fmnum=0x00000000 perst=0x00000000
lsthrs=0x00000628
ohci_dumpregs:564:                desca=0x02000b03 descb=0x00000000 stat=0x00000000
ohci_dumpregs:567:                port1=0x00000100 port2=0x00000100
ohci_dumpregs:573:          HCCA: frame_number=0x0000 done_head=0x00000000
ohci_dumpregs:540: ohci_dumpregs: rev=0x00000110 control=0x000000af
command=0x00000000
ohci_dumpregs:544:                intrstat=0x00000004 intre=0x8000005a
intrd=0x8000005a
ohci_dumpregs:548:                hcca=0x030a8000 percur=0x00000000
ctrlhd=0x030a9000
ohci_dumpregs:552:                ctrlcur=0x00000000 bulkhd=0x030b1000
bulkcur=0x00000000
ohci_dumpregs:556:                done=0x00000000 fmival=0xa7782edf fmrem=0x800013d5
ohci_dumpregs:560:                fmnum=0x0000000d perst=0x00002a2f
lsthrs=0x00000628
ohci_dumpregs:564:                desca=0x02000b03 descb=0x00000000 stat=0x00000000
ohci_dumpregs:567:                port1=0x00000100 port2=0x00000100
ohci_dumpregs:573:          HCCA: frame_number=0x000e done_head=0x00000000
ohci_controller_init:297: dump of ohci0 regs:
ohci_dumpregs:540: ohci_dumpregs: rev=0x00000110 control=0x000000af
command=0x00000000
ohci_dumpregs:544:                intrstat=0x00000004 intre=0x8000005a
intrd=0x8000005a
ohci_dumpregs:548:                hcca=0x0304b000 percur=0x00000000
ctrlhd=0xbfdf1c50
ohci_dumpregs:552:                ctrlcur=0x00000000 bulkhd=0x03083000
bulkcur=0x00000000
ohci_dumpregs:556:                done=0xbfdf1ca0 fmival=0xa7782edf fmrem=0x80002e51
ohci_dumpregs:560:                fmnum=0x0000019f perst=0x00002a2f
lsthrs=0x00000628
ohci_dumpregs:564:                desca=0x02000b03 descb=0x00000000 stat=0x00000000
ohci_dumpregs:567:                port1=0x00000303 port2=0x00000100
ohci_dumpregs:573:          HCCA: frame_number=0x019f done_head=0x00000000

So, as expected, reset does clear the registers, programming does set them
correctly.
But as soon as we are done programming ohci1, ctrlhd of ohci0 gets re-programmed
to  0xbfdf1c50.

BTW, to answer your question, other lists seem to be unaffected, head/cur values
seem to be preserved intact. hcca register is also OK.

Not sure how to interpret this.
Either a timing issue, i.e. the register gets over-written some time after we
program it.
Or perhaps a bug in SMM code, i.e. when we generate an SMI (e.g. while doing
ohci1 takeover) SMM code erroneously writes something to ohci0 ctrlhead.
Or something else... :)

-- 
Andriy Gapon
From hselasky at c2i.net  Fri Sep 25 07:28:14 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Sep 25 07:28:26 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4ABC646D.4070604@icyb.net.ua>
References: <4ABA36B1.9070706@icyb.net.ua>
	<200909241651.47850.hselasky@c2i.net>
	<4ABC646D.4070604@icyb.net.ua>
Message-ID: <200909250928.51515.hselasky@c2i.net>

On Friday 25 September 2009 08:34:21 Andriy Gapon wrote:
> Not sure how to interpret this.

In ohci_controller_init() try to disable the 

DPRINTF("SMM active, request owner change\n");

part of the code for !(ohci_unit == 0) or (ohci_unit == 2) and see what 
happens.

Your clue might also indicate that we should request owner change for all 
OHCI's before resetting any of them. Possibly a BIOS bug!

--HPS
From avg at icyb.net.ua  Fri Sep 25 08:11:50 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Fri Sep 25 08:12:02 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4ABC7912.6070301@stillbilde.net>
References: <4ABA36B1.9070706@icyb.net.ua>	<200909241651.47850.hselasky@c2i.net>
	<4ABC646D.4070604@icyb.net.ua> <4ABC7912.6070301@stillbilde.net>
Message-ID: <4ABC7B3C.6090803@icyb.net.ua>

on 25/09/2009 11:02 Svein Skogen (listmail account) said the following:
> Andriy Gapon wrote:
>> on 24/09/2009 17:51 Hans Petter Selasky said the following:
> 
> *SNIP!*
> 
>> Not sure how to interpret this.
>> Either a timing issue, i.e. the register gets over-written some time after we
>> program it.
>> Or perhaps a bug in SMM code, i.e. when we generate an SMI (e.g. while doing
>> ohci1 takeover) SMM code erroneously writes something to ohci0 ctrlhead.
>> Or something else... :)
> 
> Could it be related to "USB Legacy Devices" in bios, and thus be the
> same problem that was discussed recently (regarding HZ larger than 1000)?
> 
> An usb-legacy setup might explain both the register-changing _AND_ the
> timing issue...

It very well could, but...

We do perform proper OHCI takeover, so we don't expect firmware to mess with the
controllers after it is finished.

Also, I personally have everything "USB legacy" disabled in my BIOS ("USB Legacy
Support", "USB Keyboard support", "USB Mouse support"). Although, Gigabyte BIOSes
are known to be sometimes smarter than they appear and to "autodetect" things when
they are explicitly turned off in settings.

Last point. Explaining is half the job. Fixing / working around is the other half.

P.S. I am not sure what "timing issue" you referred to.

-- 
Andriy Gapon
From svein-listmail at stillbilde.net  Fri Sep 25 08:18:06 2009
From: svein-listmail at stillbilde.net (Svein Skogen (listmail account))
Date: Fri Sep 25 08:18:13 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4ABC646D.4070604@icyb.net.ua>
References: <4ABA36B1.9070706@icyb.net.ua>	<200909241651.47850.hselasky@c2i.net>
	<4ABC646D.4070604@icyb.net.ua>
Message-ID: <4ABC7912.6070301@stillbilde.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andriy Gapon wrote:
> on 24/09/2009 17:51 Hans Petter Selasky said the following:

*SNIP!*

> 
> Not sure how to interpret this.
> Either a timing issue, i.e. the register gets over-written some time after we
> program it.
> Or perhaps a bug in SMM code, i.e. when we generate an SMI (e.g. while doing
> ohci1 takeover) SMM code erroneously writes something to ohci0 ctrlhead.
> Or something else... :)

Could it be related to "USB Legacy Devices" in bios, and thus be the
same problem that was discussed recently (regarding HZ larger than 1000)?

An usb-legacy setup might explain both the register-changing _AND_ the
timing issue...

//Svein

- --
- --------+-------------------+-------------------------------
  /"\   |Svein Skogen       | svein@d80.iso100.no
  \ /   |Solberg ?stli 9    | PGP Key:  0xE5E76831
   X    |2020 Skedsmokorset | svein@jernhuset.no
  / \   |Norway             | PGP Key:  0xCE96CE13
        |                   | svein@stillbilde.net
 ascii  |                   | PGP Key:  0x58CD33B6
 ribbon |System Admin       | svein-listmail@stillbilde.net
Campaign|stillbilde.net     | PGP Key:  0x22D494A4
        +-------------------+-------------------------------
        |msn messenger:     | Mobile Phone: +47 907 03 575
        |svein@jernhuset.no | RIPE handle:    SS16503-RIPE
- --------+-------------------+-------------------------------
         If you really are in a hurry, mail me at
               svein-mobile@stillbilde.net
 This mailbox goes directly to my cellphone and is checked
        even when I'm not in front of my computer.
- ------------------------------------------------------------
                     Picture Gallery:
          https://gallery.stillbilde.net/v/svein/
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq8eREACgkQODUnwSLUlKS6QgCeM/4e26Hs8VeBnfySo/cKpxNQ
RYsAnA6Cu72Rb4by0VTQ98DwLURdaZ79
=Urht
-----END PGP SIGNATURE-----
From svein-listmail at stillbilde.net  Fri Sep 25 08:22:24 2009
From: svein-listmail at stillbilde.net (Svein Skogen (listmail account))
Date: Fri Sep 25 08:22:36 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4ABC7B3C.6090803@icyb.net.ua>
References: <4ABA36B1.9070706@icyb.net.ua>	<200909241651.47850.hselasky@c2i.net>	<4ABC646D.4070604@icyb.net.ua>
	<4ABC7912.6070301@stillbilde.net> <4ABC7B3C.6090803@icyb.net.ua>
Message-ID: <4ABC7DBF.30607@stillbilde.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andriy Gapon wrote:
> on 25/09/2009 11:02 Svein Skogen (listmail account) said the following:
>> Andriy Gapon wrote:
>>> on 24/09/2009 17:51 Hans Petter Selasky said the following:
>> *SNIP!*
>>
>>> Not sure how to interpret this.
>>> Either a timing issue, i.e. the register gets over-written some time after we
>>> program it.
>>> Or perhaps a bug in SMM code, i.e. when we generate an SMI (e.g. while doing
>>> ohci1 takeover) SMM code erroneously writes something to ohci0 ctrlhead.
>>> Or something else... :)
>> Could it be related to "USB Legacy Devices" in bios, and thus be the
>> same problem that was discussed recently (regarding HZ larger than 1000)?
>>
>> An usb-legacy setup might explain both the register-changing _AND_ the
>> timing issue...
> 
> It very well could, but...
> 
> We do perform proper OHCI takeover, so we don't expect firmware to mess with the
> controllers after it is finished.
> 
> Also, I personally have everything "USB legacy" disabled in my BIOS ("USB Legacy
> Support", "USB Keyboard support", "USB Mouse support"). Although, Gigabyte BIOSes
> are known to be sometimes smarter than they appear and to "autodetect" things when
> they are explicitly turned off in settings.
> 
> Last point. Explaining is half the job. Fixing / working around is the other half.
> 
> P.S. I am not sure what "timing issue" you referred to.

http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/051812.html

//Svein

- --
- --------+-------------------+-------------------------------
  /"\   |Svein Skogen       | svein@d80.iso100.no
  \ /   |Solberg ?stli 9    | PGP Key:  0xE5E76831
   X    |2020 Skedsmokorset | svein@jernhuset.no
  / \   |Norway             | PGP Key:  0xCE96CE13
        |                   | svein@stillbilde.net
 ascii  |                   | PGP Key:  0x58CD33B6
 ribbon |System Admin       | svein-listmail@stillbilde.net
Campaign|stillbilde.net     | PGP Key:  0x22D494A4
        +-------------------+-------------------------------
        |msn messenger:     | Mobile Phone: +47 907 03 575
        |svein@jernhuset.no | RIPE handle:    SS16503-RIPE
- --------+-------------------+-------------------------------
         If you really are in a hurry, mail me at
               svein-mobile@stillbilde.net
 This mailbox goes directly to my cellphone and is checked
        even when I'm not in front of my computer.
- ------------------------------------------------------------
                     Picture Gallery:
          https://gallery.stillbilde.net/v/svein/
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq8fb8ACgkQODUnwSLUlKSqXQCgiIvShHz0AoLx7U5M3v29hgHc
5egAnjdPqAQdWeVxx26oZiKxXdLsW0vl
=hcEc
-----END PGP SIGNATURE-----
From doconnor at gsoft.com.au  Fri Sep 25 09:47:30 2009
From: doconnor at gsoft.com.au (Daniel O'Connor)
Date: Fri Sep 25 09:47:37 2009
Subject: sb600/sb700 ohci experimental patch
Message-ID: <200909251842.08223.doconnor@gsoft.com.au>

This patch works for me, I get..

usbus0: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0xcfdf1c50
(hw power) control head => 0x3f7a000
usbus1: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x3dd6000
(hw power) control head => 0x3dd6000
usbus2: 480Mbps High Speed USB v2.0
usbus3: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x2961000
(hw power) control head => 0x2961000
usbus4: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x29a9000
(hw power) control head => 0x29a9000
usbus5: 480Mbps High Speed USB v2.0
usbus6: 12Mbps Full Speed USB v1.0
(hw power) control head <= 0x41de000
(hw power) control head => 0x41de000
...
uhub2: 6 ports with 6 removable, self powered
uhub5: 6 ports with 6 removable, self powered
(hw power) control head <= 0x3f7a000
(hw power) control head => 0x3f7a000
ugen0.2: <Logitech> at usbus0
ums0: <Logitech USB-PS/2 Optical Mouse, class 0/0, rev 2.00/27.30, addr 2> on usbus0
ums0: 8 buttons and [XYZ] coordinates ID=0
(hw power) control head <= 0x3f7a000
(hw power) control head => 0x3f7a000
(hw power) control head <= 0x3f7a000
(hw power) control head => 0x3f7a000
(hw power) control head <= 0x3f7a000
(hw power) control head => 0x3f7a000

Thanks! :)

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090925/c5ee4702/attachment.pgp
From gtodd at bellanet.org  Fri Sep 25 16:20:04 2009
From: gtodd at bellanet.org (Graham Todd)
Date: Fri Sep 25 16:20:09 2009
Subject: usb/79269: [ohci] USB ohci da0 plug/unplug causes crashes and
 lockups.
Message-ID: <200909251620.n8PGK3Gn096604@freefall.freebsd.org>

The following reply was made to PR usb/79269; it has been noted by GNATS.

From: Graham Todd <gtodd@bellanet.org>
To: bug-followup@FreeBSD.org, murray_baker@ihug.com.au
Cc:  
Subject: Re: usb/79269: [ohci] USB ohci da0 plug/unplug causes crashes and
 lockups.
Date: Fri, 25 Sep 2009 12:12:41 -0400

 At least one release with improvements in USB robustness has occurred 
 since the report. As well, the FreeBSD Foundation sponsored project to 
 fix the long standing USB mass storage panic.
 
 Is this bug a duplicate of usb/46176? Can it be closed?
From hselasky at freebsd.org  Fri Sep 25 17:08:52 2009
From: hselasky at freebsd.org (Hans Petter Selasky)
Date: Fri Sep 25 17:09:13 2009
Subject: Polling support for USB serial port adapters
Message-ID: <200909251909.31503.hselasky@freebsd.org>

Hi,

At EuroBSDcon 2009 I was requested to add support for polling mode to the USB 
serial port adapters alike UKBD and UMASS.

Which USB serial port adapters should have this support at first? And I also 
need someone to volunteers testing this!

--HPS

From ed at 80386.nl  Fri Sep 25 17:26:55 2009
From: ed at 80386.nl (Ed Schouten)
Date: Fri Sep 25 17:28:07 2009
Subject: Polling support for USB serial port adapters
In-Reply-To: <200909251909.31503.hselasky@freebsd.org>
References: <200909251909.31503.hselasky@freebsd.org>
Message-ID: <20090925172653.GT95398@hoeg.nl>

Hi Hans,

* Hans Petter Selasky <hselasky@freebsd.org> wrote:
> At EuroBSDcon 2009 I was requested to add support for polling mode to the USB 
> serial port adapters alike UKBD and UMASS.
> 
> Which USB serial port adapters should have this support at first? And I also 
> need someone to volunteers testing this!

I guess uplcom and uftdi are the most common ones, right?

-- 
 Ed Schouten <ed@80386.nl>
 WWW: http://80386.nl/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090925/323c5408/attachment.pgp
From mike at sentex.net  Fri Sep 25 18:36:13 2009
From: mike at sentex.net (Mike Tancsa)
Date: Fri Sep 25 18:36:26 2009
Subject: Polling support for USB serial port adapters
In-Reply-To: <200909251909.31503.hselasky@freebsd.org>
References: <200909251909.31503.hselasky@freebsd.org>
Message-ID: <200909251832.n8PIWSoZ013693@lava.sentex.ca>

At 01:09 PM 9/25/2009, Hans Petter Selasky wrote:
>Hi,
>
>At EuroBSDcon 2009 I was requested to add support for polling mode to the USB
>serial port adapters alike UKBD and UMASS.
>
>Which USB serial port adapters should have this support at first? And I also
>need someone to volunteers testing this!

uftdi is the most common around here. I have a couple of 
manufacturers that I would be happy to try in some high speed and low 
speed apps.

         ---Mike 

From rink at FreeBSD.org  Fri Sep 25 18:53:24 2009
From: rink at FreeBSD.org (Rink Springer)
Date: Fri Sep 25 18:53:30 2009
Subject: Polling support for USB serial port adapters
In-Reply-To: <20090925172653.GT95398@hoeg.nl>
References: <200909251909.31503.hselasky@freebsd.org>
	<20090925172653.GT95398@hoeg.nl>
Message-ID: <20090925183403.GA6563@rink.nu>

On Fri, Sep 25, 2009 at 07:26:53PM +0200, Ed Schouten wrote:
> * Hans Petter Selasky <hselasky@freebsd.org> wrote:
> > At EuroBSDcon 2009 I was requested to add support for polling mode to the USB 
> > serial port adapters alike UKBD and UMASS.
> > 
> > Which USB serial port adapters should have this support at first? And I also 
> > need someone to volunteers testing this!
> 
> I guess uplcom and uftdi are the most common ones, right?

Yeah, these are very easy to obtain; in any case, I would start with
these.

Regards,

-- 
Rink P.W. Springer                                - http://rink.nu
"Beauty often seduces us on the road to truth."
- Dr. Wilson
From olivier at cochard.me  Fri Sep 25 20:40:02 2009
From: olivier at cochard.me (Olivier Cochard-Labbe)
Date: Fri Sep 25 20:40:09 2009
Subject: usb/139142: [regression] ehci drivers (NVIDIA nForce4 USB 2.0
	controller ) not working with 8.0-RC1
Message-ID: <200909252038.n8PKcEch066064@www.freebsd.org>


>Number:         139142
>Category:       usb
>Synopsis:       [regression] ehci drivers (NVIDIA nForce4 USB 2.0 controller ) not working with 8.0-RC1
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 25 20:40:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Olivier Cochard-Labbe
>Release:        8.0 RC1
>Organization:
FreeNAS/BSDRP
>Environment:
>Description:
I meet a problem since 8.0 Beta1 to 8.0-RC1 (amd64 and i386) on an Asus K8N4-E Deluxe motherboard:

During the kernel load, my system hang (no dump, no error message).
The last messages are (hand copy) in verbose mode:

ohci0: <OHCI (generic) USB controller> irq 21 at device 2.0 on pci0
ohci0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0x80000000
ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x80000000
ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 0 vector 49
ohci0: [MPSAFE]
ohci0: [ITHREAD]
usbus0: SMM does not respond, resetting
usbus0: reset timeout
ohci0: USB init failed
device_attach: ohci0 attach returned 6
ehci0: <NVIDIA nForce4 USB 2.0 controller> irq 22 at device 2.1 on pci0
ehci0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0x80000000
ehci0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0x80000000
ioapci0: routing intpin 22 (PCI IRQ 22) to lapic 0 vector 49
ehci0: [MPSAFE]
ehci0: [ITHREAD]

If I disable the USB 2.0 controller in the BIOS: The system can
continue to load the kernel.

The ehci drivers works great with FreeBSD 7.2: The file attached include the dmesg and pciconf -lv under FreeBSD 7.2.

Thanks,
>How-To-Repeat:
Using 8.0-RC1 on an Asus K8N4-E Delux motherboard
>Fix:
Disable USB 2.0 controller in the BIOS.

Patch attached with submission follows:

[olivier@dev64]~>dmesg
Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009
    root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3000+ (2010.31-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x20fc2  Stepping = 2
  Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
  Features2=0x1<SSE3>
  AMD Features=0xe2500800<SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow!>
  AMD Features2=0x1<LAHF>
usable memory = 2134417408 (2035 MB)
avail memory  = 2058027008 (1962 MB)
ACPI APIC Table: <Nvidia AWRDACPI>
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: <Nvidia AWRDACPI> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 7fef0000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <memory> at device 0.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 1.1 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xd3003000-0xd3003fff irq 21 at device 2.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 10 ports with 10 removable, self powered
atapci0: <nVidia nForce CK804 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
atapci1: <nVidia nForce CK804 SATA300 controller> port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xd3002000-0xd3002fff irq 22 at device 7.0 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
atapci2: <nVidia nForce CK804 SATA300 controller> port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xd3001000-0xd3001fff irq 23 at device 8.0 on pci0
atapci2: [ITHREAD]
ata4: <ATA channel 0> on atapci2
ata4: [ITHREAD]
ata5: <ATA channel 1> on atapci2
ata5: [ITHREAD]
pcib1: <ACPI PCI-PCI bridge> at device 9.0 on pci0
pci5: <ACPI PCI bus> on pcib1
nfe0: <NVIDIA nForce4 CK804 MCP9 Networking Adapter> port 0xb000-0xb007 mem 0xd3000000-0xd3000fff irq 21 at device 10.0 on pci0
miibus0: <MII bus> on nfe0
e1000phy0: <Marvell 88E1111 Gigabit PHY> PHY 15 on miibus0
e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
nfe0: Ethernet address: 00:13:d4:d6:3a:7b
nfe0: [FILTER]
pcib2: <ACPI PCI-PCI bridge> at device 11.0 on pci0
pci4: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> at device 12.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 13.0 on pci0
pci2: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> at device 14.0 on pci0
pci1: <ACPI PCI bus> on pcib5
vgapci0: <VGA-compatible display> mem 0xd0000000-0xd0ffffff,0xc0000000-0xcfffffff,0xd1000000-0xd1ffffff irq 18 at device 0.0 on pci1
acpi_tz0: <Thermal Zone> on acpi0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio0: [FILTER]
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
powernow0: <Cool`n'Quiet K8> on cpu0
orm0: <ISA Option ROM> at iomem 0xd0000-0xd3fff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
ppc0: cannot reserve I/O port range
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
uhub1: <BTC USB Keyboard, class 9/0, rev 1.10/0.03, addr 2> on uhub0
uhub1: 2 ports with 1 removable, bus powered
ukbd0: <BTC USB Keyboard, class 0/0, rev 1.10/0.03, addr 3> on uhub1
kbd2 at ukbd0
uhid0: <BTC USB Keyboard, class 0/0, rev 1.10/0.03, addr 3> on uhub1
ums0: <vendor 0x04b3 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 4> on uhub1
ums0: 3 buttons and Z dir.
Timecounter "TSC" frequency 2010312369 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 286168MB <SAMSUNG HD300LD WK100-12> at ata0-master UDMA100
ad8: 953869MB <SAMSUNG HD103UJ 1AA01113> at ata4-master SATA150
GEOM: ad0: the secondary GPT table is corrupt or invalid.
GEOM: ad0: using the primary only -- recovery suggested.
GEOM_LABEL: Label for provider ad0p1 is ufsid/477f45096d16161b.
GEOM_LABEL: Label for provider ad0p1 is ufs/Disque1.
GEOM_LABEL: Label for provider ad0s1a is ufsid/4a675b954a5764b7.
GEOM_LABEL: Label for provider ad8p1 is ufsid/499c8ec590cbe4cd.
GEOM_LABEL: Label for provider ad8p1 is ufs/1TB3.
Trying to mount root from ufs:/dev/ad0s1a
GEOM_LABEL: Label ufs/Disque1 removed.
GEOM_LABEL: Label ufsid/477f45096d16161b removed.
GEOM_LABEL: Label ufsid/4a675b954a5764b7 removed.
GEOM_LABEL: Label for provider ad0s1a is ufsid/4a675b954a5764b7.
GEOM_LABEL: Label ufsid/4a675b954a5764b7 removed.
GEOM_LABEL: Label ufsid/499c8ec590cbe4cd removed.
WARNING: /mnt was not properly dismounted
kqemu version 0x00010400
kqemu: KQEMU installed, max_locked_mem=1042196kB.
[olivier@dev64]~>pciconf -lv
none0@pci0:0:0:0:	class=0x058000 card=0x815a1043 chip=0x005e10de rev=0xa3 hdr=0x00
    vendor     = 'Nvidia Corp'
    device     = 'nForce4 Memory Controller'
    class      = memory
isab0@pci0:0:1:0:	class=0x060100 card=0x815a1043 chip=0x005010de rev=0xa3 hdr=0x00
    vendor     = 'Nvidia Corp'
    device     = 'nForce4 PCI to ISA Bridge'
    class      = bridge
    subclass   = PCI-ISA
none1@pci0:0:1:1:	class=0x0c0500 card=0x815a1043 chip=0x005210de rev=0xa2 hdr=0x00
    vendor     = 'Nvidia Corp'
    device     = 'nForce4 SMBus'
    class      = serial bus
    subclass   = SMBus
ohci0@pci0:0:2:0:	class=0x0c0310 card=0x815a1043 chip=0x005a10de rev=0xa2 hdr=0x00
    vendor     = 'Nvidia Corp'
    device     = 'nForce4 USB Controller'
    class      = serial bus
    subclass   = USB
atapci0@pci0:0:6:0:	class=0x01018a card=0x815a1043 chip=0x005310de rev=0xf2 hdr=0x00
    vendor     = 'Nvidia Corp'
    device     = 'NVidia nForce 4 SLI IDE Controller'
    class      = mass storage
    subclass   = ATA
atapci1@pci0:0:7:0:	class=0x010185 card=0x815a1043 chip=0x005410de rev=0xf3 hdr=0x00
    vendor     = 'Nvidia Corp'
    device     = 'NVidia nForce 4 SLI IDE Controller'
    class      = mass storage
    subclass   = ATA
atapci2@pci0:0:8:0:	class=0x010185 card=0x815a1043 chip=0x005510de rev=0xf3 hdr=0x00
    vendor     = 'Nvidia Corp'
    device     = 'NVidia nForce 4 SLI IDE Controller'
    class      = mass storage
    subclass   = ATA
pcib1@pci0:0:9:0:	class=0x060401 card=0x00000000 chip=0x005c10de rev=0xa2 hdr=0x01
    vendor     = 'Nvidia Corp'
    device     = 'nForce4 PCI Bridge'
    class      = bridge
    subclass   = PCI-PCI
nfe0@pci0:0:10:0:	class=0x068000 card=0x81411043 chip=0x005710de rev=0xa3 hdr=0x00
    vendor     = 'Nvidia Corp'
    device     = 'nForce4 Ultra NVidia Network Bus Enumerator'
    class      = bridge
pcib2@pci0:0:11:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3 hdr=0x01
    vendor     = 'Nvidia Corp'
    device     = 'nForce4 PCIe Bridge'
    class      = bridge
    subclass   = PCI-PCI
pcib3@pci0:0:12:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3 hdr=0x01
    vendor     = 'Nvidia Corp'
    device     = 'nForce4 PCIe Bridge'
    class      = bridge
    subclass   = PCI-PCI
pcib4@pci0:0:13:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3 hdr=0x01
    vendor     = 'Nvidia Corp'
    device     = 'nForce4 PCIe Bridge'
    class      = bridge
    subclass   = PCI-PCI
pcib5@pci0:0:14:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3 hdr=0x01
    vendor     = 'Nvidia Corp'
    device     = 'nForce4 PCIe Bridge'
    class      = bridge
    subclass   = PCI-PCI
hostb0@pci0:0:24:0:	class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00
    vendor     = 'Advanced Micro Devices (AMD)'
    device     = '(K8) Athlon 64/Opteron HyperTransport Technology Configuration'
    class      = bridge
    subclass   = HOST-PCI
hostb1@pci0:0:24:1:	class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00
    vendor     = 'Advanced Micro Devices (AMD)'
    device     = '(K8) Athlon 64/Opteron Address Map'
    class      = bridge
    subclass   = HOST-PCI
hostb2@pci0:0:24:2:	class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00
    vendor     = 'Advanced Micro Devices (AMD)'
    device     = '(K8) Athlon 64/Opteron DRAM Controller'
    class      = bridge
    subclass   = HOST-PCI
hostb3@pci0:0:24:3:	class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00
    vendor     = 'Advanced Micro Devices (AMD)'
    device     = '(K8) Athlon 64/Opteron Miscellaneous Control'
    class      = bridge
    subclass   = HOST-PCI
vgapci0@pci0:1:0:0:	class=0x030000 card=0x00000000 chip=0x01d310de rev=0xa1 hdr=0x00
    vendor     = 'Nvidia Corp'
    device     = 'GeForce 7300 SE'
    class      = display
    subclass   = VGA



>Release-Note:
>Audit-Trail:
>Unformatted:
From wxs at FreeBSD.org  Fri Sep 25 21:28:21 2009
From: wxs at FreeBSD.org (Wesley Shields)
Date: Fri Sep 25 21:28:28 2009
Subject: Polling support for USB serial port adapters
In-Reply-To: <200909251909.31503.hselasky@freebsd.org>
References: <200909251909.31503.hselasky@freebsd.org>
Message-ID: <20090925211257.GA17421@atarininja.org>

On Fri, Sep 25, 2009 at 07:09:30PM +0200, Hans Petter Selasky wrote:
> Hi,
> 
> At EuroBSDcon 2009 I was requested to add support for polling mode to the USB 
> serial port adapters alike UKBD and UMASS.
> 
> Which USB serial port adapters should have this support at first? And I also 
> need someone to volunteers testing this!

I have a device I just plugged in for the first time ever and it is
apparently a uftdi device. I'd be willing to test any patches you have.

-- WXS
From spawk at acm.poly.edu  Fri Sep 25 23:42:10 2009
From: spawk at acm.poly.edu (Boris Kochergin)
Date: Fri Sep 25 23:42:16 2009
Subject: Polling support for USB serial port adapters
In-Reply-To: <200909251909.31503.hselasky@freebsd.org>
References: <200909251909.31503.hselasky@freebsd.org>
Message-ID: <4ABD4EDF.4040807@acm.poly.edu>

Hans Petter Selasky wrote:
> Hi,
>
> At EuroBSDcon 2009 I was requested to add support for polling mode to the USB 
> serial port adapters alike UKBD and UMASS.
>
> Which USB serial port adapters should have this support at first? And I also 
> need someone to volunteers testing this!
>
> --HPS
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>   
We have a bunch of uplcom adapters, and I can test patches.

-Boris
From gcr+freebsd-current at tharned.org  Sat Sep 26 02:56:10 2009
From: gcr+freebsd-current at tharned.org (Greg Rivers)
Date: Sat Sep 26 02:56:17 2009
Subject: Polling support for USB serial port adapters
In-Reply-To: <200909251909.31503.hselasky@freebsd.org>
References: <200909251909.31503.hselasky@freebsd.org>
Message-ID: <alpine.BSF.2.00.0909252112040.1307@blue.tharned.org>

On Fri, 25 Sep 2009, Hans Petter Selasky wrote:

> At EuroBSDcon 2009 I was requested to add support for polling mode to 
> the USB serial port adapters alike UKBD and UMASS.
>
> Which USB serial port adapters should have this support at first? And I 
> also need someone to volunteers testing this!
>

I'd be happy to test the umct driver that you repaired last week.  Thanks 
again for that.

I've been trying to use the recently added VirtualBox serial pass-through 
feature with the umct driver to allow a program running in a Windows guest 
OS to load data onto an old GPS, but no luck.  Might it be the lack of 
polling support that prevents this from working?

-- 
Greg Rivers
From eugen at kuzbass.ru  Sat Sep 26 04:53:20 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Sat Sep 26 04:53:27 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
Message-ID: <20090926042423.GA12216@svzserv.kemerovo.su>

Hi!

I have got fanless computer named NICE 3120,
it is based on EBC 420-LX8 motherboard and AMD Geode LX800 processor.

I've installed 8.0-RC1 here and it runs just fine as a router
using internal CompactFlash 256Mb card. Now I'm trying to use USB 2.0 HDD
<Seagate FreeAgent Go 102D> that gives me stable 27 megabyte/sec
write speed to /dev/da0 using dd when connected to another 8.0-RC1 system
with ICH7 but with this CS5536 its behavour is very strange.

"dd if=/dev/zero bs=256k of=/dev/da0 count=100" may result in 1.7MBytes/s
or 16Mbytes/s or 400Kbyte/s (sic!) write speed. dd measures speed right,
very often it writes way too slow.

"systat -vm 1" shows that most of time nothing is written in process;
then suddenly lots of bytes are written, then it sits idle again for long time.

As for timecounting,
kern.timecounter.choice: TSC(800) ACPI-safe(850) i8254(0) dummy(-1000000)

ACPI-safe is non-functional here (3 seconds for 30 minutes of real time),
so I use TSC, it works just fine. I've tried i8254 but found no differences.
Ntpd drift is about 148.331 for both of TSC and i8254 and
ntpd keeps time correct.

"pciconf -lv" shows for EHCI:

ehci0@pci0:0:15:5:      class=0x0c0320 card=0x20951022 chip=0x20951022          
rev=0x02 hdr=0x00                                                               
    vendor     = 'Advanced Micro Devices (AMD)'                                 
    device     = 'CS5536 EHCI USB Host Controller (CS5536)'                     
    class      = serial bus                                                     
    subclass   = USB


This machine is used as home router only and I'm ready to debug.
Remote access is available on request.

The kernel is built with options:

machine         i386        
cpu             I586_CPU    
cpu             I686_CPU    
options         NO_F00F_HACK
options         CPU_GEODE   
options         CPU_SOEKRIS 
options         SCHED_ULE   
options         PREEMPTION  

$ dmesg -a | fgrep -i Geode
CPU: Geode(TM) Integrated Processor by AMD PCS (499.90-MHz 586-class CPU)
glxsb0: <AMD Geode LX Security Block (AES-128-CBC, RNG)> mem 0xef010000-0xef013fff at device 1.2 on pci0
ehci0: <AMD CS5536 (Geode) USB 2.0 controller> mem 0xef018000-0xef018fff irq 10 at device 15.5 on pci0
usbus1: <AMD CS5536 (Geode) USB 2.0 controller> on ehci0

$ sysctl kern.timecounter
kern.timecounter.tick: 1
kern.timecounter.choice: TSC(800) ACPI-safe(850) i8254(0) dummy(-1000000)
kern.timecounter.hardware: TSC
kern.timecounter.stepwarnings: 0
kern.timecounter.tc.i8254.mask: 4294967295
kern.timecounter.tc.i8254.counter: 3806
kern.timecounter.tc.i8254.frequency: 1193182
kern.timecounter.tc.i8254.quality: 0
kern.timecounter.tc.ACPI-safe.mask: 16777215
kern.timecounter.tc.ACPI-safe.counter: 4294967295
kern.timecounter.tc.ACPI-safe.frequency: 3579545
kern.timecounter.tc.ACPI-safe.quality: 850
kern.timecounter.tc.TSC.mask: 4294967295
kern.timecounter.tc.TSC.counter: 1502810203
kern.timecounter.tc.TSC.frequency: 499904675
kern.timecounter.tc.TSC.quality: 800
kern.timecounter.invariant_tsc: 0

Please help.

Eugene Grosbein
From hselasky at c2i.net  Sat Sep 26 07:08:15 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Sep 26 07:08:21 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <20090926042423.GA12216@svzserv.kemerovo.su>
References: <20090926042423.GA12216@svzserv.kemerovo.su>
Message-ID: <200909260908.48389.hselasky@c2i.net>

On Saturday 26 September 2009 06:24:23 Eugene Grosbein wrote:
> Hi!
>
> I have got fanless computer named NICE 3120,
> it is based on EBC 420-LX8 motherboard and AMD Geode LX800 processor.
>
> I've installed 8.0-RC1 here and it runs just fine as a router
> using internal CompactFlash 256Mb card. Now I'm trying to use USB 2.0 HDD
> <Seagate FreeAgent Go 102D> that gives me stable 27 megabyte/sec
> write speed to /dev/da0 using dd when connected to another 8.0-RC1 system
> with ICH7 but with this CS5536 its behavour is very strange.
>
> "dd if=/dev/zero bs=256k of=/dev/da0 count=100" may result in 1.7MBytes/s
> or 16Mbytes/s or 400Kbyte/s (sic!) write speed. dd measures speed right,
> very often it writes way too slow.

Hi,

Try using bs=65536

Any difference.

Output from "usbconfig" would also be nice. Might sound like your device is 
sometimes connected at FULL speed.

Have you taken spin-up time into account?

--HPS
From hselasky at c2i.net  Sat Sep 26 07:16:09 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Sep 26 07:16:16 2009
Subject: usb/139142: [regression] ehci drivers (NVIDIA nForce4 USB 2.0
	controller ) not working with 8.0-RC1
In-Reply-To: <200909252038.n8PKcEch066064@www.freebsd.org>
References: <200909252038.n8PKcEch066064@www.freebsd.org>
Message-ID: <200909260916.45106.hselasky@c2i.net>

On Friday 25 September 2009 22:38:14 Olivier Cochard-Labbe wrote:
> >Number:         139142
> >Category:       usb
> >Synopsis:       [regression] ehci drivers (NVIDIA nForce4 USB 2.0
> > controller ) not working with 8.0-RC1 Confidential:   no
> >Severity:       serious
> >Priority:       low
> >Responsible:    freebsd-usb
> >State:          open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Fri Sep 25 20:40:02 UTC 2009
> >Closed-Date:
> >Last-Modified:
> >Originator:     Olivier Cochard-Labbe
> >Release:        8.0 RC1
> >Organization:
>
> FreeNAS/BSDRP
>
> >Environment:
> >Description:
>
> I meet a problem since 8.0 Beta1 to 8.0-RC1 (amd64 and i386) on an Asus
> K8N4-E Deluxe motherboard:
>
> During the kernel load, my system hang (no dump, no error message).
> The last messages are (hand copy) in verbose mode:
>
> ohci0: <OHCI (generic) USB controller> irq 21 at device 2.0 on pci0
> ohci0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0x80000000
> ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x80000000
> ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 0 vector 49
> ohci0: [MPSAFE]
> ohci0: [ITHREAD]
> usbus0: SMM does not respond, resetting
> usbus0: reset timeout
> ohci0: USB init failed
> device_attach: ohci0 attach returned 6
> ehci0: <NVIDIA nForce4 USB 2.0 controller> irq 22 at device 2.1 on pci0
> ehci0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0x80000000
> ehci0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0x80000000
> ioapci0: routing intpin 22 (PCI IRQ 22) to lapic 0 vector 49
> ehci0: [MPSAFE]
> ehci0: [ITHREAD]
>
> If I disable the USB 2.0 controller in the BIOS: The system can
> continue to load the kernel.
>
> The ehci drivers works great with FreeBSD 7.2: The file attached include
> the dmesg and pciconf -lv under FreeBSD 7.2.
>
> Thanks,
>
> >How-To-Repeat:
>
> Using 8.0-RC1 on an Asus K8N4-E Delux motherboard
>
> >Fix:
>
> Disable USB 2.0 controller in the BIOS.
>
> Patch attached with submission follows:
>
> [olivier@dev64]~>dmesg
> Copyright (c) 1992-2009 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> 	The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009
>     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: AMD Athlon(tm) 64 Processor 3000+ (2010.31-MHz K8-class CPU)
>   Origin = "AuthenticAMD"  Id = 0x20fc2  Stepping = 2
>  
> Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
>,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> Features2=0x1<SSE3>
>   AMD Features=0xe2500800<SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow!>
>   AMD Features2=0x1<LAHF>
> usable memory = 2134417408 (2035 MB)
> avail memory  = 2058027008 (1962 MB)
> ACPI APIC Table: <Nvidia AWRDACPI>
> ioapic0 <Version 1.1> irqs 0-23 on motherboard
> kbd1 at kbdmux0
> acpi0: <Nvidia AWRDACPI> on motherboard
> acpi0: [ITHREAD]
> acpi0: Power Button (fixed)
> acpi0: reservation of 0, a0000 (3) failed
> acpi0: reservation of 100000, 7fef0000 (3) failed
> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
> acpi_button0: <Power Button> on acpi0
> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> pci0: <ACPI PCI bus> on pcib0
> pci0: <memory> at device 0.0 (no driver attached)
> isab0: <PCI-ISA bridge> at device 1.0 on pci0
> isa0: <ISA bus> on isab0
> pci0: <serial bus, SMBus> at device 1.1 (no driver attached)
> ohci0: <OHCI (generic) USB controller> mem 0xd3003000-0xd3003fff irq 21 at
> device 2.0 on pci0 ohci0: [GIANT-LOCKED]
> ohci0: [ITHREAD]
> usb0: OHCI version 1.0, legacy support
> usb0: SMM does not respond, resetting
> usb0: <OHCI (generic) USB controller> on ohci0
> usb0: USB revision 1.0
> uhub0: <nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
> uhub0: 10 ports with 10 removable, self powered
> atapci0: <nVidia nForce CK804 UDMA133 controller> port
> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0
> ata0: <ATA channel 0> on atapci0
> ata0: [ITHREAD]
> ata1: <ATA channel 1> on atapci0
> ata1: [ITHREAD]
> atapci1: <nVidia nForce CK804 SATA300 controller> port
> 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem
> 0xd3002000-0xd3002fff irq 22 at device 7.0 on pci0 atapci1: [ITHREAD]
> ata2: <ATA channel 0> on atapci1
> ata2: [ITHREAD]
> ata3: <ATA channel 1> on atapci1
> ata3: [ITHREAD]
> atapci2: <nVidia nForce CK804 SATA300 controller> port
> 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem
> 0xd3001000-0xd3001fff irq 23 at device 8.0 on pci0 atapci2: [ITHREAD]
> ata4: <ATA channel 0> on atapci2
> ata4: [ITHREAD]
> ata5: <ATA channel 1> on atapci2
> ata5: [ITHREAD]
> pcib1: <ACPI PCI-PCI bridge> at device 9.0 on pci0
> pci5: <ACPI PCI bus> on pcib1
> nfe0: <NVIDIA nForce4 CK804 MCP9 Networking Adapter> port 0xb000-0xb007 mem
> 0xd3000000-0xd3000fff irq 21 at device 10.0 on pci0 miibus0: <MII bus> on
> nfe0
> e1000phy0: <Marvell 88E1111 Gigabit PHY> PHY 15 on miibus0
> e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX,
> auto nfe0: Ethernet address: 00:13:d4:d6:3a:7b
> nfe0: [FILTER]
> pcib2: <ACPI PCI-PCI bridge> at device 11.0 on pci0
> pci4: <ACPI PCI bus> on pcib2
> pcib3: <ACPI PCI-PCI bridge> at device 12.0 on pci0
> pci3: <ACPI PCI bus> on pcib3
> pcib4: <ACPI PCI-PCI bridge> at device 13.0 on pci0
> pci2: <ACPI PCI bus> on pcib4
> pcib5: <ACPI PCI-PCI bridge> at device 14.0 on pci0
> pci1: <ACPI PCI bus> on pcib5
> vgapci0: <VGA-compatible display> mem
> 0xd0000000-0xd0ffffff,0xc0000000-0xcfffffff,0xd1000000-0xd1ffffff irq 18 at
> device 0.0 on pci1 acpi_tz0: <Thermal Zone> on acpi0
> sio0: configured irq 4 not in bitmap of probed irqs 0
> sio0: port may not be enabled
> sio0: configured irq 4 not in bitmap of probed irqs 0
> sio0: port may not be enabled
> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
> acpi0 sio0: type 16550A
> sio0: [FILTER]
> cpu0: <ACPI CPU> on acpi0
> acpi_throttle0: <ACPI CPU Throttling> on cpu0
> powernow0: <Cool`n'Quiet K8> on cpu0
> orm0: <ISA Option ROM> at iomem 0xd0000-0xd3fff on isa0
> atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
> atkbd0: <AT Keyboard> irq 1 on atkbdc0
> kbd0 at atkbd0
> atkbd0: [GIANT-LOCKED]
> atkbd0: [ITHREAD]
> ppc0: cannot reserve I/O port range
> sc0: <System console> at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x300>
> sio1: configured irq 3 not in bitmap of probed irqs 0
> sio1: port may not be enabled
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> uhub1: <BTC USB Keyboard, class 9/0, rev 1.10/0.03, addr 2> on uhub0
> uhub1: 2 ports with 1 removable, bus powered
> ukbd0: <BTC USB Keyboard, class 0/0, rev 1.10/0.03, addr 3> on uhub1
> kbd2 at ukbd0
> uhid0: <BTC USB Keyboard, class 0/0, rev 1.10/0.03, addr 3> on uhub1
> ums0: <vendor 0x04b3 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 4>
> on uhub1 ums0: 3 buttons and Z dir.
> Timecounter "TSC" frequency 2010312369 Hz quality 800
> Timecounters tick every 1.000 msec
> ad0: 286168MB <SAMSUNG HD300LD WK100-12> at ata0-master UDMA100
> ad8: 953869MB <SAMSUNG HD103UJ 1AA01113> at ata4-master SATA150
> GEOM: ad0: the secondary GPT table is corrupt or invalid.
> GEOM: ad0: using the primary only -- recovery suggested.
> GEOM_LABEL: Label for provider ad0p1 is ufsid/477f45096d16161b.
> GEOM_LABEL: Label for provider ad0p1 is ufs/Disque1.
> GEOM_LABEL: Label for provider ad0s1a is ufsid/4a675b954a5764b7.
> GEOM_LABEL: Label for provider ad8p1 is ufsid/499c8ec590cbe4cd.
> GEOM_LABEL: Label for provider ad8p1 is ufs/1TB3.
> Trying to mount root from ufs:/dev/ad0s1a
> GEOM_LABEL: Label ufs/Disque1 removed.
> GEOM_LABEL: Label ufsid/477f45096d16161b removed.
> GEOM_LABEL: Label ufsid/4a675b954a5764b7 removed.
> GEOM_LABEL: Label for provider ad0s1a is ufsid/4a675b954a5764b7.
> GEOM_LABEL: Label ufsid/4a675b954a5764b7 removed.
> GEOM_LABEL: Label ufsid/499c8ec590cbe4cd removed.
> WARNING: /mnt was not properly dismounted
> kqemu version 0x00010400
> kqemu: KQEMU installed, max_locked_mem=1042196kB.
> [olivier@dev64]~>pciconf -lv
> none0@pci0:0:0:0:	class=0x058000 card=0x815a1043 chip=0x005e10de rev=0xa3
> hdr=0x00 vendor     = 'Nvidia Corp'
>     device     = 'nForce4 Memory Controller'
>     class      = memory
> isab0@pci0:0:1:0:	class=0x060100 card=0x815a1043 chip=0x005010de rev=0xa3
> hdr=0x00 vendor     = 'Nvidia Corp'
>     device     = 'nForce4 PCI to ISA Bridge'
>     class      = bridge
>     subclass   = PCI-ISA
> none1@pci0:0:1:1:	class=0x0c0500 card=0x815a1043 chip=0x005210de rev=0xa2
> hdr=0x00 vendor     = 'Nvidia Corp'
>     device     = 'nForce4 SMBus'
>     class      = serial bus
>     subclass   = SMBus
> ohci0@pci0:0:2:0:	class=0x0c0310 card=0x815a1043 chip=0x005a10de rev=0xa2
> hdr=0x00 vendor     = 'Nvidia Corp'
>     device     = 'nForce4 USB Controller'
>     class      = serial bus
>     subclass   = USB
> atapci0@pci0:0:6:0:	class=0x01018a card=0x815a1043 chip=0x005310de rev=0xf2
> hdr=0x00 vendor     = 'Nvidia Corp'
>     device     = 'NVidia nForce 4 SLI IDE Controller'
>     class      = mass storage
>     subclass   = ATA
> atapci1@pci0:0:7:0:	class=0x010185 card=0x815a1043 chip=0x005410de rev=0xf3
> hdr=0x00 vendor     = 'Nvidia Corp'
>     device     = 'NVidia nForce 4 SLI IDE Controller'
>     class      = mass storage
>     subclass   = ATA
> atapci2@pci0:0:8:0:	class=0x010185 card=0x815a1043 chip=0x005510de rev=0xf3
> hdr=0x00 vendor     = 'Nvidia Corp'
>     device     = 'NVidia nForce 4 SLI IDE Controller'
>     class      = mass storage
>     subclass   = ATA
> pcib1@pci0:0:9:0:	class=0x060401 card=0x00000000 chip=0x005c10de rev=0xa2
> hdr=0x01 vendor     = 'Nvidia Corp'
>     device     = 'nForce4 PCI Bridge'
>     class      = bridge
>     subclass   = PCI-PCI
> nfe0@pci0:0:10:0:	class=0x068000 card=0x81411043 chip=0x005710de rev=0xa3
> hdr=0x00 vendor     = 'Nvidia Corp'
>     device     = 'nForce4 Ultra NVidia Network Bus Enumerator'
>     class      = bridge
> pcib2@pci0:0:11:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3
> hdr=0x01 vendor     = 'Nvidia Corp'
>     device     = 'nForce4 PCIe Bridge'
>     class      = bridge
>     subclass   = PCI-PCI
> pcib3@pci0:0:12:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3
> hdr=0x01 vendor     = 'Nvidia Corp'
>     device     = 'nForce4 PCIe Bridge'
>     class      = bridge
>     subclass   = PCI-PCI
> pcib4@pci0:0:13:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3
> hdr=0x01 vendor     = 'Nvidia Corp'
>     device     = 'nForce4 PCIe Bridge'
>     class      = bridge
>     subclass   = PCI-PCI
> pcib5@pci0:0:14:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3
> hdr=0x01 vendor     = 'Nvidia Corp'
>     device     = 'nForce4 PCIe Bridge'
>     class      = bridge
>     subclass   = PCI-PCI
> hostb0@pci0:0:24:0:	class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00
> hdr=0x00 vendor     = 'Advanced Micro Devices (AMD)'
>     device     = '(K8) Athlon 64/Opteron HyperTransport Technology
> Configuration' class      = bridge
>     subclass   = HOST-PCI
> hostb1@pci0:0:24:1:	class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00
> hdr=0x00 vendor     = 'Advanced Micro Devices (AMD)'
>     device     = '(K8) Athlon 64/Opteron Address Map'
>     class      = bridge
>     subclass   = HOST-PCI
> hostb2@pci0:0:24:2:	class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00
> hdr=0x00 vendor     = 'Advanced Micro Devices (AMD)'
>     device     = '(K8) Athlon 64/Opteron DRAM Controller'
>     class      = bridge
>     subclass   = HOST-PCI
> hostb3@pci0:0:24:3:	class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00
> hdr=0x00 vendor     = 'Advanced Micro Devices (AMD)'
>     device     = '(K8) Athlon 64/Opteron Miscellaneous Control'
>     class      = bridge
>     subclass   = HOST-PCI
> vgapci0@pci0:1:0:0:	class=0x030000 card=0x00000000 chip=0x01d310de rev=0xa1
> hdr=0x00 vendor     = 'Nvidia Corp'
>     device     = 'GeForce 7300 SE'
>     class      = display
>     subclass   = VGA
>
> >Release-Note:
> >Audit-Trail:
> >Unformatted:

Have you tried only disabling USB Legacy support?

There is another USB related thread going on:

"sb600/sb700 ohci experimental patch" on -current.

Have you tried any patches from there?

diff --git a/sys/dev/usb/controller/ohci.c b/sys/dev/usb/controller/ohci.c
index 30592c1..fb6ba34 100644
--- a/sys/dev/usb/controller/ohci.c
+++ b/sys/dev/usb/controller/ohci.c
@@ -247,8 +249,8 @@ reset:
        OWRITE4(sc, OHCI_INTERRUPT_ENABLE, sc->sc_eintrs | OHCI_MIE);
        /* switch on desired functional features */
        ctl = OREAD4(sc, OHCI_CONTROL);
-       ctl &= ~(OHCI_CBSR_MASK | OHCI_LES | OHCI_HCFS_MASK | OHCI_IR);
-       ctl |= OHCI_PLE | OHCI_IE | OHCI_CLE | OHCI_BLE |
+       ctl &= ~(OHCI_CBSR_MASK | OHCI_LES | OHCI_HCFS_MASK | OHCI_IR | 
OHCI_CLE |
OHCI_CLF);
+       ctl |= OHCI_PLE | OHCI_IE | /*OHCI_CLE |*/ OHCI_BLE |
            OHCI_RATIO_1_4 | OHCI_HCFS_OPERATIONAL;
        /* And finally start it! */
        OWRITE4(sc, OHCI_CONTROL, ctl);
@@ -2727,8 +2729,17 @@ ohci_set_hw_power(struct usb_bus *bus)
        temp = OREAD4(sc, OHCI_CONTROL);
        temp &= ~(OHCI_PLE | OHCI_IE | OHCI_CLE | OHCI_BLE);

-       if (flags & USB_HW_POWER_CONTROL)
+       if (flags & USB_HW_POWER_CONTROL) {
+               struct usb_page_search buf_res;
+
+               buf_res.physaddr = OREAD4(sc, OHCI_CONTROL_HEAD_ED);
+               printf("(hw power) control head <= %p\n", 
(void*)buf_res.physaddr);
+               usbd_get_page(&sc->sc_hw.ctrl_start_pc, 0, &buf_res);
+               printf("(hw power) control head => %p\n", 
(void*)buf_res.physaddr);
+               OWRITE4(sc, OHCI_CONTROL_HEAD_ED, buf_res.physaddr);
+
                temp |= OHCI_CLE;
+       }

--HPS

From eugen at kuzbass.ru  Sat Sep 26 08:17:44 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Sat Sep 26 08:17:50 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <200909260908.48389.hselasky@c2i.net>
Message-ID: <20090926081733.GA24121@svzserv.kemerovo.su>

> Try using bs=65536
> Any difference.

Not better.

> Output from "usbconfig" would also be nice

%usbconfig
ugen0.1: <OHCI root HUB AMD> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen1.1: <EHCI root HUB AMD> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
ugen1.2: <FreeAgent Go Seagate> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON

HDD has only one cable connection, so it is powered from USB.

> Have you taken spin-up time into account?

I made severals tests in a row, speed varies greatly stiil.
And there is no such problem with ICH7-based system (975XBX motherboard).

Please CC: me as I'm not in list.

Eugene Grosbein
From hselasky at c2i.net  Sat Sep 26 08:20:06 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Sep 26 08:20:12 2009
Subject: usb/139142: [regression] ehci drivers (NVIDIA nForce4 USB 2.0
	controller ) not working with 8.0-RC1
Message-ID: <200909260820.n8Q8K5s3035639@freefall.freebsd.org>

The following reply was made to PR usb/139142; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: "Olivier Cochard-Labbe" <olivier@cochard.me>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/139142: [regression] ehci drivers (NVIDIA nForce4 USB 2.0 controller ) not working with 8.0-RC1
Date: Sat, 26 Sep 2009 09:16:43 +0200

 On Friday 25 September 2009 22:38:14 Olivier Cochard-Labbe wrote:
 > >Number:         139142
 > >Category:       usb
 > >Synopsis:       [regression] ehci drivers (NVIDIA nForce4 USB 2.0
 > > controller ) not working with 8.0-RC1 Confidential:   no
 > >Severity:       serious
 > >Priority:       low
 > >Responsible:    freebsd-usb
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Fri Sep 25 20:40:02 UTC 2009
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Olivier Cochard-Labbe
 > >Release:        8.0 RC1
 > >Organization:
 >
 > FreeNAS/BSDRP
 >
 > >Environment:
 > >Description:
 >
 > I meet a problem since 8.0 Beta1 to 8.0-RC1 (amd64 and i386) on an Asus
 > K8N4-E Deluxe motherboard:
 >
 > During the kernel load, my system hang (no dump, no error message).
 > The last messages are (hand copy) in verbose mode:
 >
 > ohci0: <OHCI (generic) USB controller> irq 21 at device 2.0 on pci0
 > ohci0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0x80000000
 > ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x80000000
 > ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 0 vector 49
 > ohci0: [MPSAFE]
 > ohci0: [ITHREAD]
 > usbus0: SMM does not respond, resetting
 > usbus0: reset timeout
 > ohci0: USB init failed
 > device_attach: ohci0 attach returned 6
 > ehci0: <NVIDIA nForce4 USB 2.0 controller> irq 22 at device 2.1 on pci0
 > ehci0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0x80000000
 > ehci0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0x80000000
 > ioapci0: routing intpin 22 (PCI IRQ 22) to lapic 0 vector 49
 > ehci0: [MPSAFE]
 > ehci0: [ITHREAD]
 >
 > If I disable the USB 2.0 controller in the BIOS: The system can
 > continue to load the kernel.
 >
 > The ehci drivers works great with FreeBSD 7.2: The file attached include
 > the dmesg and pciconf -lv under FreeBSD 7.2.
 >
 > Thanks,
 >
 > >How-To-Repeat:
 >
 > Using 8.0-RC1 on an Asus K8N4-E Delux motherboard
 >
 > >Fix:
 >
 > Disable USB 2.0 controller in the BIOS.
 >
 > Patch attached with submission follows:
 >
 > [olivier@dev64]~>dmesg
 > Copyright (c) 1992-2009 The FreeBSD Project.
 > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 > 	The Regents of the University of California. All rights reserved.
 > FreeBSD is a registered trademark of The FreeBSD Foundation.
 > FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009
 >     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
 > Timecounter "i8254" frequency 1193182 Hz quality 0
 > CPU: AMD Athlon(tm) 64 Processor 3000+ (2010.31-MHz K8-class CPU)
 >   Origin = "AuthenticAMD"  Id = 0x20fc2  Stepping = 2
 >  
 > Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
 >,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> Features2=0x1<SSE3>
 >   AMD Features=0xe2500800<SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow!>
 >   AMD Features2=0x1<LAHF>
 > usable memory = 2134417408 (2035 MB)
 > avail memory  = 2058027008 (1962 MB)
 > ACPI APIC Table: <Nvidia AWRDACPI>
 > ioapic0 <Version 1.1> irqs 0-23 on motherboard
 > kbd1 at kbdmux0
 > acpi0: <Nvidia AWRDACPI> on motherboard
 > acpi0: [ITHREAD]
 > acpi0: Power Button (fixed)
 > acpi0: reservation of 0, a0000 (3) failed
 > acpi0: reservation of 100000, 7fef0000 (3) failed
 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
 > acpi_button0: <Power Button> on acpi0
 > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
 > pci0: <ACPI PCI bus> on pcib0
 > pci0: <memory> at device 0.0 (no driver attached)
 > isab0: <PCI-ISA bridge> at device 1.0 on pci0
 > isa0: <ISA bus> on isab0
 > pci0: <serial bus, SMBus> at device 1.1 (no driver attached)
 > ohci0: <OHCI (generic) USB controller> mem 0xd3003000-0xd3003fff irq 21 at
 > device 2.0 on pci0 ohci0: [GIANT-LOCKED]
 > ohci0: [ITHREAD]
 > usb0: OHCI version 1.0, legacy support
 > usb0: SMM does not respond, resetting
 > usb0: <OHCI (generic) USB controller> on ohci0
 > usb0: USB revision 1.0
 > uhub0: <nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
 > uhub0: 10 ports with 10 removable, self powered
 > atapci0: <nVidia nForce CK804 UDMA133 controller> port
 > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0
 > ata0: <ATA channel 0> on atapci0
 > ata0: [ITHREAD]
 > ata1: <ATA channel 1> on atapci0
 > ata1: [ITHREAD]
 > atapci1: <nVidia nForce CK804 SATA300 controller> port
 > 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem
 > 0xd3002000-0xd3002fff irq 22 at device 7.0 on pci0 atapci1: [ITHREAD]
 > ata2: <ATA channel 0> on atapci1
 > ata2: [ITHREAD]
 > ata3: <ATA channel 1> on atapci1
 > ata3: [ITHREAD]
 > atapci2: <nVidia nForce CK804 SATA300 controller> port
 > 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem
 > 0xd3001000-0xd3001fff irq 23 at device 8.0 on pci0 atapci2: [ITHREAD]
 > ata4: <ATA channel 0> on atapci2
 > ata4: [ITHREAD]
 > ata5: <ATA channel 1> on atapci2
 > ata5: [ITHREAD]
 > pcib1: <ACPI PCI-PCI bridge> at device 9.0 on pci0
 > pci5: <ACPI PCI bus> on pcib1
 > nfe0: <NVIDIA nForce4 CK804 MCP9 Networking Adapter> port 0xb000-0xb007 mem
 > 0xd3000000-0xd3000fff irq 21 at device 10.0 on pci0 miibus0: <MII bus> on
 > nfe0
 > e1000phy0: <Marvell 88E1111 Gigabit PHY> PHY 15 on miibus0
 > e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX,
 > auto nfe0: Ethernet address: 00:13:d4:d6:3a:7b
 > nfe0: [FILTER]
 > pcib2: <ACPI PCI-PCI bridge> at device 11.0 on pci0
 > pci4: <ACPI PCI bus> on pcib2
 > pcib3: <ACPI PCI-PCI bridge> at device 12.0 on pci0
 > pci3: <ACPI PCI bus> on pcib3
 > pcib4: <ACPI PCI-PCI bridge> at device 13.0 on pci0
 > pci2: <ACPI PCI bus> on pcib4
 > pcib5: <ACPI PCI-PCI bridge> at device 14.0 on pci0
 > pci1: <ACPI PCI bus> on pcib5
 > vgapci0: <VGA-compatible display> mem
 > 0xd0000000-0xd0ffffff,0xc0000000-0xcfffffff,0xd1000000-0xd1ffffff irq 18 at
 > device 0.0 on pci1 acpi_tz0: <Thermal Zone> on acpi0
 > sio0: configured irq 4 not in bitmap of probed irqs 0
 > sio0: port may not be enabled
 > sio0: configured irq 4 not in bitmap of probed irqs 0
 > sio0: port may not be enabled
 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
 > acpi0 sio0: type 16550A
 > sio0: [FILTER]
 > cpu0: <ACPI CPU> on acpi0
 > acpi_throttle0: <ACPI CPU Throttling> on cpu0
 > powernow0: <Cool`n'Quiet K8> on cpu0
 > orm0: <ISA Option ROM> at iomem 0xd0000-0xd3fff on isa0
 > atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
 > atkbd0: <AT Keyboard> irq 1 on atkbdc0
 > kbd0 at atkbd0
 > atkbd0: [GIANT-LOCKED]
 > atkbd0: [ITHREAD]
 > ppc0: cannot reserve I/O port range
 > sc0: <System console> at flags 0x100 on isa0
 > sc0: VGA <16 virtual consoles, flags=0x300>
 > sio1: configured irq 3 not in bitmap of probed irqs 0
 > sio1: port may not be enabled
 > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 > uhub1: <BTC USB Keyboard, class 9/0, rev 1.10/0.03, addr 2> on uhub0
 > uhub1: 2 ports with 1 removable, bus powered
 > ukbd0: <BTC USB Keyboard, class 0/0, rev 1.10/0.03, addr 3> on uhub1
 > kbd2 at ukbd0
 > uhid0: <BTC USB Keyboard, class 0/0, rev 1.10/0.03, addr 3> on uhub1
 > ums0: <vendor 0x04b3 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 4>
 > on uhub1 ums0: 3 buttons and Z dir.
 > Timecounter "TSC" frequency 2010312369 Hz quality 800
 > Timecounters tick every 1.000 msec
 > ad0: 286168MB <SAMSUNG HD300LD WK100-12> at ata0-master UDMA100
 > ad8: 953869MB <SAMSUNG HD103UJ 1AA01113> at ata4-master SATA150
 > GEOM: ad0: the secondary GPT table is corrupt or invalid.
 > GEOM: ad0: using the primary only -- recovery suggested.
 > GEOM_LABEL: Label for provider ad0p1 is ufsid/477f45096d16161b.
 > GEOM_LABEL: Label for provider ad0p1 is ufs/Disque1.
 > GEOM_LABEL: Label for provider ad0s1a is ufsid/4a675b954a5764b7.
 > GEOM_LABEL: Label for provider ad8p1 is ufsid/499c8ec590cbe4cd.
 > GEOM_LABEL: Label for provider ad8p1 is ufs/1TB3.
 > Trying to mount root from ufs:/dev/ad0s1a
 > GEOM_LABEL: Label ufs/Disque1 removed.
 > GEOM_LABEL: Label ufsid/477f45096d16161b removed.
 > GEOM_LABEL: Label ufsid/4a675b954a5764b7 removed.
 > GEOM_LABEL: Label for provider ad0s1a is ufsid/4a675b954a5764b7.
 > GEOM_LABEL: Label ufsid/4a675b954a5764b7 removed.
 > GEOM_LABEL: Label ufsid/499c8ec590cbe4cd removed.
 > WARNING: /mnt was not properly dismounted
 > kqemu version 0x00010400
 > kqemu: KQEMU installed, max_locked_mem=1042196kB.
 > [olivier@dev64]~>pciconf -lv
 > none0@pci0:0:0:0:	class=0x058000 card=0x815a1043 chip=0x005e10de rev=0xa3
 > hdr=0x00 vendor     = 'Nvidia Corp'
 >     device     = 'nForce4 Memory Controller'
 >     class      = memory
 > isab0@pci0:0:1:0:	class=0x060100 card=0x815a1043 chip=0x005010de rev=0xa3
 > hdr=0x00 vendor     = 'Nvidia Corp'
 >     device     = 'nForce4 PCI to ISA Bridge'
 >     class      = bridge
 >     subclass   = PCI-ISA
 > none1@pci0:0:1:1:	class=0x0c0500 card=0x815a1043 chip=0x005210de rev=0xa2
 > hdr=0x00 vendor     = 'Nvidia Corp'
 >     device     = 'nForce4 SMBus'
 >     class      = serial bus
 >     subclass   = SMBus
 > ohci0@pci0:0:2:0:	class=0x0c0310 card=0x815a1043 chip=0x005a10de rev=0xa2
 > hdr=0x00 vendor     = 'Nvidia Corp'
 >     device     = 'nForce4 USB Controller'
 >     class      = serial bus
 >     subclass   = USB
 > atapci0@pci0:0:6:0:	class=0x01018a card=0x815a1043 chip=0x005310de rev=0xf2
 > hdr=0x00 vendor     = 'Nvidia Corp'
 >     device     = 'NVidia nForce 4 SLI IDE Controller'
 >     class      = mass storage
 >     subclass   = ATA
 > atapci1@pci0:0:7:0:	class=0x010185 card=0x815a1043 chip=0x005410de rev=0xf3
 > hdr=0x00 vendor     = 'Nvidia Corp'
 >     device     = 'NVidia nForce 4 SLI IDE Controller'
 >     class      = mass storage
 >     subclass   = ATA
 > atapci2@pci0:0:8:0:	class=0x010185 card=0x815a1043 chip=0x005510de rev=0xf3
 > hdr=0x00 vendor     = 'Nvidia Corp'
 >     device     = 'NVidia nForce 4 SLI IDE Controller'
 >     class      = mass storage
 >     subclass   = ATA
 > pcib1@pci0:0:9:0:	class=0x060401 card=0x00000000 chip=0x005c10de rev=0xa2
 > hdr=0x01 vendor     = 'Nvidia Corp'
 >     device     = 'nForce4 PCI Bridge'
 >     class      = bridge
 >     subclass   = PCI-PCI
 > nfe0@pci0:0:10:0:	class=0x068000 card=0x81411043 chip=0x005710de rev=0xa3
 > hdr=0x00 vendor     = 'Nvidia Corp'
 >     device     = 'nForce4 Ultra NVidia Network Bus Enumerator'
 >     class      = bridge
 > pcib2@pci0:0:11:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3
 > hdr=0x01 vendor     = 'Nvidia Corp'
 >     device     = 'nForce4 PCIe Bridge'
 >     class      = bridge
 >     subclass   = PCI-PCI
 > pcib3@pci0:0:12:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3
 > hdr=0x01 vendor     = 'Nvidia Corp'
 >     device     = 'nForce4 PCIe Bridge'
 >     class      = bridge
 >     subclass   = PCI-PCI
 > pcib4@pci0:0:13:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3
 > hdr=0x01 vendor     = 'Nvidia Corp'
 >     device     = 'nForce4 PCIe Bridge'
 >     class      = bridge
 >     subclass   = PCI-PCI
 > pcib5@pci0:0:14:0:	class=0x060400 card=0x00000000 chip=0x005d10de rev=0xa3
 > hdr=0x01 vendor     = 'Nvidia Corp'
 >     device     = 'nForce4 PCIe Bridge'
 >     class      = bridge
 >     subclass   = PCI-PCI
 > hostb0@pci0:0:24:0:	class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00
 > hdr=0x00 vendor     = 'Advanced Micro Devices (AMD)'
 >     device     = '(K8) Athlon 64/Opteron HyperTransport Technology
 > Configuration' class      = bridge
 >     subclass   = HOST-PCI
 > hostb1@pci0:0:24:1:	class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00
 > hdr=0x00 vendor     = 'Advanced Micro Devices (AMD)'
 >     device     = '(K8) Athlon 64/Opteron Address Map'
 >     class      = bridge
 >     subclass   = HOST-PCI
 > hostb2@pci0:0:24:2:	class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00
 > hdr=0x00 vendor     = 'Advanced Micro Devices (AMD)'
 >     device     = '(K8) Athlon 64/Opteron DRAM Controller'
 >     class      = bridge
 >     subclass   = HOST-PCI
 > hostb3@pci0:0:24:3:	class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00
 > hdr=0x00 vendor     = 'Advanced Micro Devices (AMD)'
 >     device     = '(K8) Athlon 64/Opteron Miscellaneous Control'
 >     class      = bridge
 >     subclass   = HOST-PCI
 > vgapci0@pci0:1:0:0:	class=0x030000 card=0x00000000 chip=0x01d310de rev=0xa1
 > hdr=0x00 vendor     = 'Nvidia Corp'
 >     device     = 'GeForce 7300 SE'
 >     class      = display
 >     subclass   = VGA
 >
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 
 Have you tried only disabling USB Legacy support?
 
 There is another USB related thread going on:
 
 "sb600/sb700 ohci experimental patch" on -current.
 
 Have you tried any patches from there?
 
 diff --git a/sys/dev/usb/controller/ohci.c b/sys/dev/usb/controller/ohci.c
 index 30592c1..fb6ba34 100644
 --- a/sys/dev/usb/controller/ohci.c
 +++ b/sys/dev/usb/controller/ohci.c
 @@ -247,8 +249,8 @@ reset:
         OWRITE4(sc, OHCI_INTERRUPT_ENABLE, sc->sc_eintrs | OHCI_MIE);
         /* switch on desired functional features */
         ctl = OREAD4(sc, OHCI_CONTROL);
 -       ctl &= ~(OHCI_CBSR_MASK | OHCI_LES | OHCI_HCFS_MASK | OHCI_IR);
 -       ctl |= OHCI_PLE | OHCI_IE | OHCI_CLE | OHCI_BLE |
 +       ctl &= ~(OHCI_CBSR_MASK | OHCI_LES | OHCI_HCFS_MASK | OHCI_IR | 
 OHCI_CLE |
 OHCI_CLF);
 +       ctl |= OHCI_PLE | OHCI_IE | /*OHCI_CLE |*/ OHCI_BLE |
             OHCI_RATIO_1_4 | OHCI_HCFS_OPERATIONAL;
         /* And finally start it! */
         OWRITE4(sc, OHCI_CONTROL, ctl);
 @@ -2727,8 +2729,17 @@ ohci_set_hw_power(struct usb_bus *bus)
         temp = OREAD4(sc, OHCI_CONTROL);
         temp &= ~(OHCI_PLE | OHCI_IE | OHCI_CLE | OHCI_BLE);
 
 -       if (flags & USB_HW_POWER_CONTROL)
 +       if (flags & USB_HW_POWER_CONTROL) {
 +               struct usb_page_search buf_res;
 +
 +               buf_res.physaddr = OREAD4(sc, OHCI_CONTROL_HEAD_ED);
 +               printf("(hw power) control head <= %p\n", 
 (void*)buf_res.physaddr);
 +               usbd_get_page(&sc->sc_hw.ctrl_start_pc, 0, &buf_res);
 +               printf("(hw power) control head => %p\n", 
 (void*)buf_res.physaddr);
 +               OWRITE4(sc, OHCI_CONTROL_HEAD_ED, buf_res.physaddr);
 +
                 temp |= OHCI_CLE;
 +       }
 
 --HPS
 
From hselasky at freebsd.org  Sat Sep 26 09:53:35 2009
From: hselasky at freebsd.org (Hans Petter Selasky)
Date: Sat Sep 26 09:53:42 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <20090926081733.GA24121@svzserv.kemerovo.su>
References: <20090926081733.GA24121@svzserv.kemerovo.su>
Message-ID: <200909261054.13174.hselasky@freebsd.org>

On Saturday 26 September 2009 10:17:33 Eugene Grosbein wrote:
> > Try using bs=65536
> > Any difference.
>
> Not better.
>
> > Output from "usbconfig" would also be nice
>
> %usbconfig
> ugen0.1: <OHCI root HUB AMD> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON ugen1.1: <EHCI root HUB AMD> at usbus1, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=ON ugen1.2: <FreeAgent Go Seagate> at usbus1, cfg=0 md=HOST
> spd=HIGH (480Mbps) pwr=ON
>
> HDD has only one cable connection, so it is powered from USB.
>
> > Have you taken spin-up time into account?
>
> I made severals tests in a row, speed varies greatly stiil.
> And there is no such problem with ICH7-based system (975XBX motherboard).

Hi,

Could you check if these are due to device timeouts in the CAM layer?

There is some debugging you can turn on:

sysctl hw.usb.umass.debug=-1

Probably it will flood the console. Maybe you could add some prints to 
/sys/dev/usb/storage/umass.c in all the "default:" cases in the USB callbacks 
and print out the "error" code. That would quickly indicate if your device has 
an issue with timing, I.E. that the firmware in the USB device part is 
hanging.

--HPS

From tom at tomjudge.com  Sat Sep 26 15:12:44 2009
From: tom at tomjudge.com (Tom Judge)
Date: Sat Sep 26 15:12:56 2009
Subject: Polling support for USB serial port adapters
In-Reply-To: <4ABD4EDF.4040807@acm.poly.edu>
References: <200909251909.31503.hselasky@freebsd.org>
	<4ABD4EDF.4040807@acm.poly.edu>
Message-ID: <4ABE2B4F.6080104@tomjudge.com>

Boris Kochergin wrote:
> Hans Petter Selasky wrote:
>> Hi,
>>
>> At EuroBSDcon 2009 I was requested to add support for polling mode to 
>> the USB serial port adapters alike UKBD and UMASS.
>>
>> Which USB serial port adapters should have this support at first? And 
>> I also need someone to volunteers testing this!
>>
>> --HPS
>>
>> _______________________________________________
>> freebsd-current@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to 
>> "freebsd-current-unsubscribe@freebsd.org"
>>   
> We have a bunch of uplcom adapters, and I can test patches.
>
> -Boris
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe@freebsd.org"
+1 for testing uplcom.

Tom
From pldrouin at pldrouin.net  Sun Sep 27 05:05:42 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Sun Sep 27 05:05:49 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <200909230851.03442.hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909221847.26679.hselasky@c2i.net>
	<4AB915CE.8090503@pldrouin.net>
	<200909230851.03442.hselasky@c2i.net>
Message-ID: <4ABEF2A6.6010801@pldrouin.net>

Hans Petter Selasky wrote:
> On Tuesday 22 September 2009 20:22:06 Pierre-Luc Drouin wrote:
>   
>> Hans Petter Selasky wrote:
>>     
>>> On Tuesday 22 September 2009 18:40:40 Pierre-Luc Drouin wrote:
>>>       
>>>> Hans Petter Selasky wrote:
>>>>         
>>>>> On Tuesday 22 September 2009 18:15:19 Pierre-Luc Drouin wrote:
>>>>>           
>>>>>> Hans Petter Selasky wrote:
>>>>>>             
>>>>>>> On Tuesday 22 September 2009 17:21:28 Pierre-Luc Drouin wrote:
>>>>>>>               
>>>>>>>>>> Thanks!
>>>>>>>>>>                     
>>>>>>>>> It indicates that your device is not sending any data.
>>>>>>>>>
>>>>>>>>> --HPS
>>>>>>>>>                   
>>>>>>>> So does it mean that the write statement (a status request) is not
>>>>>>>> transmitted to the device either?
>>>>>>>>                 
>>>>>>> No, the "xxx_get()" message means that the data you write is sent and
>>>>>>> transmitted.
>>>>>>>
>>>>>>> BTW: I have a FTDI adapter here, and it works fine with loopback when
>>>>>>> the baudrate is set correctly.
>>>>>>>
>>>>>>>               
>>>>>>>> Because this write statement should be
>>>>>>>> followed by data sent from the device and it effectively does on
>>>>>>>> Linux. And about SIGIO, shouldn't this signal be generated only when
>>>>>>>> there is data available to read? Why is it generated in asynchronous
>>>>>>>> mode and then the read statement returns EINTR?
>>>>>>>>                 
>>>>>>> Ed has to answer these questions. This stuff is not handled in the
>>>>>>> USB stack for FTDI devices.
>>>>>>>
>>>>>>> --HPS
>>>>>>>               
>>>>>> In the manual page for the uftdi driver, the chip I am using (FT232BL)
>>>>>> is not listed. According to the FTDI website, it is based on
>>>>>> FT8U232AM, but  it has extra functionalities. Have you had the chance
>>>>>> to test an device that uses either a FT232BM, FT232BL or FT232BQ chip?
>>>>>> I just tested the device on FreeBSD 7.2 and it does not work either...
>>>>>>             
>>>>> No, I haven't.
>>>>>
>>>>> --HPS
>>>>>           
>>>> Are there additional tests I can do in synchronous mode to try pinning
>>>> down the problem?
>>>>         
>>> Hi,
>>>
>>> If the device doesn't work, then there are probably some FTDI USB
>>> registers which are not programmed correctly.
>>>
>>> If you could debug that it would be great.
>>>
>>> --HPS
>>>       
>> ok, so yes I can probably try debugging the driver for the FT232BL chip,
>> but the support for my device's manufacturer is very limited, so it
>> might not be optimal to try doing debugging with that. Plus although I
>> do programming all day (statistical data analysis), I've never done
>> coding at the kernel level or driver programming, so I will need to get
>> familiar with it first.
>>     
>
> Don't worry about your coding skills. If you can add the code that makes it 
> working, I will fix the rest for you.
>
>   
>> Would something like
>> http://www.eurodesign.bg/eudesignbg/USB_RS232.html be the ideal tool for
>> debugging?
>>     
>
> I don't know ....
>
> --HPS
>   
Hi,

so I compared the control commands sent by uftdi to the ones sent by 
ftdio_sio (linux kernel module) and I tried different hacks to finally 
realize that the problem was that FreeBSD was not sending the right baud 
rate to the device. FreeBSD uses c_ospeed (in termios struct) to get the 
baud rate while Linux uses c_cflag. So I removed the baud rate from 
c_cflag in my code and I am now using cfsetispeed and cfsetospeed. I 
though the termios structure and flags were Posix but it looks like it's 
not :S.


So to conclude, it looks like uftdi is working fine :)

Thanks for the support!
From avg at icyb.net.ua  Sun Sep 27 12:18:05 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Sun Sep 27 12:18:17 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <200909250928.51515.hselasky@c2i.net>
References: <4ABA36B1.9070706@icyb.net.ua>
	<200909241651.47850.hselasky@c2i.net>
	<4ABC646D.4070604@icyb.net.ua>
	<200909250928.51515.hselasky@c2i.net>
Message-ID: <4ABF57F5.1050106@icyb.net.ua>

on 25/09/2009 10:28 Hans Petter Selasky said the following:
> On Friday 25 September 2009 08:34:21 Andriy Gapon wrote:
>> Not sure how to interpret this.
> 
> In ohci_controller_init() try to disable the 
> 
> DPRINTF("SMM active, request owner change\n");
> 
> part of the code for !(ohci_unit == 0) or (ohci_unit == 2) and see what 
> happens.
> 
> Your clue might also indicate that we should request owner change for all 
> OHCI's before resetting any of them. Possibly a BIOS bug!

Haven't tried the suggested changes yet, but here is some more info.
This is register dump of ohci0 just _before_ we start doing anything with it:

ohci0: <OHCI (generic) USB controller> mem 0xfe02e000-0xfe02efff irq 16 at
device 18.0 on pci0
ohci0: [ITHREAD]
ohci_dumpregs:567: ohci_dumpregs: rev=0x00000110 control=0x00000184
command=0x00000000
ohci_dumpregs:571:                intrstat=0x00000024 intre=0xc0000042
intrd=0xc0000042
ohci_dumpregs:575:                hcca=0xbfdf1f00 percur=0x00000000
ctrlhd=0xbfdf1c50
ohci_dumpregs:579:                ctrlcur=0x00000000 bulkhd=0x00000000
bulkcur=0x00000000
ohci_dumpregs:583:                done=0xbfdf1ca0 fmival=0x27782edf fmrem=0x000009bd
ohci_dumpregs:587:                fmnum=0x00008e3a perst=0x00002a27
lsthrs=0x00000628
ohci_dumpregs:591:                desca=0x02000b03 descb=0x00000000 stat=0x00000000
ohci_dumpregs:594:                port1=0x00000303 port2=0x00000100
ohci_dumpregs:600:          HCCA: frame_number=0x0000 done_head=0x00000000

This is dump just after we programmed it:
ohci_controller_init:308: rewrite head regs
ohci_dumpregs:567: ohci_dumpregs: rev=0x00000110 control=0x000000af
command=0x00000000
ohci_dumpregs:571:                intrstat=0x00000044 intre=0x8000005a
intrd=0x8000005a
ohci_dumpregs:575:                hcca=0x06647000 percur=0x00000000
ctrlhd=0x06692000
ohci_dumpregs:579:                ctrlcur=0x00000000 bulkhd=0x06693000
bulkcur=0x00000000
ohci_dumpregs:583:                done=0x00000000 fmival=0xa7782edf fmrem=0x80001096
ohci_dumpregs:587:                fmnum=0x0000000d perst=0x00002a2f
lsthrs=0x00000628
ohci_dumpregs:591:                desca=0x02000b03 descb=0x00000000 stat=0x00000000
ohci_dumpregs:594:                port1=0x00010301 port2=0x00000100
ohci_dumpregs:600:          HCCA: frame_number=0x000e done_head=0x00000000

This is dump of ohci0 registers just before we run takeover code of ohci1:
ohci1: <OHCI (generic) USB controller> mem 0xfe02d000-0xfe02dfff irq 16 at
device 18.1 on pci0
ohci1: [ITHREAD]
ohci_controller_init:185: reread ohci0 regs:
ohci_dumpregs:567: ohci_dumpregs: rev=0x00000110 control=0x000000af
command=0x00000000
ohci_dumpregs:571:                intrstat=0x00000044 intre=0x8000005a
intrd=0x8000005a
ohci_dumpregs:575:                hcca=0x06647000 percur=0x00000000
ctrlhd=0x06692000
ohci_dumpregs:579:                ctrlcur=0x00000000 bulkhd=0x06693000
bulkcur=0x00000000
ohci_dumpregs:583:                done=0x00000000 fmival=0xa7782edf fmrem=0x800003b5
ohci_dumpregs:587:                fmnum=0x00000012 perst=0x00002a2f
lsthrs=0x00000628
ohci_dumpregs:591:                desca=0x02000b03 descb=0x00000000 stat=0x00000000
ohci_dumpregs:594:                port1=0x00010301 port2=0x00000100
ohci_dumpregs:600:          HCCA: frame_number=0x0012 done_head=0x00000000

And this is dump of ohci0 right after we've taken over ohci1:
ohci_controller_init:195: SMM active, request owner change
ohci_controller_init:219: usbus1: resetting
ohci_controller_init:246: reread ohci0 regs:
ohci_dumpregs:567: ohci_dumpregs: rev=0x00000110 control=0x000000af
command=0x00000000
ohci_dumpregs:571:                intrstat=0x00000004 intre=0x8000005a
intrd=0x8000005a
ohci_dumpregs:575:                hcca=0x06647000 percur=0x00000000
ctrlhd=0xbfdf1c50
ohci_dumpregs:579:                ctrlcur=0x00000000 bulkhd=0x06693000
bulkcur=0x00000000
ohci_dumpregs:583:                done=0xbfdf1ca0 fmival=0xa7782edf fmrem=0x80002122
ohci_dumpregs:587:                fmnum=0x00000192 perst=0x00002a2f
lsthrs=0x00000628
ohci_dumpregs:591:                desca=0x02000b03 descb=0x00000000 stat=0x00000000
ohci_dumpregs:594:                port1=0x00000303 port2=0x00000100
ohci_dumpregs:600:          HCCA: frame_number=0x0192 done_head=0x00000000

As you can see, indeed, the register gets over-written right when we take over
ohci1.
Some additional observations:
1. frame_number seems to grow quite a lot for ohci0
2. before we touch ohci0 it has port1=0x00000303, after reset port1=0x00010301,
after ohci1 takeover port1=0x00000303 again.

I'd say that this is a pretty strong evidence that BIOS does something to ohci0
after we took over it and while we are taking over ohci1.

Another idea of working around this:
1) in pci fixup code disable USB SMI for these chipsets
2) (optional) in ohci code skip takeover step
Sounds messy.

-- 
Andriy Gapon
From avg at freebsd.org  Sun Sep 27 13:26:29 2009
From: avg at freebsd.org (Andriy Gapon)
Date: Sun Sep 27 13:26:35 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4ABF57F5.1050106@icyb.net.ua>
References: <4ABA36B1.9070706@icyb.net.ua>
	<200909241651.47850.hselasky@c2i.net>
	<4ABC646D.4070604@icyb.net.ua>
	<200909250928.51515.hselasky@c2i.net>
	<4ABF57F5.1050106@icyb.net.ua>
Message-ID: <4ABF643D.1080705@freebsd.org>

on 27/09/2009 15:17 Andriy Gapon said the following:
> Another idea of working around this:
> 1) in pci fixup code disable USB SMI for these chipsets
> 2) (optional) in ohci code skip takeover step
> Sounds messy.

BTW, just for the sake of experiment I did exactly what I suggested.
I've got the following messages:

kernel: ohci_controller_init:195: SMM active, request owner change
kernel: usbus0: SMM does not respond, resetting
kernel: ohci_controller_init:195: SMM active, request owner change
kernel: usbus1: SMM does not respond, resetting
kernel: ohci_controller_init:195: SMM active, request owner change
kernel: usbus3: SMM does not respond, resetting
kernel: ohci_controller_init:195: SMM active, request owner change
kernel: usbus4: SMM does not respond, resetting
kernel: ohci_controller_init:195: SMM active, request owner change
kernel: usbus6: SMM does not respond, resetting

And the register value stayed intact after initial programming, so no
re-programming was needed.

Here is the (dirty) hack:
diff --git a/sys/dev/pci/fixup_pci.c b/sys/dev/pci/fixup_pci.c
index 566e503..1463c24 100644
--- a/sys/dev/pci/fixup_pci.c
+++ b/sys/dev/pci/fixup_pci.c
@@ -53,6 +53,7 @@ static int	fixup_pci_probe(device_t dev);
 static void	fixwsc_natoma(device_t dev);
 static void	fixc1_nforce2(device_t dev);
 static void	fixrtc_piix4(device_t dev);
+static void	fixsmi_usb(device_t dev);

 static device_method_t fixup_pci_methods[] = {
     /* Device interface */
@@ -84,6 +85,9 @@ fixup_pci_probe(device_t dev)
     case 0x01e010de:		/* nVidia nForce2 */
 	fixc1_nforce2(dev);
 	break;
+    case 0x96001022:		/* AMD SB700 */
+	fixsmi_usb(dev);
+	break;
     }
     return(ENXIO);
 }
@@ -124,6 +128,21 @@
 }


+/* Disable USB SMI */
+static void
+fixsmi_usb(device_t dev)
+{
+    uint32_t		features;
+
+    dev = pci_find_device(0x1002, 0x4385);
+    features = pci_read_config(dev, 0x64, 4);
+    if (features & (1 << 15)) {
+	printf("Disabling USB SMI on SB7xx\n");
+	features &= ~(1 << 15);
+	pci_write_config(dev, 0x64, features, 4);
+    }
+}
+
 /*
  * Set the SYSTEM_IDLE_TIMEOUT to 80 ns on nForce2 systems to work
  * around a hang that is triggered when the CPU generates a very fast

-- 
Andriy Gapon
From hselasky at c2i.net  Sun Sep 27 13:31:34 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Sep 27 13:31:40 2009
Subject: usb/138659: uftdi driver broken in RELENG_8/CURRENT
In-Reply-To: <4ABEF2A6.6010801@pldrouin.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909230851.03442.hselasky@c2i.net>
	<4ABEF2A6.6010801@pldrouin.net>
Message-ID: <200909271532.12237.hselasky@c2i.net>

On Sunday 27 September 2009 07:05:42 Pierre-Luc Drouin wrote:
>
> So to conclude, it looks like uftdi is working fine :)
>

Great. Nothing better!

--HPS

From avg at freebsd.org  Sun Sep 27 13:58:30 2009
From: avg at freebsd.org (Andriy Gapon)
Date: Sun Sep 27 13:58:35 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4ABF643D.1080705@freebsd.org>
References: <4ABA36B1.9070706@icyb.net.ua>
	<200909241651.47850.hselasky@c2i.net>
	<4ABC646D.4070604@icyb.net.ua>
	<200909250928.51515.hselasky@c2i.net>
	<4ABF57F5.1050106@icyb.net.ua> <4ABF643D.1080705@freebsd.org>
Message-ID: <4ABF6F7F.4050101@freebsd.org>

on 27/09/2009 16:10 Andriy Gapon said the following:

> kernel: ohci_controller_init:195: SMM active, request owner change
> kernel: usbus0: SMM does not respond, resetting
> kernel: ohci_controller_init:195: SMM active, request owner change
> kernel: usbus1: SMM does not respond, resetting
> kernel: ohci_controller_init:195: SMM active, request owner change
> kernel: usbus3: SMM does not respond, resetting
> kernel: ohci_controller_init:195: SMM active, request owner change
> kernel: usbus4: SMM does not respond, resetting
> kernel: ohci_controller_init:195: SMM active, request owner change
> kernel: usbus6: SMM does not respond, resetting
> 
> And the register value stayed intact after initial programming, so no
> re-programming was needed.

I think that I didn't finished what I was saying.
I think that now we can be very sure what is the culprit here.
Now we need to find the best strategy to work around the problem.
(Of course, it would be just the second best with the best being fixing SMM
code, but that's beyond our control).

-- 
Andriy Gapon
From eugen at kuzbass.ru  Sun Sep 27 14:12:12 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Sun Sep 27 14:12:19 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <20090926081733.GA24121@svzserv.kemerovo.su>
Message-ID: <20090927141205.GA19251@svzserv.kemerovo.su>

> Could you check if these are due to device timeouts in the CAM layer?
> There is some debugging you can turn on:
>
> sysctl hw.usb.umass.debug=-1
>
> Probably it will flood the console.

That's not a problem. Anyway, I rlogin to this system
and use syslog to write all console/kernel logs to console.log
and kernel.log

So, I have done:

%sysctl hw.usb.umass.debug=-1
hw.usb.umass.debug: 0 -> -1

Then used another terminal to ran:

%iostat -d -K -w 10 da0
             da0
  KB/t tps  MB/s
  2.88   0  0.00

After it started, I switched back to first terminal and ran:

%dd if=/dev/zero bs=64k of=/dev/da0 count=1000

It started to work, meantime iostat output was:

 63.62  17  1.05
  0.00   0  0.00
  0.00   0  0.00
  0.00   0  0.00
  0.00   0  0.00
  0.00   0  0.00
 64.00   2  0.15
 62.31  83  5.06
  0.25   0  0.00
  0.00   0  0.00
  0.00   0  0.00
^C

To this moment, dd has finished his work and printed:

1000+0 records in
1000+0 records out
65536000 bytes transferred in 78.627073 secs (833504 bytes/sec)

One can see, it sent first chunk of data to the device
than there was quite large period of time without any activity,
more than 50 seconds. Then it has finished.

As for debug log, its uncompressed size is over megabyte
so I've made it available here (25KB compressed):

http://www.grosbein.pp.ru/umass.log.gz

I cannot read/understand it yet.

> Maybe you could add some prints to 
> /sys/dev/usb/storage/umass.c in all the "default:" cases in the USB callbacks 
> and print out the "error" code. That would quickly indicate if your device has 
> an issue with timing, I.E. that the firmware in the USB device part is hanging.

I still suppose the device is fine because it presents no such problem
being connected to another box with the same 8.0-RC1 (same sources).

Also, I don't feel myself confident with the code to debug it yet...

Eugene Grosbein
From eugen at kuzbass.ru  Sun Sep 27 14:31:40 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Sun Sep 27 14:31:48 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <20090927141205.GA19251@svzserv.kemerovo.su>
References: <20090926081733.GA24121@svzserv.kemerovo.su>
	<20090927141205.GA19251@svzserv.kemerovo.su>
Message-ID: <20090927143138.GA20842@svzserv.kemerovo.su>

> %dd if=/dev/zero bs=64k of=/dev/da0 count=1000
> 
> It started to work, meantime iostat output was:
> 
>  63.62  17  1.05
>   0.00   0  0.00
>   0.00   0  0.00
>   0.00   0  0.00
>   0.00   0  0.00
>   0.00   0  0.00
>  64.00   2  0.15
>  62.31  83  5.06
>   0.25   0  0.00
>   0.00   0  0.00
>   0.00   0  0.00
> ^C
> 
> To this moment, dd has finished his work and printed:
> 
> 1000+0 records in
> 1000+0 records out
> 65536000 bytes transferred in 78.627073 secs (833504 bytes/sec)

After some googling, I've tried sysctl hw.usb.ehci.no_hs=1,
reconnected HDD and retried the test. iostat output was:

%iostat -d -K -w 10 da0
             da0
  KB/t tps  MB/s
  2.88   0  0.00
 63.19   8  0.49
 64.00  11  0.69
 64.00  11  0.69
 64.00  11  0.68
 64.00  11  0.69
 64.00  11  0.69
 64.00  11  0.69
 64.00  11  0.68
 64.00  11  0.69
 41.81   7  0.28
  0.00   0  0.00
^C

%dd if=/dev/zero bs=64k of=/dev/da0 count=1000
1000+0 records in
1000+0 records out
65536000 bytes transferred in 91.364733 secs (717301 bytes/sec)

So, this time no idle periods but I'm still not happy with the speed.

Eugene Grosbein
From hselasky at freebsd.org  Sun Sep 27 14:43:52 2009
From: hselasky at freebsd.org (Hans Petter Selasky)
Date: Sun Sep 27 14:43:58 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <20090927141205.GA19251@svzserv.kemerovo.su>
References: <20090927141205.GA19251@svzserv.kemerovo.su>
Message-ID: <200909271629.31368.hselasky@freebsd.org>

On Sunday 27 September 2009 16:12:05 Eugene Grosbein wrote:
> > Could you check if these are due to device timeouts in the CAM layer?
> > There is some debugging you can turn on:
> >
> > sysctl hw.usb.umass.debug=-1
> >
> > Probably it will flood the console.
>
> That's not a problem. Anyway, I rlogin to this system
> and use syslog to write all console/kernel logs to console.log
> and kernel.log
>
> So, I have done:
>
> %sysctl hw.usb.umass.debug=-1
> hw.usb.umass.debug: 0 -> -1
>
> Then used another terminal to ran:
>
> %iostat -d -K -w 10 da0
>              da0
>   KB/t tps  MB/s
>   2.88   0  0.00
>
> After it started, I switched back to first terminal and ran:
>
> %dd if=/dev/zero bs=64k of=/dev/da0 count=1000
>
> It started to work, meantime iostat output was:
>
>  63.62  17  1.05
>   0.00   0  0.00
>   0.00   0  0.00
>   0.00   0  0.00
>   0.00   0  0.00
>   0.00   0  0.00
>  64.00   2  0.15
>  62.31  83  5.06
>   0.25   0  0.00
>   0.00   0  0.00
>   0.00   0  0.00
> ^C
>
> To this moment, dd has finished his work and printed:
>
> 1000+0 records in
> 1000+0 records out
> 65536000 bytes transferred in 78.627073 secs (833504 bytes/sec)
>
> One can see, it sent first chunk of data to the device
> than there was quite large period of time without any activity,
> more than 50 seconds. Then it has finished.
>
> As for debug log, its uncompressed size is over megabyte
> so I've made it available here (25KB compressed):
>
> http://www.grosbein.pp.ru/umass.log.gz
>
> I cannot read/understand it yet.
>
> > Maybe you could add some prints to
> > /sys/dev/usb/storage/umass.c in all the "default:" cases in the USB
> > callbacks and print out the "error" code. That would quickly indicate if
> > your device has an issue with timing, I.E. that the firmware in the USB
> > device part is hanging.
>
> I still suppose the device is fine because it presents no such problem
> being connected to another box with the same 8.0-RC1 (same sources).
>
> Also, I don't feel myself confident with the code to debug it yet...
>

Hi,

The following debug prints clearly show that your device does not respond. And 
the USB stack kicks in after a while to fetch the status of the drive. 
Previously when I have seen this kind of issues, it was always the USB device 
stack that was at failure. I've never seen that it was the fault of the USB 
host stack. You would need an USB analyser to figure out for sure. If the 
situation is that the USB device hardware is reponding with NAKs to the OUT or 
PING tokens (USB term), then the schedule on the USB host is setup correctly 
and it is a device problem.

Have you tried contacting the manufacturer of your USB device about this?

What is the CPU speed difference between the two boxes you are running tests 
on?

Sep 27 21:50:13 gw kernel: umass0:umass_dump_buffer: 0x 
00000000000000000000000000000000 ...
Sep 27 21:50:13 gw kernel: umass0:umass_bbb_dump_cbw: CBW 208: cmd = 10b 
(0x2a0000005400...), data = 65536b, lun = 0, dir = out
Sep 27 21:50:13 gw kernel: umass0:umass_transfer_start: transfer index = 6
Sep 27 21:50:13 gw kernel: umass0:umass_t_bbb_data_write_callback: 
max_bulk=131072, data_rem=65536
Sep 27 21:51:17 gw kernel: umass0:umass_transfer_start: transfer index = 7
Sep 27 21:51:17 gw kernel: umass0:umass_transfer_start: transfer index = 8
Sep 27 21:51:17 gw kernel: umass0:umass_bbb_dump_csw: CSW 208: sig = 
0x53425355 (valid), tag = 0x000000d0, res = 65536, status = 0x01 (failed)
Sep 27 21:51:17 gw kernel: umass0:umass_t_bbb_status_callback: Command failed, 
residue = 65536

--HPS

From eugen at kuzbass.ru  Sun Sep 27 16:14:11 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Sun Sep 27 16:14:17 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <20090927143138.GA20842@svzserv.kemerovo.su>
References: <20090926081733.GA24121@svzserv.kemerovo.su>
	<20090927141205.GA19251@svzserv.kemerovo.su>
	<20090927143138.GA20842@svzserv.kemerovo.su>
Message-ID: <20090927161407.GA25879@svzserv.kemerovo.su>

On Sun, Sep 27, 2009 at 10:31:38PM +0800, Eugene Grosbein wrote:

> > %dd if=/dev/zero bs=64k of=/dev/da0 count=1000
> > 
> > It started to work, meantime iostat output was:
> > 
> >  63.62  17  1.05
> >   0.00   0  0.00
> >   0.00   0  0.00
> >   0.00   0  0.00
> >   0.00   0  0.00
> >   0.00   0  0.00
> >  64.00   2  0.15
> >  62.31  83  5.06
> >   0.25   0  0.00
> >   0.00   0  0.00
> >   0.00   0  0.00
> > ^C

I've repeated the test with my USB flash drive formatted as FAT32.
It gives the same result: for ICH7-based system I get 26 megabyte/s
file writing speed and for AMD CS5536 it suffers from long periods of inactivity
while writing data, hence very low awarage writing speed.

It seems the root of the problem is in the interaction
between USB stack and AMD CS5536 (Geode) USB 2.0 controller
and not in media devices themselves.

Any more hints please?

Eugene Grosbein
From hselasky at freebsd.org  Sun Sep 27 17:50:15 2009
From: hselasky at freebsd.org (Hans Petter Selasky)
Date: Sun Sep 27 17:50:24 2009
Subject: Polling support for USB serial port adapters [patches]
In-Reply-To: <4ABE2B4F.6080104@tomjudge.com>
References: <200909251909.31503.hselasky@freebsd.org>
	<4ABD4EDF.4040807@acm.poly.edu> <4ABE2B4F.6080104@tomjudge.com>
Message-ID: <200909271950.55189.hselasky@freebsd.org>

Hi,

Here is a patchset which you can try.

http://perforce.freebsd.org/chv.cgi?CH=168932

You need to download at least:

usb_serial.h
and
usb_serial.c

Download serial port drivers as needed.

You need to at least recompile all USB serial modules.

To enable you set:

hw.usb.ucom.cons_unit=0
hw.usb.ucom.cons_baud=9600

In /boot/loader.conf

NOTE: The patches have not been tested yet, only carefully reviewed. If you 
experience any problems, please debug and send patch to me.

--HPS

From hselasky at freebsd.org  Sun Sep 27 18:39:54 2009
From: hselasky at freebsd.org (Hans Petter Selasky)
Date: Sun Sep 27 18:40:00 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <20090927161407.GA25879@svzserv.kemerovo.su>
References: <20090926081733.GA24121@svzserv.kemerovo.su>
	<20090927143138.GA20842@svzserv.kemerovo.su>
	<20090927161407.GA25879@svzserv.kemerovo.su>
Message-ID: <200909271940.32878.hselasky@freebsd.org>

On Sunday 27 September 2009 18:14:08 Eugene Grosbein wrote:
> On Sun, Sep 27, 2009 at 10:31:38PM +0800, Eugene Grosbein wrote:
> > > %dd if=/dev/zero bs=64k of=/dev/da0 count=1000
> > >
> > > It started to work, meantime iostat output was:
> > >
> > >  63.62  17  1.05
> > >   0.00   0  0.00
> > >   0.00   0  0.00
> > >   0.00   0  0.00
> > >   0.00   0  0.00
> > >   0.00   0  0.00
> > >  64.00   2  0.15
> > >  62.31  83  5.06
> > >   0.25   0  0.00
> > >   0.00   0  0.00
> > >   0.00   0  0.00
> > > ^C
>
> I've repeated the test with my USB flash drive formatted as FAT32.
> It gives the same result: for ICH7-based system I get 26 megabyte/s
> file writing speed and for AMD CS5536 it suffers from long periods of
> inactivity while writing data, hence very low awarage writing speed.
>
> It seems the root of the problem is in the interaction
> between USB stack and AMD CS5536 (Geode) USB 2.0 controller
> and not in media devices themselves.
>
> Any more hints please?

sysctl hw.usb.ehci.debug=15

If the USB stack puts the new job into the schedule and the USB controller 
does not pick it up, it is not an USB stack problem ...

--HPS

From olivier at cochard.me  Sun Sep 27 19:39:08 2009
From: olivier at cochard.me (=?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?=)
Date: Sun Sep 27 19:39:40 2009
Subject: usb/139142: [regression] ehci drivers (NVIDIA nForce4 USB 2.0 
	controller ) not working with 8.0-RC1
In-Reply-To: <200909260916.45106.hselasky@c2i.net>
References: <200909252038.n8PKcEch066064@www.freebsd.org>
	<200909260916.45106.hselasky@c2i.net>
Message-ID: <3131aa530909271210j203238f0w67056025e08fc345@mail.gmail.com>

Hi,

On Sat, Sep 26, 2009 at 9:16 AM, Hans Petter Selasky <hselasky@c2i.net> wrote:

> Have you tried only disabling USB Legacy support?

No change with USB Legacy support disabled on the BIOS: kernel still
hang on the same place.

>
> There is another USB related thread going on:
>
> "sb600/sb700 ohci experimental patch" on -current.
>
> Have you tried any patches from there?

No change with this patch: kernel still hang on the same place.
I hope that my patched ohci.c h was correct because I need to
"manualy" patch the file: the given patch file have an error:

[root@d630]/usr/src/sys/dev/usb/controller#patch < patch-2.diff
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/sys/dev/usb/controller/ohci.c b/sys/dev/usb/controller/ohci.c
|index 30592c1..fb6ba34 100644
|--- a/sys/dev/usb/controller/ohci.c
|+++ b/sys/dev/usb/controller/ohci.c
--------------------------
Patching file ohci.c using Plan A...
patch: **** malformed patch at line 12: OHCI_CLE |


Thanks,

Olivier
From olivier at cochard.me  Sun Sep 27 19:40:04 2009
From: olivier at cochard.me (=?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?=)
Date: Sun Sep 27 19:40:13 2009
Subject: usb/139142: [regression] ehci drivers (NVIDIA nForce4 USB 2.0 
	controller ) not working with 8.0-RC1
Message-ID: <200909271940.n8RJe32U069184@freefall.freebsd.org>

The following reply was made to PR usb/139142; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= <olivier@cochard.me>
To: Hans Petter Selasky <hselasky@c2i.net>
Cc: freebsd-usb@freebsd.org, freebsd-gnats-submit@freebsd.org
Subject: Re: usb/139142: [regression] ehci drivers (NVIDIA nForce4 USB 2.0 
	controller ) not working with 8.0-RC1
Date: Sun, 27 Sep 2009 21:10:19 +0200

 Hi,
 
 On Sat, Sep 26, 2009 at 9:16 AM, Hans Petter Selasky <hselasky@c2i.net> wrote:
 
 > Have you tried only disabling USB Legacy support?
 
 No change with USB Legacy support disabled on the BIOS: kernel still
 hang on the same place.
 
 >
 > There is another USB related thread going on:
 >
 > "sb600/sb700 ohci experimental patch" on -current.
 >
 > Have you tried any patches from there?
 
 No change with this patch: kernel still hang on the same place.
 I hope that my patched ohci.c h was correct because I need to
 "manualy" patch the file: the given patch file have an error:
 
 [root@d630]/usr/src/sys/dev/usb/controller#patch < patch-2.diff
 Hmm...  Looks like a unified diff to me...
 The text leading up to this was:
 --------------------------
 |diff --git a/sys/dev/usb/controller/ohci.c b/sys/dev/usb/controller/ohci.c
 |index 30592c1..fb6ba34 100644
 |--- a/sys/dev/usb/controller/ohci.c
 |+++ b/sys/dev/usb/controller/ohci.c
 --------------------------
 Patching file ohci.c using Plan A...
 patch: **** malformed patch at line 12: OHCI_CLE |
 
 
 Thanks,
 
 Olivier
From eugen at kuzbass.ru  Mon Sep 28 00:09:59 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Mon Sep 28 00:10:05 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <200909271629.31368.hselasky@freebsd.org>
Message-ID: <20090928000954.GA55370@svzserv.kemerovo.su>

> The following debug prints clearly show that your device does not respond.
> And the USB stack kicks in after a while to fetch the status of the drive.
> Previously when I have seen this kind of issues, it was always the USB device 
> stack that was at failure. I've never seen that it was the fault of the USB 
> host stack.

Then I wonder why both devices (HDD and flash) do not respond being attached
to this CS5536-system and work just fine with another systems.

> You would need an USB analyser to figure out for sure. If the 
> situation is that the USB device hardware is reponding with NAKs to the OUT
> or PING tokens (USB term), then the schedule on the USB host is setup correctly 
> and it is a device problem.

What is USB analyser in first place? :-)

> Have you tried contacting the manufacturer of your USB device about this?

No, because it works with other boxes.

> What is the CPU speed difference between the two boxes you are running
> tests on?

CS5536-based system is uniprocessor and has:

CPU: Geode(TM) Integrated Processor by AMD PCS (499.90-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x5a2  Stepping = 2
  Features=0x88a93d<FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CLFLUSH,MMX>
  AMD Features=0xc0400000<MMX+,3DNow!+,3DNow!>

The CPU is idle while dd is running:

CPU:  0.4% user,  0.0% nice,  0.8% system,  1.2% interrupt, 97.7% idle

My ICH7-based desktop is SMP and has:

CPU: Intel(R) Pentium(R) D CPU 2.80GHz (2805.72-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf62  Stepping = 2

Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0xe43d<SSE3,DTES64,MON,DS_CPL,VMX,CNXT-ID,CX16,xTPR,PDCM>
  AMD Features=0x20100000<NX,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant

Eugene Grosbein
From eugen at kuzbass.ru  Mon Sep 28 03:42:11 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Mon Sep 28 03:42:17 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <200909271940.32878.hselasky@freebsd.org>
Message-ID: <20090928034208.GA64444@svzserv.kemerovo.su>

>> I've repeated the test with my USB flash drive formatted as FAT32.
>> It gives the same result: for ICH7-based system I get 26 megabyte/s
>> file writing speed and for AMD CS5536 it suffers from long periods of
>> inactivity while writing data, hence very low awarage writing speed.
>>
>> It seems the root of the problem is in the interaction
>> between USB stack and AMD CS5536 (Geode) USB 2.0 controller
>> and not in media devices themselves.
>>
>> Any more hints please?
>
> sysctl hw.usb.ehci.debug=15

For USB HDD:

%sysctl hw.usb.ehci.debug=15
hw.usb.ehci.debug: 0 -> 15
%date; dd if=/dev/zero bs=64k of=/dev/da0 count=100; date
Mon Sep 28 11:25:26 KRAST 2009
100+0 records in
100+0 records out
6553600 bytes transferred in 14.912198 secs (439479 bytes/sec)
Mon Sep 28 11:25:43 KRAST 2009

The log is half-megabyte and is available here (13KB compressed):

http://www.grosbein.pp.ru/ehci.log.gz

> If the USB stack puts the new job into the schedule and the USB controller 
> does not pick it up, it is not an USB stack problem ...

If so, any workarounds possible?

Eugene Grisbeibn
From pldrouin at pldrouin.net  Mon Sep 28 04:48:38 2009
From: pldrouin at pldrouin.net (Pierre-Luc Drouin)
Date: Mon Sep 28 04:49:51 2009
Subject: Asynchronous Communications with uftdi/ucom (Is there a bug?)
Message-ID: <4AC04026.9090202@pldrouin.net>

Hi,

I am trying to communicate with a fan controller that uses a FTDI 
FT232BL chip with uftdi/ucom and I am having troubles with asynchronous 
communications on FreeBSD (7.2 amd64 and 8.0-RC1 amd64, although what I 
present here has been obtained with 8.0-RC1 amd64). The exact same code 
works perfectly on Linux (amd64 on the same machine). I got synchronous 
communications working, but it seems that in asynchronous 
communications, SIGIO is generated randomly and read statements produce 
either junk or return the EINT, "Interrupted system call" error.

What I did is to write simplified code where I only request the device 
to provide its status. I have a source file that performs this in 
synchronous mode (bigngtest.c) and another one that does this in 
asynchronous mode (bigngtestasync.c). I ran both codes while enabling 
debug mode for uftdi and ucom and I put the output to stdout and the 
output to dmesg in some files. I also created files where I put the 
output when running the same codes on Linux.

These files can be found in a bzipped2 tar file here: 
http://download.yousendit.com/Y1Ryc0wwdGpVbTlFQlE9PQ

To summarize, here is how I set asynchronous mode compared to 
synchronous mode, in a "diff" format
 >   struct sigaction saio;
<   fd=open(DEV, O_RDWR | O_NOCTTY);
 >   fd=open(DEV, O_RDWR | O_NOCTTY | O_NONBLOCK);
...
 >   /* Install the signal handler before making the device asynchronous */
 >   saio.sa_handler = signal_handler_IO;
 >   result = sigemptyset(&saio.sa_mask);
 >   if(result<0) {
 >       perror("sigemptyset");
 >       return 1;
 >   }
 >   saio.sa_flags = 0;
 >   sigaction(SIGIO,&saio,NULL);
 >
 >   /* Allow the process to receive SIGIO */
 >   fcntl(fd, F_SETOWN, getpid());
 >   /* Make the file descriptor asynchronous */
 >   fcntl(fd, F_SETFL, FASYNC);

Please let me know if there are additional commands that are required to 
set asynchronous mode correctly on FreeBSD. Otherwise, it looks like 
there might be a bug somewhere in a kernel driver...

Thank you!
Pierre-Luc Drouin
From hselasky at freebsd.org  Mon Sep 28 06:48:46 2009
From: hselasky at freebsd.org (Hans Petter Selasky)
Date: Mon Sep 28 06:48:54 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <20090928034208.GA64444@svzserv.kemerovo.su>
References: <20090928034208.GA64444@svzserv.kemerovo.su>
Message-ID: <200909280849.22346.hselasky@freebsd.org>

On Monday 28 September 2009 05:42:08 Eugene Grosbein wrote:
> >> I've repeated the test with my USB flash drive formatted as FAT32.
> >> It gives the same result: for ICH7-based system I get 26 megabyte/s
> >> file writing speed and for AMD CS5536 it suffers from long periods of
> >> inactivity while writing data, hence very low awarage writing speed.
> >>
> >> It seems the root of the problem is in the interaction
> >> between USB stack and AMD CS5536 (Geode) USB 2.0 controller
> >> and not in media devices themselves.
> >>
> >> Any more hints please?
> >
> > sysctl hw.usb.ehci.debug=15
>
> For USB HDD:
>
> %sysctl hw.usb.ehci.debug=15
> hw.usb.ehci.debug: 0 -> 15
> %date; dd if=/dev/zero bs=64k of=/dev/da0 count=100; date
> Mon Sep 28 11:25:26 KRAST 2009
> 100+0 records in
> 100+0 records out
> 6553600 bytes transferred in 14.912198 secs (439479 bytes/sec)
> Mon Sep 28 11:25:43 KRAST 2009
>
> The log is half-megabyte and is available here (13KB compressed):
>
> http://www.grosbein.pp.ru/ehci.log.gz

I don't see any timeouts in there. You need to run the test until you see 
something about "timeout".

>
> > If the USB stack puts the new job into the schedule and the USB
> > controller does not pick it up, it is not an USB stack problem ...
>
> If so, any workarounds possible?

None which I know about.

--HPS
From hselasky at freebsd.org  Mon Sep 28 06:51:18 2009
From: hselasky at freebsd.org (Hans Petter Selasky)
Date: Mon Sep 28 06:51:24 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <20090928000954.GA55370@svzserv.kemerovo.su>
References: <20090928000954.GA55370@svzserv.kemerovo.su>
Message-ID: <200909280851.58539.hselasky@freebsd.org>

On Monday 28 September 2009 02:09:54 Eugene Grosbein wrote:
> What is USB analyser in first place? :-)

Search for beagle USB analyzer at google.

--HPS
From eugen at kuzbass.ru  Mon Sep 28 07:27:29 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Mon Sep 28 07:27:36 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <200909280849.22346.hselasky@freebsd.org>
References: <20090928034208.GA64444@svzserv.kemerovo.su>
	<200909280849.22346.hselasky@freebsd.org>
Message-ID: <20090928072726.GA75536@svzserv.kemerovo.su>

On Mon, Sep 28, 2009 at 08:49:21AM +0200, Hans Petter Selasky wrote:

> > For USB HDD:
> >
> > %sysctl hw.usb.ehci.debug=15
> > hw.usb.ehci.debug: 0 -> 15
> > %date; dd if=/dev/zero bs=64k of=/dev/da0 count=100; date
> > Mon Sep 28 11:25:26 KRAST 2009
> > 100+0 records in
> > 100+0 records out
> > 6553600 bytes transferred in 14.912198 secs (439479 bytes/sec)
> > Mon Sep 28 11:25:43 KRAST 2009
> >
> > The log is half-megabyte and is available here (13KB compressed):
> >
> > http://www.grosbein.pp.ru/ehci.log.gz
> 
> I don't see any timeouts in there. You need to run the test until you see 
> something about "timeout".

It's so strange... While hw.usb.ehci.debug=15 idle periods are very seldom,
iostat shows nearly constat (but very slow) data rate:

 KB/t tps  MB/s 
 64.00   9  0.57 
 64.00   9  0.57 
 64.00   9  0.57 
 64.00   9  0.57 
 64.00   9  0.57

No 'timeout' word in the log. It seems that debugging changes something.

Eugene Grosbein
From dfilter at FreeBSD.ORG  Mon Sep 28 07:50:02 2009
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Mon Sep 28 07:50:15 2009
Subject: usb/138389: commit references a PR
Message-ID: <200909280750.n8S7o2Kc052338@freefall.freebsd.org>

The following reply was made to PR usb/138389; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: usb/138389: commit references a PR
Date: Mon, 28 Sep 2009 07:40:07 +0000 (UTC)

 Author: thompsa
 Date: Mon Sep 28 07:39:51 2009
 New Revision: 197558
 URL: http://svn.freebsd.org/changeset/base/197558
 
 Log:
   Fix NULL-pointer dereference in usb_endpoint_foreach().
   
   PR:		usb/138389
   Submitted by:	Patroklos Argyroudis at census, inc
 
 Modified:
   head/sys/dev/usb/usb_device.c
 
 Modified: head/sys/dev/usb/usb_device.c
 ==============================================================================
 --- head/sys/dev/usb/usb_device.c	Mon Sep 28 07:32:11 2009	(r197557)
 +++ head/sys/dev/usb/usb_device.c	Mon Sep 28 07:39:51 2009	(r197558)
 @@ -367,12 +367,14 @@ usb_init_endpoint(struct usb_device *ude
  struct usb_endpoint *
  usb_endpoint_foreach(struct usb_device *udev, struct usb_endpoint *ep)
  {
 -	struct usb_endpoint *ep_end = udev->endpoints + udev->endpoints_max;
 +	struct usb_endpoint *ep_end;
  
  	/* be NULL safe */
  	if (udev == NULL)
  		return (NULL);
  
 +	ep_end = udev->endpoints + udev->endpoints_max;
 +
  	/* get next endpoint */
  	if (ep == NULL)
  		ep = udev->endpoints;
 _______________________________________________
 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 dfilter at FreeBSD.ORG  Mon Sep 28 07:50:04 2009
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Mon Sep 28 07:50:15 2009
Subject: usb/138563: commit references a PR
Message-ID: <200909280750.n8S7o4tZ052367@freefall.freebsd.org>

The following reply was made to PR usb/138563; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: usb/138563: commit references a PR
Date: Mon, 28 Sep 2009 07:41:31 +0000 (UTC)

 Author: thompsa
 Date: Mon Sep 28 07:41:17 2009
 New Revision: 197559
 URL: http://svn.freebsd.org/changeset/base/197559
 
 Log:
   Add support for USB language selection.
   
   PR:		usb/138563
   Reported by:	Bruce Cran
   Submitted by:	Hans Petter Selasky
 
 Modified:
   head/sys/dev/usb/usb_bus.h
   head/sys/dev/usb/usb_device.c
 
 Modified: head/sys/dev/usb/usb_bus.h
 ==============================================================================
 --- head/sys/dev/usb/usb_bus.h	Mon Sep 28 07:39:51 2009	(r197558)
 +++ head/sys/dev/usb/usb_bus.h	Mon Sep 28 07:41:17 2009	(r197559)
 @@ -98,10 +98,14 @@ struct usb_bus {
  	uint8_t	devices_max;		/* maximum number of USB devices */
  	uint8_t	do_probe;		/* set if USB BUS should be re-probed */
  
 +	/* 
 +	 * The scratch area can only be used inside the explore thread
 +	 * belonging to the give serial bus.
 +	 */
  	union {
  		struct usb_hw_ep_scratch hw_ep_scratch[1];
  		struct usb_temp_setup temp_setup[1];
 -		uint8_t	data[128];
 +		uint8_t	data[255];
  	}	scratch[1];
  };
  
 
 Modified: head/sys/dev/usb/usb_device.c
 ==============================================================================
 --- head/sys/dev/usb/usb_device.c	Mon Sep 28 07:39:51 2009	(r197558)
 +++ head/sys/dev/usb/usb_device.c	Mon Sep 28 07:41:17 2009	(r197559)
 @@ -105,9 +105,23 @@ static void	usb_cdev_cleanup(void *);
  
  int	usb_template = 0;
  
 +TUNABLE_INT("hw.usb.usb_template", &usb_template);
  SYSCTL_INT(_hw_usb, OID_AUTO, template, CTLFLAG_RW,
      &usb_template, 0, "Selected USB device side template");
  
 +/* English is default language */
 +
 +static int usb_lang_id = 0x0009;
 +static int usb_lang_mask = 0x00FF;
 +
 +TUNABLE_INT("hw.usb.usb_lang_id", &usb_lang_id);
 +SYSCTL_INT(_hw_usb, OID_AUTO, usb_lang_id, CTLFLAG_RW,
 +    &usb_lang_id, 0, "Preferred USB language ID");
 +
 +TUNABLE_INT("hw.usb.usb_lang_mask", &usb_lang_mask);
 +SYSCTL_INT(_hw_usb, OID_AUTO, usb_lang_mask, CTLFLAG_RW,
 +    &usb_lang_mask, 0, "Preferred USB language mask");
 +
  static const char* statestr[USB_STATE_MAX] = {
  	[USB_STATE_DETACHED]	= "DETACHED",
  	[USB_STATE_ATTACHED]	= "ATTACHED",
 @@ -1436,7 +1450,7 @@ usb_alloc_device(device_t parent_dev, st
  	struct usb_device *adev;
  	struct usb_device *hub;
  	uint8_t *scratch_ptr;
 -	uint32_t scratch_size;
 +	size_t scratch_size;
  	usb_error_t err;
  	uint8_t device_index;
  
 @@ -1682,8 +1696,35 @@ usb_alloc_device(device_t parent_dev, st
  	if (err || (scratch_ptr[0] < 4)) {
  		udev->flags.no_strings = 1;
  	} else {
 -		/* pick the first language as the default */
 -		udev->langid = UGETW(scratch_ptr + 2);
 +		uint16_t langid;
 +		uint16_t pref;
 +		uint16_t mask;
 +		uint8_t x;
 +
 +		/* load preferred value and mask */
 +		pref = usb_lang_id;
 +		mask = usb_lang_mask;
 +
 +		/* align length correctly */
 +		scratch_ptr[0] &= ~1;
 +
 +		/* fix compiler warning */
 +		langid = 0;
 +
 +		/* search for preferred language */
 +		for (x = 2; (x < scratch_ptr[0]); x += 2) {
 +			langid = UGETW(scratch_ptr + x);
 +			if ((langid & mask) == pref)
 +				break;
 +		}
 +		if (x >= scratch_ptr[0]) {
 +			/* pick the first language as the default */
 +			DPRINTFN(1, "Using first language\n");
 +			langid = UGETW(scratch_ptr + 2);
 +		}
 +
 +		DPRINTFN(1, "Language selected: 0x%04x\n", langid);
 +		udev->langid = langid;
  	}
  
  	/* assume 100mA bus powered for now. Changed when configured. */
 @@ -2149,34 +2190,35 @@ usbd_set_device_strings(struct usb_devic
  #ifdef USB_VERBOSE
  	const struct usb_knowndev *kdp;
  #endif
 -	char temp[64];
 +	uint8_t *temp_ptr;
 +	size_t temp_size;
  	uint16_t vendor_id;
  	uint16_t product_id;
  
 +	temp_ptr = udev->bus->scratch[0].data;
 +	temp_size = sizeof(udev->bus->scratch[0].data);
 +
  	vendor_id = UGETW(udd->idVendor);
  	product_id = UGETW(udd->idProduct);
  
  	/* get serial number string */
 -	bzero(temp, sizeof(temp));
 -	usbd_req_get_string_any(udev, NULL, temp, sizeof(temp),
 +	usbd_req_get_string_any(udev, NULL, temp_ptr, temp_size,
  	    udev->ddesc.iSerialNumber);
 -	udev->serial = strdup(temp, M_USB);
 +	udev->serial = strdup(temp_ptr, M_USB);
  
  	/* get manufacturer string */
 -	bzero(temp, sizeof(temp));
 -	usbd_req_get_string_any(udev, NULL, temp, sizeof(temp),
 +	usbd_req_get_string_any(udev, NULL, temp_ptr, temp_size,
  	    udev->ddesc.iManufacturer);
 -	usb_trim_spaces(temp);
 -	if (temp[0] != '\0')
 -		udev->manufacturer = strdup(temp, M_USB);
 +	usb_trim_spaces(temp_ptr);
 +	if (temp_ptr[0] != '\0')
 +		udev->manufacturer = strdup(temp_ptr, M_USB);
  
  	/* get product string */
 -	bzero(temp, sizeof(temp));
 -	usbd_req_get_string_any(udev, NULL, temp, sizeof(temp),
 +	usbd_req_get_string_any(udev, NULL, temp_ptr, temp_size,
  	    udev->ddesc.iProduct);
 -	usb_trim_spaces(temp);
 -	if (temp[0] != '\0')
 -		udev->product = strdup(temp, M_USB);
 +	usb_trim_spaces(temp_ptr);
 +	if (temp_ptr[0] != '\0')
 +		udev->product = strdup(temp_ptr, M_USB);
  
  #ifdef USB_VERBOSE
  	if (udev->manufacturer == NULL || udev->product == NULL) {
 @@ -2202,12 +2244,12 @@ usbd_set_device_strings(struct usb_devic
  #endif
  	/* Provide default strings if none were found */
  	if (udev->manufacturer == NULL) {
 -		snprintf(temp, sizeof(temp), "vendor 0x%04x", vendor_id);
 -		udev->manufacturer = strdup(temp, M_USB);
 +		snprintf(temp_ptr, temp_size, "vendor 0x%04x", vendor_id);
 +		udev->manufacturer = strdup(temp_ptr, M_USB);
  	}
  	if (udev->product == NULL) {
 -		snprintf(temp, sizeof(temp), "product 0x%04x", product_id);
 -		udev->product = strdup(temp, M_USB);
 +		snprintf(temp_ptr, temp_size, "product 0x%04x", product_id);
 +		udev->product = strdup(temp_ptr, M_USB);
  	}
  }
  
 _______________________________________________
 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 bugmaster at FreeBSD.org  Mon Sep 28 11:07:06 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Sep 28 11:09:41 2009
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200909281107.n8SB756S064196@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o usb/139142   usb        [regression] ehci drivers (NVIDIA nForce4 USB 2.0 cont
o usb/138915   usb        [patch][usb8][usb67] add support for SheevaPlug serial
o usb/138904   usb        [rum] unpluging USB wifi card panics system
f usb/138882   usb        [ohci] [panic] Can't install FreeBSD 7.2 due to ohci p
o usb/138879   usb        [uftdi] [patch] Patch to add support for CTI USB-Mini 
o usb/138798   usb        8.0-BETA4 can't boot from USB flash drive
o usb/138675   usb        [usb8] [panic] page fault, perhaps in USB
o usb/138659   usb        [usb8][uftdi] driver broken in RELENG_8/CURRENT
o usb/138563   usb        [usb8] [patch] Increase buffer sizes to accomodate lon
o usb/138389   usb        [usb8] [patch] NULL pointer dereference in usb_endpoin
o usb/138175   usb        [usb67] [boot] System cannot boot, when USB reader wit
o usb/138172   usb        Additional dev id for u3g (Option mini PCIe)
o usb/138138   usb        Novatel U760 for u3g (Verizon and Bell Canada)
o usb/138124   usb        [usb8] Axed uaudio functionality in the usbng (alterna
o usb/138119   usb        MultiBay CDROM (propably on USB bus) is not recognized
o usb/137872   usb        slow booting on usb flash drive
f usb/137848   usb        Page fault when using an USB bluetooth adapter
o usb/137806   usb        [ukbd] USB keyboard doesn't work until it's unplugged
o usb/137763   usb        [usb67][ukbd] Logitech wireless keyboard media keys no
o usb/137616   usb        [usb67][usb8][usbdevs] [patch]: usbdevs update: Please
o usb/137377   usb        [usb8] Support for Huawei E180
o usb/137341   usb        [usb8][rum] driver if_rum doesn't work at all and thro
p usb/137226   usb        [usb67][patch] quirk for Philips extern USB disk
o usb/137191   usb        [usb8][patch] export ums(4) output report parser data 
o 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        SteelSeries Ikari USB laser mouse not attaching
o usb/137035   usb        Sony cyber-shot DSC-P72 not accessible - cam quirks
p usb/136761   usb        [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H
o usb/135938   usb        [aue] aue driver only passes traffic in promisc mode
f usb/135857   usb        RTL8187 Wireless Adapter
o usb/135575   usb        [usbdevs] [patch] Add HTC Wizard phone vid/pid informa
o usb/135542   usb        [keyboard] boot loader does not work with a usb keyboa
p usb/135372   usb        [usb67][umass] Quirk report for Teclast TL-C300 usb me
o usb/135348   usb        [umass] USB Drive Hangs with ZFS (JMicron USB2/eSata)
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/134633   usb        Add support for WILLCOM03(SHARP smart phone)
o usb/134631   usb        [usbdevs] [patch] WiSPY DBx support requires usb tweak
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/134117   usb        [Patch] Add support for 'Option GlobeTrotter HSDPA Mod
o usb/134085   usb        [umass] Adding usb quirk for Sony USB flash drive
o usb/133989   usb        [newusb] [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
p usb/132799   usb        [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CA
o usb/132785   usb        [usb] [patch] Gemtech remote powersocket is classed as
o usb/132594   usb        USB subsystem causes page fault and crashes
o usb/132312   usb        Xorg 7.4 halts USB controller
o usb/132080   usb        [patch] [usb] [rum] Kernel panic after NOMEM caused by
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/131912   usb        [uslcom] [patch] New devices using Silicon Labs chips 
o usb/131900   usb        [usbdevs] [patch] Additional product identification co
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
o usb/131123   usb        [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk
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/130325   usb        [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh
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        [newusb] DVD drive detects as 'da' device
o usb/129945   usb        [usbdevs] [patch] add u3g support for Longcheer WM66 U
o usb/129766   usb        [usb] plugging in usb modem HUAWEI E226 panics system
o usb/129758   usb        [uftdi] [patch] add Pyramid LCD usb support
o usb/129673   usb        [uhci] uhci (uhub) confused on replugging USB 1.1 scan
o usb/129522   usb        [ubsa] [patch] add support for ZTE AC8700 modem
o usb/129500   usb        [umass] [panic] FreeBSD Crashes when connecting SanDis
o usb/129311   usb        [usb] [panic] Instant crash with an USB card reader
o usb/129251   usb        [usbdevs] [patch] Liebert UPS being assigned uhid and 
o usb/129173   usb        [uplcom] [patch] Add support for Corega CG-USBRS232R a
s usb/128990   usb        [usb] u3g does not handle RTS/CTS available on for exa
o usb/128977   usb        [usb] [patch] uaudio is not full duplex
o 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/128324   usb        [uplcom] [patch] remove baud rate restriction for PL23
o usb/127980   usb        [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an
o usb/127926   usb        [boot] USB Timeout during bootup
s usb/127549   usb        [umass] [patch] Meizu MiniPlayer M6 (SL) requires some
s usb/127453   usb        [request] ubsa, uark, ubser, uftdi, and friends should
o usb/127423   usb        [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr
o usb/127342   usb        [boot] [panic] enabling usb keyboard and mouse support
o usb/127248   usb        [ucom] panic while uplcom devices attaach 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/125736   usb        [ukbd] [hang] system hangs after AT keyboard detect if
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
p usb/125264   usb        [patch] sysctl for set usb mouse rate (very useful for
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
o 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/123352   usb        [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom
o usb/123351   usb        [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2
o usb/122992   usb        [umass] [patch] MotoROKR Z6 Phone not recognised by um
o usb/122956   usb        [ubsa] [patch] add support for Novatel Wireless XU870 
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/122621   usb        [new driver] [patch] New driver for Sierra Wireless 3G
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/122025   usb        [uscanner] [patch] uscanner does not attach to Epson R
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/121426   usb        [patch] [uscanner] add HP ScanJet 3570C
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        [umass] [patch] quirk to support ASUS P535 as umass (a
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/118485   usb        [usbdevs] [patch] Logitech Headset Workaround
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        [uaudio] [patch] Not possible to record with Plantroni
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
o 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/107935   usb        [usb67] [uplcom] [panic] panic while accessing /dev/cu
o usb/107924   usb        [usb67] usbd(8) does not call detach
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/107243   usb        [usb67] [cam] [quirk] [patch] Apacer USB Flash Drive q
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/99538    usb        [keyboard] while using USB keyboard default params of 
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/93155    usb        [ulpt] /dev/ulpt0: device busy, USB printer does not w
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/91629    usb        [usb] usbd_abort_pipe() may result in infinite loop
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
f usb/84750    usb        [hang] 6-BETA2 reboot/shutdown with root_fs on externa
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/80862    usb        [patch] USB locking issues: missing some Giant calls
o usb/80854    usb        [patch] [request] suggestion for new iface-no-probe me
o usb/80829    usb        [modules] [panic] possible panic when loading USB-modu
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 "
o usb/80361    usb        [umass] [patch] mounting of Dell usb-stick fails
o 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/79722    usb        [ehci] wrong alignments in ehci.h
a usb/79656    usb        [ehci] RHSC interrupts lost
o usb/79524    usb        [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa
o usb/79287    usb        [uhci] [hang] UHCI hang after interrupt transfer
o usb/79269    usb        [ohci] USB ohci da0 plug/unplug causes crashes and loc
o usb/78984    usb        [umass] [patch] Creative MUVO umass failure
o usb/77294    usb        [ucom] [panic] ucom + ulpcom panic
o usb/77184    usb        [umass] [panic] kernel panic on USB device disconnect,
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
o 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
o 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 
o usb/75705    usb        [umass] [panic] da0 attach / Optio S4 (with backtrace)
o 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 i386/46371   usb        USB controller cannot be initialized on IBM Netfinity 
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

311 problems total.

From hselasky at c2i.net  Mon Sep 28 12:00:14 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Sep 28 12:00:20 2009
Subject: usb/138675: [usb8] [panic] page fault, perhaps in USB
Message-ID: <200909281200.n8SC0EIV021610@freefall.freebsd.org>

The following reply was made to PR usb/138675; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: bug-followup@freebsd.org,
 jhanna@pangolin-systems.com
Cc:  
Subject: usb/138675: [usb8] [panic] page fault, perhaps in USB
Date: Mon, 28 Sep 2009 13:56:38 +0200

 I believe this issue has been fixed. Please close.
 
 --HPS
From doconnor at gsoft.com.au  Mon Sep 28 13:10:58 2009
From: doconnor at gsoft.com.au (Daniel O'Connor)
Date: Mon Sep 28 13:11:05 2009
Subject: SANE vs USB scanner on 8.0
Message-ID: <200909282240.53802.doconnor@gsoft.com.au>

Hi,
I'm trying to get a USB scanner to work with FreeBSD 8.0, it did work 
with 7.2 via uscanner.

It's an AcerScan 620U and I have the firmware and 
modified /usr/local/etc/sane.d/snapscan.conf.

sane-find-scanner sees it, eg
[midget 22:37] ~ >sudo sane-find-scanner  -q
found USB scanner (vendor=0x04a5 [Color], product=0x2060 [ FlatbedScanner 13]) at libusb:/dev/usb:/dev/ugen0.5
found USB scanner (vendor=0x0403 [FTDI], product=0xee18 [MaxStream PKG-U]) at libusb:/dev/usb:/dev/ugen1.2

I have no idea why the FTDI serial device appears there..

However scanimage -L doesn't show the scanner..
[midget 22:40] ~ >sudo env SANE_DEBUG_SNAPSCAN=255 scanimage -v -v -L
[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.53
[snapscan] add_usb_device(libusb:/dev/usb:/dev/ugen0.5)
[snapscan] add_usb_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(libusb:/dev/usb:/dev/ugen0.5)
[snapscan] snapscani_mutex_open: could not parse device string: No such file or directory
[snapscan] snapscani_usb_open: Can't get semaphore
[snapscan] add_usb_device: error opening device libusb:/dev/usb:/dev/ugen0.5: Invalid argument
[snapscan] sane_snapscan_get_devices (0x7fffffffe200, 0)

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
Calling sane_exit
[snapscan] sane_snapscan_exit
scanimage: finished

Anyone have any suggestions?

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090928/79d10a13/attachment.pgp
From hselasky at c2i.net  Mon Sep 28 13:36:02 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Sep 28 13:36:09 2009
Subject: SANE vs USB scanner on 8.0
In-Reply-To: <200909282240.53802.doconnor@gsoft.com.au>
References: <200909282240.53802.doconnor@gsoft.com.au>
Message-ID: <200909281536.38747.hselasky@c2i.net>

On Monday 28 September 2009 15:10:52 Daniel O'Connor wrote:
> Hi,
> I'm trying to get a USB scanner to work with FreeBSD 8.0, it did work
> with 7.2 via uscanner.
>
> It's an AcerScan 620U and I have the firmware and
> modified /usr/local/etc/sane.d/snapscan.conf.
>
> sane-find-scanner sees it, eg
> [midget 22:37] ~ >sudo sane-find-scanner  -q
> found USB scanner (vendor=0x04a5 [Color], product=0x2060 [ FlatbedScanner
> 13]) at libusb:/dev/usb:/dev/ugen0.5 found USB scanner (vendor=0x0403
> [FTDI], product=0xee18 [MaxStream PKG-U]) at libusb:/dev/usb:/dev/ugen1.2
>
> I have no idea why the FTDI serial device appears there..
>
> However scanimage -L doesn't show the scanner..
> [midget 22:40] ~ >sudo env SANE_DEBUG_SNAPSCAN=255 scanimage -v -v -L
> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [snapscan] sane_snapscan_init: Snapscan backend version 1.4.53
> [snapscan] add_usb_device(libusb:/dev/usb:/dev/ugen0.5)
> [snapscan] add_usb_device: Detected (kind of) an USB device
> [snapscan] snapscani_usb_open(libusb:/dev/usb:/dev/ugen0.5)
> [snapscan] snapscani_mutex_open: could not parse device string: No such
> file or directory [snapscan] snapscani_usb_open: Can't get semaphore
> [snapscan] add_usb_device: error opening device
> libusb:/dev/usb:/dev/ugen0.5: Invalid argument [snapscan]
> sane_snapscan_get_devices (0x7fffffffe200, 0)
>
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
> Calling sane_exit
> [snapscan] sane_snapscan_exit
> scanimage: finished
>
> Anyone have any suggestions?

Hi,

Try this patch:

diff -u ./work/sane-backends-1.0.20/backend/snapscan-mutex.c ./snapscan-
mutex.c
--- ./work/sane-backends-1.0.20/backend/snapscan-mutex.c        2008-03-28 
21:39:02.000000000 +0100
+++ ./snapscan-mutex.c  2009-09-28 15:33:41.000000000 +0200
@@ -130,7 +130,8 @@
            return 0;
        }
 
-       if (sscanf(dev, "libusb:%d:%d", &busnum, &devnum) != 2)
+       if ((sscanf(dev, "libusb:%d:%d", &busnum, &devnum) != 2) &&
+           (sscanf(dev, "libusb:/dev/usb:ugen%d.%d", &busnum, &devnum) != 2))
        {
            DBG (DL_MAJOR_ERROR, "%s: could not parse device string: %s\n", 
me, strerror(errno));
            return 0;

If it works, get the patch sent to the sane developers.

--HPS

From john at baldwin.cx  Mon Sep 28 13:47:08 2009
From: john at baldwin.cx (John Baldwin)
Date: Mon Sep 28 13:47:15 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4ABF643D.1080705@freebsd.org>
References: <4ABA36B1.9070706@icyb.net.ua> <4ABF57F5.1050106@icyb.net.ua>
	<4ABF643D.1080705@freebsd.org>
Message-ID: <200909280748.45528.john@baldwin.cx>

On Sunday 27 September 2009 9:10:21 am Andriy Gapon wrote:
> on 27/09/2009 15:17 Andriy Gapon said the following:
> > Another idea of working around this:
> > 1) in pci fixup code disable USB SMI for these chipsets
> > 2) (optional) in ohci code skip takeover step
> > Sounds messy.
> 
> BTW, just for the sake of experiment I did exactly what I suggested.
> I've got the following messages:
> 
> kernel: ohci_controller_init:195: SMM active, request owner change
> kernel: usbus0: SMM does not respond, resetting
> kernel: ohci_controller_init:195: SMM active, request owner change
> kernel: usbus1: SMM does not respond, resetting
> kernel: ohci_controller_init:195: SMM active, request owner change
> kernel: usbus3: SMM does not respond, resetting
> kernel: ohci_controller_init:195: SMM active, request owner change
> kernel: usbus4: SMM does not respond, resetting
> kernel: ohci_controller_init:195: SMM active, request owner change
> kernel: usbus6: SMM does not respond, resetting
> 
> And the register value stayed intact after initial programming, so no
> re-programming was needed.
> 
> Here is the (dirty) hack:
> diff --git a/sys/dev/pci/fixup_pci.c b/sys/dev/pci/fixup_pci.c
> index 566e503..1463c24 100644
> --- a/sys/dev/pci/fixup_pci.c
> +++ b/sys/dev/pci/fixup_pci.c
> @@ -53,6 +53,7 @@ static int	fixup_pci_probe(device_t dev);
>  static void	fixwsc_natoma(device_t dev);
>  static void	fixc1_nforce2(device_t dev);
>  static void	fixrtc_piix4(device_t dev);
> +static void	fixsmi_usb(device_t dev);
> 
>  static device_method_t fixup_pci_methods[] = {
>      /* Device interface */
> @@ -84,6 +85,9 @@ fixup_pci_probe(device_t dev)
>      case 0x01e010de:		/* nVidia nForce2 */
>  	fixc1_nforce2(dev);
>  	break;
> +    case 0x96001022:		/* AMD SB700 */
> +	fixsmi_usb(dev);
> +	break;
>      }
>      return(ENXIO);
>  }
> @@ -124,6 +128,21 @@
>  }
> 
> 
> +/* Disable USB SMI */
> +static void
> +fixsmi_usb(device_t dev)
> +{
> +    uint32_t		features;
> +
> +    dev = pci_find_device(0x1002, 0x4385);
> +    features = pci_read_config(dev, 0x64, 4);
> +    if (features & (1 << 15)) {
> +	printf("Disabling USB SMI on SB7xx\n");
> +	features &= ~(1 << 15);
> +	pci_write_config(dev, 0x64, features, 4);
> +    }
> +}
> +
>  /*
>   * Set the SYSTEM_IDLE_TIMEOUT to 80 ns on nForce2 systems to work
>   * around a hang that is triggered when the CPU generates a very fast

I don't think you can do this because it is a "feature" to not disable SMM if 
ohci(4) is not loaded so that a USB keyboard works when the USB driver isn't 
loaded via PS/2 emulation, even when the OS is running.  I am curious if we 
really need to do the handover for each controller or if disabling it for 
ohci0 effectively disables it for all controllers?  What do other OS's do?

-- 
John Baldwin
From avg at freebsd.org  Mon Sep 28 13:55:49 2009
From: avg at freebsd.org (Andriy Gapon)
Date: Mon Sep 28 13:56:01 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <200909280748.45528.john@baldwin.cx>
References: <4ABA36B1.9070706@icyb.net.ua> <4ABF57F5.1050106@icyb.net.ua>
	<4ABF643D.1080705@freebsd.org> <200909280748.45528.john@baldwin.cx>
Message-ID: <4AC0C060.20109@freebsd.org>

on 28/09/2009 14:48 John Baldwin said the following:
> I don't think you can do this because it is a "feature" to not disable SMM if 
> ohci(4) is not loaded so that a USB keyboard works when the USB driver isn't 
> loaded via PS/2 emulation, even when the OS is running.

Very good point.

> I am curious if we 
> really need to do the handover for each controller or if disabling it for 
> ohci0 effectively disables it for all controllers?  What do other OS's do?
> 

Don't have an answer about other OSes.
But OHCI controllers have individual "used by SMM" bits and taking over one
controller doesn't affect the bits of the other controllers - they remain set.
Not that it means that SMM code actually keeps on controlling them.

Actually, just checked - Linux also does it per controller:
http://lxr.linux.no/#linux+v2.6.31/drivers/usb/host/ohci-hcd.c#L495

-- 
Andriy Gapon
From jhb at FreeBSD.org  Mon Sep 28 14:11:06 2009
From: jhb at FreeBSD.org (John Baldwin)
Date: Mon Sep 28 14:11:14 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <4AC0C060.20109@freebsd.org>
References: <4ABA36B1.9070706@icyb.net.ua> <200909280748.45528.john@baldwin.cx>
	<4AC0C060.20109@freebsd.org>
Message-ID: <200909281010.50427.jhb@FreeBSD.org>

On Monday 28 September 2009 9:55:44 am Andriy Gapon wrote:
> on 28/09/2009 14:48 John Baldwin said the following:
> > I don't think you can do this because it is a "feature" to not disable SMM if 
> > ohci(4) is not loaded so that a USB keyboard works when the USB driver isn't 
> > loaded via PS/2 emulation, even when the OS is running.
> 
> Very good point.
> 
> > I am curious if we 
> > really need to do the handover for each controller or if disabling it for 
> > ohci0 effectively disables it for all controllers?  What do other OS's do?
> > 
> 
> Don't have an answer about other OSes.
> But OHCI controllers have individual "used by SMM" bits and taking over one
> controller doesn't affect the bits of the other controllers - they remain set.
> Not that it means that SMM code actually keeps on controlling them.
> 
> Actually, just checked - Linux also does it per controller:
> http://lxr.linux.no/#linux+v2.6.31/drivers/usb/host/ohci-hcd.c#L495

Hmm, it seems Linux now disables SMM for USB controllers (ohci, ehci, and uhci)
via PCI quirks rather than doing it in the device drivers themselves, which
matches your original suggestion.  I'm not sure how best to fix that while also
allowing USB to work w/o drivers loaded.

-- 
John Baldwin
From avg at freebsd.org  Mon Sep 28 14:28:25 2009
From: avg at freebsd.org (Andriy Gapon)
Date: Mon Sep 28 14:28:34 2009
Subject: sb600/sb700 ohci experimental patch
In-Reply-To: <200909281010.50427.jhb@FreeBSD.org>
References: <4ABA36B1.9070706@icyb.net.ua> <200909280748.45528.john@baldwin.cx>
	<4AC0C060.20109@freebsd.org> <200909281010.50427.jhb@FreeBSD.org>
Message-ID: <4AC0C805.6070909@freebsd.org>

on 28/09/2009 17:10 John Baldwin said the following:
> On Monday 28 September 2009 9:55:44 am Andriy Gapon wrote:
>> on 28/09/2009 14:48 John Baldwin said the following:
>>> I don't think you can do this because it is a "feature" to not disable SMM if 
>>> ohci(4) is not loaded so that a USB keyboard works when the USB driver isn't 
>>> loaded via PS/2 emulation, even when the OS is running.
>> Very good point.
>>
>>> I am curious if we 
>>> really need to do the handover for each controller or if disabling it for 
>>> ohci0 effectively disables it for all controllers?  What do other OS's do?
>>>
>> Don't have an answer about other OSes.
>> But OHCI controllers have individual "used by SMM" bits and taking over one
>> controller doesn't affect the bits of the other controllers - they remain set.
>> Not that it means that SMM code actually keeps on controlling them.
>>
>> Actually, just checked - Linux also does it per controller:
>> http://lxr.linux.no/#linux+v2.6.31/drivers/usb/host/ohci-hcd.c#L495
> 
> Hmm, it seems Linux now disables SMM for USB controllers (ohci, ehci, and uhci)
> via PCI quirks rather than doing it in the device drivers themselves, which
> matches your original suggestion.  I'm not sure how best to fix that while also
> allowing USB to work w/o drivers loaded.
> 

I looked at the quirk code (for OHCI only) and they don't disable SMI - they do
exactly the same takeover dance, only earlier:
http://lxr.linux.no/#linux+v2.6.31/drivers/usb/host/pci-quirks.c#L169

I.e. this actually matches what Hans suggested before - first early takeover of
all controllers, then probe/attach pass.
Not sure how to implement this best in our architecture - also using quirks or
perhaps something along the lines of multi-pass? :-)

-- 
Andriy Gapon
From eugen at kuzbass.ru  Mon Sep 28 17:29:54 2009
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Mon Sep 28 17:30:01 2009
Subject: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour
In-Reply-To: <200909280849.22346.hselasky@freebsd.org>
References: <20090928034208.GA64444@svzserv.kemerovo.su>
	<200909280849.22346.hselasky@freebsd.org>
Message-ID: <20090928172950.GA6865@svzserv.kemerovo.su>

On Mon, Sep 28, 2009 at 08:49:21AM +0200, Hans Petter Selasky wrote:

> > > If the USB stack puts the new job into the schedule and the USB
> > > controller does not pick it up, it is not an USB stack problem ...
> >
> > If so, any workarounds possible?
> 
> None which I know about.

I've just found one. I noticed that USB controller here uses IRQ10
and shares it with NIC and FireWire. This system does not support IO-APIC.
I've disabled ACPI and NIC has moved to another IRQ,
USB and FireWire still share one IRQ but now there are no stalled transfers.
I get stable 16.2 megabyte/s writing speed to USB HDD.

Now I wonder if there is another way to assign distinct IRQ for USB,
BIOS Setup does not help.

Eugene Grosbein.
From alexbestms at math.uni-muenster.de  Wed Sep 30 13:14:06 2009
From: alexbestms at math.uni-muenster.de (Alexander Best)
Date: Wed Sep 30 13:14:12 2009
Subject: mouse behaving strange on high cpu load and rapid movements
Message-ID: <permail-200909301314031e86ffa800000c22-a_best01@message-id.uni-muenster.de>

hi there,

i'm running -CURRENT (i386, r197623). on heavy cpu load i get random
copy&pastes when moving my mouse rapidly. this happens under X as well as on
the console.

these are the moused options i have in my rc.conf:

moused_enable="NO"
moused_ums0_enable="YES"
moused_flags="-z4 -a 0.2,0.2"
moused_port="/dev/ums0"
moused_type="auto"

this also happens with if i add -F 1000 or -F 500 to the moused_flags.

cheers.
alex
From alexbestms at math.uni-muenster.de  Wed Sep 30 13:23:36 2009
From: alexbestms at math.uni-muenster.de (Alexander Best)
Date: Wed Sep 30 13:23:45 2009
Subject: mouse behaving strange on high cpu load and rapid movements
Message-ID: <permail-200909301323181e86ffa80000168a-a_best01@message-id.uni-muenster.de>

here's some debug output:

ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 f6 1a 00 f6 ff 1a 00
ums_intr_callback:291: x:-10 y:-26 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 fd 19 00 fd ff 19 00
ums_intr_callback:291: x:-3 y:-25 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 04 18 00 04 00 18 00
ums_intr_callback:291: x:4 y:-24 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 0b 17 00 0b 00 17 00
ums_intr_callback:291: x:11 y:-23 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 13 15 00 13 00 15 00
ums_intr_callback:291: x:19 y:-21 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 16 12 00 16 00 12 00
ums_intr_callback:291: x:22 y:-18 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 1c 0e 00 1c 00 0e 00
ums_intr_callback:291: x:28 y:-14 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 54 c5 00 54 00 c5 ff
ums_intr_callback:291: x:84 y:59 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 fb f8 00 fb ff f8 ff
ums_intr_callback:291: x:-5 y:8 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 fd fa 00 fd ff fa ff
ums_intr_callback:291: x:-3 y:6 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 fe fc 00 fe ff fc ff
ums_intr_callback:291: x:-2 y:4 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 ff fd 00 ff ff fd ff
ums_intr_callback:291: x:-1 y:3 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 00 ff 00 00 00 ff ff
ums_intr_callback:291: x:0 y:1 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 00 ff 00 00 00 ff ff
ums_intr_callback:291: x:0 y:1 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 00 01 00 00 00 01 00
ums_intr_callback:291: x:0 y:-1 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 00 01 00 00 00 01 00
ums_intr_callback:291: x:0 y:-1 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 ff 01 00 ff ff 01 00
ums_intr_callback:291: x:-1 y:-1 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 00 03 00 00 00 03 00
ums_intr_callback:291: x:0 y:-3 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 ff 03 00 ff ff 03 00
ums_intr_callback:291: x:-1 y:-3 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 ff 03 00 ff ff 03 00
ums_intr_callback:291: x:-1 y:-3 z:0 t:0 w:0 buttons:0x00000000
ums_intr_callback:207: sc=0xc95f1800 actlen=8
ums_intr_callback:225: data = 00 ff 00 00 ff ff 00 00
ums_intr_callback:291: x:-1 y:0 z:0 t:0 w:0 buttons:0x00000000

cheers.
alex
From doconnor at gsoft.com.au  Wed Sep 30 14:12:02 2009
From: doconnor at gsoft.com.au (Daniel O'Connor)
Date: Wed Sep 30 14:12:08 2009
Subject: SANE vs USB scanner on 8.0
In-Reply-To: <200909281536.38747.hselasky@c2i.net>
References: <200909282240.53802.doconnor@gsoft.com.au>
	<200909281536.38747.hselasky@c2i.net>
Message-ID: <200909302341.40232.doconnor@gsoft.com.au>

On Mon, 28 Sep 2009, Hans Petter Selasky wrote:

> -       if (sscanf(dev, "libusb:%d:%d", &busnum, &devnum) != 2)
> +       if ((sscanf(dev, "libusb:%d:%d", &busnum, &devnum) != 2) &&
> +           (sscanf(dev, "libusb:/dev/usb:ugen%d.%d", &busnum,
> &devnum) != 2)) {
>             DBG (DL_MAJOR_ERROR, "%s: could not parse device string:
> %s\n", me, strerror(errno));
>             return 0;
>
> If it works, get the patch sent to the sane developers.

Unfortunately no (I reworked it to match the path it uses) and now it 
segfaults. I rebuilt sane with debugging (is there some way to make libtool
not strip on install? It's so tedious manually editing makefiles to remove
-s..) as well as libusb.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 801b021c0 (LWP 100292)]
0x000000080140e715 in libusb20_dev_open (pdev=0x801b13d00, nTransferMax=32)
    at /usr/src/lib/libusb/libusb20.c:550
550             error = pdev->beMethods->open_device(pdev, nTransferMax);
(gdb) bt
#0  0x000000080140e715 in libusb20_dev_open (pdev=0x801b13d00, nTransferMax=32)
    at /usr/src/lib/libusb/libusb20.c:550
#1  0x0000000801408f15 in usb_open (dev=0x801b1ae00)
    at /usr/src/lib/libusb/libusb20_compat01.c:150
#2  0x000000080065c34f in sanei_usb_open (
    devname=0x801b09380 "libusb:/dev/usb:/dev/ugen0.5", dn=0x7fffffffdc0c)
    at sanei_usb.c:1143
#3  0x00000008025e5ad3 in snapscani_usb_open (
    dev=0x801b09380 "libusb:/dev/usb:/dev/ugen0.5", fdp=0x7fffffffdc0c,
    sense_handler=0x8025df7c0 <sense_handler>, pss=0x0) at snapscan-usb.c:178
#4  0x00000008025eb985 in add_usb_device (
    full_name=0x801b09080 "libusb:/dev/usb:/dev/ugen0.5") at snapscan.c:590
#5  0x000000080065c0ed in sanei_usb_find_devices (vendor=1189, product=8288,
    attach=0x8025eb880 <add_usb_device>) at sanei_usb.c:1091
#6  0x000000080065bb3e in sanei_usb_attach_matching_devices (name=0x7fffffffdcc1 "",
    attach=0x8025eb880 <add_usb_device>) at sanei_usb.c:965
#7  0x00000008025ebdac in sane_snapscan_init (version_code=0x7fffffffe0f8,
    authorize=0x401b50 <auth_callback>) at snapscan.c:735
#8  0x000000080066579b in init (be=0x801b0da00) at dll.c:613
#9  0x000000080066621b in sane_dll_get_devices (device_list=0x7fffffffea00,
---Type <return> to continue, or q <return> to quit---
    local_only=0) at dll.c:1034
#10 0x0000000800658bbb in sane_get_devices (dl=0x7fffffffea00, local=0) at dll-s.c:17
#11 0x0000000000405a11 in main (argc=4, argv=0x7fffffffeb30) at scanimage.c:1771
(gdb) print *pdev
$1 = {ddesc = {LIBUSB20_DEVICE_DESC_FORMAT = 0x0, bLength = 0 '\0',
    bDescriptorType = 0 '\0', bcdUSB = 0, bDeviceClass = 0 '\0',
    bDeviceSubClass = 0 '\0', bDeviceProtocol = 0 '\0', bMaxPacketSize0 = 0 '\0',
    idVendor = 0, idProduct = 0, bcdDevice = 0, iManufacturer = 0 '\0',
    iProduct = 0 '\0', iSerialNumber = 0 '\0', bNumConfigurations = 0 '\0'},
  session_data = {session_data = 0, tv = {tv_sec = 0, tv_nsec = 0}, plugtime = 0},
  dev_entry = {tqe_next = 0x0, tqe_prev = 0x0}, methods = 0x0, beMethods = 0x0,
  pTransfer = 0x801b48500, privBeData = 0x0, privLuData = 0x0,
  claimed_interface = 0 '\0', file = 0, file_ctrl = 0, debug = 0, nTransfer = 32,
  bus_number = 0 '\0', device_address = 0 '\0', usb_mode = 0 '\0',
  usb_speed = 0 '\0', is_opened = 0 '\0', usb_desc = '\0' <repeats 95 times>}
(gdb) up
#1  0x0000000801408f15 in usb_open (dev=0x801b1ae00)
    at /usr/src/lib/libusb/libusb20_compat01.c:150
150             err = libusb20_dev_open(dev->dev, 16 * 2);
(gdb) print *dev
$2 = {next = 0x0, prev = 0x0, filename = "/dev/ugen0.5", '\0' <repeats 1012 times>,
  bus = 0x801510020, descriptor = {bLength = 18 '\022', bDescriptorType = 1 '\001',
    bcdUSB = 256, bDeviceClass = 255 '?', bDeviceSubClass = 255 '?',
    bDeviceProtocol = 255 '?', bMaxPacketSize0 = 8 '\b', idVendor = 1189,
    idProduct = 8288, bcdDevice = 256, iManufacturer = 1 '\001',
    iProduct = 2 '\002', iSerialNumber = 0 '\0', bNumConfigurations = 1 '\001'},
  config = 0x801b23280, dev = 0x801b13d00, devnum = 0 '\0', num_children = 0 '\0',
  children = 0x0}
(gdb) print dev->dev
$3 = (void *) 0x801b13d00
(gdb) up
#2  0x000000080065c34f in sanei_usb_open (
    devname=0x801b09380 "libusb:/dev/usb:/dev/ugen0.5", dn=0x7fffffffdc0c)
    at sanei_usb.c:1143
1143          devices[devcount].libusb_handle =
(gdb) list
1138    #ifdef HAVE_LIBUSB
1139          struct usb_device *dev;
1140          struct usb_interface_descriptor *interface;
1141          int result, num;
1142
1143          devices[devcount].libusb_handle =
1144            usb_open (devices[devcount].libusb_device);
1145          if (!devices[devcount].libusb_handle)
1146            {
1147              SANE_Status status = SANE_STATUS_INVAL;
(gdb) print *devices[devcount].libusb_device
$4 = {next = 0x0, prev = 0x0, filename = "/dev/ugen0.5", '\0' <repeats 1012 times>,
  bus = 0x801510020, descriptor = {bLength = 18 '\022', bDescriptorType = 1 '\001',
    bcdUSB = 256, bDeviceClass = 255 '?', bDeviceSubClass = 255 '?',
    bDeviceProtocol = 255 '?', bMaxPacketSize0 = 8 '\b', idVendor = 1189,
    idProduct = 8288, bcdDevice = 256, iManufacturer = 1 '\001',
    iProduct = 2 '\002', iSerialNumber = 0 '\0', bNumConfigurations = 1 '\001'},
  config = 0x801b23280, dev = 0x801b13d00, devnum = 0 '\0', num_children = 0 '\0',
  children = 0x0}

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090930/8447f131/attachment.pgp
From linimon at FreeBSD.org  Wed Sep 30 16:10:02 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Sep 30 16:10:09 2009
Subject: usb/139243: [uhci] unplug prolific USB serial ->
	uhci_abort_xfer: not in process context
Message-ID: <200909301610.n8UGA24c026103@freefall.freebsd.org>

Old Synopsis: unplug prolific USB serial -> uhci_abort_xfer: not in process context
New Synopsis: [uhci] unplug prolific USB serial -> uhci_abort_xfer: not in process context

Responsible-Changed-From-To: freebsd-bugs->freebsd-usb
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Sep 30 16:09:43 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=139243