From: David Mansfield <bluez@dm.cobite.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: bluez: bluetoothd: segmentation fault
Date: Wed, 28 Jan 2009 09:54:45 -0500 [thread overview]
Message-ID: <1233154485.32572.23.camel@gandalf.cobite.com> (raw)
> [AO_ALSA] alsa-lib: pcm_bluetooth.c:1531:(audioservice_recv) Error
receiving data \
> from audio service: Success(0) [AO_ALSA] alsa-lib: \
> pcm_bluetooth.c:1547:(audioservice_expect) Bogus message BT_GETCAPABILITIES_REQ \
> received while BT_GETCAPABILITIES_RSP was expected [AO_ALSA] Playback open error: \
> Invalid argument
>
I believe, but cannot prove, that this is caused by the bug I found in
pcm_bluetooth.c the other day (see a previous post) which causes random
memory corruption.
If you can test, try editing audio/pcm_bluetooth.c around line 801. Try
replacing:
revents[0] = (pfds[0].revents & ~POLLIN) | POLLOUT;
revents[1] = (pfds[1].revents & ~POLLIN);
with:
*revents = (pfds[0].revents & ~POLLIN) | (pfds[1].revents & ~POLLIN)| POLLOUT;
and rebuild.
Thanks,
David
next reply other threads:[~2009-01-28 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 14:54 David Mansfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-23 22:46 bluez: bluetoothd: segmentation fault Eric Rannaud
2009-01-28 5:49 ` 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=1233154485.32572.23.camel@gandalf.cobite.com \
--to=bluez@dm.cobite.com \
--cc=linux-bluetooth@vger.kernel.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