* bnep and refcnt
@ 2004-03-07 15:25 wim delvaux
2004-03-08 0:27 ` [Bluez-users] " Marcel Holtmann
0 siblings, 1 reply; 3+ messages in thread
From: wim delvaux @ 2004-03-07 15:25 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: BlueZ Mailing List
Hi,
after browsing the Linux 2.6 code there is a remark in net/core/dev.c that
state what the problem with the following message that I get is
unregister_netdevice: waiting for bnep0 to become free. Usage count = 6
The comment with the function in dev.c states that this error is caused by
buggy protocols that should unregister after receiving notification that the
devices they are using has been unregistered. They should call
unregister_netdev which decreases the refcnt.
Can anybody help me tracking down this problem I have with explaning which
protocols could be using bnep0 ?
W
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bluez-users] Re: bnep and refcnt
2004-03-07 15:25 bnep and refcnt wim delvaux
@ 2004-03-08 0:27 ` Marcel Holtmann
2004-03-08 1:02 ` wim delvaux
0 siblings, 1 reply; 3+ messages in thread
From: Marcel Holtmann @ 2004-03-08 0:27 UTC (permalink / raw)
To: wim delvaux; +Cc: BlueZ Mailing List
Hi Wim,
> after browsing the Linux 2.6 code there is a remark in net/core/dev.c that
> state what the problem with the following message that I get is
>
> unregister_netdevice: waiting for bnep0 to become free. Usage count = 6
>
> The comment with the function in dev.c states that this error is caused by
> buggy protocols that should unregister after receiving notification that the
> devices they are using has been unregistered. They should call
> unregister_netdev which decreases the refcnt.
looks like we need a more detailed audit for the BNEP module and some of
the 2.6 changes in the network device layer.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: bnep and refcnt
2004-03-08 0:27 ` [Bluez-users] " Marcel Holtmann
@ 2004-03-08 1:02 ` wim delvaux
0 siblings, 0 replies; 3+ messages in thread
From: wim delvaux @ 2004-03-08 1:02 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: BlueZ Mailing List
On Monday 08 March 2004 01:27, Marcel Holtmann wrote:
> Hi Wim,
>
> > after browsing the Linux 2.6 code there is a remark in net/core/dev.c
> > that state what the problem with the following message that I get is
> >
> > unregister_netdevice: waiting for bnep0 to become free. Usage count = 6
> >
> > The comment with the function in dev.c states that this error is caused
> > by buggy protocols that should unregister after receiving notification
> > that the devices they are using has been unregistered. They should call
> > unregister_netdev which decreases the refcnt.
>
> looks like we need a more detailed audit for the BNEP module and some of
> the 2.6 changes in the network device layer.
I tried that but did not find anything usefull.
I noticed (after GREP) that the BNEP module does not have a notify function
(does it need one ?).
Hence I think we need to look for those systems (HCID?) that have a
reference to the bnep module. Probably those do not unregister properly
How can I compile them in debug ?
Thanx
W
>
> Regards
>
> Marcel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-03-08 1:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-07 15:25 bnep and refcnt wim delvaux
2004-03-08 0:27 ` [Bluez-users] " Marcel Holtmann
2004-03-08 1:02 ` wim delvaux
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).