All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Freeman <johnf@optimation.com.au>
To: Brad Midgley <bmidgley@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Intermittent "Address already in use" error
Date: Fri, 31 Jul 2009 11:06:35 +1000	[thread overview]
Message-ID: <27008598.1249002400393.JavaMail.root@safetgram> (raw)
In-Reply-To: <2648525.1248996255356.JavaMail.root@safetgram>

Brad Midgley wrote:
>> Can anyone suggest where I should start looking?
> 
> Are you using a recent kernel and bluez?

Very recent:
Kernel  2.6.29.5-84.fc10.i686
bluez-4.30-2.fc10.i386

 > Do you have example code that
 > will cause the problem? Even better if it is in script like python.

The code that causes the problem is 4000 lines of python, most of which I can't 
publish; you probably wouldn't want to look at it anyway.  I haven't been able 
to reduce it to a simple example because minor changes cause the problem to 
disappear.  Even running strace on the program makes the problem go away, so it 
looks like it's timing-related.

I was asking where in kernel/bluez code should I start looking.


  parent reply	other threads:[~2009-07-31  1:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 10:08 Intermittent "Address already in use" error John Freeman
2009-07-24 16:47 ` Brad Midgley
     [not found] ` <5111969.1248454126654.JavaMail.root@safetgram>
2009-07-28  8:36   ` John Freeman
2009-07-28 17:31     ` Brad Midgley
     [not found]     ` <27042187.1248802358830.JavaMail.root@safetgram>
2009-07-30  9:17       ` John Freeman
2009-07-30 23:23         ` Brad Midgley
     [not found]         ` <2648525.1248996255356.JavaMail.root@safetgram>
2009-07-31  1:06           ` John Freeman [this message]
     [not found]           ` <33459247.1249002454978.JavaMail.root@safetgram>
2009-07-31  6:36             ` John Freeman

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=27008598.1249002400393.JavaMail.root@safetgram \
    --to=johnf@optimation.com.au \
    --cc=bmidgley@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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.