reattach 3g0 device: could not allocate new device

[Hans Petter Selasky]

On Tuesday 24 February 2009, Kim Culhan wrote:
> On Tue, Feb 24, 2009 at 3:05 AM, Hans Petter Selasky <hselasky at c2i.net> 
wrote:
> > On Monday 23 February 2009, Kim Culhan wrote:
> >> On Mon, Feb 23, 2009 at 3:56 PM, Hans Petter Selasky <hselasky at 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   usb2_serial_3g
> >> >>
> >> >> Any help is greatly appreciated
> >> >
> >> > Hi,
> >> >
> >> > Can you turn on USB HUB debugging:
> >> >
> >> > sysctl hw.usb2.uhub.debug=15
> >> > sysctl hw.usb.uhub.debug=15
> >>
> >> Sure here is dmesg with sysctl hw.usb2.uhub.debug=15
> >>
> >> uhub_read_port_status:259: port 2, wPortStatus=0x0103,
> >> wPortChange=0x0000, err=USB_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] = 0xc6bc6000
> >> 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] = 0
> >> uhub_reattach_port:414: could not allocate new device!
> >> usb2_needs_explore:1345:
> >> usb2_bus_powerd:1516: bus=0xc670bcf0
> >> usb2_bus_powerd:1599: Recomputing power masks
> >> uhub_explore:522: udev=0xc6a93000 addr=1
> >>
> >> 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:  SCSI over Bulk-Only; quirks =
> >> 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> Removable CD-ROM SCSI-2 device
> >> Feb 22 10:38:39 smallster kernel: cd0: 1.000MB/s transfers
> >> Feb 22 10:38:39 smallster kernel: cd0: Attempt to query device size
> >> failed: NOT READY, Medium not present
> >> Feb 22 10:40:27 smallster kernel: g_vfs_done():cd0[READ(offset=65536,
> >> length=8192)]error = 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 device
> >> 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 command. 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.
> >
> > --HPS
>
> The latter case is for the obsolete usb driver but I included it for
> information RE
> the CD-ROM eject action.
>
> How would it work in the case of the new usb2 driver?

Hi,

It works the same like in the old driver, if you unload the u3g module (which 
takes around 16 seconds)

--HPS