From: Edd Dumbill <edd@usefulinc.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: Lockups (was Re: [Bluez-devel] Bluetooth kernel patch for 2.6.0)
Date: Tue, 06 Jan 2004 23:54:51 +0000 [thread overview]
Message-ID: <1073433290.2674.2.camel@saag> (raw)
In-Reply-To: <1073428132.2508.106.camel@pegasus>
On Tue, 2004-01-06 at 22:28, Marcel Holtmann wrote:
> at the moment I am not able reproduce it. Try to track the problem and
> give me reports on it. It must be some kind of strange bug that can't be
> easily found.
I can reliably reproduce it here (just tried again with 2.6.1-rc2 (+your
patches). Can you recommend any technique I might be able to use to
provide you with more information?
>>From hcidump, the lockup appears to happen before ever I see any traffic
from the dump: so it's as the connection is established from the remote
device (yes, my trusty P800!). I've tried with and without PREEMPT set.
-- Edd
next prev parent reply other threads:[~2004-01-06 23:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 10:58 [Bluez-devel] Bluetooth kernel patch for 2.6.0 Marcel Holtmann
2004-01-02 14:04 ` Olivier Bornet
2004-01-02 23:40 ` Marcel Holtmann
2004-01-02 23:03 ` Edd Dumbill
2004-01-02 23:31 ` Marcel Holtmann
2004-01-03 12:17 ` Lockups (was Re: [Bluez-devel] Bluetooth kernel patch for 2.6.0) Edd Dumbill
2004-01-03 14:43 ` Edd Dumbill
2004-01-06 20:24 ` Edd Dumbill
2004-01-06 22:28 ` Marcel Holtmann
2004-01-06 23:54 ` Edd Dumbill [this message]
2004-01-07 1:29 ` Edd Dumbill
2004-01-07 4:57 ` [Bluez-devel] Re: Lockups Marcel Holtmann
2004-01-07 14:19 ` Lockups Edd Dumbill
2004-01-07 15:08 ` [Bluez-devel] Lockups Marcel Holtmann
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=1073433290.2674.2.camel@saag \
--to=edd@usefulinc.com \
--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 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.