I can confirm it. I use Hardy, my device is (obtained via lsusb):
Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
I'll attach my system information.
--
syslog is flooded with messages after connecting bluetooth usb dongle
** Attachment added: mgol-dmesg.log
http://launchpadlibrarian.net/27871879/mgol-dmesg.log
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
** Attachment added: mgol-lsusb.log
http://launchpadlibrarian.net/27871885/mgol-lsusb.log
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
** Attachment added: mgol-uname-a.log
http://launchpadlibrarian.net/27871890/mgol-uname-a.log
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
** Attachment added: mgol-lspci-vnvn.log
http://launchpadlibrarian.net/27871882/mgol-lspci-vnvn.log
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: mgol-version.log
http://launchpadlibrarian.net/27871892/mgol-version.log
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
OK, I don't know if this bug report should be touched any longer as it is
closed. I reported another one:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/386736
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received
The same problem with
Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
on
2.6.24-24-generic #1 SMP Wed Apr 15 15:11:35 UTC 2009 x86_64 GNU/Linux
Still no solution?
--
syslog is flooded with messages after connecting bluetooth usb dongle
I changed hci_usb.c to
{ USB_DEVICE(0x0a12, 0x0001), .driver_info = HCI_CSR |
HCI_BROKEN_ISOC},
so now there is no
hci_scodata_packet: hci0 SCO packet for unknown connection handle 92
messages
But when I try to pair with my wm5 phone ubuntu crashes.
--
syslog is flooded with messages
Same problem on Hardy 64 bit, kernel 2.6.24-24
Attached is the lsusb -v output (I selected only the part related to the
interested device (0a12:0001 - Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)).
** Attachment added: lsusb.txt
http://launchpadlibrarian.net/23721908/lsusb.txt
Same continuing issue on 2 different Ubuntu boxes:
$ dmesg | grep hci0
Thousands of,,
[13231.381436] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
$ uname -srmo
Linux 2.6.24-23-generic i686 GNU/Linux
$ lsusb
...
Bus 003 Device 006: ID 0a12:0001 Cambridge Silicon Radio,
Reverting eSCO worked for me.
Always reconnect from BT Headset for reliable connection before using aplay or
skype dialing.
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member
Having the same problem with my stick:
ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
Adding HCI_BROKEN_ISOC to hci_usb.c worked for me as well:
{ USB_DEVICE(0x1131, 0x1001), .driver_info = HCI_RESET |
HCI_BROKEN_ISOC },
Using Ubuntu 8.04 and kernel
The bug task without a package is not valid so I'm setting its status to
Invalid.
** Changed in: ubuntu
Status: Incomplete = Invalid
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because
I have the same problem with hardy heron and
- bluez-utils version 3.26-0ubuntu6.
- linux 2.6.24-18-generic
- Motorola H500 headset (SCO)
- my dell latitude integrated bluetooth
When I associate the headset and try it
mplayer -ao alsa:device=bluetooth /usr/share/example-content/ubuntu
Still happening on 2.6.24-16-generic :(
lots of hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
attached lsusb -v
thanks
On Fri, Apr 11, 2008 at 6:15 PM, MsTiFtS [EMAIL PROTECTED] wrote:
@quixote_arg: can't reproduce problem on 2.6.24-16-generic. My headset
does still
With 2.6.24-16-generic, my Motorola H300 works fine. I suspect that
those of you who still have problems may be experiencing something
similar to http://bugzilla.kernel.org/show_bug.cgi?id=6833 .
--
syslog is flooded with messages after connecting bluetooth usb dongle
@quixote_arg: can't reproduce problem on 2.6.24-16-generic. My headset
does still not work, but the syslog flood doesn't occur any more.
Sometimes there are still single SCO packet for unknown connection
handle, but not several thousands per second(!) as I experienced
before.
--
syslog is
problem persists on 2.6.24-14-generic
ID 1131:1001 Integrades System Solution Corp. KY-BT100 Bluetooth Adapter
On Sun, Mar 30, 2008 at 7:50 PM, Launchpad Bug Tracker
[EMAIL PROTECTED] wrote:
This bug was fixed in the package linux - 2.6.24-13.23
---
linux (2.6.24-13.23) hardy;
This bug was fixed in the package linux - 2.6.24-13.23
---
linux (2.6.24-13.23) hardy; urgency=low
[Alessio Igor Bogani]
* rt: Updated configuration files
[Ben Collins]
* openvz: New custom flavour for OpenVZ
* config: Disable IDE AMD driver in favor of PATA version
Please use the Simpler patch near the bottom (one-liner)
** Changed in: linux (Ubuntu)
Target: None = ubuntu-8.04
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Stefan Bader
(stefan-bader-canonical)
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Committed
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
This is the patch that I'm using right now.
** Attachment added: Simpler patch: Always use SCO
http://launchpadlibrarian.net/12699239/always_use_sco.patch
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug
It does work on vanilla 2.6.24.3 in the sense that it doesn't crash the
system, but it also occasionally generates white noise instead of the
correct audio. If somebody thinks it's useful, I could bisect between
the vanilla and hardy kernels to find what change in combination with
the patch causes
I've been told that the oops-causing patches mentioned above actually
work on vanilla kernel.org kernels.
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete = Triaged
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received
How can i use this patch, help me please)
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
From #bluez irc channel, talking to Brad Midgley, one of the bluez
developers:
bmidgley johanbr: the audio patch I referred to is broken and needs reworking
[...]
bmidgley johanbr the last resolution i saw for this was reverting esco
... so it seems like the only solution available at present is
I've bisected down to the bad commit between 2.6.22 and 2.6.24. It's
this:
commit b6a0dc822497e1c0b9e8c4add270cc27fce48454
Author: Marcel Holtmann [EMAIL PROTECTED]
Date: Sat Oct 20 14:55:10 2007 +0200
[Bluetooth] Add support for handling simple eSCO links
With the Bluetooth 1.2
Reverting that commit in the latest Hardy kernel and fixing the
conflicts gets me a working headset!
Meanwhile, the latest patch I tried crashes like the others:
http://thread.gmane.org/gmane.linux.bluez.kernel/14
--
syslog is flooded with messages after connecting bluetooth usb dongle
Same here.
hci_scodata_packet: hci0 SCO packet for unknown connection handle 92
hci_scodata_packet: hci0 SCO packet for unknown connection handle 92
hci_scodata_packet: hci0 SCO packet for unknown connection handle 92
hci_scodata_packet: hci0 SCO packet for unknown connection handle 92
Thank you for the testing, Brian. I guess dropping the eSCO support
isn't ideal, but in my opinion it's better than having a non-working
connection that floods the syslog. Brian, is there any chance you could
attach a clean patch against the Hardy kernel?
--
syslog is flooded with messages after
Related kernel.org bug: http://bugzilla.kernel.org/show_bug.cgi?id=9871
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Here's a patch.
** Attachment added: Revert eSCO support
http://launchpadlibrarian.net/12347009/revert-esco.patch
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of
I have this problem, and that patch just causes an OOPS for me when I
try to play audio to my headset. I wasn't able to record the contents.
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because
Hmm. There's an alternate patch at
http://thread.gmane.org/gmane.linux.bluez.user/13573/focus=13592
If Brian (or anyone else) could try that, it'd be much appreciated.
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received
Same crash (as far as I can tell) with the new patch. Also, I should
specify that I'm trying the patch on Hardy's 2.6.24 kernel in git.
2.6.22 did not have this problem for me.
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You
Hi Guys,
I just need some clarification. It was stated Here the same problem
with Linux ubuntu 2.6.24 (gutsy 7.10) but that would seem to be a
contradiction. Gutsy 7.10 uses the 2.6.22 kernel. Hardy Heron 8.04
uses the 2.6.24 kernel. Care to post a correction as to what you are
really running
** Attachment added: uname
http://launchpadlibrarian.net/12287151/uname
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
** Attachment added: version
http://launchpadlibrarian.net/12287152/version
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
** Attachment added: lspci
http://launchpadlibrarian.net/12287155/lspci
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
I have this problem on Hardy. Attaching the requested files, except for
dmesg which only consists of thousands of lines saying
[ 503.613772] hci_scodata_packet: hci0 SCO packet for unknown
connection handle 1
For a dmesg which includes the boot messages, see
Link to (untested) patch that supposedly fixes the problem:
http://lkml.org/lkml/2008/2/27/105
Please note that Marcel Holtmann, the bluetooth maintainer, thinks this
patch is correct.
--
syslog is flooded with messages after connecting bluetooth usb dongle
Here the same problem with Linux ubuntu 2.6.24 (gutsy 7.10)
How Can I fix it? When fix is gone???
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I've opened a task for this bug against the linux source package as the
continued reports appear to indicate a continuing issue (as if the bug
were actually Fix Released on 7th July 2007, it would be unlikely to
affect users of Ubuntu 7.10. Please reclose if there is a patch fixing
this that I do
Here the same problem with Linux ubuntu 2.6.24 (gutsy 7.10)
a short time after booting all is ok, but then
[ 487.936916] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 46
[ 487.936923] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 46
and so on.
**
Same here. Gutsy 7.10, kernel 2.6.22-14-generic, dongle recognized as 0e5e:6622
(it is a phonix PHB410), and the syslog continues giving messages such as
[19325.944260] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[19325.944265] hci_scodata_packet: hci0 SCO packet for
I have the same problem with my Blue Soleil Bluetooth dongle
(Vendor:Device = 0e5e:6622). I've found you can suppress generation of
the messages by changing the isoc parameter passed to the hci_usb
kernel module. Depending on distro, you might put hci_usb isoc=new
value in '/etc/modules' or
I have the same problem with my Blue Soleil Bluetooth dongle
(Vendor:Device = 0e5e:6622). I've found you can suppress generation of
the messages by changing the isoc parameter passed to the hci_usb
kernel module. Depending on distro, you might put hci_usb isoc=new
value in '/etc/modules' or
I have the same problem with my Blue Soleil Bluetooth dongle
(Vendor:Device = 0e5e:6622). I've found you can suppress generation of
the messages by changing the isoc parameter passed to the hci_usb
kernel module. Depending on distro, you might put hci_usb isoc=new
value in '/etc/modules' or
I have the same problem with my Blue Soleil Bluetooth dongle
(Vendor:Device = 0e5e:6622). I've found you can suppress generation of
the messages by changing the isoc parameter passed to the hci_usb
kernel module. Depending on distro, you might put hci_usb isoc=new
value in '/etc/modules' or
I have the same problem with my Blue Soleil Bluetooth dongle
(Vendor:Device = 0e5e:6622). I've found you can suppress generation of
the messages by changing the isoc parameter passed to the hci_usb
kernel module. Depending on distro, you might put hci_usb isoc=new
value in '/etc/modules' or
I have the same problem with my Blue Soleil Bluetooth dongle
(Vendor:Device = 0e5e:6622). I've found you can suppress generation of
the messages by changing the isoc parameter passed to the hci_usb
kernel module. Depending on distro, you might put hci_usb isoc=new
value in '/etc/modules' or
Correction: In my last post, I meant to specify that the line options
hci_usb isoc=new value, if used, should be added to
'/etc/modprobe.conf'.
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification
Here is the output of running lsusb -v on my machine, with the
BlueSoleil USB bluetooth dongle (Vendor:Device 0e5e:6622) inserted.
** Attachment added: lsusb -v Output
http://launchpadlibrarian.net/5756/lsusb_v.txt
--
syslog is flooded with messages after connecting bluetooth usb dongle
These messages can be filtered out of syslog. The basic instructions
are here:
http://www.giacintosblog.splinder.com/post/15040472/Ubuntu%3A+Palliativo+per+il+bug+
You need to install syslog-ng, and add to /etc/syslog-ng/syslog-ng.conf:
filter f_bluetooth_error {
facility(kern) and
I have same problem in gutsy, causing massive sized syslog and kern.log
files.
uname -srmo
Linux 2.6.22-14-generic i686 GNU/Linux
dmesg |tail
[ 443.549732] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[ 443.549735] hci_scodata_packet: hci0 SCO packet for unknown
I have same problem in gutsy, causing massive sized syslog and kern.log
files.
uname -srmo
Linux 2.6.22-14-generic i686 GNU/Linux
dmesg |tail
[ 443.549732] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[ 443.549735] hci_scodata_packet: hci0 SCO packet for unknown
Seeing the same problem.
Attached is my lsusb -v
uname -srmo
Linux 2.6.22-14-generic i686 GNU/Linux
dmesg |tail
[426929.428099] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[426929.428102] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
Linux mobigreg 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007
i686 GNU/Linux
ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
attached lsusb -v
** Attachment added: lsusb-v.txt
http://launchpadlibrarian.net/10285717/lsusb-v.txt
--
syslog is flooded with
I have the same thing with 0e5e:6622 in gutsy. The output from lsusb is
attached.
$ dmesg
[11193.473686] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[11193.483659] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[11193.483670] hci_scodata_packet:
Somehow the upstream fix has not lead to progress in Ubuntu.
** Changed in: ubuntu
Status: Invalid = Incomplete
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of
I've just upgraded to gutsy and I'm still getting the same flooding messages as
above. Any chances to fix it before the gutsy final version?
I don't attach lsusb -v, since it's the same device as japuzzo's one
(0e5e:6622).
--
syslog is flooded with messages after connecting bluetooth usb
have the same issue with:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.04
DISTRIB_CODENAME=feisty
DISTRIB_DESCRIPTION=Ubuntu 7.04
Kernel: 2.6.20-16-lowlatency
Platform: x86_64
dmesg is full of:
[107224.059239] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[107224.059241]
Sorry, just read your message. Was on vacation ;-)
Attached you can find my lsusb -v
Thanks a lot
Il giorno lun, 06/08/2007 alle 14.30 +, Chuck Short ha scritto:
For those who are still having this problem, can you attach the full
output of lsusb -v. To this bug Ill see If I can get a fix
I think filtering these messages would be possible using e.g. the
syslog-ng logging daemon. But just filtering the log is no clean
solution, as this would spend lots of CPU cycles on generating and
filtering syslog messages.
As the upstream bug I filed
For those who are still having this problem, can you attach the full
output of lsusb -v. To this bug Ill see If I can get a fix in for gutsy.
Thanks
chuck
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug
Since the device works for everyone here, wouldnt be possible to manage on
the syslog daemon and configure it to ignore such messages? Does anyone know
how to do it? I think i found something like this somewhere, but can't
remember where.
--
syslog is flooded with messages after connecting
This bug exists in feisty as well here is the output of the shell
commands I ran
[EMAIL PROTECTED]:~$ lsusb
Bus 002 Device 001: ID :
Bus 005 Device 001: ID :
Bus 004 Device 001: ID :
Bus 003 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100
Getting the same error.
lsusb
Bus 001 Device 004: ID 0e5e:6622
uname -a
Linux dave-laptop 2.6.22-9-generic #1 SMP Wed Aug 1 17:31:10 GMT 2007 i686
GNU/Linux
dmesg
-SNIP
[37829.836000] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[37829.836000]
Same problem here :
[ 449.245982] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[ 449.246224] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[ 449.255678] hci_scodata_packet: hci0 SCO packet for unknown connection
handle 92
[ 449.255919]
** Changed in: linux (upstream)
Importance: Unknown = Undecided
Bugwatch: Linux Kernel Bug Tracker #6833 = None
Status: Invalid = New
** Changed in: linux (upstream)
Status: New = Fix Released
--
syslog is flooded with messages after connecting bluetooth usb dongle
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Fix Committed = Fix Released
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Fix Released = Fix Committed
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Fix Committed = Fix Released
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://bugs.launchpad.net/bugs/39414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
I apparently have the same problem. I have a CNet CBD-120 Bluetooth V2.0
USB Adapter. My syslog and kern.log is flooded with this type of
messages:
Jul 2 07:39:13 mirshafie kernel: [144467.293717] usb 7-4: clear tt 1
(9282) error -71
--
syslog is flooded with messages after connecting
The bug still exists in 2.6.15-28-686.
It is mildened in the way that the syslog is no longer really flooded by a
seemingly new printk feature, so syslog says now:
Mar 30 16:20:23 nx7000 kernel: [17180739.048000] Bluetooth: HCI USB driver ver
2.9
Mar 30 16:20:23 nx7000 kernel: [17180739.052000]
Going through Fix Committed bugs that are old. What is the status of
this one?
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://launchpad.net/bugs/39414
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Rejecting bug filed on Ubuntu, as bug filed under linux-source-2.6.15
has been fixed.
** Changed in: Ubuntu
Status: Unconfirmed = Rejected
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://launchpad.net/bugs/39414
--
ubuntu-bugs mailing list
I´m having the same problem.
My system: 2.6.15-27-386
lsusb:
Bus 001 Device 002: ID 0846:4240 NetGear, Inc. WG111 WiFi (v2)
Bus 001 Device 001: ID :
Bus 002 Device 005: ID 0400:080a National Semiconductor Corp.
Bus 002 Device 004: ID 03f0:7204 Hewlett-Packard DeskJet 36xx
Bus 002 Device
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) = Ben Collins
Status: Confirmed = Fix Committed
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://launchpad.net/bugs/39414
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: linux (upstream)
Status: Unknown = Confirmed
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://launchpad.net/bugs/39414
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Same problem with the exactly same dongle.
lsusb: Bus 003 Device 004: ID 0400:080a National Semiconductor Corp.
Running 2.6.15-26-686 #1 SMP PREEMPT Fri Jul 7 19:48:22 UTC 2006 (dapper
6.06).
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Unconfirmed = Confirmed
--
syslog is
** Bug watch added: Linux Kernel Bug Tracker #6833
http://bugzilla.kernel.org/show_bug.cgi?id=6833
** Also affects: linux (upstream) via
http://bugzilla.kernel.org/show_bug.cgi?id=6833
Importance: Unknown
Status: Unknown
--
syslog is flooded with messages after connecting
I have exactly the same problem with exactly the same dongle.
Running 2.6.15-25-386 (Dapper 6.06)
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://launchpad.net/bugs/39414
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: linux-image-2.6.15-19-386 (Ubuntu)
Sourcepackagename: linux-image-2.6.15-19-386 = linux-source-2.6.15
--
syslog is flooded with messages after connecting bluetooth usb dongle
https://launchpad.net/bugs/39414
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
87 matches
Mail list logo
