Date: Thu, 26 Feb 2009 09:39:59 -0500 From: Kim Culhan <w8hdkim@gmail.com> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: Novatel U727 not recognized Message-ID: <89dbfdc30902260639q44372d37xf702b3e023ebb8a5@mail.gmail.com> In-Reply-To: <200902250800.00365.hselasky@c2i.net> References: <89dbfdc30902241338h2e56af93q5d8fb3905454ea36@mail.gmail.com> <200902250800.00365.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 25, 2009 at 1:59 AM, Hans Petter Selasky <hselasky@c2i.net> wro= te: > On Tuesday 24 February 2009, Kim Culhan wrote: >> On Tue, Feb 24, 2009 at 4:34 AM, Hans Petter Selasky <hselasky@c2i.net> > wrote: >> > On Tuesday 24 February 2009, Kim Culhan wrote: >> >> On Tue, Feb 24, 2009 at 3:05 AM, Hans Petter Selasky <hselasky@c2i.ne= t> >> > >> > wrote: >> >> > On Monday 23 February 2009, Kim Culhan wrote: >> >> >> On Mon, Feb 23, 2009 at 3:56 PM, Hans Petter Selasky >> >> >> <hselasky@c2i.net> >> >> > >> >> > wrote: >> >> >> > On Monday 23 February 2009, Kim Culhan wrote: >> >> >> >> Running 8.0-CURRENT as of 2-22-09 >> >> >> >> >> >> >> >> The 3g0 device is a Novatel U727 EVDO wireless radio. >> >> >> >> >> >> >> >> If the machine boots with the device attached, dmesg reads: >> >> >> >> >> >> >> >> u3g0: <Data Interface> on usbus2 >> >> >> >> >> >> >> >> Remove the device and this is logged: >> >> >> >> >> >> >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) >> >> >> >> >> >> >> >> Reattach the device and there is this message: >> >> >> >> >> >> >> >> uhub_reattach_port:414: could not allocate new device! >> >> >> >> >> >> >> >> kernel config has: >> >> >> >> >> >> >> >> device =A0 usb2_serial_3g >> >> >> >> >> >> >> >> Any help is greatly appreciated >> >> >> > >> >> >> > Hi, >> >> >> > >> >> >> > Can you turn on USB HUB debugging: >> >> >> > >> >> >> > sysctl hw.usb2.uhub.debug=3D15 >> >> >> > sysctl hw.usb.uhub.debug=3D15 >> >> >> >> >> >> Sure here is dmesg with sysctl hw.usb2.uhub.debug=3D15 >> >> >> >> >> >> uhub_read_port_status:259: port 2, wPortStatus=3D0x0103, >> >> >> wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION >> >> >> usb2_transfer_power_ref:1470: Adding type 0 to power state >> >> >> usb2_transfer_power_ref:1483: needs power >> >> >> u3g_huawei_init:278: >> >> >> usb2_alloc_device:1618: Found Huawei auto-install disk! >> >> >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] =3D 0xc6b= c6000 >> >> >> ugen2.2: <Novatel Wireless Inc.> at usbus2 >> >> >> ugen2.2: <Novatel Wireless Inc.> at usbus2 (disconnected) >> >> >> usb2_bus_port_set_device:1334: bus 0xc6733cf0 devices[2] =3D 0 >> >> >> uhub_reattach_port:414: could not allocate new device! >> >> >> usb2_needs_explore:1345: >> >> >> usb2_bus_powerd:1516: bus=3D0xc670bcf0 >> >> >> usb2_bus_powerd:1599: Recomputing power masks >> >> >> uhub_explore:522: udev=3D0xc6a93000 addr=3D1 >> >> >> >> >> >> With the old usb, this was returned: >> >> >> >> >> >> Feb 22 10:38:37 smallster kernel: ugen2.2: <Novatel Wireless Inc.>= at >> >> >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: <Novatel Wireless >> >> >> Inc. Novatel Wireless CDMA, class 0/0, rev 1.10/0.00, addr 2> on >> >> >> usbus2 Feb 22 10:38:37 smallster kernel: umass0: =A0SCSI over >> >> >> Bulk-Only; quirks =3D 0x0000 Feb 22 10:38:38 smallster kernel: >> >> >> umass0:1:0:-1: Attached to scbus1 Feb 22 10:38:39 smallster kernel= : >> >> >> (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 >> >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): CAM >> >> >> Status: SCSI Status Error >> >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): SCSI >> >> >> Status: Check Condition >> >> >> Feb 22 10:38:39 smallster kernel: (probe0:umass-sim0:0:0:0): NOT >> >> >> READY asc:3a,0 Feb 22 10:38:39 smallster kernel: >> >> >> (probe0:umass-sim0:0:0:0): Medium not present Feb 22 10:38:39 >> >> >> smallster kernel: >> >> >> (probe0:umass-sim0:0:0:0): Unretryable error Feb 22 10:38:39 >> >> >> smallster kernel: cd0 at umass-sim0 bus 0 target 0 lun 0 Feb 22 >> >> >> 10:38:39 smallster kernel: cd0: <Novatel Mass Storage 1.00> Remova= ble >> >> >> CD-ROM SCSI-2 device Feb 22 10:38:39 smallster kernel: cd0: 1.000M= B/s >> >> >> transfers >> >> >> Feb 22 10:38:39 smallster kernel: cd0: Attempt to query device siz= e >> >> >> failed: NOT READY, Medium not present >> >> >> Feb 22 10:40:27 smallster kernel: g_vfs_done():cd0[READ(offset=3D6= 5536, >> >> >> length=3D8192)]error =3D 5 >> >> >> Feb 22 10:43:39 smallster kernel: umass0: at ushub2, port 1, addr = 2 >> >> >> (disconnected) >> >> >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): lost dev= ice >> >> >> Feb 22 10:43:39 smallster kernel: (cd0:umass-sim0:0:0:0): removing >> >> >> device entry Feb 22 10:43:39 smallster kernel: ugen2.2: <Novatel >> >> >> Wireless Inc.> at usbus2 (disconnected) >> >> >> >> >> >> The device initially attempts to simulate the presence of a cdrom. >> >> >> >> >> >> Maybe this is creating the problem for usb2. >> >> >> >> >> >> -kim >> >> > >> >> > Hi Kim, >> >> > >> >> > In the latter case you don't have the U3G driver loaded. The U3G >> >> > driver will detect the CD-ROM and send an eject or propritary comma= nd. >> >> > After some while the device should show up like a u3g0 device. The >> >> > error message you get is like it should be when CD-ROM detection is >> >> > enabled. >> >> AFAIK there is no seperate CD-ROM detection which can be enabled/disable= d. >> >> The device does not show up as a u3g0 device unless the u3g module is >> loaded after the system is booted with _u3g commented out of the kernel >> config_ >> >> After boot: >> >> kldload u3g >> >> returns >> >> u3g0: <Data Interface> on usbus2 >> u3g0: Found 4 ports. >> >> If I remove the usb device it reports: >> >> u3g0: at ushub2, port 2, addr 2 (disconnected) >> umass0: at ushub2, port 2, addr 2 (disconnected) >> (da0:umass-sim0:0:0:0): lost device >> (da0:umass-sim0:0:0:0): removing device entry >> ugen2.2: <Novatel Wireless Inc.> at usbus2 (disconnected) >> >> If I reattach the device it reports: >> >> u3g_huawei_init:278: >> usb2_alloc_device:1618: Found Huawei auto-install disk! >> ugen2.2: <Novatel Wireless Inc.> at usbus2 >> ugen2.2: <Novatel Wireless Inc.> at usbus2 (disconnected) >> uhub_reattach_port:414: could not allocate new device! >> > > If your device does not re-appear within 10 seconds, then try this: > > 1) Add a quirk: > > kldload usb_quirk > kldload usb2_quirk > > usbconfig add_dev_quirk_vplh vid pid 0 0xFFFF UQ_CFG_INDEX_0 > > Replace vid and pid by the info provided by "usbconfig -u 2 -a 2 > dump_device_desc". > > 2) Dump USB configuration: > > usbconfig -u 2 -a 2 dump_curr_config_desc running this on 8-CURRENT of Feb 25 2008 ~ 2100 UTC # usbconfig -u 2 -a 2 dump_device_desc returns No device match or lack of permissions. # usbconfig -u 2 -a 2 dump_curr_config_desc returns the same Also, at this point booting without u3g in the kernel then inserting the Novatel U727 device returns the usual output relating to the cd0 device: ugen2.2: <Novatel Wireless Inc.> at usbus2 umass0: <Novatel Wireless Inc. Novatel Wireless CDMA, class 0/0, rev 1.10/0.00, addr 2> on usbus2 umass0: SCSI over Bulk-Only; quirks =3D 0x0000 umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 [deleted] Then on loading the u3g module: kldload u3g Now returns nothing, no output to dmesg kldunload u3g returns a LOR and backtrace: lock order reversal: 1st 0xc0d66da0 kernel linker (kernel linker) @ kern/kern_linker.c:1059 2nd 0xc0d68804 sysctl lock (sysctl lock) @ kern/kern_sysctl.c:250 KDB: stack backtrace: db_trace_self_wrapper(c0c1af34,e9595ac8,c0891525,4,c0c16550,...) at db_trace_self_wrapper+0x26 kdb_backtrace(4,c0c16550,c6523740,c6521ad0,e9595b24,...) at kdb_backtrace+0= x29 _witness_debugger(c0c1dc29,c0d68804,c0c18a34,c6521ad0,c0c18953,...) at _witness_debugger+0x25 witness_checkorder(c0d68804,9,c0c1894a,fa,0,...) at witness_checkorder+0x83= 9 _sx_xlock(c0d68804,0,c0c1894a,fa,c7164b80,...) at _sx_xlock+0x85 sysctl_ctx_free(c7164bcc,c7164b80,e9595bac,c0879d35,c7164b80,...) at sysctl_ctx_free+0x30 device_sysctl_fini(c7164b80,0,c0c1d176,c6b23ac0,c6ae9800,...) at device_sysctl_fini+0x1a device_detach(c7164b80,40088,c70ebb80,1,c717215c,...) at device_detach+0x1f= 5 devclass_delete_driver(c66398c0,c7172170,c0c16366,109,0,...) at devclass_delete_driver+0x91 driver_module_handler(c70ebbc0,1,c717215c,109,0,...) at driver_module_handler+0xd5 module_unload(c70ebbc0,c0c148cf,273,270,c0837376,...) at module_unload+0x43 linker_file_unload(c716c800,0,c0c148cf,423,c716f000,...) at linker_file_unload+0x15e kern_kldunload(c6b7d6c0,3,0,e9595d2c,c0b55ca3,...) at kern_kldunload+0xd5 kldunloadf(c6b7d6c0,e9595cf8,8,c0c1ec53,c0cfc720,...) at kldunloadf+0x2b syscall(e9595d38) at syscall+0x2a3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (444, FreeBSD ELF32, kldunloadf), eip =3D 0x280ce6ab, esp =3D 0xbfbfe48c, ebp =3D 0xbfbfecd8 --- Hope this helps regards -kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?89dbfdc30902260639q44372d37xf702b3e023ebb8a5>