[Kernel-packages] [Bug 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786664 Title: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description: Ubuntu 18.04.1 LTS Release: 18.04 logs as attachments are following To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950825] RfKill.txt
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540507/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem here:
https:/
[Kernel-packages] [Bug 1950825] ProcEnviron.txt
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540503/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem her
[Kernel-packages] [Bug 1950825] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540500/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar
[Kernel-packages] [Bug 1950825] acpidump.txt
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540510/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Attachment removed: "AlsaInfo.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540492/+files/AlsaInfo.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540493/+files/CRDA.txt
** Attachment removed: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540494/+files/CurrentDmesg.txt
** Attachment removed: "IwConfig.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540495/+files/IwConfig.txt
** Attachment removed: "Lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540496/+files/Lspci.txt
** Attachment removed: "Lspci-vt.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540497/+files/Lspci-vt.txt
** Attachment removed: "Lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540498/+files/Lsusb.txt
** Attachment removed: "ProcCpuinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540501/+files/ProcCpuinfo.txt
** Attachment removed: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540502/+files/ProcCpuinfoMinimal.txt
** Attachment removed: "ProcEnviron.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540503/+files/ProcEnviron.txt
** Attachment removed: "UdevDb.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540508/+files/UdevDb.txt
** Attachment removed: "acpidump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540510/+files/acpidump.txt
** Attachment removed: "RfKill.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540507/+files/RfKill.txt
** Attachment removed: "ProcModules.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540505/+files/ProcModules.txt
** Attachment removed: "ProcInterrupts.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540504/+files/ProcInterrupts.txt
** Attachment removed: "PulseList.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540506/+files/PulseList.txt
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540509/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
[Kernel-packages] [Bug 1950825] ProcCpuinfo.txt
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540501/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem her
[Kernel-packages] [Bug 1950825] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540499/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar
[Kernel-packages] [Bug 1950825] PulseList.txt
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540506/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem here:
[Kernel-packages] [Bug 1950825] ProcModules.txt
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540505/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem her
[Kernel-packages] [Bug 1950825] UdevDb.txt
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540508/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem here:
https:/
[Kernel-packages] [Bug 1950825] ProcInterrupts.txt
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540504/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar probl
[Kernel-packages] [Bug 1950825] WifiSyslog.txt
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540509/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem here:
[Kernel-packages] [Bug 1950825] ProcCpuinfoMinimal.txt
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540502/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a simil
[Kernel-packages] [Bug 1950825] CRDA.txt
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540493/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem here:
https://ask
[Kernel-packages] [Bug 1950825] Lsusb.txt
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540498/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem here:
https://a
[Kernel-packages] [Bug 1950825] CurrentDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540494/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem h
[Kernel-packages] [Bug 1950825] Lspci-vt.txt
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540497/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem here:
ht
[Kernel-packages] [Bug 1950825] Lspci.txt
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540496/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem here:
https://a
[Kernel-packages] [Bug 1950825] IwConfig.txt
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1950825/+attachment/5540495/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950825
Title:
Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
headset / speakers
Status in linux package in Ubuntu:
Confirmed
Bug description:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request,
but never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not
being able to connect to the Teufel speakers?
There is also another report with a similar problem here:
ht
[Kernel-packages] [Bug 1950825] Re: Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some headset / speakers
** Tags added: apport-collected focal
** Description changed:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets /
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy
Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0]
8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0]
8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0]
39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0]
39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0]
39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request, but
never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0]
4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0]
4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0]
4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0]
5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0]
5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0]
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not being
able to connect to the Teufel speakers?
There is also another report with a similar problem here:
https://askubuntu.com/questions/1020584/apple-keyboard-a1016-pairing-fails
How to further debug this problem?
Is it necessary to buy some bt sniffer hardware to get to the bottom of this?
I would invest in a cheapo 10€ CC2531 clone sniffer (like this
https://www.amazon.com/-/en/dp/B081WRGL31) but I am not sure if they are
sufficient to capture the pairing proce
[Kernel-packages] [Bug 1950825] [NEW] Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some headset / speakers
Public bug reported:
I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb
The driver / chip has problems to connect / pair with some headsets / speakers.
Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel
itself pair fine with other linux laptops / android smartphones. I'd like to
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #22 [hci0] 8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #23 [hci0] 8.822352
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11 #28 [hci0] 39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0] 39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0] 39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0] 39.891575
Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
So it pretty much looks like the laptop sends a connection request, but
never sees a reply from the Teufel headset.
Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:
@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13 #50 [hci0] 4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 #51 [hci0] 4.928927
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2 #55 [hci0] 5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4 #56 [hci0] 5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]
What could cause the Intel 8087 / 0029 bluetooth chip / driver not being
able to connect to the Teufel speakers?
There is also another report with a similar problem here:
https://askubuntu.com/questions/1020584/apple-keyboard-a1016-pairing-fails
How to further debug this problem?
Is it necessary to buy some bt sniffer hardware to get to the bottom of this? I
would invest in a cheapo 10€ CC2531 clone sniffer (like this
https://www.amazon.com/-/en/dp/B081WRGL31) but I am not sure if they are
sufficient to capture the pairing process.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
[Kernel-packages] [Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Reading the initial bug report I see kolAflash said > nomodeset seems to be essential, but not sufficient. When I added nomodeset to /etc/default/grub ( GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" ) then I can boot without issues, but suspend does not work. To reiterate: * the TTY1 screen is not blank on boot * sleep works * suspend does not work - you get this bug Given this error in syslog: > kernel: [0.047848] You have booted with nomodeset. This means your GPU > drivers are DISABLED > kernel: [0.047849] Unless you actually understand what nomodeset does, > you should reboot without enabling it > [0.047849] Any video related functionality will be severely degraded, and > you may not even be able to suspend the system properly > [0.047849] Unless you actually understand what nomodeset does, you should > reboot without enabling it I tried a few things without nomodeset in grub options. In this case: * the default screen, TTY1, (CTRL-ALT-F1) is blank on boot (or has the HP logo only) * sleep works * suspend doesn't seem to work. If you leave the laptop in suspend mode for a long time it does not resume. The screen is black with just a white underscore on it. The last log lines in /var/log/syslog is systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[8263]: Suspending system... kernel: [ 9425.088936] PM: suspend entry (s2idle) As a workaround for the default screen being blank on boot, you can go to TTY2 (CTRL-ALT-F2), log in and run startx from the command prompt. Some tests: * This does not seem to be the same issue as https://bugzilla.kernel.org/show_bug.cgi?id=204241 because the following command works just fine. for i in $(seq 30); do sudo rtcwake -m mem -s 5; sleep 15; done * I've tried adding GRUB_GFXMODE=1920x1080 to /etc/default/grub but that doesn't seem to solve the issue with the screen on TTY1 being blank on boot. The commands pm-hibernate and pm-suspend give the errors in /var/log/syslog > [ 2566.154192] Lockdown: grep: hibernation is restricted; see man > kernel_lockdown.7 and nothing happens The command pm-powersave gives the same "hibernation is restricted" error in /var/log/syslog but the system goes blank and the is unresponsive. ** Bug watch added: Linux Kernel Bug Tracker #204241 https://bugzilla.kernel.org/show_bug.cgi?id=204241 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searc
[Kernel-packages] [Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Update 2: This isn't actually fully solved. What's working is short-term "Sleep" but if you leave the laptop lid closed for a while it goes to suspend (s2idle) and that crashes the system. Aug 23 14:22:56 REDACTED systemd[1]: NetworkManager-dispatcher.service: Succeeded. Aug 23 14:23:08 REDACTED kernel: [ 124.757545] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Aug 23 14:23:08 REDACTED NetworkManager[734]: [1598210588.2565] manager: sleep: sleep requested (sleeping: no enabled: yes) Aug 23 14:23:08 REDACTED NetworkManager[734]: [1598210588.2567] manager: NetworkManager state is now ASLEEP Aug 23 14:23:08 REDACTED whoopsie[1113]: [14:23:08] offline Aug 23 14:23:08 REDACTED kernel: [ 124.760864] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Aug 23 14:23:08 REDACTED kernel: [ 124.761905] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Aug 23 14:23:08 REDACTED systemd[1]: Reached target Sleep. Aug 23 14:23:08 REDACTED systemd[1]: Starting Suspend... Aug 23 14:23:08 REDACTED kernel: [ 124.775535] PM: suspend entry (s2idle) Aug 23 14:23:08 REDACTED systemd-sleep[1370]: Suspending system... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Ver
[Kernel-packages] [Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
update: installed pm-utils ( sudo apt install pm-utils ) and the machine no longer gives a black screen when raising the laptop lid and resumes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 9YN58EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881494/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscri
[Kernel-packages] [Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Have the same issue with HP envy x360 running KDE and Ubuntu 20.04.1 LTS uname -a Linux rix360 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux First entry in /proc/cpuinfo shows processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 96 model name : AMD Ryzen 7 4700U with Radeon Graphics stepping: 1 microcode : 0x8600103 cpu MHz : 1395.962 cache size : 512 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 8 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 16 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_ apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topo ext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp v mmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv 1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vml oad vgif umip rdpid overflow_recov succor smca bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass bogomips: 3992.69 TLB size: 3072 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] - -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd6
[Kernel-packages] [Bug 1890023] Re: Cheese is failing to start WebCam
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/linux/+question/692278 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890023 Title: Cheese is failing to start WebCam Status in linux package in Ubuntu: Invalid Bug description: Cheese is failing to start WebCam and throws the below error. eese:15219): cheese-WARNING **: 11:07:46.807: Device '/dev/video11' has no supported format: gstv4l2object.c(3752): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for NV12 @ 5120x3840: Invalid argument Operating System: Ubuntu 20.04.1 LTS Kernel: Linux 5.7.11-surface ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 Uname: Linux 5.7.11-surface x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 11:03:16 2020 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Microsoft Corporation Surface Pro ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03.24.2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 235.3192.768 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr235.3192.768:bd03.24.2020:svnMicrosoftCorporation:pnSurfacePro:pvr1240D0B09F5C09P38S01E0:rvnMicrosoftCorporation:rnSurfacePro:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro dmi.product.sku: Surface_Pro_1796 dmi.product.version: 1240D:0B:09F:5C:09P:38S:01E:0 dmi.sys.vendor: Microsoft Corporation lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:09c0 Microsoft Corp. Surface Type Cover Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bluetooth and Wireless LAN Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal wayland-session Uname: Linux 5.7.11-surface x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890023] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1890023/+attachment/5397904/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890023 Title: Cheese is failing to start WebCam Status in linux package in Ubuntu: Confirmed Bug description: Cheese is failing to start WebCam and throws the below error. eese:15219): cheese-WARNING **: 11:07:46.807: Device '/dev/video11' has no supported format: gstv4l2object.c(3752): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for NV12 @ 5120x3840: Invalid argument Operating System: Ubuntu 20.04.1 LTS Kernel: Linux 5.7.11-surface ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 Uname: Linux 5.7.11-surface x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 11:03:16 2020 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Microsoft Corporation Surface Pro ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03.24.2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 235.3192.768 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr235.3192.768:bd03.24.2020:svnMicrosoftCorporation:pnSurfacePro:pvr1240D0B09F5C09P38S01E0:rvnMicrosoftCorporation:rnSurfacePro:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro dmi.product.sku: Surface_Pro_1796 dmi.product.version: 1240D:0B:09F:5C:09P:38S:01E:0 dmi.sys.vendor: Microsoft Corporation lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:09c0 Microsoft Corp. Surface Type Cover Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bluetooth and Wireless LAN Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal wayland-session Uname: Linux 5.7.11-surface x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890023] Re: Cheese is failing to start WebCam
apport information ** Tags added: apport-collected ** Description changed: Cheese is failing to start WebCam and throws the below error. eese:15219): cheese-WARNING **: 11:07:46.807: Device '/dev/video11' has no supported format: gstv4l2object.c(3752): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for NV12 @ 5120x3840: Invalid argument Operating System: Ubuntu 20.04.1 LTS Kernel: Linux 5.7.11-surface ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 Uname: Linux 5.7.11-surface x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 11:03:16 2020 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Microsoft Corporation Surface Pro ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03.24.2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 235.3192.768 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr235.3192.768:bd03.24.2020:svnMicrosoftCorporation:pnSurfacePro:pvr1240D0B09F5C09P38S01E0:rvnMicrosoftCorporation:rnSurfacePro:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro dmi.product.sku: Surface_Pro_1796 dmi.product.version: 1240D:0B:09F:5C:09P:38S:01E:0 dmi.sys.vendor: Microsoft Corporation lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:09c0 Microsoft Corp. Surface Type Cover Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bluetooth and Wireless LAN Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-07-10 (22 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: linux (not installed) + Tags: focal wayland-session + Uname: Linux 5.7.11-surface x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1890023/+attachment/5397903/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890023 Title: Cheese is failing to start WebCam Status in linux package in Ubuntu: Confirmed Bug description: Cheese is failing to start WebCam and throws the below error. eese:15219): cheese-WARNING **: 11:07:46.807: Device '/dev/video11' has no supported format: gstv4l2object.c(3752): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for NV12 @ 5120x3840: Invalid argument Operating System: Ubuntu 20.04.1 LTS Kernel: Linux 5.7.11-surface ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 Uname: Linux 5.7.11-surface x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 11:03:16 2020 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Microsoft Corporation Surface Pro ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03.24.2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 235.3192.768 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr235.3192.768:bd03.24.2020:svnMicrosoftCorporation:pnSurfacePro:pvr1240D0B09F5C09P38S01E0:rvnMicrosoftCorporation:rnSurfacePro:rvr:cvnMicrosoftCorpor
[Kernel-packages] [Bug 1890023] [NEW] Cheese is failing to start WebCam
Public bug reported: Cheese is failing to start WebCam and throws the below error. eese:15219): cheese-WARNING **: 11:07:46.807: Device '/dev/video11' has no supported format: gstv4l2object.c(3752): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for NV12 @ 5120x3840: Invalid argument Operating System: Ubuntu 20.04.1 LTS Kernel: Linux 5.7.11-surface ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 Uname: Linux 5.7.11-surface x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 11:03:16 2020 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Microsoft Corporation Surface Pro ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03.24.2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 235.3192.768 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr235.3192.768:bd03.24.2020:svnMicrosoftCorporation:pnSurfacePro:pvr1240D0B09F5C09P38S01E0:rvnMicrosoftCorporation:rnSurfacePro:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro dmi.product.sku: Surface_Pro_1796 dmi.product.version: 1240D:0B:09F:5C:09P:38S:01E:0 dmi.sys.vendor: Microsoft Corporation lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:09c0 Microsoft Corp. Surface Type Cover Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bluetooth and Wireless LAN Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal gstreamer-error wayland-session ** Attachment added: "Error screenshot" https://bugs.launchpad.net/bugs/1890023/+attachment/5397897/+files/Screenshot%20from%202020-08-02%2011-08-48.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890023 Title: Cheese is failing to start WebCam Status in linux package in Ubuntu: New Bug description: Cheese is failing to start WebCam and throws the below error. eese:15219): cheese-WARNING **: 11:07:46.807: Device '/dev/video11' has no supported format: gstv4l2object.c(3752): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for NV12 @ 5120x3840: Invalid argument Operating System: Ubuntu 20.04.1 LTS Kernel: Linux 5.7.11-surface ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 Uname: Linux 5.7.11-surface x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 11:03:16 2020 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Microsoft Corporation Surface Pro ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03.24.2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 235.3192.768 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr235.3192.768:bd03.24.2020:svnMicrosoftCorporation:pnSurfacePro:pvr1240D0B09F5C09P38S01E0:rvnMicrosoftCorporation:rnSurfacePro:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro dmi.product.sku: Surface_Pro_1796 dmi.product.version: 1240D:0B:09F:5C:09P:38S:01E:0 dmi.sys.vendor: Microsoft Corporation lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:09c0 Microsoft Corp. Surface Type Cover Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bluetooth and Wireless LAN Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sour
[Kernel-packages] [Bug 1872055] [NEW] Ubuntu 19.10 says no wifi adapter found
Public bug reported: I have installed the ubuntu 19.10 and since the installation it says no wifi adpter found but the wifi was working with Windows perfectly but since I switch to ubuntu I am not able to use the wifi. I have tried lots of different methods to fix this issue on the internet and also asked on Ubuntu community for help but none worked for me. It seems there's some bug on the os because during the installation the wifi was working but after the installation has completed the wifi stoped working and says No wifi adapter found. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anu2180 F pulseaudio /dev/snd/controlC0: anu2180 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:31:11 2020 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp0s16u3 no wireless extensions. enp1s0no wireless extensions. MachineType: LENOVO 81FS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=9462d35f-9a18-4b4c-8372-6429117b7939 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7UCN28WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E41-25 dmi.modalias: dmi:bvnLENOVO:bvr7UCN28WW(V2.02):bd11/14/2019:svnLENOVO:pn81FS:pvrLenovoE41-25:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE41-25: dmi.product.family: E41-25 dmi.product.name: 81FS dmi.product.sku: LENOVO_MT_81FS_BU_idea_FM_E41-25 dmi.product.version: Lenovo E41-25 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872055 Title: Ubuntu 19.10 says no wifi adapter found Status in linux package in Ubuntu: New Bug description: I have installed the ubuntu 19.10 and since the installation it says no wifi adpter found but the wifi was working with Windows perfectly but since I switch to ubuntu I am not able to use the wifi. I have tried lots of different methods to fix this issue on the internet and also asked on Ubuntu community for help but none worked for me. It seems there's some bug on the os because during the installation the wifi was working but after the installation has completed the wifi stoped working and says No wifi adapter found. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anu2180 F pulseaudio /dev/snd/controlC0: anu2180 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:31:11 2020 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp0s16u3 no wireless extensions. enp1s0no wireless extensions. MachineType: LENOVO 81FS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=9462d35f-9a18-4b4c-8372-6429117b7939 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7UCN28WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E41-25 dmi.modalias: dmi:bvnLENOVO:bvr7UCN28WW(V2.02):bd11/14/2019:svnLENOVO:pn81FS:pvrLenovoE41-25:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE41-25: dmi.product.family: E41-25 dmi.
[Kernel-packages] [Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20 - 5.3
Also happening with HP Zbook x360, but only recently started (today). As a workaround to stop your HD from filling up with this, create the file /etc/rsyslog.d/10-hidsensor.conf With the two lines: # Disable runaway messages: :msg, contains, "hid-sensor-hub 001F:8087:0AC2.0003" ~ Then run sudo service rsyslog restart -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 - 5.3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) [Fix] Let HID core allow longer input report length. [Test] User confirmed the fix works. [Regression Potential] Low. Longer input report length is now considered valid, shorter input report length doesn't get touched. === Original Bug Report === Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
I can confirm kernel 4.18.10 there is no flickering. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
Can confirm this is happening on fresh install of Linux Mint and Manjaro as well. Tried installing Kernel 5.0.2 but no fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3
I have installed the v4.18.rc8-generic kernel (uname: 4.18.0-041800rc8-generic) Unfortunately the problem remains. Although the driver reports itself as the exact same version as in the Ubuntu kernel (info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p154) it produced a slightly different dmesg output which might be of help here. I do not know how to set tags here, I would ask you to set 'kernel-bug-exists-upstream'. ** Attachment added: "dmesg.4.18.generic.crop.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+attachment/5174903/+files/dmesg.4.18.generic.crop.log ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786664 Title: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description: Ubuntu 18.04.1 LTS Release: 18.04 logs as attachments are following To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3
Is it possible that the idle power state of the driver is broken? Referring to this output in the dmesg: ... [ 753.636901] mwifiex_pcie :01:00.0: Firmware wakeup failed ... ** Description changed: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. - After an varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. + After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description: Ubuntu 18.04.1 LTS Release: 18.04 logs as attachments are following -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786664 Title: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description: Ubuntu 18.04.1 LTS Release: 18.04 logs as attachments are following To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786664] [NEW] wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3
Public bug reported: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description:Ubuntu 18.04.1 LTS Release:18.04 logs as attachments are following ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786664 Title: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description: Ubuntu 18.04.1 LTS Release: 18.04 logs as attachments are following To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3
** Attachment added: "mwifiex.lspci.crop.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+attachment/5174353/+files/mwifiex.lspci.crop.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786664 Title: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description: Ubuntu 18.04.1 LTS Release: 18.04 logs as attachments are following To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3
** Attachment added: "networkmanager0804.crop.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+attachment/5174355/+files/networkmanager0804.crop.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786664 Title: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description: Ubuntu 18.04.1 LTS Release: 18.04 logs as attachments are following To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3
** Attachment added: "wlan_dmesg.crop.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+attachment/5174354/+files/wlan_dmesg.crop.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786664 Title: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3. After a varying amount of time the wifi connection is gone. The driver does not seem to respond anymore to any action invoked by the gnome ui. My only known workaround for this is to reboot. In this state the shutdown process may take several minutes. Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18 lsb_release: Description: Ubuntu 18.04.1 LTS Release: 18.04 logs as attachments are following To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686687] Re: fstrim destroying XFS on SAN
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686687 Title: fstrim destroying XFS on SAN Status in linux package in Ubuntu: Confirmed Bug description: We observed severe data loss/filesystem corruption when executing fstrim on a filesystem hosted on an Eternus DX600 S3 system. There is multipathing via a fibre channel fabrics but the issue could be reproduced when disabling multipathing and using one of the block devices directly. It could not be reproduced when creating a multipathing device via dmsetup with four paths pointing to four loop devices mapping the same file. The observed behavior is that XFS cannot read vital filesystem metadata as the underlying storage device returns blocks of 0x00. The blocks are discarded via UNMAP commands and since thin provisioning is used, the SAN deallocates them and returns 0x00 on subsequent reads. Invoking find yields error messages like "find: ./dir_16: Structure needs cleaning". In other tests, where more data had been written, files were accessible but checksums did no longer match. In consequence, the XFS filesystem is in an unusable state and has to be created freshly, equaling complete data loss. Trying to repair the filesystem had proven not to be worth it as backups were available and trust had already been compromised. The problem was discovered after installing a new storage server with ubuntu 16.04, intending to replace the current machine running 14.04. Every weekend, the test volumes were corrupted. Investigation pointed towards Sunday, 06:47, which is the time `cron.weekly` is run. The job file `/etc/cron.weekly/fstrim` seemed most likely, so `fstrim -a` was run manually after `mkfs.xfs` and the filesystem became damaged. The damage only became apparent after a `umount` `mount` cycle, when all buffers were flushed and data was re-read from the device. We now could use config management to install a cronjob that (every minute!) checks for /sbin/fstrim and renames it, if present. This would be extremely unsatisfactory as it is a brittle workaround. So for now, we are locked on ubuntu 14.04. Since util-linux is one of the most central packages, there is no way to not have fstrim or the cronjob on a ubuntu system. I have attached a script used to reproduce the bug reliably on our system and its log output, as well as excerpts from syslog and md5sum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686687] Re: fstrim destroying XFS on SAN
We did get around to do more testing and follow suggestions. The
filesystem corruption could be reproduced. The run was done bypassing
multipathing and using a single path directly.
OUTPUT reproduce.sh (tail):
+ fstrim -v /mnt/san
/mnt/san: 120 TiB (131939249291264 bytes) trimmed
+ umount -vvv /mnt/san
umount: /mnt/san unmounted
+ sync
+ mount -vvv
/dev/disk/by-path/pci-:02:00.0-fc-0x-lun-0 /mnt/san
mount: mount /dev/sde on /mnt/san failed: Structure needs cleaning
+ fail '3rd mount failed'
+ echo 'ERROR: 3rd mount failed'
ERROR: 3rd mount failed
+ exit 11
OUTPUT dmesg:
[13568.741492] XFS (sde): metadata I/O error: block 0x39fc70
("xfs_trans_read_buf_map") error 74 numblks 8 [13568.891639] XFS (sde):
Metadata CRC error detected at
xfs_agi_read_verify+0x5e/0x110 [xfs], xfs_agi block 0x3a7c68 [13569.033899]
XFS (sde): Unmount and run xfs_repair [13569.103826] XFS (sde): First 64 bytes
of corrupted metadata buffer:
[13569.174222] 9107a8836000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
[13569.314629] 9107a8836010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
[13569.454924] 9107a8836020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
[13569.595204] 9107a8836030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
Since there is no fstab entry, mount options are determined by whatever
mechanism decides on defaults. In this case, mount reported the
following:
xfs (rw,relatime,attr2,inode64,noquota)
The kernel for this run:
$ uname -a
Linux xxx 4.11.0-041100rc8-generic #201704232131 SMP Mon Apr 24 01:32:55
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1686687
Title:
fstrim destroying XFS on SAN
Status in linux package in Ubuntu:
Confirmed
Bug description:
We observed severe data loss/filesystem corruption when executing
fstrim on a filesystem hosted on an Eternus DX600 S3 system.
There is multipathing via a fibre channel fabrics but the issue could
be reproduced when disabling multipathing and using one of the block
devices directly.
It could not be reproduced when creating a multipathing device via
dmsetup with four paths pointing to four loop devices mapping the same
file.
The observed behavior is that XFS cannot read vital filesystem
metadata as the underlying storage device returns blocks of 0x00. The
blocks are discarded via UNMAP commands and since thin provisioning is
used, the SAN deallocates them and returns 0x00 on subsequent reads.
Invoking find yields error messages like "find: ./dir_16: Structure
needs cleaning". In other tests, where more data had been written,
files were accessible but checksums did no longer match.
In consequence, the XFS filesystem is in an unusable state and has to
be created freshly, equaling complete data loss. Trying to repair the
filesystem had proven not to be worth it as backups were available and
trust had already been compromised.
The problem was discovered after installing a new storage server with
ubuntu 16.04, intending to replace the current machine running 14.04.
Every weekend, the test volumes were corrupted. Investigation pointed
towards Sunday, 06:47, which is the time `cron.weekly` is run. The job
file `/etc/cron.weekly/fstrim` seemed most likely, so `fstrim -a` was
run manually after `mkfs.xfs` and the filesystem became damaged. The
damage only became apparent after a `umount` `mount` cycle, when all
buffers were flushed and data was re-read from the device.
We now could use config management to install a cronjob that (every
minute!) checks for /sbin/fstrim and renames it, if present. This
would be extremely unsatisfactory as it is a brittle workaround. So
for now, we are locked on ubuntu 14.04. Since util-linux is one of the
most central packages, there is no way to not have fstrim or the
cronjob on a ubuntu system.
I have attached a script used to reproduce the bug reliably on our
system and its log output, as well as excerpts from syslog and md5sum.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686687/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686687] Re: fstrim destroying XFS on SAN
Marked as Confirmed in accordance with comment #3. Further detail might be provided on request. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686687 Title: fstrim destroying XFS on SAN Status in linux package in Ubuntu: Confirmed Bug description: We observed severe data loss/filesystem corruption when executing fstrim on a filesystem hosted on an Eternus DX600 S3 system. There is multipathing via a fibre channel fabrics but the issue could be reproduced when disabling multipathing and using one of the block devices directly. It could not be reproduced when creating a multipathing device via dmsetup with four paths pointing to four loop devices mapping the same file. The observed behavior is that XFS cannot read vital filesystem metadata as the underlying storage device returns blocks of 0x00. The blocks are discarded via UNMAP commands and since thin provisioning is used, the SAN deallocates them and returns 0x00 on subsequent reads. Invoking find yields error messages like "find: ./dir_16: Structure needs cleaning". In other tests, where more data had been written, files were accessible but checksums did no longer match. In consequence, the XFS filesystem is in an unusable state and has to be created freshly, equaling complete data loss. Trying to repair the filesystem had proven not to be worth it as backups were available and trust had already been compromised. The problem was discovered after installing a new storage server with ubuntu 16.04, intending to replace the current machine running 14.04. Every weekend, the test volumes were corrupted. Investigation pointed towards Sunday, 06:47, which is the time `cron.weekly` is run. The job file `/etc/cron.weekly/fstrim` seemed most likely, so `fstrim -a` was run manually after `mkfs.xfs` and the filesystem became damaged. The damage only became apparent after a `umount` `mount` cycle, when all buffers were flushed and data was re-read from the device. We now could use config management to install a cronjob that (every minute!) checks for /sbin/fstrim and renames it, if present. This would be extremely unsatisfactory as it is a brittle workaround. So for now, we are locked on ubuntu 14.04. Since util-linux is one of the most central packages, there is no way to not have fstrim or the cronjob on a ubuntu system. I have attached a script used to reproduce the bug reliably on our system and its log output, as well as excerpts from syslog and md5sum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686687] Re: fstrim destroying XFS on SAN
For us, fstrim was the frontend to the bug and running it consistently damaged our filesystems. That is why util-linux was chosen as the affected package. Also removing the cron file will not be sufficient as any update to the package (using cron-apt) might re-install it. Maybe a conflicting change would be a better choice. Still seems to brittle in light of such severe consequences. Mitigated by not upgrading to 16.04 for now. Since the system concerned is not connected to the web, Apport as described here (https://wiki.ubuntu.com/Apport#Tools) will not work. Also, Ubuntu server did not install apport when selecting 'Basic Ubuntu Server' in the installer. If there is additional information that might be useful, let us know. Further response may be delayed due to people going on vacation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686687 Title: fstrim destroying XFS on SAN Status in linux package in Ubuntu: Confirmed Bug description: We observed severe data loss/filesystem corruption when executing fstrim on a filesystem hosted on an Eternus DX600 S3 system. There is multipathing via a fibre channel fabrics but the issue could be reproduced when disabling multipathing and using one of the block devices directly. It could not be reproduced when creating a multipathing device via dmsetup with four paths pointing to four loop devices mapping the same file. The observed behavior is that XFS cannot read vital filesystem metadata as the underlying storage device returns blocks of 0x00. The blocks are discarded via UNMAP commands and since thin provisioning is used, the SAN deallocates them and returns 0x00 on subsequent reads. Invoking find yields error messages like "find: ./dir_16: Structure needs cleaning". In other tests, where more data had been written, files were accessible but checksums did no longer match. In consequence, the XFS filesystem is in an unusable state and has to be created freshly, equaling complete data loss. Trying to repair the filesystem had proven not to be worth it as backups were available and trust had already been compromised. The problem was discovered after installing a new storage server with ubuntu 16.04, intending to replace the current machine running 14.04. Every weekend, the test volumes were corrupted. Investigation pointed towards Sunday, 06:47, which is the time `cron.weekly` is run. The job file `/etc/cron.weekly/fstrim` seemed most likely, so `fstrim -a` was run manually after `mkfs.xfs` and the filesystem became damaged. The damage only became apparent after a `umount` `mount` cycle, when all buffers were flushed and data was re-read from the device. We now could use config management to install a cronjob that (every minute!) checks for /sbin/fstrim and renames it, if present. This would be extremely unsatisfactory as it is a brittle workaround. So for now, we are locked on ubuntu 14.04. Since util-linux is one of the most central packages, there is no way to not have fstrim or the cronjob on a ubuntu system. I have attached a script used to reproduce the bug reliably on our system and its log output, as well as excerpts from syslog and md5sum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
Ok, the solution here for me was to update to the latest kernel headers/image (4.4 at this time) using some instructions something like this: wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc3-wily/linux- headers-4.4.0-040400rc3_4.4.0-040400rc3.201511300321_all.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc3-wily/linux- headers-4.4.0-040400rc3-generic_4.4.0-040400rc3.201511300321_i386.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc3-wily/linux- image-4.4.0-040400rc3-generic_4.4.0-040400rc3.201511300321_i386.deb sudo dpkg -i linux-headers-4.4*.deb linux-image-4.4*.deb The latest linux kernel will detect the mousepad ok on the next boot, however, it doesn't include the keyboard drivers on boot to unlock the encrypted hard-drive at startup. You can bypass this by plugging in an old clickety-clackety usb keyboard and typing in the password there. To get around that permanently, alter the file: /etc/initramfs-tools/modules add these lines at the end of the file for some better boot-up keyboard/s driver support: hid hid-rmi hid-generic ohci_pci usbhid you may also try these lines for other keyboard support on various related devices: hid_logitech hid_logitech_dj hid-logitech-hidpp hid_microsoft hid_apple mac_hid as noted here: https://bugs.launchpad.net/ubuntu/+source/initramfs- tools/+bug/1238194 specifically, I believe hid-rmi was the one the Razer Blade 14" wanted for keyboard support at boot HD encryption unlock time. You may also find you need the "touchpad fix" ala Alex Cabal, here: https://alexcabal.com/get-a-working-touchpad-on-a-14-razer-blade- running-linuxubuntu/ which includes the commands: synclient ClickPad=0 synclient PalmDetect=1 and adding a file to the system: /usr/share/X11/xorg.conf.d/60-synaptics-options.conf containing the lines: Section "InputClass" Identifier "touchpad catchall" Driver "synaptics" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "PalmDetect" "1" Option "ClickPad" "0" EndSection -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in linux package in Ubuntu: Confirmed Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
oh yeah and sudo update-initramfs -u after updating /etc/initramfs-tools/modules in the above notes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in linux package in Ubuntu: Confirmed Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
Ok finally got mouse support back, and even enabled two-finger scroll via the touchpad, by commenting out the #Section "InputClass" #Identifier "evdev touchpad catchall" piece in /usr/share/X11/xorg.conf.d/10-evdev.conf and putting this in /usr/share/X11/xorg.conf.d/50-synaptics.conf: Section "InputClass" Identifier "Touchpad" Driver "synaptics" MatchIsTouchpad "yes" MatchDevicePath "/dev/input/event*" Option "SHMConfig" "on" Option "MinSpeed" "0.5" Option "MaxSpeed" "1.0" Option "AccelFactor" "0.075" Option "TapButton1""1" Option "TapButton2""2" # multitouch Option "TapButton3""3" # multitouch Option "VertTwoFingerScroll" "1" # multitouch Option "HorizTwoFingerScroll" "1" # multitouch Option "VertEdgeScroll""1" Option "CoastingSpeed" "8" Option "CornerCoasting""1" Option "CircularScrolling" "1" Option "CircScrollTrigger" "7" Option "EdgeMotionUseAlways" "1" Option "LBCornerButton""8" # browser "back" btn Option "RBCornerButton""9" # browser "forward" btn Option "HorizHysteresis" "0" # mouse "stickiness" Option "VertHysteresis""0" # mouse "stickiness" EndSection then sudo depmod -a sudo update-grub Now if I could only get the actual wifi mouse to work at the same time :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in linux package in Ubuntu: Confirmed Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
seems that something in kernel 3.19 killed the trackpad for good and now I just have to clean reinstalla dufferent distro. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in linux package in Ubuntu: Confirmed Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
oh no, after playing with various fixes, the trackpad is now COMPLETELY disabled under all kernels. posting from cellphone :( any idea how to just reset it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in linux package in Ubuntu: Confirmed Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
When I tried to use the latest 4.2 kernel, the keyboard became unresponsive and I was unable to decrypt the HD at bootup, so had to revert... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in linux package in Ubuntu: Confirmed Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
I'm on Linux Mint 17.3, have tried 13.3, 13.4, 13.7, 4.2.0 Same error on every kernel: I was able to install the hid patched driver on kernel 13.14 I beleive, but no positive effect. Couldn't find synaptics properties. No synaptics driver loaded? I can't beleive I'm actually considering dumping Mint on a new expensive gaming laptop because TRACKPAD support is completely gone... Here's some more data in case it can help you help me. This is on the latest kernel I tried, the latest 13.16 kernel. tpconfig -i Could not open PS/2 Port [/dev/psaux]. Found Synaptics Touchpad. Firmware: 8.96 (multiple-byte mode). Sensor type: unknown (0). Geometry: rectangular/landscape/up. Packets: absolute, 80 packets per second. Corner taps disabled; no tap gestures. Edge motion: none. Z threshold: 6 of 7. 2 button mode; corner tap is right button click. synclient ClickPad=0 Couldn't find synaptics properties. No synaptics driver loaded? (always, every kernel does the same thing here from what I've seen) This is on the 2014 Razer Blade 14" model, no touchscreen. Thanks for any help you can offer here! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in linux package in Ubuntu: Confirmed Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315360] Re: [Razer Blade] Trackpad detected as mouse only
BUMP. Can't figure out how to get trackpad support with scroll on ANY kernel of Linux Mint, at all. Couldn't find synaptics properties. No synaptics driver loaded? damnit, damnit, damnit. Wasting hours and hours on this. Someone please help? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315360 Title: [Razer Blade] Trackpad detected as mouse only Status in linux package in Ubuntu: Confirmed Bug description: The trackpad works as a mouse and tap-to-click works, but no scrolling (neither two-finger nor edge) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 1570 F pulseaudio /dev/snd/controlC1: mike 1570 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 08:45:39 2014 HibernationDevice: RESUME=UUID=ba977027-c742-470c-9a92-199f27ebea08 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c72e4937-c906-4466-8990-b28729f9d39d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: RAZER dmi.bios.version: 2.24 dmi.board.asset.tag: NULL dmi.board.name: RAZER dmi.board.vendor: RAZER dmi.board.version: 1.00 dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 10 dmi.chassis.vendor: RAZER dmi.chassis.version: N/A dmi.modalias: dmi:bvnRAZER:bvr2.24:bd03/24/2014:svnRazer:pnBlade:pvr2.04:rvnRAZER:rnRAZER:rvr1.00:cvnRAZER:ct10:cvrN/A: dmi.product.name: Blade dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 760142] Re: ImPS/2 ALPS GlidePoint configure as PS/2 mouse instead of proper touchpad
BUMP. Big hardware bug here. I'm seeing the same thing on a brand new Razer Blade 14". Trackpad detected as mouse, neither side-scrolling or two button scrolling is working. Been trying to fix it for hours and hours and hours now. Looks like we have borked trackpads in many many devices now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/760142 Title: ImPS/2 ALPS GlidePoint configure as PS/2 mouse instead of proper touchpad Status in linux package in Ubuntu: Incomplete Bug description: On the Dell 15R. the touchpad is not recognised as a touchpad, it is recognised as a mouse. $ cat /proc/bus/input/devices [snip] I: Bus=0011 Vendor=0002 Product=0005 Version=7326 N: Name="ImPS/2 ALPS GlidePoint" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input7 U: Uniq= H: Handlers=mouse0 event7 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=103 [snip] ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jude 1571 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f0 irq 54' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:111d76d1,102804b0,00100205 HDA:80862805,80860101,0010' Controls : 18 Simple ctrls : 10 CurrentDmesg: [ 35.342430] eth0: no IPv6 routers present [ 48.913433] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0 Date: Wed Apr 13 20:11:55 2011 HibernationDevice: RESUME=UUID=9203eac6-4c4c-41c8-bf51-e18329de0e3f InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Dell Inc. Inspiron N5110 ProcEnviron: LANGUAGE= LANG=en_IE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=64711ccc-07ea-40e8-ac9d-c9e7c40ca1f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.50 SourcePackage: linux UpgradeStatus: Upgraded to natty on 2011-04-11 (1 days ago) dmi.bios.date: 03/02/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 034W60 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA02:bd03/02/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA02:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/760142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465322] Re: regression: "df: `/sys/kernel/debug': Function not implemented" with 3.2.0-85.122
Please note, does this bug affect any other software but just df command? (definitely kernel related, after update from 3.2.0-84 to 3.2.0-86) My setup is also affected by this bug: $ df -h df: ”/sys/kernel/debug”: Funktion toteutus puuttuu Tiedostojärjestelmä Koko Käyt Vapaa Käy% Liitospiste /dev/sda1 22G 4,2G 16G 21% / ... $ LANG=C df -h df: `/sys/kernel/debug': Function not implemented Filesystem Size Used Avail Use% Mounted on /dev/sda122G 4.2G 16G 21% / ... $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu 12.04.5 LTS" $ uname -a Linux machine 3.2.0-86-generic-pae #123-Ubuntu SMP Sun Jun 14 18:30:54 UTC 2015 i686 athlon i386 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465322 Title: regression: "df: `/sys/kernel/debug': Function not implemented" with 3.2.0-85.122 Status in linux package in Ubuntu: In Progress Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1405489] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
+ Did this not occur with a prior version of the NVIDIA proprietary drivers? Unknown. This is a fresh install. + Does this happen with nouveau? It did not. + Did this happen in a prior release? Unknown. This is a fresh install on a new machine but there is a bug opened for Ubuntu 14.04 on the same laptop model by someone else at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762?comments=all -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 14.10 has random freezes and lock ups. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afan 9511 F pulseaudio /dev/snd/controlC0: afan 9511 F pulseaudio CurrentDesktop: KDE Date: Wed Dec 24 16:49:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-23 (1 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ZBook 15 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=31ffafeb-d84a-4173-81a4-99a3bde628f3 ro quiet splash rcutree.rcu_idle_gp_delay=1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.21 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.53 dmi.chassis.asset.tag: USH446L1YV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.21:bd08/13/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.53:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1405489] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
As per comment #4 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 has random freezes and lock ups. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afan 9511 F pulseaudio /dev/snd/controlC0: afan 9511 F pulseaudio CurrentDesktop: KDE Date: Wed Dec 24 16:49:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-23 (1 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ZBook 15 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=31ffafeb-d84a-4173-81a4-99a3bde628f3 ro quiet splash rcutree.rcu_idle_gp_delay=1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.21 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.53 dmi.chassis.asset.tag: USH446L1YV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.21:bd08/13/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.53:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1405489] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
I have updated the BIOS. ( Asside: For any other ZBook users note that the directions at https://help.ubuntu.com/community/BIOSUpdate are incorrect as there is no README in the download from HP. Instead, on Boot press "ESC" to get into the BIOS setup and follow the instructions in the "BIOS Upgrade" section. ) After having upgraded the BIOS I changed NVIDIA back to the "NVIDIA - Power mode" $ cat /proc/acpi/bbswitch :01:00.0 ON And now can confirm that this issue still occurs. Changing to confirmed as per instructions and posting updated BIOS data. $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date L70 Ver. 01.30 12/08/2014 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 has random freezes and lock ups. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afan 9511 F pulseaudio /dev/snd/controlC0: afan 9511 F pulseaudio CurrentDesktop: KDE Date: Wed Dec 24 16:49:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-23 (1 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ZBook 15 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=31ffafeb-d84a-4173-81a4-99a3bde628f3 ro quiet splash rcutree.rcu_idle_gp_delay=1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.21 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.53 dmi.chassis.asset.tag: USH446L1YV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.21:bd08/13/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.53:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1310762] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.04 random freeze and lock up
Done: See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405489 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310762 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.04 random freeze and lock up Status in linux package in Ubuntu: Incomplete Bug description: Just upgraded to 14.04 and started to experience random freezes. Only workaround in to ctrl+alt+tab+F2 and ctrl+alt+tab+f7 to unfreeze laptop. Or hard reset. Currently happens when browser is open (occures for firefox, chromium). Switching from nouveau to nvidia proprietary drivers (tried both stable and updated version) didn't help. WORKAROUND: Switched to Intel card and no lockups. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 21 22:32:25 2014 DistUpgraded: 2014-04-21 17:22:37,996 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1909] NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1909] InstallationDate: Installed on 2014-01-13 (98 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP ZBook 15 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=66d5c91d-34a5-4682-ad13-5523786548db ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-21 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.06 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.06:bd10/25/2013:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10303:rvnHewlett-Packard:rn1909:rvrKBCVersion94.47:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Apr 21 21:41:25 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1405489] [NEW] [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
Public bug reported: As per Comment #31 on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762/comments/31 creating bug via "ubuntu-bug linux". This issue is a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762?comments=all but with Ubuntu 14.10 instead of 14.04 $ cat /proc/version_signature Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afan 9511 F pulseaudio /dev/snd/controlC0: afan 9511 F pulseaudio CurrentDesktop: KDE Date: Wed Dec 24 16:49:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-23 (1 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ZBook 15 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=31ffafeb-d84a-4173-81a4-99a3bde628f3 ro quiet splash rcutree.rcu_idle_gp_delay=1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.21 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.53 dmi.chassis.asset.tag: USH446L1YV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.21:bd08/13/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.53:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug nvidia utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA Status in linux package in Ubuntu: Confirmed Bug description: As per Comment #31 on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762/comments/31 creating bug via "ubuntu-bug linux". This issue is a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762?comments=all but with Ubuntu 14.10 instead of 14.04 $ cat /proc/version_signature Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afan 9511 F pulseaudio /dev/snd/controlC0: afan 9511 F pulseaudio CurrentDesktop: KDE Date: Wed Dec 24 16:49:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-23 (1 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ZBook 15 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=31ffafeb-d84a-4173-81a4-99a3bde628f3 ro quiet splash rcutree.rcu_idle_gp_delay=1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.21 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.53 dmi.chassis.asset.tag: USH446L1YV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.21:bd08/13/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.53:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1310762] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.04 random freeze and lock up
Also getting this with a zBook 15 and Ubuntu 14.10 Linux 3.16.0-28-generic #38-Ubuntu SMP Fri Dec 12 17:37:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev ff) $ dpkg --list | grep nvidia ii nvidia-331 331.113-0ubuntu0.1 amd64NVIDIA binary driver - version 331.113 ii nvidia-331-uvm 331.113-0ubuntu0.1 amd64NVIDIA Unified Memory kernel module ii nvidia-opencl-icd-331 331.113-0ubuntu0.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.6.7 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 331.20-0ubuntu8 amd64Tool for configuring the NVIDIA graphics driver Ctrl-alt-F1 , ctrl-alt-f7 workaround unlocks things. Tried changing /etc/default/grub to have GRUB_CMDLINE_LINUX_DEFAULT="quiet splash rcutree.rcu_idle_gp_delay=1" but it did not change the lockup. In kern.log get kernel: [ 6891.094246] ACPI Warning: \_SB_.PCI0.PEGP.DGFX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) If I run "nvidia-settings" and change "PRIME profiles" from NVIDIA (Performance Mode) to Intel (Power Saving Mode) then it stops the lock up May be related to https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=763272 as I noticed that With PRIME profile as NVIDIA you get (the below number is from memory - but the ON I know was set ) $ cat /proc/acpi/bbswitch :01:00.0 ON and it can't be changed as per bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763272 Also with PRIME profile as Intel you get $ cat /proc/acpi/bbswitch :01:00.0 OFF ** Bug watch added: Debian Bug tracker #763272 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763272 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310762 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.04 random freeze and lock up Status in linux package in Ubuntu: Incomplete Bug description: Just upgraded to 14.04 and started to experience random freezes. Only workaround in to ctrl+alt+tab+F2 and ctrl+alt+tab+f7 to unfreeze laptop. Or hard reset. Currently happens when browser is open (occures for firefox, chromium). Switching from nouveau to nvidia proprietary drivers (tried both stable and updated version) didn't help. WORKAROUND: Switched to Intel card and no lockups. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 21 22:32:25 2014 DistUpgraded: 2014-04-21 17:22:37,996 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1909] NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1909] InstallationDate: Installed on 2014-01-13 (98 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP ZBook 15 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=66d5c91d-34a5-4682-ad13-5523786548db ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-21 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.06 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: K
[Kernel-packages] [Bug 1065490] Re: [Lenovo ThinkPad X230 Tablet 3434] total system freeze
Hi Christopher,
Unfortunately for this bug, I'm not willing to continue to use the 3.2.*
kernels at all (I've been happily using the 3.5.* kernels without any problems
for months now). Trying to track down this bug when I couldn't workout the
trigger, was an exercise in frustration. I still don't know the trigger, but
I'm not being frustrated by anything related to this bug any more (including
lack of sound from 3.6.*).
I hope you'll forgive me for not trying to track down the bug when
things are working for me.
Cheers.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1065490
Title:
[Lenovo ThinkPad X230 Tablet 3434] total system freeze
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
This has happened a number of times now, the system has totally
frozen.
Symtoms:
System does not respond to mouse.
System does not respond to keyboard (including ctrl-alt-del,
ctrl-alt-backspace (yes I renabled it in the keyboard settings) and Magic Sysrq
(yes it's enabled, and yes it works properly otherwise)).
If music is playing, it repeats the same part over again (the same few
milliseconds of sound).
If I plugin a network cable, and then attempt to ping the computer via what
should be the wired IP address (from another computer) I get a error
unreachable destination. (I have not tried to ping over the wireless network as
I haven't had the IP address for the problem machine. I've just recorded the
present address, and will try in the future. But because of DHCP, it might not
be the same address ...)
Things I've done:
Ran memtest (it's a new computer though, so it shouldn't be the problem...).
Looked in /var/log/syslog but can't see anything I recognize as bad.
I cannot determine a cause, and it is very frustrating to lose my
work.
If you need anything else, please ask.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-31-generic 3.2.0-31.50
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: m 1810 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf253 irq 44'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,17aa2203,00100203
HDA:80862806,80860101,0010'
Controls : 35
Simple ctrls : 14
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
Date: Thu Oct 11 12:49:49 2012
HibernationDevice: RESUME=UUID=0e396851-47a9-401b-9951-74bb81ec37b6
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120823.1)
IwConfig: Error: [Errno 2] No such file or directory
MachineType: LENOVO 3434CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic
root=UUID=50f6d1aa-a1ee-4399-a205-3870a2fa448e ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-31-generic N/A
linux-backports-modules-3.2.0-31-generic N/A
linux-firmware1.79.1
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UdevDb: Error: [Errno 2] No such file or directory
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/01/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET20WW (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3434CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrGCET20WW(1.09):bd06/01/2012:svnLENOVO:pn3434CTO:pvrThinkPadX230Tablet:rvnLENOVO:rn3434CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3434CTO
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065490/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
M
