From: Marcel Holtmann <marcel@holtmann.org>
To: Pierre Savary <pierre.savary@kerlink.fr>
Cc: BlueZ-Dev <bluez-devel@lists.sourceforge.net>,
bluez-users@lists.sourceforge.net,
linux-bluetooth@vger.kernel.org
Subject: Re: problems with kernel 2.6.23 + bluez 3.36 + SCO
Date: Thu, 23 Oct 2008 06:57:47 +0200 [thread overview]
Message-ID: <1224737867.9386.184.camel@californication> (raw)
In-Reply-To: <000001c92e07$010874f0$03195ed0$@savary@kerlink.fr>
Hi Pierre,
> We develop an application for our board based on SCO. We use the kernel
> version 2.6.23 and the bluez-lib 3.36. However we have a lot of problems and
> some "kernel panic". Below this message you will find some of these kernel
> messages.
> How can we stop it? Have you ever saw that?
switch to a 2.6.27 kernel.
Regards
Marcel
next prev parent reply other threads:[~2008-10-23 4:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 14:13 problems with kernel 2.6.23 + bluez 3.36 + SCO Pierre Savary
2008-10-23 4:57 ` Marcel Holtmann [this message]
2008-10-24 9:18 ` [Bluez-devel] " rakesh agarwal
2008-10-24 10:22 ` Marcel Holtmann
2008-10-29 14:49 ` Pierre Savary
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=1224737867.9386.184.camel@californication \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-users@lists.sourceforge.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pierre.savary@kerlink.fr \
/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