Linux bluetooth development
 help / color / mirror / Atom feed
From: Eugene Crosser <crosser@average.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Reproducible kernel oops on PPP session start
Date: Tue, 13 Jan 2004 01:02:33 +0300	[thread overview]
Message-ID: <1073944953.5527.16.camel@pccross.average.org> (raw)
In-Reply-To: <1073943342.8198.8.camel@pegasus>

On Tue, 2004-01-13 at 00:35, Marcel Holtmann wrote:

> 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.

while right now I only have one host where l2test can be run, I tried
it:

l2test -s 00:01:02:03:04:05
 - l2cap count increased by 2, then I get "Host is down" and count
decreased by 2

l2test -r
 - count increased by 3, program waits.  When I hit ctrl-break, count
decreased by 3

Eugene

  reply	other threads:[~2004-01-12 22:02 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
2004-01-12 22:02                       ` Eugene Crosser [this message]
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=1073944953.5527.16.camel@pccross.average.org \
    --to=crosser@average.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox