bionic/linux-fde: 4.15.0-1033.36 snap-debs snap:interactive-strength-fs0001-kernel

Bug #2024219 reported by Thadeu Lima de Souza Cascardo
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Snap-certification-testing
Fix Released
Medium
Canonical Hardware Certification
Snap-prepare
Fix Released
Medium
Canonical Kernel Team
Snap-qa-testing
Fix Released
Medium
OEM Services QA
Snap-release-to-beta
Fix Released
Medium
Canonical Kernel Team
Snap-release-to-candidate
Fix Released
Medium
Canonical Kernel Team
Snap-release-to-edge
Fix Released
Medium
Canonical Kernel Team
Snap-release-to-stable
Fix Released
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://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
issue: KSRU-7808
kernel-stable-master-bug: 2024220
phase: Complete
phase-changed: Thursday, 29. June 2023 08:50 UTC
reason: {}
snap-name: interactive-strength-fs0001-kernel
variant: snap-debs
~~:
  clamps:
    parent: 4.15.0-1033.36
    self: 4.15.0-1033.36

tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2023.04.17-8
description: updated
tags: added: kernel-sru-derivative-of-2024220
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: Confirmed → Triaged
description: updated
summary: - bionic/linux-fde: <version to be filled> snap-debs
+ bionic/linux-fde: <version to be filled> snap-debs snap:interactive-
+ strength-fs0001-kernel
Changed in kernel-sru-workflow:
status: Triaged → In Progress
tags: added: kernel-jira-issue-ksru-7808
description: updated
description: updated
summary: - bionic/linux-fde: <version to be filled> snap-debs snap:interactive-
- strength-fs0001-kernel
+ bionic/linux-fde: 4.15.0-1033.36 snap-debs snap:interactive-strength-
+ fs0001-kernel
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Devices Certification Bot (ce-certification-qa) wrote :

Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/BTMeeW8Z/7431-interactive-strength-fs0001-kernel-4150-103336-35-latest

description: updated
description: updated
Revision history for this message
Kent Lin (kent-jclin) wrote :

Gsensor & Touchpanel test pass: https://certification.canonical.com/submissions/status/209500

Speaker test pass with following command:
sudo interactive-strength-pulseaudio.speaker-test -Dhw:CARD=Device -c 2

tags: added: qa-testing-passed
description: updated
description: updated
description: updated
Revision history for this message
Kent Lin (kent-jclin) wrote :

@All,

We need to revert the Kernel. I just found that WiFi is not loaded with this Kernel.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Workflow done!

All tasks have been completed and the bug is being closed

Changed in kernel-sru-workflow:
status: In Progress → Fix Committed
description: updated
description: updated
Revision history for this message
Stefan Bader (smb) wrote :

This is the bug opened by QA: https://bugs.launchpad.net/presidio/+bug/2025352 (System will auto reboot every 15 mins after update 4.15.0-1033.36 kernel snap from -candidate channel and wifi will not work).

Revision history for this message
Jesse Sung (wenchien) wrote :

WiFi is disabled in the NetworkManager by default. After enabling it with nmcli, WiFi seems to work w/o an issue.

Tried to roll back to an old kernel (rev 32) and I can see that it behaves the same. It looks more likely caused by NetworkManager than the kernel if it used to work with rev 32.

Revision history for this message
Kent Lin (kent-jclin) wrote :
Download full text (7.3 KiB)

ased on the below log from Network-Manager, WiFi is disabled by Network-Manager when LAN is connected.

forme@202011-28403:~$ snap logs network-manager -f
2023-07-04T02:01:00Z NetworkManager[2098]: <info> [1688436060.5988] policy: set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS
2023-07-04T02:01:00Z NetworkManager[2098]: <info> [1688436060.5995] device (eth0): Activation: successful, device activated.
2023-07-04T02:01:00Z NetworkManager[2098]: <info> [1688436060.6001] manager: NetworkManager state is now CONNECTED_GLOBAL
2023-07-04T02:01:01Z NetworkManager[2098]: <info> [1688436061.0763] manager: rfkill: WiFi hardware radio set disabled
2023-07-04T02:01:01Z NetworkManager[2098]: <info> [1688436061.0763] device (wlan0): state change: disconnected -> unavailable (reason 'none', sys-iface-state: 'managed')
2023-07-04T02:01:01Z NetworkManager[2098]: <info> [1688436061.0878] audit: op="radio-control" arg="wireless-enabled:0" pid=7918 uid=0 result="success"
2023-07-04T02:01:01Z NetworkManager[2098]: <info> [1688436061.0881] manager: rfkill: WiFi now disabled by radio killswitch
2023-07-04T02:32:35Z NetworkManager[2098]: <info> [1688437955.5605] device changed (path: /sys/devices/pci0000:00/0000:00:1d.0/0000:02:00.0/net/wlan0, iface: wlan0)
2023-07-04T02:32:35Z NetworkManager[2098]: <info> [1688437955.5673] device changed (path: /sys/devices/pci0000:00/0000:00:1f.6/net/eth0, iface: eth0)
2023-07-04T02:32:35Z NetworkManager[2098]: <info> [1688437955.7658] device changed (path: /sys/devices/virtual/net/lo, iface: lo)
2023-07-04T03:50:26Z NetworkManager[2098]: <info> [1688442626.0426] manager: rfkill: WiFi hardware radio set enabled
2023-07-04T03:50:26Z NetworkManager[2098]: <info> [1688442626.2498] audit: op="radio-control" arg="wireless-enabled:1" pid=9849 uid=0 result="success"
2023-07-04T03:50:26Z NetworkManager[2098]: <info> [1688442626.2500] manager: rfkill: WiFi now enabled by radio killswitch
2023-07-04T03:50:26Z NetworkManager[2098]: <info> [1688442626.2963] sup-iface[0x557634b25ac0,wlan0]: supports 5 scan SSIDs
2023-07-04T03:50:26Z NetworkManager[2098]: <info> [1688442626.2973] device (wlan0): supplicant interface state: starting -> ready
2023-07-04T03:50:26Z NetworkManager[2098]: <info> [1688442626.2974] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
2023-07-04T03:50:31Z NetworkManager[2098]: <info> [1688442631.1570] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2023-07-04T03:50:31Z NetworkManager[2098]: <info> [1688442631.1572] dhcp4 (eth0): canceled DHCP transaction
2023-07-04T03:50:31Z NetworkManager[2098]: <info> [1688442631.1572] dhcp4 (eth0): state changed bound -> done
2023-07-04T03:50:31Z NetworkManager[2098]: <info> [1688442631.1586] manager: NetworkManager state is now CONNECTED_SITE
2023-07-04T03:50:31Z NetworkManager[2098]: <info> [1688442631.1601] manager: NetworkManager state is now CONNECTED_LOCAL
2023-07-04T03:50:31Z NetworkManager[2098]: <info> [1688442631.1605] manager: NetworkManager state is now DISCONNECTED
2023-07-04T03:51:11Z NetworkManager[2098]: <info> [1688442671.52...

Read more...

Revision history for this message
Kent Lin (kent-jclin) wrote :
Download full text (6.9 KiB)

forme@202011-28402:~$ snap logs network-manager -f
2023-07-04T05:33:29Z NetworkManager[2330]: <info> [1688448809.4859] dhcp4 (eth0): address 10.102.162.121
2023-07-04T05:33:29Z NetworkManager[2330]: <info> [1688448809.4860] dhcp4 (eth0): plen 22
2023-07-04T05:33:29Z NetworkManager[2330]: <info> [1688448809.4860] dhcp4 (eth0): expires in 600 seconds
2023-07-04T05:33:29Z NetworkManager[2330]: <info> [1688448809.4861] dhcp4 (eth0): nameserver '10.102.160.2'
2023-07-04T05:33:29Z NetworkManager[2330]: <info> [1688448809.4861] dhcp4 (eth0): nameserver '10.102.160.1'
2023-07-04T05:33:29Z NetworkManager[2330]: <info> [1688448809.4861] dhcp4 (eth0): domain search 'maas'
2023-07-04T05:33:29Z NetworkManager[2330]: <info> [1688448809.4861] dhcp4 (eth0): domain name 'maas'
2023-07-04T05:33:29Z NetworkManager[2330]: <info> [1688448809.4862] dhcp4 (eth0): gateway 10.102.160.1
2023-07-04T05:33:29Z NetworkManager[2330]: <info> [1688448809.4862] dhcp4 (eth0): ntp server '10.102.160.2'
2023-07-04T05:33:29Z NetworkManager[2330]: <info> [1688448809.4877] dhcp4 (eth0): state changed bound -> bound
2023-07-04T05:38:32Z NetworkManager[2330]: <info> [1688449112.1993] manager: rfkill: WiFi hardware radio set enabled
2023-07-04T05:38:32Z NetworkManager[2330]: <info> [1688449112.4128] audit: op="radio-control" arg="wireless-enabled:1" pid=26845 uid=0 result="success"
2023-07-04T05:38:32Z NetworkManager[2330]: <info> [1688449112.4134] manager: rfkill: WiFi now enabled by radio killswitch
2023-07-04T05:38:32Z NetworkManager[2330]: <info> [1688449112.4761] sup-iface[0x557afea4f190,wlan0]: supports 5 scan SSIDs
2023-07-04T05:38:32Z NetworkManager[2330]: <info> [1688449112.4805] device (wlan0): supplicant interface state: starting -> ready
2023-07-04T05:38:32Z NetworkManager[2330]: <info> [1688449112.4806] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
2023-07-04T05:38:37Z NetworkManager[2330]: <info> [1688449117.2443] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2023-07-04T05:38:37Z NetworkManager[2330]: <info> [1688449117.2444] dhcp4 (eth0): canceled DHCP transaction
2023-07-04T05:38:37Z NetworkManager[2330]: <info> [1688449117.2444] dhcp4 (eth0): state changed bound -> done
2023-07-04T05:38:37Z NetworkManager[2330]: <info> [1688449117.2456] manager: NetworkManager state is now CONNECTED_SITE
2023-07-04T05:38:37Z NetworkManager[2330]: <info> [1688449117.2472] manager: NetworkManager state is now CONNECTED_LOCAL
2023-07-04T05:38:37Z NetworkManager[2330]: <info> [1688449117.2476] manager: NetworkManager state is now DISCONNECTED
2023-07-04T05:38:57Z NetworkManager[2330]: <info> [1688449137.4534] device (eth0): carrier: link connected
2023-07-04T05:38:57Z NetworkManager[2330]: <info> [1688449137.4540] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2023-07-04T05:38:57Z NetworkManager[2330]: <info> [1688449137.4555] policy: auto-activating connection 'Wired connection 1'
2023-07-04T05:38:57Z NetworkManager[2330]: <info> [1688449137.4579] device (eth0): Activation: starting connecti...

Read more...

Andy Whitcroft (apw)
description: updated
description: updated
Changed in kernel-sru-workflow:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.