From: Thomas Kear <thomas.kear@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Excessive output from snd-bt-sco in dmesg
Date: Sat, 28 Oct 2006 14:31:41 +1300 [thread overview]
Message-ID: <200610281431.45651.thomas.kear@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2348 bytes --]
I have my suspicions this could be something to do with a problem that is
causing audio output to my headset to go completely silent on random
occaisions (usually a 'killall -USR2 btsco' fixes it, but in extreme cases I
have had to unload the module and reload it).
From dmesg, repeated nearly 1500 times:
snd-bt-sco: Shift problem detected! Fixing to 1.
snd-bt-sco: Shift problem detected! Fixing to 0.
And occaisionally this message (or some variation on the number of files):
snd-bt-sco: file_count is 4 (expected 3)
Headset is a Sony Ericsson HBH-IV835
BD Address: 00:18:13:7e:bc:7a
Device Name: HBH-IV835
LMP Version: 2.0 (0x3) LMP Subversion: 0xe1b
Manufacturer: Texas Instruments Inc. (13)
Features: 0xff 0xfd 0x29 0x78 0x18 0x18 0x00 0x80
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <transparent SCO>
<enhanced iscan> <interlaced iscan> <interlaced pscan>
<inquiry with RSSI> <AFH cap. slave> <AFH class. slave>
<AFH cap. master> <AFH class. master> <extended features>
Adapter is 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
hci0: Type: USB
BD Address: 00:02:72:B0:36:D7 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:21511295 acl:351 sco:420012 events:8971 errors:0
TX bytes:21398439 acl:305 sco:418646 commands:7868 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'insanity'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing, Object Transfer,
Audio
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x110 LMP Ver: 1.1 (0x1) LMP Subver: 0x110
Manufacturer: Cambridge Silicon Radio (10)
Since 99% of the time there is no problem that needs to be solved, is there a
simple way to just reduce the verbosity of output to the system log?
--Thomas
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 373 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2006-10-28 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 1:31 Thomas Kear [this message]
2006-10-28 7:02 ` [Bluez-users] Excessive output from snd-bt-sco in dmesg Marcus C. Gottwald
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=200610281431.45651.thomas.kear@gmail.com \
--to=thomas.kear@gmail.com \
--cc=bluez-users@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