Re: False positive uipaq probe

2009-08-18 Thread Alexander Motin
Hans Petter Selasky wrote:
 On Friday 14 August 2009 22:26:32 Alexander Motin wrote:
 USB-connected WM6 communicators are able to operate in two main comm
 modes: serial and RNDIS. That two modes reported with different device
 IDs. I have noticed that my HTC Prophet WM6 communicator started to
 behave wrong on recent CURRENT:

 uipaq0: HTC Generic RNDIS, class 239/1, rev 2.00/0.00, addr 2 on usbus3
 device_attach: uipaq0 attach returned 6
 uipaq0: HTC Generic RNDIS, class 239/1, rev 2.00/0.00, addr 2 on usbus3
 device_attach: uipaq0 attach returned 6

 As soon as uipaq is a kind of serial driver, it should not attach to
 RNDIS device.
 
 Can you provide output from usbconfig -u XXX -a YYY dump_device_desc 
 dump_curr_config_desc in the Serial and RNDIS case?

Attached.

-- 
Alexander Motin
ugen0.2: Generic RNDIS HTC at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x00ef 
  bDeviceSubClass = 0x0001 
  bDeviceProtocol = 0x0001 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x0bb4 
  idProduct = 0x0bce 
  bcdDevice = 0x 
  iManufacturer = 0x0001  HTC
  iProduct = 0x0002  Generic RNDIS
  iSerialNumber = 0x  no string
  bNumConfigurations = 0x0001 


 Configuration index 0

bLength = 0x0009 
bDescriptorType = 0x0002 
wTotalLength = 0x003e 
bNumInterfaces = 0x0002 
bConfigurationValue = 0x0001 
iConfiguration = 0x  no string
bmAttributes = 0x00c0 
bMaxPower = 0x0032 

Interface 0
  bLength = 0x0009 
  bDescriptorType = 0x0004 
  bInterfaceNumber = 0x 
  bAlternateSetting = 0x 
  bNumEndpoints = 0x0001 
  bInterfaceClass = 0x00ef 
  bInterfaceSubClass = 0x0001 
  bInterfaceProtocol = 0x0001 
  iInterface = 0x  no string

  Additional Descriptor

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


  Additional Descriptor

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


  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x02
   RAW dump: 
   0x00 | 0x05, 0x24, 0x02, 0x00, 0x01


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


Interface 1
  bLength = 0x0009 
  bDescriptorType = 0x0004 
  bInterfaceNumber = 0x0001 
  bAlternateSetting = 0x 
  bNumEndpoints = 0x0002 
  bInterfaceClass = 0x000a 
  bInterfaceSubClass = 0x 
  bInterfaceProtocol = 0x 
  iInterface = 0x  no string

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

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



ugen0.2: USB Serial for Prophet HTC at usbus0, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x 
  bDeviceSubClass = 0x 
  bDeviceProtocol = 0x 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x0bb4 
  idProduct = 0x0a51 
  bcdDevice = 0x 
  iManufacturer = 0x0001  HTC
  iProduct = 0x0002  USB Serial for Prophet
  iSerialNumber = 0x  no string
  bNumConfigurations = 0x0001 


 Configuration index 0

bLength = 0x0009 
bDescriptorType = 0x0002 
wTotalLength = 0x0020 
bNumInterfaces = 0x0001 
bConfigurationValue = 0x0001 
iConfiguration = 0x  no string
bmAttributes = 0x00c0 
bMaxPower = 0x0032 

Interface 0
  bLength = 0x0009 
  bDescriptorType = 0x0004 
  bInterfaceNumber = 0x 
  bAlternateSetting = 0x 
  bNumEndpoints = 0x0002 
  bInterfaceClass = 0x00ff 
  bInterfaceSubClass = 0x00ff 
  bInterfaceProtocol = 0x00ff 
  iInterface = 0x  no string

 Endpoint 0
bLength = 0x0007 
bDescriptorType = 0x0005 
bEndpointAddress = 0x0081 
bmAttributes = 0x0002 
wMaxPacketSize = 0x0040 
bInterval = 0x 
bRefresh = 0x 
bSynchAddress = 0x 

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

Re: usb/137789: Add quirks for EeePC 901 SD card reader

2009-08-18 Thread Hans Petter Selasky
On Saturday 15 August 2009 08:44:36 OISHI Masakuni wrote:
 Number: 137789

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

--HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org


Re: usb/135372: Quirk report for Teclast TL-C300 usb media player

2009-08-18 Thread Hans Petter Selasky
On Monday 08 June 2009 16:11:15 Duncan Bertwistle wrote:
 usb/135372

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

--HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org


Re: usb/137789: Add quirks for EeePC 901 SD card reader

2009-08-18 Thread Hans Petter Selasky
The following reply was made to PR usb/137789; it has been noted by GNATS.

From: Hans Petter Selasky hsela...@c2i.net
To: freebsd-usb@freebsd.org
Cc: OISHI Masakuni yam...@bsdhouse.org,
 freebsd-gnats-sub...@freebsd.org
Subject: Re: usb/137789: Add quirks for EeePC 901 SD card reader
Date: Tue, 18 Aug 2009 17:39:40 +0200

 On Saturday 15 August 2009 08:44:36 OISHI Masakuni wrote:
  Number: 137789
 
 http://perforce.freebsd.org/chv.cgi?CH=167476
 
 --HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org


Re: usb/135372: Quirk report for Teclast TL-C300 usb media player

2009-08-18 Thread Hans Petter Selasky
The following reply was made to PR usb/135372; it has been noted by GNATS.

From: Hans Petter Selasky hsela...@c2i.net
To: freebsd-usb@freebsd.org
Cc: Duncan Bertwistle jd...@clix.pt,
 freebsd-gnats-sub...@freebsd.org
Subject: Re: usb/135372: Quirk report for Teclast TL-C300 usb media player
Date: Tue, 18 Aug 2009 17:39:47 +0200

 On Monday 08 June 2009 16:11:15 Duncan Bertwistle wrote:
  usb/135372
 
 http://perforce.freebsd.org/chv.cgi?CH=167476
 
 --HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org


Re: False positive uipaq probe

2009-08-18 Thread Hans Petter Selasky
On Tuesday 18 August 2009 12:54:22 Alexander Motin wrote:
 Alexander Motin m...@freebsd.org

Try this patch:

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

--HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org


Re: False positive uipaq probe

2009-08-18 Thread Alexander Motin

Hans Petter Selasky wrote:

On Tuesday 18 August 2009 12:54:22 Alexander Motin wrote:

Alexander Motin m...@freebsd.org


Try this patch:

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


Now it looks better. uipaq attaches to serial, but not to RNDIS.

--
Alexander Motin
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org


Re: u3g driver sometimes loses the Huawei E169 modem after upgrade to 8.0BETA2

2009-08-18 Thread Peter Jeremy
On 2009-Aug-14 09:40:39 +0200, Hans Petter Selasky hsela...@c2i.net wrote:
On Thursday 13 August 2009 23:32:52 Edwin Groothuis wrote:
 On 7.x this never happened, but on 8.x now and then (once or twice
 every traintrip) the E169 modem gets lost: You see the kernel
 messages that the device disappeared, /dev/cua0.0 disappears and
 thus PPP stops etc.

I'm seeing something similar, though not as frequently as Edwin and
the symptoms vary.  For my latest crash, the devices didn't disappear
(in particular, e169-stats - which uses ttyU0.2 - kept running and
there were no kernel messages).  It seems to get worse the longer my
system is running (or maybe the more often I connect/disconnect the
E169).

At least sometimes, the dropout _is_ triggered by a signal glitch
(moving through cuttings and tunnels without in-tunnel coverage) but
I've also seen it sitting at my office desk.  The reconnect issues I
have suggest that there's some sort of resource leak in the kernel as
well.

How much traffic is being passed when the modem stops?

In my case, virtually none - maybe 1 packet every few seconds (mostly
due to chatting to Edwin and others on IRC).

sysctl hw.usb.ehci.no_hs=1

Before plugging the device. This will limit the speed to FULL speed only.

It's a full-speed device only, so will this have any effect?
ugen0.2: HUAWEI Mobile Huawei Technologies at usbus0, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON

In my case, I'm also seeing situations where the modem will not
reconnect (I get Too many IPCP REQs sent - abandoning negotiation
from ppp(8)) until it is physically disconnected and reconnected.
Associated with this, I notice an increase in active mbufs that I
can't explain (last time, netstat -m was reporting ~840 active mbufs
whereas I was expecting ~330).

A full set of probe messages for me looks like:
Aug 19 05:35:54 aspire kernel: u3g_huawei_init:253: 
Aug 19 05:35:54 aspire kernel: usb2_alloc_device:1762: Found Huawei 
auto-install disk!
Aug 19 05:35:54 aspire kernel: ugen0.2: Huawei Technologies at usbus0
Aug 19 05:35:54 aspire kernel: ugen0.2: Huawei Technologies at usbus0 
(disconnected)
Aug 19 05:35:54 aspire kernel: uhub_reattach_port:416: could not allocate new 
device!
Aug 19 05:35:57 aspire root: Unknown USB device: vendor 0x12d1 product 0x1001 
bus uhub0
Aug 19 05:35:57 aspire kernel: ugen0.2: Huawei Technologies at usbus0
Aug 19 05:35:57 aspire kernel: u3g0: Data Interface on usbus0
Aug 19 05:35:57 aspire kernel: u3g0: Found 3 ports.
Aug 19 05:35:57 aspire kernel: umass0: Huawei Technologies HUAWEI Mobile, 
class 0/0, rev 1.10/0.00, addr 2 on usbus0
Aug 19 05:35:57 aspire kernel: umass0:  SCSI over Bulk-Only; quirks = 0x
Aug 19 05:35:59 aspire kernel: umass0:0:0:-1: Attached to scbus0
Aug 19 05:35:59 aspire kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 
0 0 0 0 0 0 
Aug 19 05:35:59 aspire kernel: (probe0:umass-sim0:0:0:0): CAM Status: SCSI 
Status Error
Aug 19 05:35:59 aspire kernel: (probe0:umass-sim0:0:0:0): SCSI Status: Check 
Condition
Aug 19 05:35:59 aspire kernel: (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0
Aug 19 05:35:59 aspire kernel: (probe0:umass-sim0:0:0:0): Medium not present
Aug 19 05:35:59 aspire kernel: (probe0:umass-sim0:0:0:0): Unretryable error
Aug 19 05:35:59 aspire kernel: cd0 at umass-sim0 bus 0 target 0 lun 0
Aug 19 05:35:59 aspire kernel: cd0: HUAWEI Mass Storage 2.31 Removable CD-ROM 
SCSI-2 device 
Aug 19 05:35:59 aspire kernel: cd0: 1.000MB/s transfers
Aug 19 05:35:59 aspire kernel: cd0: Attempt to query device size failed: NOT 
READY, Medium not present
Aug 19 05:36:00 aspire kernel: (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 
0 20 0 0 0 0 
Aug 19 05:36:00 aspire kernel: (probe0:umass-sim0:0:0:1): CAM Status: SCSI 
Status Error
Aug 19 05:36:00 aspire kernel: (probe0:umass-sim0:0:0:1): SCSI Status: Check 
Condition
Aug 19 05:36:00 aspire kernel: (probe0:umass-sim0:0:0:1): NOT READY asc:3a,0
Aug 19 05:36:00 aspire kernel: (probe0:umass-sim0:0:0:1): Medium not present
Aug 19 05:36:00 aspire kernel: (probe0:umass-sim0:0:0:1): Unretryable error
Aug 19 05:36:00 aspire kernel: da0 at umass-sim0 bus 0 target 0 lun 1
Aug 19 05:36:00 aspire kernel: da0: HUAWEI SD Storage 2.31 Removable Direct 
Access SCSI-2 device 
Aug 19 05:36:00 aspire kernel: da0: 1.000MB/s transfers
Aug 19 05:36:00 aspire kernel: da0: Attempt to query device size failed: NOT 
READY, Medium not present
Aug 19 05:36:00 aspire kernel: can't re-use a leaf (minimum_cmd_size)!

The last message looks a bit strange, though it is currently working.

-- 
Peter Jeremy


pgpmKPTJ2cQEo.pgp
Description: PGP signature