[Kernel-packages] [Bug 1881159] Re: BUG: soft lockup on return from recover to run mode on rpi3a+
** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1881159 Title: BUG: soft lockup on return from recover to run mode on rpi3a+ Status in snapd: Invalid Status in linux-raspi package in Ubuntu: Fix Released Bug description: Image: core20 beta 20200527.5 (arm64) Device RPI3A+ === Steps to reproduce === 1. sudo snap install http 2. switch to recovery mode using: sudo http --pretty=format POST snapd:///v2/systems/$(ls /run/mnt/ubuntu-seed/systems/) action=do mode=recover 3. Once in recover mode, sudo snap install http 4. switch back to run mode: sudo http --pretty=format POST snapd:///v2/systems/$(ls /run/mnt/ubuntu-seed/systems/) action=do mode=run When I did this, the system never seems to fully return to run mode. I get errors about a soft lockup (see below) on the serial console after it reboots. However, if I pull the power at that point, and plug it back in, it does get back into run mode ## Info: input data size = 2 = 0x2 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 3 ms (1.5 MiB/s) ## Executing script at 0240 4096 bytes read in 5 ms (799.8 KiB/s) 4096 bytes read in 3 ms (1.3 MiB/s) 8378005 bytes read in 369 ms (21.7 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 18758066 bytes read in 819 ms (21.8 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 0260a065 Starting kernel ... [2.359758] spi-bcm2835 3f204000.spi: could not get clk: -517 [ 220.013319] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 248.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 276.013308] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 304.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 332.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 360.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 388.013314] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 416.013308] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 444.013309] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881159/+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 1881159] Re: BUG: soft lockup on return from recover to run mode on rpi3a+
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1881159 Title: BUG: soft lockup on return from recover to run mode on rpi3a+ Status in snapd: Invalid Status in linux-raspi package in Ubuntu: New Bug description: Image: core20 beta 20200527.5 (arm64) Device RPI3A+ === Steps to reproduce === 1. sudo snap install http 2. switch to recovery mode using: sudo http --pretty=format POST snapd:///v2/systems/$(ls /run/mnt/ubuntu-seed/systems/) action=do mode=recover 3. Once in recover mode, sudo snap install http 4. switch back to run mode: sudo http --pretty=format POST snapd:///v2/systems/$(ls /run/mnt/ubuntu-seed/systems/) action=do mode=run When I did this, the system never seems to fully return to run mode. I get errors about a soft lockup (see below) on the serial console after it reboots. However, if I pull the power at that point, and plug it back in, it does get back into run mode ## Info: input data size = 2 = 0x2 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 3 ms (1.5 MiB/s) ## Executing script at 0240 4096 bytes read in 5 ms (799.8 KiB/s) 4096 bytes read in 3 ms (1.3 MiB/s) 8378005 bytes read in 369 ms (21.7 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 18758066 bytes read in 819 ms (21.8 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 0260a065 Starting kernel ... [2.359758] spi-bcm2835 3f204000.spi: could not get clk: -517 [ 220.013319] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 248.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 276.013308] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 304.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 332.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 360.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 388.013314] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 416.013308] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 444.013309] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881159/+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
