jammy/linux-raspi: 5.15.0-1031.34 snap-debs snap:pi-kernel
Bug #2019414 reported by
Roxana Nicolescu
This bug report is a duplicate of:
Bug #2023060: jammy/linux-raspi: 5.15.0-1032.35 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 |
New
|
Medium
|
Canonical Hardware Certification | ||
| Snap-prepare |
New
|
Medium
|
Canonical Kernel Team | ||
| Snap-release-to-beta |
New
|
Medium
|
Canonical Kernel Team | ||
| Snap-release-to-candidate |
New
|
Medium
|
Canonical Kernel Team | ||
| Snap-release-to-edge |
New
|
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 --
issue: KSRU-7502
kernel-
phase: Certification Testing
phase-changed: Friday, 02. June 2023 13:36 UTC
reason:
snap-
snap-name: pi-kernel
variant: snap-debs
~~:
clamps:
parent: 5.15.0-1031.34
self: 5.15.0-1031.34
| tags: | added: kernel-release-tracking-bug-live |
| description: | updated |
| tags: | added: kernel-sru-cycle-2023.05.15-1 |
| description: | updated |
| tags: | added: kernel-sru-derivative-of-2019415 |
| Changed in kernel-sru-workflow: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in kernel-sru-workflow: | |
| status: | Confirmed → Triaged |
| description: | updated |
| summary: |
- jammy/linux-raspi: <version to be filled> snap-debs + jammy/linux-raspi: <version to be filled> snap-debs snap:pi-kernel |
| Changed in kernel-sru-workflow: | |
| status: | Triaged → In Progress |
| tags: | added: kernel-jira-issue-ksru-7502 |
| description: | updated |
| description: | updated |
| summary: |
- jammy/linux-raspi: <version to be filled> snap-debs snap:pi-kernel + jammy/linux-raspi: 5.15.0-1031.33 snap-debs snap:pi-kernel |
| description: | updated |
| summary: |
- jammy/linux-raspi: 5.15.0-1031.33 snap-debs snap:pi-kernel + jammy/linux-raspi: 5.15.0-1031.34 snap-debs snap:pi-kernel |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
Revision history for this message
| Paul Larson (pwlars) wrote | #1 |
| tags: | added: certification-testing-failed |
Revision history for this message
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Certification Testing FAILURE | #2 |
| description: | updated |
| Changed in kernel-sru-workflow: | |
| status: | In Progress → Fix Committed |
| Changed in kernel-sru-workflow: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think we might have a problem with this kernel on raspberry pi devices that have wifi. I noticed that the non-wifi devices like cm3 and rpi2 passed just fine, but for *every* device that has wifi (rpi4, rpi3, rpi400, cm4, etc), on both armhf and arm64, they all fail the bg, n, and ac wifi tests - but just when wpa is used, not for open APs.
That initially sounded more like an AP problem to me, so as a sanity test, I reverted the kernel snap to the one in stable (5.15.0-1030.32 r635) and it worked fine
As a second sanity test, I refreshed it again to the beta kernel, configured wifi to connect to one of the wpa APs, confirmed it failed. Then I reverted again to r635 without changing the config, and wifi worked immediately.
The tests we run gather some output from journalctl, etc. I've pasted a redacted version just in case it's useful:
https:/