Date: Mon, 22 Aug 2005 11:14:51 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Jonatan B <onatan@gmail.com> Cc: freebsd-current@freebsd.org, Pawel Jakub Dawidek <pjd@FreeBSD.org> Subject: Re: [PANIC] 6.0BETA2 in l2ping flood Message-ID: <bb4a86c705082211144b0e0e0b@mail.gmail.com> In-Reply-To: <430A12AB.3030800@savvis.net> References: <430A12AB.3030800@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Jonatan and Pawel, > +> This is a repeatable panic I get when l2ping flooding my tungsten. > +> Maksim? > +> > +> repeatable panic with bluetooth on SMP > +> > +> #> l2ping -fa MyTungsten -s 65531 [...] > Fixed in HEAD, thanks for the report. first, let me thank you both for reporting the problem (Jonatan) and spending time looking into this (Pawel). i was able to reproduce the problem and have fix that i will commit after brief testing. the patch Pawel has committed to HEAD indeed fixes the panic (thanks Pawel!) however it somewhat hides bigger bug in the bluetooth l2cap code. the panic happens when l2cap connection descriptor is deleted with the l2cap command(s) pending in the queue. in this case when the last l2cap command is deleted (due to cleanup) and reference counter for the l2cap connection goes down to zero the auto disconnect timeout is incorrectly set. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c705082211144b0e0e0b>