Ahhh okay...wasn't sure if it was affecting functionality...yup, 2.6.27-gentoo; and hfp r27 fixes that.
Congratulations, you just pointed out an embarrassing bug. TIOCOUTQ is a feature that needs more testing, and it is only supported on very recent kernels. I'll guess you have 2.6.27+? I just committed a change to fix the ioctl call. Please update and give it another whirl! The above message should never be seen again.
It is possible that TIOCOUTQ is not useful, and the code to use it needs to be removed from libhfp.
Yeah I wondered if it may be just that simple...I know Broadcom is a name that makes most Linuxers who know better wince...I've been through the headaches of the earlier bcm43xx days with their wifi chipsets :) I don't have any other dongles but there is a Staples in town I can pick another one up at...might be nice to have one for the desktop anyway.
BPM80 above had a similar experience with a built-in Broadcom module on his Acer Aspire system. You probably have a USB disconnect message to go along with it in /var/log/messages, and the dongle must be doing something that causes the USB subsystem to reset it. Regardless, there appear to be incompatibilities with BCM2045 right now. I'm going to start searching for a BCM2045 based dongle for my own testing. In the mean time, do you have any other dongles?