[Touch-packages] [Bug 1886714] Re: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect
The bug is still present in Ubuntu 22.10 on a Gigabyte Technology Co., Ltd. GA-990FXA-UD3, when attached to an HK Onyx Studio 6. Usually a work around is to restart the Bluetooth stack twice. My wild guess is that a (ring) buffer in the Bluetooth stack is filled, and isn't reset because the sound system can't catch up. It then goes on until it crashes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP fi
[Touch-packages] [Bug 1886714] Re: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect
I'm pretty sure this is the same bug https://bugs.freedesktop.org/show_bug.cgi?id=58746 There is a proposed patch at https://bugs.freedesktop.org/show_bug.cgi?id=58746#c14 ** Bug watch added: freedesktop.org Bugzilla #58746 https://bugs.freedesktop.org/show_bug.cgi?id=58746 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initi
[Touch-packages] [Bug 1886714] Re: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect
If I restart and try to use my Sony headphones, then sound stutter and fails. If I run `sudo hcidump --ext avdtp`, then it works… This is weird! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.8
[Touch-packages] [Bug 1886714] Re: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect
Several programs are updated, it could be that this works now even if the sound breaks up from time to time. I'll do some more testing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Blu
[Touch-packages] [Bug 1886714] Re: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect
While waiting for a new Bluetooth dongle I messed around with some other equipment. It seems like I can't make a Herman/Kardon Onyx 4 to fail, which is a bit strange. Tried to log it with hcidump and nothing unusual showed up. Logging avdtp gave identical results. So just to double-check what happen when I attached my Sony headphones I started hcidump and connected the headphone, and started playing a streamed movie. I see the effect of the sound breaking up, but I can't make the connection fail when hcidump is running. Usually it is enough to provoke some glitches in the connection, then delay builds up, and the phone disconnects. When that happen all devices using sound over USB dies. With hcidump running is does not die. This is really weird, as hcidump should not change the stream in any way. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer
[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
As soon as I can get an [Asus USB BT500](https://www.asus.com/Networking /USB-BT500/) I will try that, as I suspect this issue is somehow related to the chip in the dongle. It seems like all dongles with the same chip has the same issue. The sound problem is probably (?) a secondary effect, but that is the most prominent effect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.8353
[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
Slightly different machine, running 20.04 LTS, but not too different I guess. Uses the same BT-400 dongle as the other machine, the Hama dongle seems to create additional problems even if it should use the same chip. Also tried Fedora 32 from a live USB stick, it had the same problem. I wonder if it somehow is triggered by sampling rate, number of bits, encoding, or something similar as it wasn't triggered while I saw “The Old Guard” but when I started “Nighfliers” it emerged pretty fast. It seems to start with an increasing delay (lack of sync) until it fails. When it did fail before the apport report the sound in my Bluetooth headphones stopped, but it was still connected in the Bluetooth pane in “preference”. I turned the headphones off, but they were still listed as connected. Turned them back on, still connected. Tried to manually set the output device, no change. Then ran apport-collect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [
[Touch-packages] [Bug 1886714] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391484/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound'
[Touch-packages] [Bug 1886714] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391488/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg |
[Touch-packages] [Bug 1886714] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391492/+files/rfkill.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound'
[Touch-packages] [Bug 1886714] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391491/+files/getfacl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound'
[Touch-packages] [Bug 1886714] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391493/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound'
[Touch-packages] [Bug 1886714] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391490/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound'
[Touch-packages] [Bug 1886714] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391486/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$
[Touch-packages] [Bug 1886714] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391481/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'soun
[Touch-packages] [Bug 1886714] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391489/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep
[Touch-packages] [Bug 1886714] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391480/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound' [
[Touch-packages] [Bug 1886714] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391487/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep
[Touch-packages] [Bug 1886714] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391485/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep
[Touch-packages] [Bug 1886714] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391483/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound'
[Touch-packages] [Bug 1886714] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391482/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound' [
[Touch-packages] [Bug 1886714] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1886714/+attachment/5391479/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Incomplete Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgr
[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
apport information ** Tags added: apport-collected focal ** Description changed: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound' [7.920552] input: HDA ATI SB Rear Mic as /devices/pci:00/:00:14.2/sound/card0/input27 [7.920612] input: HDA ATI SB Front Mic as /devices/pci:00/:00:14.2/sound/card0/input28 [7.920657] input: HDA ATI SB Line as /devices/pci:00/:00:14.2/sound/card0/input29 [7.920704] input: HDA ATI SB Li
[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
>From second paragraph “I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.)” The bug was infact the reason I updated to 19.04 and later to 19.10, but it did not go away. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Won't Fix Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Blue
[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
** Description changed: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running - Ubuntu 19.10 and Gnome 3.34.2. + Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also + persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 - john@hydra:~$ dmesg | fgrep 'sound' [7.920552] input: HDA ATI SB Rear Mic as /devices/pci:00/:00:14.2/sound/card0/input27 [7.920612] input: HDA ATI SB Front Mic as /devices/pci:00/:00:14.2/sound/card0/input28 [7.920657] input: HDA ATI SB Line as /devices/pci:00/:00:14.2/sound/card0/input29 [7.920704] input: HDA ATI SB Line Out Front as /devic
[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
After the crash (hid hangs, could be a side effect) this is the dmesg.0 file still existing john@hydra:~$ tail -100 /var/log/dmesg.0 [7.277226] kernel: nvidia-uvm: Loaded the UVM driver, major device number 237. [7.498321] kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database [7.521638] kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [7.785905] kernel: snd_hda_intel :00:14.2: position_fix set to 1 for device 1458:a022 [7.820545] kernel: MCE: In-kernel MCE decoding enabled. [7.825161] kernel: EDAC amd64: Node 0: DRAM ECC disabled. [7.825163] kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Either enable ECC checking or force module loading by setting 'ecc_enable_override'. (Note that use of the override may cause unknown side effects.) [7.873127] kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889A: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line [7.873143] kernel: snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [7.873144] kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [7.873145] kernel: snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [7.873146] kernel: snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [7.873147] kernel: snd_hda_codec_realtek hdaudioC0D0:inputs: [7.873149] kernel: snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 [7.873150] kernel: snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 [7.873152] kernel: snd_hda_codec_realtek hdaudioC0D0: Line=0x1a [7.873153] kernel: snd_hda_codec_realtek hdaudioC0D0: CD=0x1c [7.873154] kernel: snd_hda_codec_realtek hdaudioC0D0:dig-in=0x1f [7.877268] kernel: EDAC amd64: Node 0: DRAM ECC disabled. [7.877271] kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Either enable ECC checking or force module loading by setting 'ecc_enable_override'. (Note that use of the override may cause unknown side effects.) [7.885647] kernel: wlan0: Broadcom BCM43b1 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) [7.885648] kernel: [7.885816] kernel: snd_hda_intel :01:00.1: Disabling MSI [7.885827] kernel: snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [7.920552] kernel: input: HDA ATI SB Rear Mic as /devices/pci:00/:00:14.2/sound/card0/input27 [7.920612] kernel: input: HDA ATI SB Front Mic as /devices/pci:00/:00:14.2/sound/card0/input28 [7.920657] kernel: input: HDA ATI SB Line as /devices/pci:00/:00:14.2/sound/card0/input29 [7.920704] kernel: input: HDA ATI SB Line Out Front as /devices/pci:00/:00:14.2/sound/card0/input30 [7.920749] kernel: input: HDA ATI SB Line Out Surround as /devices/pci:00/:00:14.2/sound/card0/input31 [7.920795] kernel: input: HDA ATI SB Line Out CLFE as /devices/pci:00/:00:14.2/sound/card0/input32 [7.920837] kernel: input: HDA ATI SB Line Out Side as /devices/pci:00/:00:14.2/sound/card0/input33 [8.035861] kernel: mc: Linux media interface: v0.10 [8.243472] kernel: videodev: Linux video capture interface: v2.00 [8.261622] kernel: usbcore: registered new interface driver r8152 [8.349483] kernel: usb 1-2.4: reset high-speed USB device number 7 using ehci-pci [8.413200] kernel: usbcore: registered new interface driver cdc_ether [8.417252] kernel: Bluetooth: Core ver 2.22 [8.417279] kernel: NET: Registered protocol family 31 [8.417280] kernel: Bluetooth: HCI device and connection manager initialized [8.417284] kernel: Bluetooth: HCI socket layer initialized [8.417286] kernel: Bluetooth: L2CAP socket layer initialized [8.417301] kernel: Bluetooth: SCO socket layer initialized [8.506254] kernel: r8152 1-2.4:1.0 eth0: v1.09.11 [8.674264] kernel: usbcore: registered new interface driver btusb [8.686155] kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input34 [8.686215] kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input35 [8.686264] kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input36 [8.686317] kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input37 [8.733961] kernel: usbcore: registered new interface driver snd-usb-audio [8.736521] kernel: uvcvideo: Found UVC 1.00 device Microsoft® LifeCam Studio(TM) (045e:0772) [8.779706] kernel: Bluetooth: hci0: BCM: chip id 63 [8.780703] kernel: Bluetooth: hci0: BCM: features 0x07 [8.796682] kernel: Bluetooth: hci0: hydra [8.800667] kernel: Bluetooth: hci0: BCM
[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
There are several reports on the net talking about random disconnects with Bluetooth dongles reporting as BCM20702A0 and BCM20702A1, that might be important. Win10 experience the same problems, but it seems like they are able to recover. It seems like my HK Onyx Studio 4 has the same problem, but much less frequently. I have not tried to make any statistics though. I had a pair of Philips Bluetooth headphones that also had this problem. In short, I'm pretty sure it is not the devices that are the problem, although they may use the same chipset. I don't experience the same problem when the sound devices are attached to Android devices. So the problem persists over several sound devices, over several Bluetooth dongles, and over several mainboards. That should indicate that the problem somehow emerge from the system, even if Win10 seems to have fixed it to some degree. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth:
[Touch-packages] [Bug 1886714] [NEW] Bluetooth disconnects, and then sound fails on reconnect
Public bug reported: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound' [7.920552] input: HDA ATI SB Rear Mic as /devices/pci:00/:00:14.2/sound/card0/input27 [7.920612] input: HDA ATI SB Front Mic as /devices/pci:00/:00:14.2/sound/card0/input28 [7.920657] input: HDA ATI SB Line as /devices/pci:00/:00:14.2/sound/card0/input29 [7.920704] input: HDA ATI SB Line Out Front as /devices/pci:00/:00:14.2/sound/card0/input30 [7.920749] input: HDA ATI SB Line Out Surround as /devices/pci:00/:00:14.2/sound/card0/input31 [7.920795] input: HDA ATI SB Line Out CLFE as /devices/pci:00/:00:14.2/sound/card0/input32 [7.920837] input: HDA ATI SB Line Out Side as /devices/pci
[Touch-packages] [Bug 1393744] Re: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04
An other computer is connected through the same wifi extender, and that too uses Ubuntu 15.04. This computer reports "Intel(R) Centrino(R) Wireless-N 2230 BGN, REV=0xC8". There is no similar error reports in dmsg on this machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1393744 Title: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04 Status in network-manager package in Ubuntu: Triaged Bug description: lsb_release -rd :Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 wi-fi disconnects and unable to reconnect since updates on 13-11-2014. Also affects Lubuntu 15.04 on same machine. Ubuntu 12.04.1 on same machine does not disconnect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.8.8-0ubuntu34 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 CurrentDesktop: XFCE Date: Tue Nov 18 11:12:23 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-01-14 (307 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140114) IpRoute: RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Petersbergd473a136-74dc-4695-aac3-1fffc9cc8095 802-11-wireless 1416308390 Tue 18 Nov 2014 10:59:50 GMT yes no /org/freedesktop/NetworkManager/Settings/2 BTWifi-with-FON a2b63b98-159a-49f4-9247-d46a0d67ed41 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 Petersberg 1 4fc01379-d340-479e-a016-9af1ab717c83 802-11-wireless 1416303120 Tue 18 Nov 2014 09:32:00 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8disconnectedenabled enabled enabledenabled disabled --- ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1938 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ffe4c76c-645c-4847-ba8c-b2323517a10f InstallationDate: Installed on 2014-01-14 (318 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140114) MachineType: VIA Technologies, Inc. VT8363 Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=ed3144cc-8873-40a1-9670-bb2bfc9190a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: vivid Uname: Linux 3.16.0-25-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/01/2000 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: 6.00 PG dmi.board.name: 8363-686A dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd08/01/2000:svnVIATechnologies,Inc.:pnVT8363:pvr:rvn:rn8363-686A:rvr:cvn:ct3:cvr: dmi.product.name: VT8363 dmi.sys.vendor: VIA Technologies, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393744] Re: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04
Same problem here. Some notes about what happen. Sorry for not providing complete logs. This is my notes which is not very readable, not even for me.. :) The machine has been continuously updated since 13.10. Updated from 14.04 to 15.04 by going through 14.10. All done yesterday. Problem detected when arriving at 15.04. Usually either a 1: ... rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0. 2: ... rt2x00mmio_regbusy_read() Indirect register access failed: offset=0x308c, value=0x00010400 this is followed by: ieee80211 phy0: wlan0: No probe response from AP after 500ms, disconnecting 3: ... rt2x00queue_flush_queue: Warning - Queue 0 failed to flush After turning on nohwcrypt error 1 went away, and was replaced by 2 and 3. With nohwcrypt turned off I got 2 and then 3, leading to a time out. 1 alone gives failing network 2 and 3, or 3 alone, later gives ... authenticate with ... ... direct probe to ... (try 1/3) ... direct probe to ... (try 2/3) ... direct probe to ... (try 3/3) ... authentication with ... timed out and then network fails $ lspci | fgrep 'Ralink' 03:07.0 Network controller: Ralink corp. RT2561/RT61 802.11.g PCI Some additional info Chipset detected - rt: 2661, rf: 0003, rev: 000b Selected rate control algorithm 'minstrel_ht' Firmware .. 0.8 It ia an AMD triple core proc $ uname -a Linux hydra 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86-64 x86_64 x86_64 GNU/Linux Just to verify that the module is in fact the latest one. I've compiled them at one point so just to make sure they are provided by the distro. $ cat /sys/module/rt2x00*/version 2.3.0 (reported three times) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1393744 Title: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04 Status in network-manager package in Ubuntu: Triaged Bug description: lsb_release -rd :Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 wi-fi disconnects and unable to reconnect since updates on 13-11-2014. Also affects Lubuntu 15.04 on same machine. Ubuntu 12.04.1 on same machine does not disconnect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.8.8-0ubuntu34 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 CurrentDesktop: XFCE Date: Tue Nov 18 11:12:23 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-01-14 (307 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140114) IpRoute: RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Petersbergd473a136-74dc-4695-aac3-1fffc9cc8095 802-11-wireless 1416308390 Tue 18 Nov 2014 10:59:50 GMT yes no /org/freedesktop/NetworkManager/Settings/2 BTWifi-with-FON a2b63b98-159a-49f4-9247-d46a0d67ed41 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 Petersberg 1 4fc01379-d340-479e-a016-9af1ab717c83 802-11-wireless 1416303120 Tue 18 Nov 2014 09:32:00 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8disconnectedenabled enabled enabledenabled disabled --- ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1938 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ffe4c76c-645c-4847-ba8c-b2323517a10f InstallationDate: Installed on 2014-01-14 (318 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140114) MachineType: VIA Technologies, Inc. VT8363 Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=ed3144cc-8873-40a1-9670-bb2bfc9190a5 ro quiet splash vt.h
