bionic/linux-raspi2: 4.15.0-1099.105 snap-debs snap:pi-kernel
Bug #1949869 reported by
Stefan Bader
This bug report is a duplicate of:
Bug #1952048: bionic/linux-raspi2: 4.15.0-1099.106 snap-debs snap:pi-kernel.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kernel SRU Workflow |
Fix Released
|
Medium
|
Unassigned | ||
Snap-certification-testing |
Incomplete
|
Medium
|
Canonical Hardware Certification | ||
Snap-prepare |
Fix Released
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-beta |
Fix Released
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-candidate |
New
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-edge |
Fix Released
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-stable |
New
|
Medium
|
Canonical Kernel Team |
Bug Description
This bug will contain status and test results related to a kernel source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https:/
-- swm properties --
kernel-
phase: Certification Testing
phase-changed: Wednesday, 17. November 2021 12:56 UTC
reason:
snap-
snap-name: pi-kernel
variant: snap-debs
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-2021.11.08-1 |
description: | updated |
tags: | added: kernel-sru-derivative-of-1949870 |
Changed in kernel-sru-workflow: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in kernel-sru-workflow: | |
status: | Confirmed → Triaged |
summary: |
- bionic/linux-raspi2: <version to be filled> snap-debs + bionic/linux-raspi2: <version to be filled> snap-debs snap:pi-kernel |
description: | updated |
Changed in kernel-sru-workflow: | |
status: | Triaged → In Progress |
summary: |
- bionic/linux-raspi2: <version to be filled> snap-debs snap:pi-kernel + bionic/linux-raspi2: 4.15.0-1099.105 snap-debs snap:pi-kernel |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | removed: kernel-release-tracking-bug-live |
Changed in kernel-sru-workflow: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
It looks like the rpi3 devices where this kernel is tested on uc18 fail to find the bluetooth controller. the pi-bluetooth snap normally takes care of the uart settings, but failed to run it's setup properly after refreshing to this kernel: 17T22:07: 58Z pi-bluetooth. btuart[ 1422]: No controller attached 17T22:07: 58Z pi-bluetooth. btuart[ 1422]: Attaching Primary controller to /dev/ttyAMA0 17T22:07: 58Z systemd[1]: snap.pi- bluetooth. btuart. service: Main process exited, code=exited, status=1/FAILURE 17T22:07: 58Z systemd[1]: snap.pi- bluetooth. btuart. service: Failed with result 'exit-code'. 17T22:07: 58Z systemd[1]: snap.pi- bluetooth. btuart. service: Service hold-off time over, scheduling restart. 17T22:07: 58Z systemd[1]: snap.pi- bluetooth. btuart. service: Scheduled restart job, restart counter is at 5. 17T22:07: 58Z systemd[1]: Stopped Service for snap application pi-bluetooth. btuart. 17T22:07: 58Z systemd[1]: snap.pi- bluetooth. btuart. service: Start request repeated too quickly. 17T22:07: 58Z systemd[1]: snap.pi- bluetooth. btuart. service: Failed with result 'exit-code'. 17T22:07: 58Z systemd[1]: Failed to start Service for snap application pi-bluetooth. btuart.
ubuntu@localhost:~$ sudo snap logs pi-bluetooth
2021-11-
2021-11-
2021-11-
2021-11-
2021-11-
2021-11-
2021-11-
2021-11-
2021-11-
2021-11-
Reverting to the previous stable kernel made it work again, and refreshing again makes it fail again, so it seems pretty easily reproducible. I noticed that rfkill with the working kernel shows both hci0 and hci1 (even though only one of these is really valid), but only an hci0 is seen by rfkill after refreshing to this kernel.