From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] 2.6.23.8: kernel panic
Date: Mon, 26 Nov 2007 07:21:35 +0100 [thread overview]
Message-ID: <1196058095.4217.79.camel@aeonflux> (raw)
In-Reply-To: <4746EC10.5080509@pracucci.com>
Hi Marco,
> I have compiled linux kernel 2.6.23.8 for a single board computer based
> on ARM architecture (EP9302 processor). I have tried to stress the
> Bluetooth subsystem, creating repeatly a lot of RFCOMM connections to
> other Bluetooth dongles (installed on remote computers) and I'm able to
> get a kernel panic in few minutes.
it would be good to know if 2.6.24-rc3 shows the same issue and if you
could also produce it on x86. And please post some example code that
would trigger this issue. I haven't seen this kind of problem so far.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-11-26 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 15:04 [Bluez-devel] 2.6.23.8: kernel panic Marco Pracucci
2007-11-26 6:21 ` Marcel Holtmann [this message]
2007-11-27 15:18 ` Marco Pracucci
2007-11-27 10:32 ` Dave Young
2007-11-27 10:38 ` Marcel Holtmann
2007-11-27 15:36 ` Marco Pracucci
2007-11-28 1:33 ` Dave Young
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=1196058095.4217.79.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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