New uhso(4) device: Globetrotter HSUPA Modem Option N.V.
jamesbrandongooch at gmail.com
Mon Feb 21 19:28:14 UTC 2011
> Yeah, I got that message. Not connecting and not getting an serial
> console is a bit different. From the output above it looks like
> random garbage on the serial port.
> Try connecting to all different serial ports (without uhsoctl running)
> with minicom or cu and try typing AT<enter>. (The diagnostic port
> doesn't work, so skip that one).
I just encountered a panic when the driver attaches after plugging in
The panic stems from uhso_attach(), and seems due to my kernel having
the VIMAGE option compiled in -- it doesn't panic on my non-VIMAGE
kernel (which I need to rebuild to continue helping debug).
I'm trying to get a textdump ATM...
OK, got it. See attached. Maybe there isn't sufficient locking applied
when working in vnet-enabled environment? Nevertheless, I'm building a
new kernel without VIMAGE to finish helping debug issue...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 119296 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20110221/ddd7a885/uhso_textdump.tar-0001.obj
More information about the freebsd-usb