| 2022-02-04 11:54:48 |
Gre0 |
bug |
|
|
added bug |
| 2022-02-04 12:01:25 |
Gre0 |
description |
With the current daily-build of 'jammy 22.04' it is not possible to enable bluetooth on (some) intel bluetooth devices.
My hardware: $ lsusb
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well.
https://bugzilla.redhat.com/show_bug.cgi?id=2027071
https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
For example on Fedora35 my Bluetooth did not initialize correctly between versions 5.14.18 > 5.15.14.
Kernel 5.15.15 changed that and since then everything went fine again.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848
I think the fix is mentioned there…
https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf194803c@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic-hwe-20.04 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
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 4 12:26:46 2022
InstallationDate: Installed on 2022-02-02 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201)
MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash
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: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F51d
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd. |
With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices.
My hardware: $ lsusb
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well.
https://bugzilla.redhat.com/show_bug.cgi?id=2027071
https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
For example on Fedora35 my Bluetooth did not initialize correctly
between versions 5.14.18 > 5.15.14.
Kernel 5.15.15 changed that and since then everything went fine again.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848
The fix is mentioned there…
https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf194803c@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94
Direct-Link to commit mentioned in the above discussion…
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic-hwe-20.04 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
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 4 12:26:46 2022
InstallationDate: Installed on 2022-02-02 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201)
MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash
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: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F51d
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd. |
|
| 2022-02-05 11:13:54 |
Gre0 |
tags |
amd64 apport-bug jammy wayland-session |
amd64 apport-bug jammy kernel-bug |
|
| 2022-02-05 11:14:36 |
Gre0 |
summary |
Bluetooth: hci0: command tx timeout |
Kernel 5.15 Bluetooth: hci0: command tx timeout |
|
| 2022-02-05 11:21:04 |
Gre0 |
summary |
Kernel 5.15 Bluetooth: hci0: command tx timeout |
| Kernel 5.15 Regression | ' Bluetooth: hci0: command tx timeout ' |
|
| 2022-02-05 11:29:07 |
Gre0 |
description |
With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices.
My hardware: $ lsusb
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well.
https://bugzilla.redhat.com/show_bug.cgi?id=2027071
https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
For example on Fedora35 my Bluetooth did not initialize correctly
between versions 5.14.18 > 5.15.14.
Kernel 5.15.15 changed that and since then everything went fine again.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848
The fix is mentioned there…
https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf194803c@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94
Direct-Link to commit mentioned in the above discussion…
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic-hwe-20.04 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
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 4 12:26:46 2022
InstallationDate: Installed on 2022-02-02 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201)
MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash
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: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F51d
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd. |
With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices.
My hardware: $ lsusb
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well.
https://bugzilla.redhat.com/show_bug.cgi?id=2027071
https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
For example on Fedora35 my Bluetooth did not initialize correctly
after warm boot between versions 5.14.18 > 5.15.14.
After a cold boot it worked. (shutdown and disconnect the DesktopPC from the power plug few seconds)
Kernel 5.15.15 changed that and since then everything went fine again.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848
The fix is mentioned there…
https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf194803c@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94
Direct-Link to commit mentioned in the above discussion…
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic-hwe-20.04 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
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 4 12:26:46 2022
InstallationDate: Installed on 2022-02-02 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201)
MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash
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: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F51d
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd. |
|
| 2022-02-05 11:32:04 |
Gre0 |
description |
With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices.
My hardware: $ lsusb
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well.
https://bugzilla.redhat.com/show_bug.cgi?id=2027071
https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
For example on Fedora35 my Bluetooth did not initialize correctly
after warm boot between versions 5.14.18 > 5.15.14.
After a cold boot it worked. (shutdown and disconnect the DesktopPC from the power plug few seconds)
Kernel 5.15.15 changed that and since then everything went fine again.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848
The fix is mentioned there…
https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf194803c@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94
Direct-Link to commit mentioned in the above discussion…
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic-hwe-20.04 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
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 4 12:26:46 2022
InstallationDate: Installed on 2022-02-02 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201)
MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash
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: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F51d
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd. |
With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices.
My hardware: $ lsusb
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well.
https://bugzilla.redhat.com/show_bug.cgi?id=2027071
https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
For example on Fedora35 my Bluetooth did not initialize correctly
after warm boot between versions 5.14.18 > 5.15.14.
After a cold boot it worked. (Turn off the desktop PC and disconnect it from power for a few seconds.)
Kernel 5.15.15 changed that and since then everything went fine again.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848
The fix is mentioned there…
https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf194803c@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94
Direct-Link to commit mentioned in the above discussion…
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic-hwe-20.04 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
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 4 12:26:46 2022
InstallationDate: Installed on 2022-02-02 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201)
MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash
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: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F51d
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd. |
|
| 2022-02-05 11:47:26 |
Gre0 |
description |
With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices.
My hardware: $ lsusb
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well.
https://bugzilla.redhat.com/show_bug.cgi?id=2027071
https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
For example on Fedora35 my Bluetooth did not initialize correctly
after warm boot between versions 5.14.18 > 5.15.14.
After a cold boot it worked. (Turn off the desktop PC and disconnect it from power for a few seconds.)
Kernel 5.15.15 changed that and since then everything went fine again.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848
The fix is mentioned there…
https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf194803c@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94
Direct-Link to commit mentioned in the above discussion…
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic-hwe-20.04 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
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 4 12:26:46 2022
InstallationDate: Installed on 2022-02-02 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201)
MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash
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: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F51d
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd. |
With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices after reboot/warm boot.
With a Cold boot it is working.
My hardware: $ lsusb
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well.
https://bugzilla.redhat.com/show_bug.cgi?id=2027071
https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
For example on Fedora35 my Bluetooth did not initialize correctly
after warm boot between versions 5.14.18 > 5.15.14.
After a cold boot it worked.
(Turned off the desktop PC and disconnected it from power for a few seconds.)
Kernel 5.15.15 changed that and since then everything went fine again.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848
The fix is mentioned there…
https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf194803c@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94
Direct-Link to commit mentioned in the above discussion…
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic-hwe-20.04 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
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 4 12:26:46 2022
InstallationDate: Installed on 2022-02-02 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201)
MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash
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: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F51d
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd. |
|
| 2022-02-09 01:05:19 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Confirmed |
|
| 2023-01-25 12:03:46 |
Andrey Kudinov |
bug watch added |
|
https://bugzilla.kernel.org/show_bug.cgi?id=215167 |
|
