From: Marcel Holtmann <marcel@holtmann.org>
To: "Williams, Richard" <Richard.Williams@VITRONICS.com>
Cc: "Bluez-Devel (E-mail)" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BNEP kernel oops
Date: Fri, 13 Aug 2004 20:54:37 +0200 [thread overview]
Message-ID: <1092423277.4501.12.camel@pegasus> (raw)
In-Reply-To: <A1F0D47583A2D711919F00600819B3A4028BB8@goofy.vitronics.com>
Hi Richard,
> I am developing an application for a single board computer running an X-scale processor with a BT dongle in the USB port.
>
> I have the following:
> Linux 2.4.26, with the patch-2.4.26-mh2.gz patch applied.
> bluez-libs-2.8
> bluez-utils-2.8
>
> I've cross-compiled all this for the X-scale and everything seems to work OK for rfcomm connections.
> However as soon as I try to create a PAN connection to a remote device, I get a kernel panic.
> The remote device is an iPAQ 5550 with built-in BT, running OPIE. The iPAQ does not crash.
verify if a previous kernel (2.4.26-mh1 or 2.4.26) worked without a
kernel oops.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-08-13 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 18:52 [Bluez-devel] BNEP kernel oops Williams, Richard
2004-08-13 18:54 ` Marcel Holtmann [this message]
2004-08-14 9:29 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2004-08-13 19:12 Williams, Richard
2004-08-13 19:13 ` Marcel Holtmann
[not found] <A1F0D47583A2D711919F00600819B3A45BDCD4@goofy.vitronics.com>
2004-08-13 19:50 ` 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=1092423277.4501.12.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Richard.Williams@VITRONICS.com \
--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