From: ilmari@ilmari.org (Dagfinn Ilmari Mannsåker)
To: bluez-devel@lists.sourceforge.net
Cc: ilmari@ilmari.org
Subject: [Bluez-devel] Re: oops when playing audio
Date: Sun, 13 Jun 2004 07:31:53 +0200 [thread overview]
Message-ID: <d8jllis10s6.fsf@wirth.ping.uio.no> (raw)
In-Reply-To: d8jpt8413da.fsf@wirth.ping.uio.no
ilmari@ilmari.org (Dagfinn Ilmari Mannsåker) writes:
> Hi,
>
> I was just playing around with hstest and my new Bluetooth headset (a
> Jabra BT250, to be precise) when I got this oops after a few minutes'
> playback:
[...]
> Call Trace:
> [<c021d4c8>] kfree_skbmem+0x8/0x20
> [<c021d56c>] __kfree_skb+0x8c/0x120
> [<d09d252e>] bt_sock_recvmsg+0x7e/0xb0 [bluetooth]
> [<c0219f40>] sock_aio_read+0xb0/0xd0
> [<c014e7ed>] do_sync_read+0x6d/0xb0
> [<c016007d>] sys_select+0x24d/0x4b0
> [<c014e917>] vfs_read+0xe7/0x110
> [<c014eb38>] sys_read+0x38/0x60
> [<c0103ef9>] sysenter_past_esp+0x52/0x71
I just had a few other, similar, oopses involving unix_stream_recvmsg
instead of bt_sock_recvmsg, so this is probably not BlueZ' fault, it
just got bit by it first.
Sorry for the bogus report (but the disconnect/reconnect thing is still
valid, it happens independantly of the oopsing).
--
ilmari
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-13 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 4:36 [Bluez-devel] oops when playing audio Dagfinn Ilmari Mannsåker
2004-06-13 5:31 ` Dagfinn Ilmari Mannsåker [this message]
2004-06-14 16:02 ` 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=d8jllis10s6.fsf@wirth.ping.uio.no \
--to=ilmari@ilmari.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