All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Eugene Crosser <crosser@average.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Reproducible kernel oops on PPP session start
Date: Mon, 12 Jan 2004 22:35:42 +0100	[thread overview]
Message-ID: <1073943342.8198.8.camel@pegasus> (raw)
In-Reply-To: <1073942535.5527.7.camel@pccross.average.org>

Hi Eugene,

> I'll ask a friend and we'll try pan during this week.

first use l2test only and don't load any other highlevel Bluetooth
protocol. I will also try to reproduce it with my test machines. If it
is a L2CAP only problem it is much more easier to find the bug.

> In the meanwhile, I tried incoming and outgoing OBEX with a cellphone.
> This is how refcounts change:
> 
>                   incoming        outgoing
>                 start   stop    start   stop
>  
> rfcomm          +1      -1      +3      -3
> l2cap           +1      -2      +2      -2

This is actually what I already thought, the problem exists only on
incoming connections. The RFCOMM refcounting is a bit more complex,
because it involves the TTY part that also modifies the refcounting. Let
us try to start on L2CAP level and then step by step narrow the problem.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-01-12 21:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 11:42 Reproducible kernel oops on PPP session start Eugene Crosser
2004-01-07 12:15 ` [Bluez-devel] " Marcel Holtmann
2004-01-07 13:57   ` Eugene Crosser
2004-01-10 12:00     ` Eugene Crosser
2004-01-10 12:11       ` Eugene Crosser
2004-01-11 14:59         ` Marcel Holtmann
2004-01-12  6:33           ` Eugene Crosser
2004-01-12 13:22             ` Marcel Holtmann
2004-01-12 14:52               ` Eugene Crosser
2004-01-12 15:15                 ` Marcel Holtmann
2004-01-12 21:22                   ` Eugene Crosser
2004-01-12 21:35                     ` Marcel Holtmann [this message]
2004-01-12 22:02                       ` Eugene Crosser
2004-01-13 17:32                         ` Marcel Holtmann
2004-01-13 19:33                           ` Marcel Holtmann
2004-01-13 21:32                             ` Eugene Crosser
2004-01-13 23:14                               ` Marcel Holtmann
2004-01-07 14:05   ` Edd Dumbill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1073943342.8198.8.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=crosser@average.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.