[RFC] rc.d integration for the bluetooth subsystem

[Vladimir Grebenschikov]

В ср, 09/11/2005 в 09:38 -0800, Maksim Yevmenkin пишет:
> Vladimir,

> >>Reconnecting usb bluetooth device lead to following error:
> >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2
> >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2
> >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3;
> >>wMaxPacketSize=49; nframes=6, buffer size=294
> >>ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5)
> 
> the drivers have not changed for a long time. perhaps something wrong 
> with usb? the message above clearly says that driver was attempting to 
> start interrupt transfer, but it failed (with strange NOMEM error).
> 
> >>And after that error bt stack does not work until reboot, reconnecting
> >>dongle does not helps.
> >>
> >>Boot scenario was:
> >>booting
> >>...
> >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2
> >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2
> >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3;
> >>wMaxPacketSize=49; nframes=6, buffer size=294
> >>Timecounter "TSC" frequency 1686969804 Hz quality 800
> >>...
> >>Trying to mount root from ufs:/dev/ad0s4a
> >>WARNING: attempt to net_add_domain(bluetooth) after domainfinalize()
> >>WARNING: attempt to net_add_domain(netgraph) after domainfinalize()
> >>...
> >>there bthidd started but does not connect mice.
> >>
> >>I have turned on-board bt off, then on by notebook switch.
> >>kernel printed:
> >>ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfer will be submitted!
> >>ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xfer will be submitted!
> >>ubt0: at uhub2 port 2 (addr 2) disconnected
> >>ubt0: detached
> >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2
> >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2
> >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294
> >>kbd2 at vkbd0
> >>
> >>BT mice start work here.
> >>after some hours of work it stop moving and l2pings also.
> >>
> >>Trying restart BT stack lead to error: 
> >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2
> >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2
> >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3;
> >>wMaxPacketSize=49; nframes=6, buffer size=294
> >>ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5)
> 
> again you get all sorts of errors back from usb. this is _not_ driver's 
> fault. i have to check what NOMEM really means and get back to you.

Actually under "driver" I mean any in-kernel code (usb, locks, newbus,
etc)

Effect is stable, after each boot it works few hours and then fails.

> thanks,
> max

-- 
Vladimir B. Grebenschikov
SWsoft Inc. vova at swsoft.com