[Kernel-packages] [Bug 1962730] Re: Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
Can you please attach `sudo lspci -vvnn` and full dmesg when the commit
is reverted?
--
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/1962730
Title:
Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
Status in linux package in Ubuntu:
In Progress
Bug description:
On a Dell T440 system the following crash is captured from reboot in
pstore. Although this example is not with the latest system BIOS it
does also happen with the latest (2.13.3). The upstream kernel tree
has reverted the patch applied for #1904225 in commit
9d3fcb28f9b9750b474811a2964ce022df56336e. The log message
specifically notes a problem with Dell R440 which is the rack mount
variation of the T440.
[ 9411.241947] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 9411.241948] {1}[Hardware Error]: event severity: fatal
[ 9411.241948] {1}[Hardware Error]: Error 0, type: fatal
[ 9411.241949] {1}[Hardware Error]: section_type: PCIe error
[ 9411.241949] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 9411.241949] {1}[Hardware Error]: version: 3.0
[ 9411.241950] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 9411.241950] {1}[Hardware Error]: device_id: :01:00.1
[ 9411.241950] {1}[Hardware Error]: slot: 1
[ 9411.241951] {1}[Hardware Error]: secondary_bus: 0x00
[ 9411.241951] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 9411.241951] {1}[Hardware Error]: class_code: 02
[ 9411.241952] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 9411.241952] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 9411.241953] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 9411.241953] Kernel panic - not syncing: Fatal hardware error!
[ 9411.241953] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: P OE
5.4.0-92-generic #103zynstra1
[ 9411.241954] Hardware name: Dell Inc. PowerEdge T440/00X7CK, BIOS 2.8.2
08/31/2020
[ 9411.241954] Call Trace:
[ 9411.241954] dump_stack+0x69/0x84
[ 9411.241955] panic+0x101/0x2e3
[ 9411.241955] __ghes_panic.part.0+0x2a/0x2a
[ 9411.241955] ghes_in_nmi_queue_one_entry.constprop.0.cold+0x5/0x16
[ 9411.241956] ghes_notify_nmi.part.0+0x3e/0xa0
[ 9411.241956] ghes_notify_nmi+0x26/0x30
[ 9411.241956] nmi_handle+0x62/0x120
[ 9411.241956] default_do_nmi+0x4c/0x130
[ 9411.241957] do_nmi.part.0+0x144/0x1a0
[ 9411.241957] do_nmi+0x34/0x40
[ 9411.241957] xennmi+0x1e/0x30
[ 9411.241958] RIP: e030:__acpi_release_global_lock+0x16/0x30
[ 9411.241958] Code: 83 fa 03 0f 95 c0 f7 d8 c3 66 66 2e 0f 1f 84 00 00 00 00
00 0f 1f 44 00 00 55 48 89 e5 8b 17 89 d1 89 d0 83 e1 fc f0 0f b1 0f <39> c2 75
ef 89 d0 5d 83 e0 01 c3 66 66 2e 0f 1f 84 00 00 00 00 00
[ 9411.241959] RSP: e02b:c90040083a98 EFLAGS: 0246
[ 9411.241960] RAX: 0002 RBX: 8890951677e0 RCX:
[ 9411.241960] RDX: 0002 RSI: 820c2160 RDI:
c90040007010
[ 9411.241960] RBP: c90040083a98 R08: R09:
88871d451e80
[ 9411.241961] R10: c90040083a40 R11: R12:
[ 9411.241961] R13: 8890865066c0 R14: 8890865068b8 R15:
0008
[ 9411.241961] acpi_ev_release_global_lock+0x93/0x128
[ 9411.241962] acpi_ex_release_mutex_object+0xb5/0xf9
[ 9411.241962] acpi_ex_release_global_lock+0x54/0x92
[ 9411.241962] acpi_ex_write_data_to_field+0x33a/0x36c
[ 9411.241963] acpi_ex_store_object_to_node+0x2ce/0x324
[ 9411.241963] acpi_ex_store+0xa3/0x273
[ 9411.241963] acpi_ex_opcode_1A_1T_1R+0x421/0x59a
[ 9411.241963] acpi_ds_exec_end_op+0x166/0x767
[ 9411.241964] acpi_ps_parse_loop+0x58a/0x660
[ 9411.241964] acpi_ps_parse_aml+0x1af/0x550
[ 9411.241964] acpi_ps_execute_method+0x208/0x2ca
[ 9411.241965] acpi_ns_evaluate+0x34e/0x4f0
[ 9411.241965] acpi_evaluate_object+0x18e/0x3b4
[ 9411.241965] acpi_enter_sleep_state_prep+0xb9/0x145
[ 9411.241965] acpi_power_off_prepare+0x35/0x50
[ 9411.241966] kernel_restart+0x4c/0x70
[ 9411.241966] __do_sys_reboot+0x1d1/0x210
[ 9411.241966] ? vfs_writev+0xce/0x100
[ 9411.241967] ? __audit_syscall_entry+0xdb/0x120
[ 9411.241967] ? syscall_trace_enter+0x1a5/0x290
[ 9411.241967] ? __audit_syscall_exit+0x25d/0x2c0
[ 9411.241967] __x64_sys_reboot+0x1e/0x20
[ 9411.241968] do_syscall_64+0x57/0x190
[ 9411.241968] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 9411.241968] RIP: 0033:0x7f5667c75487
[ 9411.241969] Code: 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90
f3 0f 1e fa 89 fa be 69 19 12 28 bf ad de e1 fe b8 a9 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 01 c3 48 8b 15 d9 29 0d 00 f7 d8 64 89 02 b8
[ 9411.241970] RSP: 002b:7fff00697cf8 EFLAGS: 0202 ORIG_RAX:
00a9
[
[Kernel-packages] [Bug 1962730] Re: Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
Thanks for the report! Let me investigate.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
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/1962730
Title:
Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
Status in linux package in Ubuntu:
In Progress
Bug description:
On a Dell T440 system the following crash is captured from reboot in
pstore. Although this example is not with the latest system BIOS it
does also happen with the latest (2.13.3). The upstream kernel tree
has reverted the patch applied for #1904225 in commit
9d3fcb28f9b9750b474811a2964ce022df56336e. The log message
specifically notes a problem with Dell R440 which is the rack mount
variation of the T440.
[ 9411.241947] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 9411.241948] {1}[Hardware Error]: event severity: fatal
[ 9411.241948] {1}[Hardware Error]: Error 0, type: fatal
[ 9411.241949] {1}[Hardware Error]: section_type: PCIe error
[ 9411.241949] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 9411.241949] {1}[Hardware Error]: version: 3.0
[ 9411.241950] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 9411.241950] {1}[Hardware Error]: device_id: :01:00.1
[ 9411.241950] {1}[Hardware Error]: slot: 1
[ 9411.241951] {1}[Hardware Error]: secondary_bus: 0x00
[ 9411.241951] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 9411.241951] {1}[Hardware Error]: class_code: 02
[ 9411.241952] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 9411.241952] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 9411.241953] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 9411.241953] Kernel panic - not syncing: Fatal hardware error!
[ 9411.241953] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: P OE
5.4.0-92-generic #103zynstra1
[ 9411.241954] Hardware name: Dell Inc. PowerEdge T440/00X7CK, BIOS 2.8.2
08/31/2020
[ 9411.241954] Call Trace:
[ 9411.241954] dump_stack+0x69/0x84
[ 9411.241955] panic+0x101/0x2e3
[ 9411.241955] __ghes_panic.part.0+0x2a/0x2a
[ 9411.241955] ghes_in_nmi_queue_one_entry.constprop.0.cold+0x5/0x16
[ 9411.241956] ghes_notify_nmi.part.0+0x3e/0xa0
[ 9411.241956] ghes_notify_nmi+0x26/0x30
[ 9411.241956] nmi_handle+0x62/0x120
[ 9411.241956] default_do_nmi+0x4c/0x130
[ 9411.241957] do_nmi.part.0+0x144/0x1a0
[ 9411.241957] do_nmi+0x34/0x40
[ 9411.241957] xennmi+0x1e/0x30
[ 9411.241958] RIP: e030:__acpi_release_global_lock+0x16/0x30
[ 9411.241958] Code: 83 fa 03 0f 95 c0 f7 d8 c3 66 66 2e 0f 1f 84 00 00 00 00
00 0f 1f 44 00 00 55 48 89 e5 8b 17 89 d1 89 d0 83 e1 fc f0 0f b1 0f <39> c2 75
ef 89 d0 5d 83 e0 01 c3 66 66 2e 0f 1f 84 00 00 00 00 00
[ 9411.241959] RSP: e02b:c90040083a98 EFLAGS: 0246
[ 9411.241960] RAX: 0002 RBX: 8890951677e0 RCX:
[ 9411.241960] RDX: 0002 RSI: 820c2160 RDI:
c90040007010
[ 9411.241960] RBP: c90040083a98 R08: R09:
88871d451e80
[ 9411.241961] R10: c90040083a40 R11: R12:
[ 9411.241961] R13: 8890865066c0 R14: 8890865068b8 R15:
0008
[ 9411.241961] acpi_ev_release_global_lock+0x93/0x128
[ 9411.241962] acpi_ex_release_mutex_object+0xb5/0xf9
[ 9411.241962] acpi_ex_release_global_lock+0x54/0x92
[ 9411.241962] acpi_ex_write_data_to_field+0x33a/0x36c
[ 9411.241963] acpi_ex_store_object_to_node+0x2ce/0x324
[ 9411.241963] acpi_ex_store+0xa3/0x273
[ 9411.241963] acpi_ex_opcode_1A_1T_1R+0x421/0x59a
[ 9411.241963] acpi_ds_exec_end_op+0x166/0x767
[ 9411.241964] acpi_ps_parse_loop+0x58a/0x660
[ 9411.241964] acpi_ps_parse_aml+0x1af/0x550
[ 9411.241964] acpi_ps_execute_method+0x208/0x2ca
[ 9411.241965] acpi_ns_evaluate+0x34e/0x4f0
[ 9411.241965] acpi_evaluate_object+0x18e/0x3b4
[ 9411.241965] acpi_enter_sleep_state_prep+0xb9/0x145
[ 9411.241965] acpi_power_off_prepare+0x35/0x50
[ 9411.241966] kernel_restart+0x4c/0x70
[ 9411.241966] __do_sys_reboot+0x1d1/0x210
[ 9411.241966] ? vfs_writev+0xce/0x100
[ 9411.241967] ? __audit_syscall_entry+0xdb/0x120
[ 9411.241967] ? syscall_trace_enter+0x1a5/0x290
[ 9411.241967] ? __audit_syscall_exit+0x25d/0x2c0
[ 9411.241967] __x64_sys_reboot+0x1e/0x20
[ 9411.241968] do_syscall_64+0x57/0x190
[ 9411.241968] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 9411.241968] RIP: 0033:0x7f5667c75487
[ 9411.241969] Code: 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90
f3 0f 1e fa 89 fa be 69 19 12 28 bf ad de e1 fe b8 a9 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 01 c3 48 8b 15 d9 29 0d 00
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Please give this patch a try, thanks! ** Patch added: "0001-net-atlantic-Fix-LP-1958770.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+attachment/5565201/+files/0001-net-atlantic-Fix-LP-1958770.patch -- 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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+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 1962769] Re: Could not receive advertising events: Broken pipe
If you would like support for a version of BlueZ that you built yourself
then please go to https://github.com/bluez/bluez/issues/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Invalid
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
= bluetoothd: Unable
[Kernel-packages] [Bug 1962769] Re: Could not receive advertising events: Broken pipe
Thanks for the bug report.
It appears you have modified Bluetooth binaries that are not from Ubuntu
so we can't support them here. The only supported version of bluez on
Ubuntu 20.04 is 5.53-0ubuntu3.5.
Although I do note that you are using:
Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
and that Cambridge Silicon Radio dongles are notoriously buggy. So I
would first recommend trying a different brand of Bluetooth dongle.
Unfortunately it is hard to know what chipset is inside before you buy
it.
If you would like to continue with bug reports then please start by
installing the Ubuntu-provided bluez packages and then open a new bug.
** Changed in: bluez (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Invalid
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
[Kernel-packages] [Bug 1962809] [NEW] package nvidia-dkms-510 510.54-0ubuntu0.21.10.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error ex
Public bug reported: software updater update and say it need send report ProblemType: Package DistroRelease: Ubuntu 21.10 Package: nvidia-dkms-510 510.54-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Mar 3 11:24:40 2022 ErrorMessage: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-03-01 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2.1 apt 2.3.9 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.54-0ubuntu0.21.10.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish need-duplicate-check package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1962809 Title: package nvidia-dkms-510 510.54-0ubuntu0.21.10.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: software updater update and say it need send report ProblemType: Package DistroRelease: Ubuntu 21.10 Package: nvidia-dkms-510 510.54-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Mar 3 11:24:40 2022 ErrorMessage: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-03-01 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2.1 apt 2.3.9 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.54-0ubuntu0.21.10.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1962809/+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 1956167] Re: CSR copy bluetooth dongles not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1956167 Title: CSR copy bluetooth dongles not working Status in linux package in Ubuntu: Expired Bug description: I have a knock off CSR bluetooth adapter version 5 which does not work with Kubuntu 21.10, kernel 5.13.0-22. The bluetooth dongle seems to register: ethan1@ethanubuntu:~$ rfkill list enter code here 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Bluetooth service appears to be running: ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-12-31 06:57:52 AWST; 4min 13s ago Docs: man:bluetoothd(8) Main PID: 1752 (bluetoothd) Status: "Running" Tasks: 1 (limit: 9317) Memory: 1.6M CPU: 17ms CGroup: /system.slice/bluetooth.service └─1752 /usr/lib/bluetooth/bluetoothd Yet running: ethan@ethanubuntu:~$ sudo hcitool dev Devices: Says the dongle is not found as no devices are found. Same with bluetoothctl: ethan@ethanubuntu:~$ bluetoothctl Agent registered [bluetooth]# show No default controller available The same issue is mentioned at kernels.org https://bugzilla.kernel.org/show_bug.cgi?id=60824 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ethan 3931 F pulseaudio /dev/snd/controlC1: ethan 3931 F pulseaudio /dev/snd/controlC0: ethan 3931 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-05-13 (233 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=09e5eabd-2875-4c25-9dfe-a2db5b12855f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-22 (71 days ago) UserGroups: adm bluetooth cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0318 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0318:bd06/08/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956167/+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 1962799] Re: Bad items from Powertop on oem kernel
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1962799 Title: Bad items from Powertop on oem kernel Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: On Jaguar2, we found some items are bad from powertop, could we set them 'Good' by default from oem kernel, so that we could save more power consumption. System info "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022", CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8], Kernel: 5.14.0-1024-oem Power Consumption === The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle passed. Default value and the value after set all ‘Good’ in powertop ShortIdle: 5.5W, 5W LongIdle: 1.8W, 2W S2Idle: 0.6W, 0.6W Bad items === * VM writeback timeout (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs) * Should we turn off the NMI watchdog for the OEM kernel? It prompt“NMI watchdog should be turned off” (/proc/sys/kernel/nmi_watchdog) * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])? By default these values are ‘on’, should we set it to ‘auto’? (/sys/bus/i2c/devices/i2c-2/device/power/control) * Runtime PM for PCI Device Intel Corporation Device [4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]? Host bridge,VGA controller,Signal processing controller,System peripheral,Serial bus controller,Network Controller,ISA bridge,USB controller,RAM memory,Serial controller. (/sys/bus/pci/devices/:00:00.0/power/control) * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75 * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a * Autosuspend for USB device USB Bridge [MCHP]? (/sys/bus/usb/devices/3-8/power/control) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962799/+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 1962799] Re: Bad items from Powertop on oem kernel
** Changed in: linux-oem (Ubuntu) Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux-oem (Ubuntu) Assignee: AaronMa (mapengyu) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1962799 Title: Bad items from Powertop on oem kernel Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: On Jaguar2, we found some items are bad from powertop, could we set them 'Good' by default from oem kernel, so that we could save more power consumption. System info "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022", CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8], Kernel: 5.14.0-1024-oem Power Consumption === The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle passed. Default value and the value after set all ‘Good’ in powertop ShortIdle: 5.5W, 5W LongIdle: 1.8W, 2W S2Idle: 0.6W, 0.6W Bad items === * VM writeback timeout (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs) * Should we turn off the NMI watchdog for the OEM kernel? It prompt“NMI watchdog should be turned off” (/proc/sys/kernel/nmi_watchdog) * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])? By default these values are ‘on’, should we set it to ‘auto’? (/sys/bus/i2c/devices/i2c-2/device/power/control) * Runtime PM for PCI Device Intel Corporation Device [4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]? Host bridge,VGA controller,Signal processing controller,System peripheral,Serial bus controller,Network Controller,ISA bridge,USB controller,RAM memory,Serial controller. (/sys/bus/pci/devices/:00:00.0/power/control) * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75 * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a * Autosuspend for USB device USB Bridge [MCHP]? (/sys/bus/usb/devices/3-8/power/control) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962799/+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 1962799] Re: Bad items from Powertop on oem kernel
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Importance: Undecided => High ** Tags added: hwe-powerconsumption -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1962799 Title: Bad items from Powertop on oem kernel Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: On Jaguar2, we found some items are bad from powertop, could we set them 'Good' by default from oem kernel, so that we could save more power consumption. System info "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022", CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8], Kernel: 5.14.0-1024-oem Power Consumption === The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle passed. Default value and the value after set all ‘Good’ in powertop ShortIdle: 5.5W, 5W LongIdle: 1.8W, 2W S2Idle: 0.6W, 0.6W Bad items === * VM writeback timeout (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs) * Should we turn off the NMI watchdog for the OEM kernel? It prompt“NMI watchdog should be turned off” (/proc/sys/kernel/nmi_watchdog) * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])? By default these values are ‘on’, should we set it to ‘auto’? (/sys/bus/i2c/devices/i2c-2/device/power/control) * Runtime PM for PCI Device Intel Corporation Device [4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]? Host bridge,VGA controller,Signal processing controller,System peripheral,Serial bus controller,Network Controller,ISA bridge,USB controller,RAM memory,Serial controller. (/sys/bus/pci/devices/:00:00.0/power/control) * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75 * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a * Autosuspend for USB device USB Bridge [MCHP]? (/sys/bus/usb/devices/3-8/power/control) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962799/+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 1962799] Re: Bad items from Powertop on oem kernel
For NMI watchdog, I found some explanation from google. What could happen if I disable nmi_watchdog permanently? Imagine your system locks up. There's 2 possibilities now: 1) You have a hardware NMI button (some servers do). Push it, then the kernel (if properly configured) dumps a trace to console and reboots. 2) Your kernel reaches a halting state that can't be interrupted by any other method. In this case, the watchdog can reboot the machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1962799 Title: Bad items from Powertop on oem kernel Status in linux-oem package in Ubuntu: New Bug description: On Jaguar2, we found some items are bad from powertop, could we set them 'Good' by default from oem kernel, so that we could save more power consumption. System info "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022", CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8], Kernel: 5.14.0-1024-oem Power Consumption === The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle passed. Default value and the value after set all ‘Good’ in powertop ShortIdle: 5.5W, 5W LongIdle: 1.8W, 2W S2Idle: 0.6W, 0.6W Bad items === * VM writeback timeout (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs) * Should we turn off the NMI watchdog for the OEM kernel? It prompt“NMI watchdog should be turned off” (/proc/sys/kernel/nmi_watchdog) * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])? By default these values are ‘on’, should we set it to ‘auto’? (/sys/bus/i2c/devices/i2c-2/device/power/control) * Runtime PM for PCI Device Intel Corporation Device [4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]? Host bridge,VGA controller,Signal processing controller,System peripheral,Serial bus controller,Network Controller,ISA bridge,USB controller,RAM memory,Serial controller. (/sys/bus/pci/devices/:00:00.0/power/control) * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75 * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a * Autosuspend for USB device USB Bridge [MCHP]? (/sys/bus/usb/devices/3-8/power/control) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1962799/+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 1962799] [NEW] Bad items from Powertop on oem kernel
Public bug reported: On Jaguar2, we found some items are bad from powertop, could we set them 'Good' by default from oem kernel, so that we could save more power consumption. System info "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022", CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8], Kernel: 5.14.0-1024-oem Power Consumption === The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle passed. Default value and the value after set all ‘Good’ in powertop ShortIdle: 5.5W, 5W LongIdle: 1.8W, 2W S2Idle: 0.6W, 0.6W Bad items === * VM writeback timeout (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs) * Should we turn off the NMI watchdog for the OEM kernel? It prompt“NMI watchdog should be turned off” (/proc/sys/kernel/nmi_watchdog) * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])? By default these values are ‘on’, should we set it to ‘auto’? (/sys/bus/i2c/devices/i2c-2/device/power/control) * Runtime PM for PCI Device Intel Corporation Device [4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]? Host bridge,VGA controller,Signal processing controller,System peripheral,Serial bus controller,Network Controller,ISA bridge,USB controller,RAM memory,Serial controller. (/sys/bus/pci/devices/:00:00.0/power/control) * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75 * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a * Autosuspend for USB device USB Bridge [MCHP]? (/sys/bus/usb/devices/3-8/power/control) ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1962799 Title: Bad items from Powertop on oem kernel Status in linux-oem package in Ubuntu: New Bug description: On Jaguar2, we found some items are bad from powertop, could we set them 'Good' by default from oem kernel, so that we could save more power consumption. System info "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022", CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8], Kernel: 5.14.0-1024-oem Power Consumption === The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle passed. Default value and the value after set all ‘Good’ in powertop ShortIdle: 5.5W, 5W LongIdle: 1.8W, 2W S2Idle: 0.6W, 0.6W Bad items === * VM writeback timeout (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs) * Should we turn off the NMI watchdog for the OEM kernel? It prompt“NMI watchdog should be turned off” (/proc/sys/kernel/nmi_watchdog) * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])? By default these values are ‘on’, should we set it to ‘auto’? (/sys/bus/i2c/devices/i2c-2/device/power/control) * Runtime PM for PCI Device Intel Corporation Device [4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]? Host bridge,VGA controller,Signal processing controller,System peripheral,Serial bus controller,Network Controller,ISA bridge,USB controller,RAM memory,Serial controller. (/sys/bus/pci/devices/:00:00.0/power/control) * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75 * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a * Autosuspend for USB device USB Bridge [MCHP]? (/sys/bus/usb/devices/3-8/power/control) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1962799/+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 1962769] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565121/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
= bluetoothd:
[Kernel-packages] [Bug 1962769] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565119/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
= bluetoothd:
[Kernel-packages] [Bug 1962769] syslog.txt
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565134/+files/syslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
= bluetoothd:
[Kernel-packages] [Bug 1962769] rfkill.txt
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565133/+files/rfkill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
= bluetoothd:
[Kernel-packages] [Bug 1962769] modified.conffile..etc.dbus-1.system.d.bluetooth.conf.txt
apport information
** Attachment added: "modified.conffile..etc.dbus-1.system.d.bluetooth.conf.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565132/+files/modified.conffile..etc.dbus-1.system.d.bluetooth.conf.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[Kernel-packages] [Bug 1962769] modified.conffile..etc.bluetooth.main.conf.txt
apport information
** Attachment added: "modified.conffile..etc.bluetooth.main.conf.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565131/+files/modified.conffile..etc.bluetooth.main.conf.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[Kernel-packages] [Bug 1962769] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565128/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
= bluetoothd:
[Kernel-packages] [Bug 1962769] getfacl.txt
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565129/+files/getfacl.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
=
[Kernel-packages] [Bug 1962769] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565126/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
[Kernel-packages] [Bug 1962769] hciconfig.txt
apport information
** Attachment added: "hciconfig.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565130/+files/hciconfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
=
[Kernel-packages] [Bug 1962769] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565127/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
=
[Kernel-packages] [Bug 1962769] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565124/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
=
[Kernel-packages] [Bug 1962769] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565125/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0]
[Kernel-packages] [Bug 1962769] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565122/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
=
[Kernel-packages] [Bug 1962769] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565120/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
=
[Kernel-packages] [Bug 1962769] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565123/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
=
[Kernel-packages] [Bug 1962769] Re: Could not receive advertising events: Broken pipe
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
= bluetoothd: Unable to register new adapter
[hci0] 98.951248
= Close Index: 00:1A:7D:DA:71:13
[Kernel-packages] [Bug 1962769] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1962769/+attachment/5565118/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
=
[Kernel-packages] [Bug 1962563] Re: bluetoothd crashed with SIGSEGV in __strlen_avx2() from _dbus_string_init_const() from _dbus_check_is_valid_path() from _dbus_check_is_valid_path() from dbus_messag
The fix for #272 is included in: bluez (5.63-0ubuntu2) jammy; urgency=medium * Cherry-pick 3 patches to fix some crash & reconnect issues (LP: #1962542) -- Jeremy Bicha Wed, 02 Mar 2022 10:26:23 +0100 ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1962563 Title: bluetoothd crashed with SIGSEGV in __strlen_avx2() from _dbus_string_init_const() from _dbus_check_is_valid_path() from _dbus_check_is_valid_path() from dbus_message_iter_append_basic() Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.63-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/05251767678452859eebd21c29df5e7c4b67ff66 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1962563/+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 1962769] Re: Could not receive advertising events: Broken pipe
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1962769
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769
Title:
Could not receive advertising events: Broken pipe
Status in bluez package in Ubuntu:
Incomplete
Bug description:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0]
1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..
1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0]
1052.238742
= bluetoothd: Unable to register new adapter [hci0]
1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0]
1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening:
[Kernel-packages] [Bug 1960933] Re: rtw89_pci constantly drops connection with old firmware
Hi,
I'm experiencing the exact same bug on impish with a Lenovo P14s, with
connection drops every 5 to 10 minutes.
I've just installed the proposed package and will update the bug report
tomorrow if the connection drops have stopped.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1960933
Title:
rtw89_pci constantly drops connection with old firmware
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Impish:
Fix Committed
Bug description:
[Impact]
This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10
(impish)
The current linux-firmware package (1.201.4+1.201.3) ships with
realtek rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin)
version v0.13.8.0.
My wifi chip wasn't able to keep a connection for more than a minute when
connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried
disabling the power_save and stuff. But that had little to no effect. I was
about to open an issue on the upstream project and did a last ditch attempt to
see if there were any firmware updates... I found linux-firmware.git and it had
two newer versions!
- v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to
show up)
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17
- v0.13.33.0 (was submitted in November 2021 and got merged in December
2021):
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983
I've downloaded and installed the latest "v0.13.33.0" on a whim and
rebooted. And what a pleasant surprise: Instantly, my wifi connection
lasted until the rest of the day.
Could you please consider updating this realtek firmware in the next
release? Thanks!
[Test Case]
See above.
[Fix]
Cherry pick two commit to match current Jammy:
4a7e1f5cabae ("rtw89: 8852a: update fw to v0.13.33.0")
ec17b637b7ab ("rtw89: 8852a: update fw to v0.13.30.0")
[Where Problems Could Occur]
Limited to wifi using RTL8852A HW.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960933/+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 1961815] Re: ftbfs with linux 5.16 & 5.17
This bug was fixed in the package nvidia-graphics-drivers-418-server - 418.226.00-0ubuntu3 --- nvidia-graphics-drivers-418-server (418.226.00-0ubuntu3) jammy; urgency=medium * Add debian/dkms_nvidia/patches/buildfix_kernel_5.16.patch, * Add debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch, * debian/templates/dkms_nvidia.conf.in: - Add support for Linux 5.16 and 5.17 (LP: #1961815). -- Alberto Milone Wed, 02 Mar 2022 17:32:28 +0100 ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1961815 Title: ftbfs with linux 5.16 & 5.17 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Bug description: [Impact] * FTBFS from with 5.16 & 5.17 kernels [Test Plan] * Install linux-generic-wip from ppa:canonical-kernel-team/unstable and linux-generic from jammy * install nvidia-dkms-390 * check that module is compiles correctly for both v5.15 and v5.17 kernels * Similar checks can be done using v5.15 & v5.16 kernels on focal using linux-hwe-20.04-edge and linux-oem-5.16 kernels. [Where problems could occur] * Fixes are backports of similar changes already present and in use in nvidia-graphics-drivers-470. Note that 390 drivers are in maintainance mode, and have stopped receiving upstream updates. Hence manual cherrypicks are performed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1961815/+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 1924741] Re: Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Hey Ian.
Nevermind. After looking at the patch file, I realized what I needed to
do and I can report that my m6700 from 9 years ago (what a journey) can
finally make use of the mic on my Bluetooth headset.
Cheers,
Anthony.
For anyone looking for the same instructions as I was, I used the
following sources:
Getting the Kernel source:
https://askubuntu.com/questions/159833/how-do-i-get-the-kernel-source-code
Compiling the module:
https://unix.stackexchange.com/questions/199350/bluetooth-btusb-how-to-replace-module-version-with-a-newer-one
--
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/1924741
Title:
Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Status in linux package in Ubuntu:
Confirmed
Bug description:
The Broadcom Bluetooth kernel module supports loading patches for
specific hardware devices. Which devices require patchram support is
defined in an array of structs in the kernel module `btusb`, which
allow matching by Vendor ID and, optionally, Product ID.
The Dell-branded device `413c:8197` requires the patch
`BCM20702A1-413c-8197.hcd`[1] to be loaded in order for HSP/HFP
functionality to work (A2DP and AVRCP work without the patch).
However, the patch is not sought for this device by `btusb`.
In 2011, `413c:8197` was included in the module[2], but not marked as
requiring patchram. Later, in 2017, a blanket entry was added for all
Dell-branded (`413c`) devices[3], marking them as requiring patchram.
However, the previous entry for `413c:8197` was not removed and
appears to block the patchram requirement from being added for this
device (presumably the algorithm stops searching after the first
match). The code stands like so:
```
static const struct usb_device_id btusb_table[] = {
...
/* Broadcom BCM20702A0 */
{ USB_DEVICE(0x413c, 0x8197) },
...
/* Dell Computer - Broadcom based */
{ USB_VENDOR_AND_INTERFACE_INFO(0x413c, 0xff, 0x01, 0x01),
.driver_info = BTUSB_BCM_PATCHRAM },
```
I would like to request removal of the earlier entry to facilitate
patchram support for device `413c:8197`.
I have tested this as working on my Dell Precision M6700 running
Ubuntu 20.04 with kernel `5.4.0-71-generic`.
[1]:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-413c-8197.hcd
[2]:
https://github.com/torvalds/linux/commit/d13431ca3eb2a2c14314f04813cdc11cd869f150
[3]:
https://github.com/torvalds/linux/commit/fdfddc601713d4ed564b0bd25b29415bd622020a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924741/+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 1930921] Re: Apache 2.4.41 corrupts files from samba share
** Changed in: debian Status: Unknown => 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/1930921 Title: Apache 2.4.41 corrupts files from samba share Status in apache2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in Debian: Confirmed Bug description: Wenn I serve a samba share with apache 2.4.41 on Ubuntu 20.04 then some files have a corrupt header during transmission. It seems that the first few bytes of the headers are truncated and sometimes other bytes of the download are not belonging to the file. A workaround I found that works is to set "EnableMMAP Off" in the apache config. See other bug reports like this: https://serverfault.com/questions/1044724/apache2-sends-corrupt-responses-when-using-a-cifs-share https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 This is most probably not a bug in Ubuntu itself but I am reporting it here since I assume that a data corruption bug is seen as critical. I am also marking it as a security vulnerability since it seems that wrong parts of memory get exposed during file download. I don't know how random the exposed memory is and if it potentially could expose e.g. secrets. Please feel free to remove the security vulnerability flag if your assessment leads to a different conclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930921/+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 1924741] Re: Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Hi Ian.
I've had my m6700 since 2012 and have never been able to use any
Bluetooth headset.
Any chance you can provide pointers on what incantations one needs to
call upon to get this fixed like you've done on your laptop?
Cheers,
Anthony.
--
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/1924741
Title:
Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Status in linux package in Ubuntu:
Confirmed
Bug description:
The Broadcom Bluetooth kernel module supports loading patches for
specific hardware devices. Which devices require patchram support is
defined in an array of structs in the kernel module `btusb`, which
allow matching by Vendor ID and, optionally, Product ID.
The Dell-branded device `413c:8197` requires the patch
`BCM20702A1-413c-8197.hcd`[1] to be loaded in order for HSP/HFP
functionality to work (A2DP and AVRCP work without the patch).
However, the patch is not sought for this device by `btusb`.
In 2011, `413c:8197` was included in the module[2], but not marked as
requiring patchram. Later, in 2017, a blanket entry was added for all
Dell-branded (`413c`) devices[3], marking them as requiring patchram.
However, the previous entry for `413c:8197` was not removed and
appears to block the patchram requirement from being added for this
device (presumably the algorithm stops searching after the first
match). The code stands like so:
```
static const struct usb_device_id btusb_table[] = {
...
/* Broadcom BCM20702A0 */
{ USB_DEVICE(0x413c, 0x8197) },
...
/* Dell Computer - Broadcom based */
{ USB_VENDOR_AND_INTERFACE_INFO(0x413c, 0xff, 0x01, 0x01),
.driver_info = BTUSB_BCM_PATCHRAM },
```
I would like to request removal of the earlier entry to facilitate
patchram support for device `413c:8197`.
I have tested this as working on my Dell Precision M6700 running
Ubuntu 20.04 with kernel `5.4.0-71-generic`.
[1]:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-413c-8197.hcd
[2]:
https://github.com/torvalds/linux/commit/d13431ca3eb2a2c14314f04813cdc11cd869f150
[3]:
https://github.com/torvalds/linux/commit/fdfddc601713d4ed564b0bd25b29415bd622020a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924741/+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 1962769] [NEW] Could not receive advertising events: Broken pipe
Public bug reported:
If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0
This happend after I updated bluez from 5.62 to 5.63.
If I do scan again, everything works fine with one adapter.
As both adapters use the same mac address, I changed the address of hci0
hci0: Type: Primary Bus: USB
BD Address: 00:01:07:00:47:0E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0
but the old address keeps reverted back which was not the case in 5.62
I ran scan again while running btmon
@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 1052.238244
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al.. 1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0] 1052.238742
= bluetoothd: Unable to register new adapter [hci0] 1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0] 1054.246981
@ MGMT Event: Index Added (0x0004) plen 0
{0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0
{0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283
{0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
Current settings: 0x0080
BR/EDR
Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use
(98)
98.951201
= bluetoothd: Failed to create GATT database for adapter
[hci0] 98.951229
= bluetoothd: Unable to register new adapter
[hci0] 98.951248
= Close Index: 00:1A:7D:DA:71:13
[hci0] 100.967001
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
[Kernel-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63
This bug was fixed in the package bluez - 5.63-0ubuntu2 --- bluez (5.63-0ubuntu2) jammy; urgency=medium * Cherry-pick 3 patches to fix some crash & reconnect issues (LP: #1962542) -- Jeremy Bicha Wed, 02 Mar 2022 10:26:23 +0100 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63 Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.13/5.13.0.1015.17~20.04.5)
All autopkgtests for the newly accepted linux-meta-azure-5.13 (5.13.0.1015.17~20.04.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.31-0ubuntu9.7 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure-5.13 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1786013] Autopkgtest regression report (linux-meta-aws/5.13.0.1015.16)
All autopkgtests for the newly accepted linux-meta-aws (5.13.0.1015.16) for impish have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.34-0ubuntu3.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
Reported here: https://gitlab.freedesktop.org/drm/amd/-/issues/1923 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1923 https://gitlab.freedesktop.org/drm/amd/-/issues/1923 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on Status in linux-hwe-5.13 package in Ubuntu: Fix Released Bug description: Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor. This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe). Others are seeing this with both NVidia and AMD graphics hardware: - https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/ - https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/ I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem. Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm-radeon1` for luck - no joy. Running a 20.04.3 live stick the problem does *not* occur. System: Thinkpad X13 Gen1 Processor: AMD Ryzen 7 PRO 4750U System Firmware: 1.35 $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Happy to assist with investigations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME Date: Thu Jan 20 19:37:09 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-06-24 (210 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20UF0014US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET67W(1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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-hwe-5.13/+bug/1958591/+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 1961815] Re: ftbfs with linux 5.16 & 5.17
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu) Status: Triaged => In Progress ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Importance: Undecided => Medium ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1961815 Title: ftbfs with linux 5.16 & 5.17 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Bug description: [Impact] * FTBFS from with 5.16 & 5.17 kernels [Test Plan] * Install linux-generic-wip from ppa:canonical-kernel-team/unstable and linux-generic from jammy * install nvidia-dkms-390 * check that module is compiles correctly for both v5.15 and v5.17 kernels * Similar checks can be done using v5.15 & v5.16 kernels on focal using linux-hwe-20.04-edge and linux-oem-5.16 kernels. [Where problems could occur] * Fixes are backports of similar changes already present and in use in nvidia-graphics-drivers-470. Note that 390 drivers are in maintainance mode, and have stopped receiving upstream updates. Hence manual cherrypicks are performed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1961815/+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 1960430] Re: IPsec tunnel mode fix inner_ipproto setting in sec_path
This bug is awaiting verification that the linux-bluefield/5.4.0-1029.32 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1960430 Title: IPsec tunnel mode fix inner_ipproto setting in sec_path Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) current code implementation did not handle the case where IPsec is used in tunnel mode. * Brief explanation of fixes As in case of IPsec tunnel mode the skb->encapsulation bit is not set in case of non-encapsulated packet (As TCP and UDP), then inner IP protocol won’t be set, change code behavior to do so also in case of IPsec Tunnel mode * How to test Need to make sure that the code compiles post this change, run TCP traffic when IPSec crypto offload with tunnel mode is configured * What it could break. NA, this function adds data to a new field introduced to struct xfrm_offload, so if not used it have no effect and it is assigned in stack and used in driver so if driver does not used it then no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1960430/+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 1960427] Re: Add inner_ipproto into sec_path
This bug is awaiting verification that the linux-bluefield/5.4.0-1029.32 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1960427 Title: Add inner_ipproto into sec_path Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) The inner_ipproto saves the inner IP protocol of the plain text packet. This allows vendor's IPsec feature making offload decision at skb's features_check and configuring hardware at ndo_start_xmit. For example, ConnectX6-DX IPsec device needs the plaintext's IP protocol to support partial checksum offload on VXLAN/GENEVE packet over IPsec transport mode tunnel * Brief explanation of fixes As this data unrelated to the specific driver (the inner ip protocol of the plain text) then it makes sense to provide it in the xfrm stack layer to avoid code duplication in various drivers and do it on the fly in the xfrm layer instead of reparse the packet at the driver layer. * How to test Need to make sure that the code compiles post this change, run TCP encapsulated traffic (for example using vxlan) when IPSec crypto offload with transport mode is configured * What it could break. NA, this function adds data to a new field introduced to struct xfrm_offload, so if not used it have no effect and it is assigned in stack and used in driver so if driver does not used it then no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1960427/+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 1962758] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1962758 Title: 'Touchpad' not detected in 'Fujitsu FMVU28013 Lifebook U9310/D' Status in linux package in Ubuntu: Confirmed Bug description: Model:FUJITSU CLIENT COMPUTING LIMITED FMVU28013 Processor:Intel® Core™ i5-10310U CPU @ 1.70GHz × 8 OS:Ubuntu 21.10 OS-Type:64-bit GNOME Version:40.4.0 Windowing System:Wayland I just did a fresh install of ubuntu 21.10 and the touchpad is not detected. It doesn't show up in xinput and when I run cat /proc/bus/input/devices, the trackpad doesn't seem to be detected. not building a dual boot environment, only Ubuntu The result of running xinput is as follows. WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointer id=2 [master pointer (3) ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2) ⎜ ↳ xwayland-pointer:17 id=6 [slave pointer (2) ⎜ ↳ xwayland-relative-pointer:17 id=7 [slave pointer (2) ⎣ Virtual core keyboard id=3 [master keyboard (2) ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3) ↳ xwayland-keyboard:17 id=8 [slave keyboard (3) I tried the following with no improvement 1 Add the following to /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash" 2 Run sudo update-grub 3 Reboot I'm sorry for my poor English. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-30-generic 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raptor 1385 F pulseaudio CasperMD5CheckResult: pass Date: Thu Mar 3 00:03:06 2022 InstallationDate: Installed on 2022-03-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVU28013 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=1cd8a9d2-d5b5-4a09-abd0-290b814e0693 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.201.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2020 dmi.bios.release: 2.13 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.13 dmi.board.name: FJNB2D9 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.13:bd06/19/2020:br2.13:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVU28013:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D9:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-JC dmi.product.name: FMVU28013 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962758/+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 1958467] Re: focal linux-firmware package omits amdgpu/navi12 firmware
My apologies for not including the specific version in my comment - I tested linux-firmware package 1.187.27 from the focal proposed repository. ubuntu@ip-172-31-38-36:~$ apt list | grep linux-firmware/ linux-firmware/focal-proposed,now 1.187.27 all [installed] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1958467 Title: focal linux-firmware package omits amdgpu/navi12 firmware Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: Invalid Bug description: [Impact] The 20.04 LTS linux-firmware package list was cut before the amdgpu/navi12* firmware files were upstreamed to the Linux kernel repository, which is unfortunate because this hardware is older than some other included firmware (navi14*), and the firmware is required for using the AMDGPU kernel module on AWS EC2 cloud instances with AMD GPUs. The files are included in 21.04 and 21.10, but to date they have not been included in the LTS hardware-enablement releases for 20.04. It would be helpful to include the navi12 firmware files for the next LTS+HWE release, since 22.04 isn't due out for a while. Without this firmware it is difficult to get AWS EC2 G4ad instances working with Ubuntu, as customers need to manually download and install the firmware from a reputable source and put it into the appropriate directory, which is not the experience they expect on hardware that is over a year old with the most recent HWE release. [Test Case] See above. [Fix] Backport amdgpu/nav12* from linux-firmware Jammy. [Where Problems Could Occur] Graphics problems, kernel crashes on machines with AMD GPU. [Notes] This is required for the HWE kernel so not updating linux-firmware in Impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958467/+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 1962758] [NEW] 'Touchpad' not detected in 'Fujitsu FMVU28013 Lifebook U9310/D'
Public bug reported: Model:FUJITSU CLIENT COMPUTING LIMITED FMVU28013 Processor:Intel® Core™ i5-10310U CPU @ 1.70GHz × 8 OS:Ubuntu 21.10 OS-Type:64-bit GNOME Version:40.4.0 Windowing System:Wayland I just did a fresh install of ubuntu 21.10 and the touchpad is not detected. It doesn't show up in xinput and when I run cat /proc/bus/input/devices, the trackpad doesn't seem to be detected. not building a dual boot environment, only Ubuntu The result of running xinput is as follows. WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointer id=2 [master pointer (3) ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2) ⎜ ↳ xwayland-pointer:17 id=6 [slave pointer (2) ⎜ ↳ xwayland-relative-pointer:17 id=7 [slave pointer (2) ⎣ Virtual core keyboard id=3 [master keyboard (2) ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3) ↳ xwayland-keyboard:17 id=8 [slave keyboard (3) I tried the following with no improvement 1 Add the following to /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash" 2 Run sudo update-grub 3 Reboot I'm sorry for my poor English. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-30-generic 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raptor 1385 F pulseaudio CasperMD5CheckResult: pass Date: Thu Mar 3 00:03:06 2022 InstallationDate: Installed on 2022-03-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED FMVU28013 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=1cd8a9d2-d5b5-4a09-abd0-290b814e0693 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.201.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2020 dmi.bios.release: 2.13 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.13 dmi.board.name: FJNB2D9 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.13:bd06/19/2020:br2.13:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnFMVU28013:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D9:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-JC dmi.product.name: FMVU28013 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1962758 Title: 'Touchpad' not detected in 'Fujitsu FMVU28013 Lifebook U9310/D' Status in linux package in Ubuntu: New Bug description: Model:FUJITSU CLIENT COMPUTING LIMITED FMVU28013 Processor:Intel® Core™ i5-10310U CPU @ 1.70GHz × 8 OS:Ubuntu 21.10 OS-Type:64-bit GNOME Version:40.4.0 Windowing System:Wayland I just did a fresh install of ubuntu 21.10 and the touchpad is not detected. It doesn't show up in xinput and when I run cat /proc/bus/input/devices, the trackpad doesn't seem to be detected. not building a dual boot environment, only Ubuntu The result of running xinput is as follows. WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointer id=2 [master pointer (3) ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2) ⎜ ↳ xwayland-pointer:17 id=6 [slave pointer (2) ⎜ ↳ xwayland-relative-pointer:17 id=7 [slave pointer (2) ⎣ Virtual core keyboard id=3 [master keyboard (2) ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3) ↳ xwayland-keyboard:17 id=8 [slave keyboard (3) I tried the following with no improvement 1 Add the following to /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash" 2 Run sudo update-grub 3 Reboot I'm sorry for my poor English. ProblemType: Bug DistroRelease: Ubuntu 21.10
[Kernel-packages] [Bug 1956855] Re: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine
Hello Hui, or anyone else affected, Accepted alsa-ucm-conf into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.2-1ubuntu0.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1956855 Title: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Released Bug description: [Impact] This Dell machine has dual Realtek 4050 USB Codecs as front and rear codec, the front codec has speaker and headset, the rear codec has line-out audio jack. Without UCM, the pulseaudio can't detect this two usb audio codec and the audio can't work at all. [Fix] Backport a upstream patch, the patch adds the front and rear profiles in the ucm, then pulseaudio will enable all audio devices in this machine. [Test] booting with patched ucm, open the gnome-sound-setting, we could see usb speaker, usb headset and usb lineout, play sound to speaker, headset and lineout, all worked well, record sound via headset, it could record the sound correctly. [Where problems could occur] This SRU adds the new ucm files to a folder, in theory it will not introduce regressions, but It adds a file USB-Audio.conf, it could make other ucm conf files in the USB-Audio folder fail to parse, and make the P620 and WD15/19's audio fail to work, but this possibility is very low, we already tested it and no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956855/+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 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4
** Tags added: 5.13 impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+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 1961406] Re: Known bug in IGC causes shutdown bug in z690 environments
When I unload the **igc** module while system is running it triggers a reboot, just like described here: - https://lore.kernel.org/all/924175a188159f4e03bd69908a91e606b574139b.ca...@gmx.de/ The 5.15.12 kernel seems to fix the issue for **igb** kernel module but not for **igc**. According to this forum thread (last message) kernel version 5.15.13 solves the problem for **igc**: - https://bbs.archlinux.org/viewtopic.php?pid=2014226#p2014226 -- 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/1961406 Title: Known bug in IGC causes shutdown bug in z690 environments Status in linux package in Ubuntu: Confirmed Bug description: I own a Asus z690 Apex board, and shutdown hangs because of a bug in IGC driver. I cannot provide any logs because this happens after filesystem driver has been shut down and display/graphics have been turned of. The PC simply never turns off. I can disable the network interface in UEFI Bios, then the problem disappears. As far as I know a newer 5.15.x version already contains a fix. Since most users that own a AlderLake / z690 will be affected by this bug it should be fixed before release. I read about some MSI boards does not have that problem, but any other mainboards (asus, asrocks, gigabyte etc) seem to have this bug. I updated my bios and tried different shutdown commands without success Related links: - https://groups.google.com/g/linux.debian.bugs.dist/c/i6buM9KpulI?pli=1 - https://bbs.archlinux.org/viewtopic.php?id=272338 - https://www.reddit.com/r/Fedora/comments/r3hxt0/restartshut_down_problem_on_kernel_5154201/ ``` phoenix@dev:~$ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 phoenix@dev:~$ cat /proc/version_signature Ubuntu 5.15.0-18.18-generic 5.15.12 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 18 13:37:10 2022 InstallationDate: Installed on 2021-06-11 (252 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=1d617086-e30d-4dd3-a313-3b435ea89649 ro quiet splash mitigations=off systemd.unified_cgroup_hierarchy=false vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-01-14 (34 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 11.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS Z690 APEX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd01/26/2022:br11.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ690APEX:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961406/+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 1923683] Re: ftrace from ubuntu_kernel_selftests failed with "test for function event triggers" on F/G/H/I
** Changed in: linux (Ubuntu Impish)
Status: New => 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/1923683
Title:
ftrace from ubuntu_kernel_selftests failed with "test for function
event triggers" on F/G/H/I
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Confirmed
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Won't Fix
Status in linux source package in Impish:
Confirmed
Bug description:
ftrace from ubuntu_kernel_selftests failed with "test for function
event triggers" on Groovy riscv 5.8.0-21.23
This test was recently added, not considering a regression
Log is getting cut off from regression test report. the below is all
that could be retrieved at the moment:
04/13 23:48:00 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 >
/proc/sys/net/ipv4/conf/all/accept_local''
04/13 23:48:00 DEBUG| utils:0116| Running 'sudo make -C
linux/tools/testing/selftests TARGETS=ftrace run_tests'
04/13 23:48:00 DEBUG| utils:0153| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
04/13 23:48:01 DEBUG| utils:0153| [stdout] make --no-builtin-rules
ARCH=riscv -C ../../.. headers_install
04/13 23:48:01 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
04/13 23:48:14 DEBUG| utils:0153| [stdout] INSTALL ./usr/include
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done
for 'all'.
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:16 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:16 DEBUG| utils:0153| [stdout] TAP version 13
04/13 23:48:16 DEBUG| utils:0153| [stdout] 1..1
04/13 23:48:16 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Setting locale
failed.
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Please check
that your locale settings:
04/13 23:48:16 ERROR| utils:0153| [stderr]LANGUAGE = (unset),
04/13 23:48:16 ERROR| utils:0153| [stderr]LC_ALL = (unset),
04/13 23:48:16 ERROR| utils:0153| [stderr]LC_CTYPE = "C.UTF-8",
04/13 23:48:16 ERROR| utils:0153| [stderr]LANG = "en_US.UTF-8"
04/13 23:48:16 ERROR| utils:0153| [stderr] are supported and
installed on your system.
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Falling back to
the standard locale ("C").
04/13 23:48:17 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
04/13 23:48:21 DEBUG| utils:0153| [stdout] # [1] Basic trace file check
[PASS]
04/13 23:49:02 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers
[PASS]
04/13 23:49:09 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test
[PASS]
04/13 23:49:13 DEBUG| utils:0153| [stdout] # [4] Basic event tracing
check[PASS]
04/13 23:49:18 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer
size [PASS]
04/13 23:49:23 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing
setting [PASS]
04/13 23:49:27 DEBUG| utils:0153| [stdout] # [7] trace_pipe and
trace_marker [PASS]
04/13 23:49:32 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct
functions against tracers [UNRESOLVED]
04/13 23:49:33 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct
functions against kprobes [UNSUPPORTED]
04/13 23:49:37 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event -
add/remove kprobe events[FAIL]
04/13 23:49:37 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event -
add/remove synthetic events [UNSUPPORTED]
04/13 23:49:38 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event -
selective clear (compatibility) [UNSUPPORTED]
04/13 23:49:39 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event -
generic clear event [UNSUPPORTED]
04/13 23:49:44 DEBUG| utils:0153| [stdout] # [14] event tracing -
enable/disable with event level files [PASS]
04/13 23:49:50 DEBUG| utils:0153| [stdout] # [15] event
[Kernel-packages] [Bug 1948377] Re: [SRU][F] USB: serial: pl2303: add support for PL2303HXN
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-iot in Ubuntu. https://bugs.launchpad.net/bugs/1948377 Title: [SRU][F] USB: serial: pl2303: add support for PL2303HXN Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-iot package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-iot source package in Focal: Fix Committed Bug description: [Impact] PL2303HXN is not supported by 5.4 kernel. 5.5 kernel starts to support it. so only SRU for focal 5.4 kernel. [Fix] Clean cherry-pick upstream commits. Add support for PL2303HXN. [Test] Verified on hardware, use minicom to test serial port, it works fine. [Where problems could occur] It may break the pl2303 ttyUSBx. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1948377/+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 1946507] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1946507 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1946507 Title: Ubuntu Install Setup Freeze Status in linux package in Ubuntu: Incomplete Bug description: Hello, While trying to Install Ubuntu 21.10 , the setup freeze after clicking continue on Step 4 where it asks if you wish to install Updates , and i have selected Normal Installation when i click continue then setup freeze so im not able to click any other button just QUIT button is working , other buttons are grayed out and not clickable , i have tried many methods since 2 days been trying nomodeset acpi=off and other but nothing works for me , i need help . Thanks ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 8 15:56:06 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+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 1962578] Re: [UBUNTU 20.04] Fix SIGP processing on KVM/s390
Kernel test builds: linux - 5.13.0-32.35~lp1962578 linux - 5.4.0-102.115~lp1962578 that incl. the commits mentioned above are available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1962578 -- 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/1962578 Title: [UBUNTU 20.04] Fix SIGP processing on KVM/s390 Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Impish: New Bug description: Decription: KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. The patches to fix this have already been picked for jammy/master- next: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" For Ubuntu 20.04 the focal/master-next already contains: d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART so we additionally need the following two upstream commits in focal 67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state 8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1962578/+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 1946507] Re: Ubuntu Install Setup Freeze
It seems that Ubuntu 20.04.4 gets stuck at the same step with the same traces appearing in the kernel log. Since the installer uses the same kernel (5.13) it likely is caused by that kernel version. Ubuntu 22.04 (nightly as of 20220301, which seems to come with 5.15) seems to work fine 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/1946507 Title: Ubuntu Install Setup Freeze Status in linux package in Ubuntu: New Bug description: Hello, While trying to Install Ubuntu 21.10 , the setup freeze after clicking continue on Step 4 where it asks if you wish to install Updates , and i have selected Normal Installation when i click continue then setup freeze so im not able to click any other button just QUIT button is working , other buttons are grayed out and not clickable , i have tried many methods since 2 days been trying nomodeset acpi=off and other but nothing works for me , i need help . Thanks ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 8 15:56:06 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+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 1946507] Re: Ubuntu Install Setup Freeze
** Changed in: linux (Ubuntu) Status: Expired => New -- 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/1946507 Title: Ubuntu Install Setup Freeze Status in linux package in Ubuntu: New Bug description: Hello, While trying to Install Ubuntu 21.10 , the setup freeze after clicking continue on Step 4 where it asks if you wish to install Updates , and i have selected Normal Installation when i click continue then setup freeze so im not able to click any other button just QUIT button is working , other buttons are grayed out and not clickable , i have tried many methods since 2 days been trying nomodeset acpi=off and other but nothing works for me , i need help . Thanks ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 8 15:56:06 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+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 1946507] Re: Ubuntu Install Setup Freeze
Similar hang on a T440s trying to install Ubuntu 21.10. The system currently has a fresh Windows 11 copy on half of its SSD hard drive. It seems that ntfsresize causes the kernel to hang. Trying to install Ubuntu gets stuck in Step 4. Install logs attached. Hardware wise, the system seems to work fine. ** Attachment added: "install-logs-2022-03-02.1.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+attachment/5564997/+files/install-logs-2022-03-02.1.zip -- 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/1946507 Title: Ubuntu Install Setup Freeze Status in linux package in Ubuntu: New Bug description: Hello, While trying to Install Ubuntu 21.10 , the setup freeze after clicking continue on Step 4 where it asks if you wish to install Updates , and i have selected Normal Installation when i click continue then setup freeze so im not able to click any other button just QUIT button is working , other buttons are grayed out and not clickable , i have tried many methods since 2 days been trying nomodeset acpi=off and other but nothing works for me , i need help . Thanks ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 8 15:56:06 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+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 1954938] Re: Include the QCA WCN 6856 v2.1 support
It looks like verification is still needed against linux-firmware 1.187.27 in focal-proposed? ** Tags removed: verification-done-focal ** Tags added: verification-needede-focal ** Tags removed: verification-needede-focal ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954938 Title: Include the QCA WCN 6856 v2.1 support Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-firmware source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] WCN685x hw2.1 takes additional/updated firmware for both WiFi and Bluetooth function. ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit] ath11k_pci :71:00.0: enabling device ( -> 0002) ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17 ath11k_pci: probe of :71:00.0 failed with error -95 [Fix] WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except for the directory path and a board-2.bin. For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from mainline are neccessary for Focal. Jammy has all of them already. For kernel, many of the prerequisite works have been committed for hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G will be turned off for the lack of userspace support, the only fix necessary is to correct read mask of version info register. ath11k 6G band lives in mainline v5.16 and was backported to oem-5.14 in bug 1939528, so only oem-5.14 has to be reverted. [Test Case] WiFi and Bluetooth devices should be up and running, pass basic operations. $ lspci -nnk|grep -A3 Network :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0ce] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci $ lsusb Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai [Where problems could occur] At the time being, WCN685x WiFi 6G support will be turnef off deliberately due to the lack of full support in the userspace management tools. [Other Info] While this is a new hardware model from OEM program, it's only nominated for Focal oem-5.14 kernel and the coming LTS Jammy. == original bug report == ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit] ath11k_pci :71:00.0: enabling device ( -> 0002) ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17 ath11k_pci: probe of :71:00.0 failed with error -95 $ lspci -nnk|grep -A3 Network :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0ce] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci $ lsusb Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+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 1958467] Re: focal linux-firmware package omits amdgpu/navi12 firmware
Can you confirm the package version that was used with proposed enabled please? We've had serious regressions in the past because the version released accidentally did not match the version tested, so I want to make sure that the version I release is the version you tested. Note that this is specified in the request for verification in comment 1, and I've also pointed it out in the past: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039745.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1958467 Title: focal linux-firmware package omits amdgpu/navi12 firmware Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: Invalid Bug description: [Impact] The 20.04 LTS linux-firmware package list was cut before the amdgpu/navi12* firmware files were upstreamed to the Linux kernel repository, which is unfortunate because this hardware is older than some other included firmware (navi14*), and the firmware is required for using the AMDGPU kernel module on AWS EC2 cloud instances with AMD GPUs. The files are included in 21.04 and 21.10, but to date they have not been included in the LTS hardware-enablement releases for 20.04. It would be helpful to include the navi12 firmware files for the next LTS+HWE release, since 22.04 isn't due out for a while. Without this firmware it is difficult to get AWS EC2 G4ad instances working with Ubuntu, as customers need to manually download and install the firmware from a reputable source and put it into the appropriate directory, which is not the experience they expect on hardware that is over a year old with the most recent HWE release. [Test Case] See above. [Fix] Backport amdgpu/nav12* from linux-firmware Jammy. [Where Problems Could Occur] Graphics problems, kernel crashes on machines with AMD GPU. [Notes] This is required for the HWE kernel so not updating linux-firmware in Impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958467/+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 1962730] Re: Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
`apport-collect` can not be installed in this environment as it runs
from a read only / image.
** 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/1962730
Title:
Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a Dell T440 system the following crash is captured from reboot in
pstore. Although this example is not with the latest system BIOS it
does also happen with the latest (2.13.3). The upstream kernel tree
has reverted the patch applied for #1904225 in commit
9d3fcb28f9b9750b474811a2964ce022df56336e. The log message
specifically notes a problem with Dell R440 which is the rack mount
variation of the T440.
[ 9411.241947] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 9411.241948] {1}[Hardware Error]: event severity: fatal
[ 9411.241948] {1}[Hardware Error]: Error 0, type: fatal
[ 9411.241949] {1}[Hardware Error]: section_type: PCIe error
[ 9411.241949] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 9411.241949] {1}[Hardware Error]: version: 3.0
[ 9411.241950] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 9411.241950] {1}[Hardware Error]: device_id: :01:00.1
[ 9411.241950] {1}[Hardware Error]: slot: 1
[ 9411.241951] {1}[Hardware Error]: secondary_bus: 0x00
[ 9411.241951] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 9411.241951] {1}[Hardware Error]: class_code: 02
[ 9411.241952] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 9411.241952] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 9411.241953] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 9411.241953] Kernel panic - not syncing: Fatal hardware error!
[ 9411.241953] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: P OE
5.4.0-92-generic #103zynstra1
[ 9411.241954] Hardware name: Dell Inc. PowerEdge T440/00X7CK, BIOS 2.8.2
08/31/2020
[ 9411.241954] Call Trace:
[ 9411.241954] dump_stack+0x69/0x84
[ 9411.241955] panic+0x101/0x2e3
[ 9411.241955] __ghes_panic.part.0+0x2a/0x2a
[ 9411.241955] ghes_in_nmi_queue_one_entry.constprop.0.cold+0x5/0x16
[ 9411.241956] ghes_notify_nmi.part.0+0x3e/0xa0
[ 9411.241956] ghes_notify_nmi+0x26/0x30
[ 9411.241956] nmi_handle+0x62/0x120
[ 9411.241956] default_do_nmi+0x4c/0x130
[ 9411.241957] do_nmi.part.0+0x144/0x1a0
[ 9411.241957] do_nmi+0x34/0x40
[ 9411.241957] xennmi+0x1e/0x30
[ 9411.241958] RIP: e030:__acpi_release_global_lock+0x16/0x30
[ 9411.241958] Code: 83 fa 03 0f 95 c0 f7 d8 c3 66 66 2e 0f 1f 84 00 00 00 00
00 0f 1f 44 00 00 55 48 89 e5 8b 17 89 d1 89 d0 83 e1 fc f0 0f b1 0f <39> c2 75
ef 89 d0 5d 83 e0 01 c3 66 66 2e 0f 1f 84 00 00 00 00 00
[ 9411.241959] RSP: e02b:c90040083a98 EFLAGS: 0246
[ 9411.241960] RAX: 0002 RBX: 8890951677e0 RCX:
[ 9411.241960] RDX: 0002 RSI: 820c2160 RDI:
c90040007010
[ 9411.241960] RBP: c90040083a98 R08: R09:
88871d451e80
[ 9411.241961] R10: c90040083a40 R11: R12:
[ 9411.241961] R13: 8890865066c0 R14: 8890865068b8 R15:
0008
[ 9411.241961] acpi_ev_release_global_lock+0x93/0x128
[ 9411.241962] acpi_ex_release_mutex_object+0xb5/0xf9
[ 9411.241962] acpi_ex_release_global_lock+0x54/0x92
[ 9411.241962] acpi_ex_write_data_to_field+0x33a/0x36c
[ 9411.241963] acpi_ex_store_object_to_node+0x2ce/0x324
[ 9411.241963] acpi_ex_store+0xa3/0x273
[ 9411.241963] acpi_ex_opcode_1A_1T_1R+0x421/0x59a
[ 9411.241963] acpi_ds_exec_end_op+0x166/0x767
[ 9411.241964] acpi_ps_parse_loop+0x58a/0x660
[ 9411.241964] acpi_ps_parse_aml+0x1af/0x550
[ 9411.241964] acpi_ps_execute_method+0x208/0x2ca
[ 9411.241965] acpi_ns_evaluate+0x34e/0x4f0
[ 9411.241965] acpi_evaluate_object+0x18e/0x3b4
[ 9411.241965] acpi_enter_sleep_state_prep+0xb9/0x145
[ 9411.241965] acpi_power_off_prepare+0x35/0x50
[ 9411.241966] kernel_restart+0x4c/0x70
[ 9411.241966] __do_sys_reboot+0x1d1/0x210
[ 9411.241966] ? vfs_writev+0xce/0x100
[ 9411.241967] ? __audit_syscall_entry+0xdb/0x120
[ 9411.241967] ? syscall_trace_enter+0x1a5/0x290
[ 9411.241967] ? __audit_syscall_exit+0x25d/0x2c0
[ 9411.241967] __x64_sys_reboot+0x1e/0x20
[ 9411.241968] do_syscall_64+0x57/0x190
[ 9411.241968] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 9411.241968] RIP: 0033:0x7f5667c75487
[ 9411.241969] Code: 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90
f3 0f 1e fa 89 fa be 69 19 12 28 bf ad de e1 fe b8 a9 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 01 c3 48 8b 15 d9 29 0d 00 f7 d8 64 89 02 b8
[ 9411.241970] RSP:
[Kernel-packages] [Bug 1962730] Re: Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
I have built a kernel with this commit reverted by including the
referenced mainline change which resolves the observed problem.
--
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/1962730
Title:
Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a Dell T440 system the following crash is captured from reboot in
pstore. Although this example is not with the latest system BIOS it
does also happen with the latest (2.13.3). The upstream kernel tree
has reverted the patch applied for #1904225 in commit
9d3fcb28f9b9750b474811a2964ce022df56336e. The log message
specifically notes a problem with Dell R440 which is the rack mount
variation of the T440.
[ 9411.241947] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 9411.241948] {1}[Hardware Error]: event severity: fatal
[ 9411.241948] {1}[Hardware Error]: Error 0, type: fatal
[ 9411.241949] {1}[Hardware Error]: section_type: PCIe error
[ 9411.241949] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 9411.241949] {1}[Hardware Error]: version: 3.0
[ 9411.241950] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 9411.241950] {1}[Hardware Error]: device_id: :01:00.1
[ 9411.241950] {1}[Hardware Error]: slot: 1
[ 9411.241951] {1}[Hardware Error]: secondary_bus: 0x00
[ 9411.241951] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 9411.241951] {1}[Hardware Error]: class_code: 02
[ 9411.241952] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 9411.241952] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 9411.241953] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 9411.241953] Kernel panic - not syncing: Fatal hardware error!
[ 9411.241953] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: P OE
5.4.0-92-generic #103zynstra1
[ 9411.241954] Hardware name: Dell Inc. PowerEdge T440/00X7CK, BIOS 2.8.2
08/31/2020
[ 9411.241954] Call Trace:
[ 9411.241954] dump_stack+0x69/0x84
[ 9411.241955] panic+0x101/0x2e3
[ 9411.241955] __ghes_panic.part.0+0x2a/0x2a
[ 9411.241955] ghes_in_nmi_queue_one_entry.constprop.0.cold+0x5/0x16
[ 9411.241956] ghes_notify_nmi.part.0+0x3e/0xa0
[ 9411.241956] ghes_notify_nmi+0x26/0x30
[ 9411.241956] nmi_handle+0x62/0x120
[ 9411.241956] default_do_nmi+0x4c/0x130
[ 9411.241957] do_nmi.part.0+0x144/0x1a0
[ 9411.241957] do_nmi+0x34/0x40
[ 9411.241957] xennmi+0x1e/0x30
[ 9411.241958] RIP: e030:__acpi_release_global_lock+0x16/0x30
[ 9411.241958] Code: 83 fa 03 0f 95 c0 f7 d8 c3 66 66 2e 0f 1f 84 00 00 00 00
00 0f 1f 44 00 00 55 48 89 e5 8b 17 89 d1 89 d0 83 e1 fc f0 0f b1 0f <39> c2 75
ef 89 d0 5d 83 e0 01 c3 66 66 2e 0f 1f 84 00 00 00 00 00
[ 9411.241959] RSP: e02b:c90040083a98 EFLAGS: 0246
[ 9411.241960] RAX: 0002 RBX: 8890951677e0 RCX:
[ 9411.241960] RDX: 0002 RSI: 820c2160 RDI:
c90040007010
[ 9411.241960] RBP: c90040083a98 R08: R09:
88871d451e80
[ 9411.241961] R10: c90040083a40 R11: R12:
[ 9411.241961] R13: 8890865066c0 R14: 8890865068b8 R15:
0008
[ 9411.241961] acpi_ev_release_global_lock+0x93/0x128
[ 9411.241962] acpi_ex_release_mutex_object+0xb5/0xf9
[ 9411.241962] acpi_ex_release_global_lock+0x54/0x92
[ 9411.241962] acpi_ex_write_data_to_field+0x33a/0x36c
[ 9411.241963] acpi_ex_store_object_to_node+0x2ce/0x324
[ 9411.241963] acpi_ex_store+0xa3/0x273
[ 9411.241963] acpi_ex_opcode_1A_1T_1R+0x421/0x59a
[ 9411.241963] acpi_ds_exec_end_op+0x166/0x767
[ 9411.241964] acpi_ps_parse_loop+0x58a/0x660
[ 9411.241964] acpi_ps_parse_aml+0x1af/0x550
[ 9411.241964] acpi_ps_execute_method+0x208/0x2ca
[ 9411.241965] acpi_ns_evaluate+0x34e/0x4f0
[ 9411.241965] acpi_evaluate_object+0x18e/0x3b4
[ 9411.241965] acpi_enter_sleep_state_prep+0xb9/0x145
[ 9411.241965] acpi_power_off_prepare+0x35/0x50
[ 9411.241966] kernel_restart+0x4c/0x70
[ 9411.241966] __do_sys_reboot+0x1d1/0x210
[ 9411.241966] ? vfs_writev+0xce/0x100
[ 9411.241967] ? __audit_syscall_entry+0xdb/0x120
[ 9411.241967] ? syscall_trace_enter+0x1a5/0x290
[ 9411.241967] ? __audit_syscall_exit+0x25d/0x2c0
[ 9411.241967] __x64_sys_reboot+0x1e/0x20
[ 9411.241968] do_syscall_64+0x57/0x190
[ 9411.241968] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 9411.241968] RIP: 0033:0x7f5667c75487
[ 9411.241969] Code: 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90
f3 0f 1e fa 89 fa be 69 19 12 28 bf ad de e1 fe b8 a9 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 01 c3 48 8b 15 d9 29 0d 00 f7 d8 64 89 02 b8
[ 9411.241970] RSP: 002b:7fff00697cf8 EFLAGS:
[Kernel-packages] [Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
It does not reproduce after update linux 5.13.0-32.35 on impish.
** Attachment added: "dmesg and OS info"
https://bugs.launchpad.net/ubuntu/jammy/+source/linux/+bug/1937295/+attachment/5564971/+files/ubuntu2110.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/1937295
Title:
[SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping
is enabled by IOMMU
Status in subiquity:
Invalid
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
A hardware partner discovered they were unable to install Ubuntu on
some servers using VROC setups. They point to this issue involving
DMAR that is blocking discovery of the VROC RAID devices:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45
`git bisect` points to this offending commit ee81ee84f873 ("PCI:
vmd: Disable MSI-X remapping when possible"), which disables VMD MSI
remapping. The IOMMU hardware blocks the compatibility format
interrupt request because Interrupt Remapping Enable Status (IRES) and
Extended Interrupt Mode Enable (EIME) are enabled. Please refer to
section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d
spec.
To fix the issue, VMD driver still enables the interrupt remapping
irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem
enables the interrupt remapping.
[Fix]
2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt
remapping is enabled by IOMMU
[Test Plan]
1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
2. Install affected Ubuntu release on the RAID10.
3. The system hangs at "Partitions formatting 33%".
[Where problems could occur]
The fix itself is a very small change to drivers/pci/controller/vmd.c
and problems should not occur. The root cause was discovered by the
hardware partner's engineers, who tested and submitted it upstream
where it was accepted and landed in 5.16.
That said, I doubt this will fix 18.04.6 as it would require a respin
to get the patched kernel onto the ISO. 20.04 should pick it up in
ISO in 20.04.5, so there could still be the initial issue since those
ISOs would be lacking the patched kernel.
[Other Info]
As noted, this would need to not only land in the kernel but land in
the kernel in the ISO to resolve the issue in the installation
process. I'll bring this back as far as Focal with the expectation
that while 20.04.4 is too late, it will be present using the GA kernel
in 20.04.5 later on.
*
Original Bug Summary:
A hardware partner has been testing 18.04 subiquity images on their
servers with VROC enabled and configured in a RAID 10 setup.
In their own words:
Steps to reproduce:
1. Boot into VRoC controller in uEFI Setup and create a raid10
disk.
2. Install Ubuntu 18.04.5 on the RAID10.
3. The system hangs at "Partitions formatting 33%".
After looking at the launchpad
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the
fix was included in the updated kernel.
[Quotes from the launchpad]
The released kernels are:
Hirsute: 5.11.0-22-generic
Groovy: 5.8.0-59-generic
Focal: 5.4.0-77-generic
Bionic: 4.15.0-147-generic
I've asked them to also confirm this on 20.04.2, and check that
20.04.3 dailies fix the issue.
It is at least a very reasonable hypothesis that this will also break
on all current ISO installs as none of them are respun once released
to include updated SRUs in the installation media. This currently
affects 20.04.2 but that will be resolved shortly when 20.04.3
releases as the GA and HWE kernels in that image should have the SRU
that fixes this issue. However, 18.04 has no further releases, and
even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com
are not built after 18.04.5 was released.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937295/+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 1962731] Re: No SYS%LPI residency after a suspend/resume when ethernet connected
Upload sos report. ** Attachment added: "sosreport-u-Latitude-5521-1962731-2022-03-02-drddnma.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1962731/+attachment/5564968/+files/sosreport-u-Latitude-5521-1962731-2022-03-02-drddnma.tar.xz ** Summary changed: - No SYS%LPI residency after a suspend/resume when ethernet connected + No SYS%LPI residency in suspend when ethernet is connected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: Try the command # turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15 ... Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 9.78 0.25 0.86 6.21 4.37 0.00 67.53 67.67 0.00 There is no SYS%LPI residency. Unplug ethernet, the residency become Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 8.63 0.13 0.07 22.56 1.24 0.00 53.95 54.08 53.82 The ethernet controller is I219-LM. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1024-oem 5.14.0-1024.26 ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21 Uname: Linux 5.14.0-1024-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 2 05:24:51 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-pidgeot+X92 InstallationDate: Installed on 2021-11-03 (118 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1962731/+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 1962731] [NEW] No SYS%LPI residency in suspend when ethernet is connected
Public bug reported: Try the command # turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15 ... Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 9.78 0.25 0.86 6.21 4.37 0.00 67.53 67.67 0.00 There is no SYS%LPI residency. Unplug ethernet, the residency become Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 8.63 0.13 0.07 22.56 1.24 0.00 53.95 54.08 53.82 The ethernet controller is I219-LM. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1024-oem 5.14.0-1024.26 ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21 Uname: Linux 5.14.0-1024-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 2 05:24:51 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-pidgeot+X92 InstallationDate: Installed on 2021-11-03 (118 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Try the command # turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15 ... Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 9.78 0.25 0.86 6.21 4.37 0.00 67.53 67.67 0.00 There is no SYS%LPI residency. Unplug ethernet, the residency become Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 8.63 0.13 0.07 22.56 1.24 0.00 53.95 54.08 53.82 + The ethernet controller is I219-LM. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1024-oem 5.14.0-1024.26 ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21 Uname: Linux 5.14.0-1024-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 2 05:24:51 2022 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200502-85+fossa-pidgeot+X92 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-pidgeot+X92 InstallationDate: Installed on 2021-11-03 (118 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: Try the command # turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15 ... Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 9.78 0.25 0.86 6.21 4.37 0.00 67.53 67.67 0.00 There is no SYS%LPI residency. Unplug ethernet, the residency become Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 8.63 0.13 0.07 22.56 1.24 0.00 53.95 54.08 53.82 The ethernet controller is I219-LM. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1024-oem 5.14.0-1024.26 ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21 Uname: Linux 5.14.0-1024-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 2 05:24:51 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-pidgeot+X92 InstallationDate: Installed on 2021-11-03 (118 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron:
[Kernel-packages] [Bug 1960430] Re: IPsec tunnel mode fix inner_ipproto setting in sec_path
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1960430 Title: IPsec tunnel mode fix inner_ipproto setting in sec_path Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) current code implementation did not handle the case where IPsec is used in tunnel mode. * Brief explanation of fixes As in case of IPsec tunnel mode the skb->encapsulation bit is not set in case of non-encapsulated packet (As TCP and UDP), then inner IP protocol won’t be set, change code behavior to do so also in case of IPsec Tunnel mode * How to test Need to make sure that the code compiles post this change, run TCP traffic when IPSec crypto offload with tunnel mode is configured * What it could break. NA, this function adds data to a new field introduced to struct xfrm_offload, so if not used it have no effect and it is assigned in stack and used in driver so if driver does not used it then no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1960430/+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 1962729] Re: No SYS%LPI residency after a suspend/resume when ethernet connected
*** This bug is a duplicate of bug 1962731 *** https://bugs.launchpad.net/bugs/1962731 ** This bug has been marked a duplicate of bug 1962731 No SYS%LPI residency after a suspend/resume when ethernet connected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962729 Title: No SYS%LPI residency after a suspend/resume when ethernet connected Status in linux-oem-5.14 package in Ubuntu: New Bug description: Try the command # turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15 ... Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 9.78 0.250.866.214.370.0067.53 67.67 0.00 There is no SYS%LPI residency. Unplug ethernet, the residency become Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 8.63 0.130.0722.56 1.240.0053.95 54.08 53.82 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1962729/+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 1962730] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1962730
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1962730
Title:
Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
Status in linux package in Ubuntu:
Incomplete
Bug description:
On a Dell T440 system the following crash is captured from reboot in
pstore. Although this example is not with the latest system BIOS it
does also happen with the latest (2.13.3). The upstream kernel tree
has reverted the patch applied for #1904225 in commit
9d3fcb28f9b9750b474811a2964ce022df56336e. The log message
specifically notes a problem with Dell R440 which is the rack mount
variation of the T440.
[ 9411.241947] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 9411.241948] {1}[Hardware Error]: event severity: fatal
[ 9411.241948] {1}[Hardware Error]: Error 0, type: fatal
[ 9411.241949] {1}[Hardware Error]: section_type: PCIe error
[ 9411.241949] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 9411.241949] {1}[Hardware Error]: version: 3.0
[ 9411.241950] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 9411.241950] {1}[Hardware Error]: device_id: :01:00.1
[ 9411.241950] {1}[Hardware Error]: slot: 1
[ 9411.241951] {1}[Hardware Error]: secondary_bus: 0x00
[ 9411.241951] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 9411.241951] {1}[Hardware Error]: class_code: 02
[ 9411.241952] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 9411.241952] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 9411.241953] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 9411.241953] Kernel panic - not syncing: Fatal hardware error!
[ 9411.241953] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: P OE
5.4.0-92-generic #103zynstra1
[ 9411.241954] Hardware name: Dell Inc. PowerEdge T440/00X7CK, BIOS 2.8.2
08/31/2020
[ 9411.241954] Call Trace:
[ 9411.241954] dump_stack+0x69/0x84
[ 9411.241955] panic+0x101/0x2e3
[ 9411.241955] __ghes_panic.part.0+0x2a/0x2a
[ 9411.241955] ghes_in_nmi_queue_one_entry.constprop.0.cold+0x5/0x16
[ 9411.241956] ghes_notify_nmi.part.0+0x3e/0xa0
[ 9411.241956] ghes_notify_nmi+0x26/0x30
[ 9411.241956] nmi_handle+0x62/0x120
[ 9411.241956] default_do_nmi+0x4c/0x130
[ 9411.241957] do_nmi.part.0+0x144/0x1a0
[ 9411.241957] do_nmi+0x34/0x40
[ 9411.241957] xennmi+0x1e/0x30
[ 9411.241958] RIP: e030:__acpi_release_global_lock+0x16/0x30
[ 9411.241958] Code: 83 fa 03 0f 95 c0 f7 d8 c3 66 66 2e 0f 1f 84 00 00 00 00
00 0f 1f 44 00 00 55 48 89 e5 8b 17 89 d1 89 d0 83 e1 fc f0 0f b1 0f <39> c2 75
ef 89 d0 5d 83 e0 01 c3 66 66 2e 0f 1f 84 00 00 00 00 00
[ 9411.241959] RSP: e02b:c90040083a98 EFLAGS: 0246
[ 9411.241960] RAX: 0002 RBX: 8890951677e0 RCX:
[ 9411.241960] RDX: 0002 RSI: 820c2160 RDI:
c90040007010
[ 9411.241960] RBP: c90040083a98 R08: R09:
88871d451e80
[ 9411.241961] R10: c90040083a40 R11: R12:
[ 9411.241961] R13: 8890865066c0 R14: 8890865068b8 R15:
0008
[ 9411.241961] acpi_ev_release_global_lock+0x93/0x128
[ 9411.241962] acpi_ex_release_mutex_object+0xb5/0xf9
[ 9411.241962] acpi_ex_release_global_lock+0x54/0x92
[ 9411.241962] acpi_ex_write_data_to_field+0x33a/0x36c
[ 9411.241963] acpi_ex_store_object_to_node+0x2ce/0x324
[ 9411.241963] acpi_ex_store+0xa3/0x273
[ 9411.241963] acpi_ex_opcode_1A_1T_1R+0x421/0x59a
[ 9411.241963] acpi_ds_exec_end_op+0x166/0x767
[ 9411.241964] acpi_ps_parse_loop+0x58a/0x660
[ 9411.241964] acpi_ps_parse_aml+0x1af/0x550
[ 9411.241964] acpi_ps_execute_method+0x208/0x2ca
[ 9411.241965] acpi_ns_evaluate+0x34e/0x4f0
[ 9411.241965] acpi_evaluate_object+0x18e/0x3b4
[ 9411.241965] acpi_enter_sleep_state_prep+0xb9/0x145
[ 9411.241965] acpi_power_off_prepare+0x35/0x50
[ 9411.241966] kernel_restart+0x4c/0x70
[ 9411.241966] __do_sys_reboot+0x1d1/0x210
[ 9411.241966] ? vfs_writev+0xce/0x100
[ 9411.241967] ? __audit_syscall_entry+0xdb/0x120
[ 9411.241967] ? syscall_trace_enter+0x1a5/0x290
[ 9411.241967] ?
[Kernel-packages] [Bug 1962730] [NEW] Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
Public bug reported:
On a Dell T440 system the following crash is captured from reboot in
pstore. Although this example is not with the latest system BIOS it
does also happen with the latest (2.13.3). The upstream kernel tree has
reverted the patch applied for #1904225 in commit
9d3fcb28f9b9750b474811a2964ce022df56336e. The log message specifically
notes a problem with Dell R440 which is the rack mount variation of the
T440.
[ 9411.241947] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 9411.241948] {1}[Hardware Error]: event severity: fatal
[ 9411.241948] {1}[Hardware Error]: Error 0, type: fatal
[ 9411.241949] {1}[Hardware Error]: section_type: PCIe error
[ 9411.241949] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 9411.241949] {1}[Hardware Error]: version: 3.0
[ 9411.241950] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 9411.241950] {1}[Hardware Error]: device_id: :01:00.1
[ 9411.241950] {1}[Hardware Error]: slot: 1
[ 9411.241951] {1}[Hardware Error]: secondary_bus: 0x00
[ 9411.241951] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 9411.241951] {1}[Hardware Error]: class_code: 02
[ 9411.241952] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 9411.241952] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 9411.241953] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 9411.241953] Kernel panic - not syncing: Fatal hardware error!
[ 9411.241953] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: P OE
5.4.0-92-generic #103zynstra1
[ 9411.241954] Hardware name: Dell Inc. PowerEdge T440/00X7CK, BIOS 2.8.2
08/31/2020
[ 9411.241954] Call Trace:
[ 9411.241954] dump_stack+0x69/0x84
[ 9411.241955] panic+0x101/0x2e3
[ 9411.241955] __ghes_panic.part.0+0x2a/0x2a
[ 9411.241955] ghes_in_nmi_queue_one_entry.constprop.0.cold+0x5/0x16
[ 9411.241956] ghes_notify_nmi.part.0+0x3e/0xa0
[ 9411.241956] ghes_notify_nmi+0x26/0x30
[ 9411.241956] nmi_handle+0x62/0x120
[ 9411.241956] default_do_nmi+0x4c/0x130
[ 9411.241957] do_nmi.part.0+0x144/0x1a0
[ 9411.241957] do_nmi+0x34/0x40
[ 9411.241957] xennmi+0x1e/0x30
[ 9411.241958] RIP: e030:__acpi_release_global_lock+0x16/0x30
[ 9411.241958] Code: 83 fa 03 0f 95 c0 f7 d8 c3 66 66 2e 0f 1f 84 00 00 00 00
00 0f 1f 44 00 00 55 48 89 e5 8b 17 89 d1 89 d0 83 e1 fc f0 0f b1 0f <39> c2 75
ef 89 d0 5d 83 e0 01 c3 66 66 2e 0f 1f 84 00 00 00 00 00
[ 9411.241959] RSP: e02b:c90040083a98 EFLAGS: 0246
[ 9411.241960] RAX: 0002 RBX: 8890951677e0 RCX:
[ 9411.241960] RDX: 0002 RSI: 820c2160 RDI: c90040007010
[ 9411.241960] RBP: c90040083a98 R08: R09: 88871d451e80
[ 9411.241961] R10: c90040083a40 R11: R12:
[ 9411.241961] R13: 8890865066c0 R14: 8890865068b8 R15: 0008
[ 9411.241961] acpi_ev_release_global_lock+0x93/0x128
[ 9411.241962] acpi_ex_release_mutex_object+0xb5/0xf9
[ 9411.241962] acpi_ex_release_global_lock+0x54/0x92
[ 9411.241962] acpi_ex_write_data_to_field+0x33a/0x36c
[ 9411.241963] acpi_ex_store_object_to_node+0x2ce/0x324
[ 9411.241963] acpi_ex_store+0xa3/0x273
[ 9411.241963] acpi_ex_opcode_1A_1T_1R+0x421/0x59a
[ 9411.241963] acpi_ds_exec_end_op+0x166/0x767
[ 9411.241964] acpi_ps_parse_loop+0x58a/0x660
[ 9411.241964] acpi_ps_parse_aml+0x1af/0x550
[ 9411.241964] acpi_ps_execute_method+0x208/0x2ca
[ 9411.241965] acpi_ns_evaluate+0x34e/0x4f0
[ 9411.241965] acpi_evaluate_object+0x18e/0x3b4
[ 9411.241965] acpi_enter_sleep_state_prep+0xb9/0x145
[ 9411.241965] acpi_power_off_prepare+0x35/0x50
[ 9411.241966] kernel_restart+0x4c/0x70
[ 9411.241966] __do_sys_reboot+0x1d1/0x210
[ 9411.241966] ? vfs_writev+0xce/0x100
[ 9411.241967] ? __audit_syscall_entry+0xdb/0x120
[ 9411.241967] ? syscall_trace_enter+0x1a5/0x290
[ 9411.241967] ? __audit_syscall_exit+0x25d/0x2c0
[ 9411.241967] __x64_sys_reboot+0x1e/0x20
[ 9411.241968] do_syscall_64+0x57/0x190
[ 9411.241968] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 9411.241968] RIP: 0033:0x7f5667c75487
[ 9411.241969] Code: 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90
f3 0f 1e fa 89 fa be 69 19 12 28 bf ad de e1 fe b8 a9 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 01 c3 48 8b 15 d9 29 0d 00 f7 d8 64 89 02 b8
[ 9411.241970] RSP: 002b:7fff00697cf8 EFLAGS: 0202 ORIG_RAX:
00a9
[ 9411.241970] RAX: ffda RBX: 0001 RCX: 7f5667c75487
[ 9411.241971] RDX: 01234567 RSI: 28121969 RDI: fee1dead
[ 9411.241971] RBP: 0001 R08: R09: 7fff00697100
[ 9411.241972] R10: 7f5666df1900 R11: 0202 R12: 0003
[ 9411.241972] R13: R14: 0001 R15:
[ 9411.242108] [ cut here ]
[ 9411.242109] WARNING: CPU: 0 PID: 1 at kernel/smp.c:433
[Kernel-packages] [Bug 1962729] [NEW] No SYS%LPI residency after a suspend/resume when ethernet connected
*** This bug is a duplicate of bug 1962731 *** https://bugs.launchpad.net/bugs/1962731 Public bug reported: Try the command # turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15 ... Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 9.780.250.866.214.370.0067.53 67.67 0.00 There is no SYS%LPI residency. Unplug ethernet, the residency become Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 8.630.130.0722.56 1.240.0053.95 54.08 53.82 ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Description changed: Try the command # turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15 ... Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 9.78 0.250.866.214.370.0067.53 67.67 0.00 There is no SYS%LPI residency. + Unplug ethernet, the residency become + + Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI + 8.63 0.130.0722.56 1.240.0053.95 54.08 53.82 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962729 Title: No SYS%LPI residency after a suspend/resume when ethernet connected Status in linux-oem-5.14 package in Ubuntu: New Bug description: Try the command # turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15 ... Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 9.78 0.250.866.214.370.0067.53 67.67 0.00 There is no SYS%LPI residency. Unplug ethernet, the residency become Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 8.63 0.130.0722.56 1.240.0053.95 54.08 53.82 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1962729/+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 1930921] Re: Apache 2.4.41 corrupts files from samba share
Looking into the Debian report it seems that this issue can be reproduced without apache2. Users have reported being able to reproduce with "Nextcloud PHP on nginx." I will set the apache2 part of this issue as incomplete for now because it does not seem to be the main cause. ** Changed in: apache2 (Ubuntu) Status: Confirmed => Incomplete -- 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/1930921 Title: Apache 2.4.41 corrupts files from samba share Status in apache2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in Debian: Unknown Bug description: Wenn I serve a samba share with apache 2.4.41 on Ubuntu 20.04 then some files have a corrupt header during transmission. It seems that the first few bytes of the headers are truncated and sometimes other bytes of the download are not belonging to the file. A workaround I found that works is to set "EnableMMAP Off" in the apache config. See other bug reports like this: https://serverfault.com/questions/1044724/apache2-sends-corrupt-responses-when-using-a-cifs-share https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 This is most probably not a bug in Ubuntu itself but I am reporting it here since I assume that a data corruption bug is seen as critical. I am also marking it as a security vulnerability since it seems that wrong parts of memory get exposed during file download. I don't know how random the exposed memory is and if it potentially could expose e.g. secrets. Please feel free to remove the security vulnerability flag if your assessment leads to a different conclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930921/+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 1950443] Re: Missing nvidia-driver-460 Transitional package for nvidia-driver-470
This bug was fixed in version 470.103.01-0ubuntu0.20.04.1 nvidia-graphics-drivers-470 (470.103.01-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1957790). * debian/templates/control.in, debian/templates/libnvidia-gl-flavour.install.in, debian/templates/libnvidia-gl-flavour.links.in: - Add build-dependency on libnvidia-egl-wayland1, and re-enable libnvidia-vulkan-producer (LP: #1935082). - Add the missing transitional packages for the 460 series. - Install the missing _nvngx.dll. -- Alberto Milone Fri, 28 Jan 2022 18:08:05 +0100 ** Changed in: nvidia-drivers-ubuntu Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1950443 Title: Missing nvidia-driver-460 Transitional package for nvidia-driver-470 Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Bug description: I cannot correctly upgrade from nvidia-driver-460 to nvidia-driver-470 because of missed nvidia-driver-460 Transitional package for nvidia-driver-470. The problem exists on Ubuntu 18.04 and 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1950443/+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 1962359] Re: Hibernation fails due to resource busy during swap file check
> Is the swap space big enough? A good point. This worked on previous versions on Ubuntu with swap (18GB) only 50% of RAM (32GB). I recreated my /swapfile with 38GB and the same issue persists. ie. $ free -m total ... Mem: 31964 Swap: 38911 > Furthermore, the hibernation failure isn't logged in the dmesg. That's correct. The machine just stalls with a blank screen. It's still awake as is apparent by motherboard lights. It cannot be awoken in any way and needs to cold restarted using power button. Curiously if I run smem before I attempt to hibernate, it does not show any processes using swap. ie $ smem --columns="swap" --no-header | tr -d " " | awk '$1 != 0' | wc -l 0 -- 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/1962359 Title: Hibernation fails due to resource busy during swap file check Status in linux package in Ubuntu: Confirmed Bug description: Hopefully, the automatically collected information is useful. The issue manifests when I try to hibernate the device. I see the following in the logs: ~$ journalctl --no-hostname -b -1 | tail -6 Feb 25 08:23:54 systemd[1]: nvidia-hibernate.service: Deactivated successfully. Feb 25 08:23:54 systemd[1]: Finished NVIDIA system hibernate actions. Feb 25 08:23:54 systemd[1]: Starting Hibernate... Feb 25 08:23:54 kernel: PM: Image not found (code -16) Feb 25 08:23:54 systemd-sleep[50360]: Entering sleep state 'hibernate'... Feb 25 08:23:54 kernel: PM: hibernation: hibernation entry I looked up error code 16 as EBUSY. This happens when using pm- hibernate or "systemctl hibernate". I played qaround with the nvidia systemd hibernate units but it didn't help. Hibernate used to work before I upgraded to jammy. I was on focal and bionic before that. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 09:27:29 2022 InstallationDate: Installed on 2019-08-07 (933 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220217.git6342082c-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962359/+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 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63
I expect this is https://github.com/bluez/bluez/issues/284 which Jeremy is going to propose the patch for. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63 Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() Hands-Free Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for
[Kernel-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63
Regarding comment #17 and missing devices from rfkill, there was just a miscommunication. I meant that the bluetooth line has not changed, and only pasted that one. But in both cases (before/after suspend), I do see all three lines as mentioned in #17. Sorry for the unnecessary confusion. I'm also attaching a full journalctl -b0 log. Then regarding https://github.com/bluez/bluez/issues/272 and https://github.com/bluez/bluez/issues/220, I do not have a systemd coredump so doesn't look like 272 directly. I could try to downgrade to bluez 5.61 and see if that fixes the issue (I expect it does since it was working fine till recently), but sounds like it's fixed in 5.64 so I'll test this older version if really necessary :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63 Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09
[Kernel-packages] [Bug 1962471] Re: iwlwifi fails after suspend (Failed to start RT ucode: -110)
Hi, this works, yes. Thanks! -- 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/1962471 Title: iwlwifi fails after suspend (Failed to start RT ucode: -110) Status in linux package in Ubuntu: Confirmed Bug description: See attachments. This is a regression from earlier kernel versions which worked fine, but I don't know at which point precisely it broke - with 5.15 perhaps? Laptop was running 24/7 mostly in the office, not a lot of suspend in there. It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have concrete product number) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jak7915 F wireplumber /dev/snd/seq:jak7907 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Mon Feb 28 13:44:03 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (1446 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220217.git6342082c-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET70W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962471/+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 1962578] Re: [UBUNTU 20.04] Fix SIGP processing on KVM/s390
** Summary changed: - [UBUNTU 20.04] Fix SIGP processing (KVM: s390) + [UBUNTU 20.04] Fix SIGP processing on KVM/s390 -- 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/1962578 Title: [UBUNTU 20.04] Fix SIGP processing on KVM/s390 Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Impish: New Bug description: Decription: KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. The patches to fix this have already been picked for jammy/master- next: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" For Ubuntu 20.04 the focal/master-next already contains: d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART so we additionally need the following two upstream commits in focal 67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state 8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1962578/+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 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63
** Summary changed: - Bluetooth headphones unable to connect after suspend + [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63 Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() Hands-Free Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Mar 01 00:47:09 fenrir
