Date: Wed, 18 May 2005 14:10:39 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: bthidd core dumped Message-ID: <428BAF4F.3080809@savvis.net> In-Reply-To: <428BADE1.1020704@centtech.com> References: <428B36BF.5070709@centtech.com> <428B69CE.1070909@savvis.net> <428B86E4.5040306@centtech.com> <428B889E.8090804@savvis.net> <428B89D1.1050306@centtech.com> <428B8BA8.2020002@savvis.net> <428BAC1A.9050500@savvis.net> <428BADE1.1020704@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric, >>>>>>>> This morning, I booted up and began using my laptop with my >>>>>>>> bluetooth mouse. I've been using this mouse for several days now >>>>>>>> without a single problem. Yesterday I added a new bluetooth >>>>>>>> mouse (MS Intellimouse), and had both running simultaneously just >>>>>>>> fine all day yesterday and last night. This morning, after my >>>>>>>> machine was up for about 30-40 minutes, my mouse stopped working. >>>>>>>> I hit the buttons, switched the on/off switch, etc. I was only >>>>>>>> using one mouse at the time (however, my second mouse was >>>>>>>> probably within range and I believe it was on in my backpack). >>>>>>>> After messing with the switch a few times, bthidd core dumped. I >>>>>>>> restarted it, and hit the switch on my mouse a few more times, >>>>>>>> and then I got mouse services back. >>>>>>> >>>>>>> [...] >>>>>>> >>>>>>>> May 18 06:44:38 neutrino kernel: pid 482 (bthidd), uid 0: exited >>>>>>>> on signal 6 (core dumped) >>>>>>> >>>>>>> signal 6 is SIGABRT (abort(3)). i bet one of the assert()'s fired. >>>>>>> do you still have bthidd(8) core file? it should be in /. can you >>>>>>> try to get a stack trace or at least assert()'s message? can you >>>>>>> try to reproduce the problem with bthidd(8) running in foreground? >>>>>> >>>>>> Yes, I still have the core file, but I'm not sure what to do with it >>>>>> :) >>>>> >>>>> gdb /path/to/executable/bthidd /path/to/code/bthidd.core >>>>> >>>>> and send me the output of gdb. then at (gdb) prompt type >>>>> >>>>> (gdb) where >>>>> >>>>> and send me the output >>>> >>>> # gdb /usr/sbin/bthidd /bthidd.core >>> >>> [...] >>> >>>> Is that what you needed? >>> >>> yes, thanks. just like i suspected one of the assert()s fired. i'm >>> going to look at this. just one question: can you put the core file >>> somewhere i can download it? if you can it would help me to >>> troubleshoot the problem faster. if you cant - no big deal. >> >> ok, i found the problem. i have attached the patch that should fix it. >> please do >> >> 1) save attached patch somewhere >> >> 2) cd /usr/src/usr.sbin/bluetooth/bthidd >> >> 3) patch < /path/to/saved/bthidd.patch.txt >> >> 4) make cleandir && make depend && make && make install >> >> this patch is against bthidd(8) sources committed to -current. > > Ok - running it now. I'll let you know if I have any issues with it - > none so far. actually, it should be pretty easy to test. just force your bluetooth mouse to disconnect. either by powering it off or taking it out of RF range (should be about 10 meters). you should see bthidd(8) saying that device was disconnected. then power on the mouse (or move it into RF range) and move it (or press button). you should see bthidd(8) saying that device is connected. try above several times. thanks for reporting this! max > > Eric > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?428BAF4F.3080809>