[Kernel-packages] [Bug 2021930] Re: kdump cannot generate coredump file on bluefield with 5.4 and 5.15 kernel
Hi William, Do you mind providing the output info of this comment for both bf-2/5.4 and bf-3/5.15? cat /etc/mlnx-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2021930 Title: kdump cannot generate coredump file on bluefield with 5.4 and 5.15 kernel Status in linux-bluefield package in Ubuntu: New Bug description: kdump cannot generate coredump file on bluefield with 5.4 kernel Bug description: Following the instruction in https://ubuntu.com/server/docs/kernel-crash-dump, the coredump file cannot be generated. Bluefield is running 5.4 kernel bf2:~$ uname -a Linux sw-mtx-008-bf2 5.4.0-1060-bluefield #66-Ubuntu SMP PREEMPT Mon Mar 27 15:52:50 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux crashkernel parameter is configured bf2:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M bf2:~$ dmesg | grep -i crash [0.00] crashkernel reserved: 0xcfe0 - 0xefe0 (512 MB) [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M [8.070921] pstore: Using crash dump compression: deflate kdump-config is as below: bf2:~$ kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1060-bluefield kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1060-bluefield current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz sysrq: bf2:/# cat /proc/sys/kernel/sysrq 176 After trigged the crash manually with "echo c > /proc/sysrq-trigger", the system could not come up because of OOM. And after change the crashkernel with 1024M memory it still hangs. With default 512M, it hangs at "Killed process 674" [8.718188] systemd-journald[368]: File /var/log/journal/8244d38b2f804fc692f3f2dbf8206f57/system.journal corrupted or uncleanly shut down, renaming and re. [ 30.252513] Out of memory: Killed process 651 (systemd-resolve) total-vm:24380kB, anon-rss:3812kB, file-rss:1828kB, shmem-rss:0kB, UID:101 pgtables:80kB o0 ... [ 34.651927] Out of memory: Killed process 674 (dbus-daemon) total-vm:7884kB, anon-rss:552kB, file-rss:1380kB, shmem-rss:0kB, UID:103 pgtables:52kB oom_sco0 With 1024M, it hangs at following [8.733323] systemd-journald[369]: File /var/log/journal/8244d38b2f804fc692f3f2dbf8206f57/system.journal corrupted or uncleanly shut down, renaming and re. After soft reboot the Bluefield, there's no coredump file generated. bf2:~$ ls /var/crash/ -la total 52 drwxrwxrwt 3 root root4096 May 31 01:43 . drwxr-xr-x 14 root root4096 Apr 30 11:26 .. drwxrwxr-x 2 ubuntu ubuntu 4096 May 31 01:43 202305310143 -rw-r- 1 root root 34307 May 31 01:18 _usr_share_netplan_netplan.script.0.crash -rw-r--r-- 1 root root 0 May 31 03:47 kdump_lock -rw-r--r-- 1 root root 358 May 31 03:48 kexec_cmd bf2:~$ ls /var/crash/202305310143/ -la total 8 drwxrwxr-x 2 ubuntu ubuntu 4096 May 31 01:43 . drwxrwxrwt 3 root root 4096 May 31 01:43 .. This issue also happens on 5.4.0-1049-bluefield kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2021930/+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 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."
I upgraded our Mt. Jade AltraMax with the latest firmware from Ampere, and then I can't reproduce this issue with the latest Ubuntu Focal, HWE kernel, and the latest upgraded firmware in the previous step[1] after rebooting a Mt. Jade wih AltraMax more than 900 times. Setting the bug as Invalid on linux. [1] More details of version number HWE kernel 5.15.0-58-generic Firmware Revision 2.17.104000 SCP Revision 2.10.20221028 UEFI Revision 2.10.20221028 ** Changed in: linux (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990294 Title: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..." Status in grub2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: Kernel trace happens when bringing up CPU with focal HWE kernel 5.15.0-43-generic Steps to reproduce: enable earlycon and run reboot loop Expected result: system boots and ready to use Actual result: kerenl trace happens when bringing up CPU. See the call trace below[1]. [1] (copy from comment #7) [ 3.321372] arch_timer: Enabling local workaround for ARM erratum 1418040 [ 3.321394] CPU245: Booted secondary processor 0x0100310100 [0x413fd0c1] [ 8.536939] CPU246: failed to come online [ 8.550338] Detected PIPT I-cache on CPU246 [ 8.555817] CPU246: failed in unknown state : 0x0 [ 8.555987] GICv3: CPU246: found redistributor 10037 region 1:0x500100f0 [ 8.562727] [ cut here ] [ 8.562809] GICv3: CPU246: using allocated LPI pending table @0x08000268 [ 8.569364] Dying CPU not properly vacated! [ 16.668834] WARNING: CPU: 0 PID: 1 at kernel/sched/core.c:9215 sched_cpu_dying+0x1d0/0x2a0 [ 16.681496] Modules linked in: [ 16.684597] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.0-43-generic #46~20.04.1-Ubuntu [ 16.693010] pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 16.700095] pc : sched_cpu_dying+0x1d0/0x2a0 [ 16.704432] lr : sched_cpu_dying+0x1d0/0x2a0 [ 16.708770] sp : 8881bbe0 [ 16.712132] x29: 8881bbe0 x28: cca930eada80 x27: [ 16.719390] x26: 7395107ce000 x25: 00f6 x24: 403e40ed6728 [ 16.726651] x23: cca930eb2618 x22: x21: 00f6 [ 16.733907] x20: cca930719100 x19: 403e40ee7100 x18: 0014 [ 16.741165] x17: 3836323030303830 x16: 3030303078304020 x15: 656c62617420676e [ 16.748425] x14: 69646e6570204950 x13: 3030303038363230 x12: 3030383030303030 [ 16.755683] x11: 78304020656c6261 x10: 7420676e69646e65 x9 : cca92e7e39a0 [ 16.762940] x8 : 6c6c6120676e6973 x7 : 205d393038323635 x6 : c000fffe [ 16.770198] x5 : 0017ffe8 x4 : x3 : 8881b8c8 [ 16.777457] x2 : x1 : x0 : [ 16.784717] Call trace: [ 16.787197] sched_cpu_dying+0x1d0/0x2a0 [ 16.791182] cpuhp_invoke_callback+0x14c/0x5a8 [ 16.795699] cpuhp_invoke_callback_range+0x5c/0xb8 [ 16.800568] _cpu_up+0x234/0x360 [ 16.803844] cpu_up+0xb8/0x110 [ 16.806945] bringup_nonboot_cpus+0x7c/0xb0 [ 16.811195] smp_init+0x3c/0x98 [ 16.814385] kernel_init_freeable+0x1a4/0x39c [ 16.818813] kernel_init+0x2c/0x158 [ 16.822359] ret_from_fork+0x10/0x20 [ 16.825992] ---[ end trace bb9ca924bc23dd10 ]--- [ 16.830685] CPU246 enqueued tasks (0 total): [ 16.835356] [ cut here ] [ 16.835431] GICv3: CPU246: found redistributor 10037 region 1:0x500100f0 [ 16.840045] Dying CPU not properly vacated! [ 16.847925] WARNING: CPU: 0 PID: 1 at kernel/sched/core.c:9215 sched_cpu_dying+0x1d0/0x2a == Original Description == When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no output appeared on the console after the EFI stub: Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint A0 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint AD EFI stub: Booting Linux Kernel... EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+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 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."
I updated the bug description to make it clear. Besides, I marked grub as invalid because at this moment it looks like a kernel issue according to the log and the reproducer. ** Changed in: grub2 (Ubuntu) Status: New => Invalid ** Description changed: - When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no - output appeared on the console after the EFI stub: + Kernel trace happens when bringing up CPU with focal HWE kernel + 5.15.0-43-generic + + Steps to reproduce: enable earlycon and run reboot loop + Expected result: system boots and ready to use + Actual result: kerenl trace happens when bringing up CPU. See the call trace below[1]. + + + [1] (copy from comment #7) + + [ 3.321372] arch_timer: Enabling local workaround for ARM erratum 1418040 + [ 3.321394] CPU245: Booted secondary processor 0x0100310100 [0x413fd0c1] + [ 8.536939] CPU246: failed to come online + [ 8.550338] Detected PIPT I-cache on CPU246 + [ 8.555817] CPU246: failed in unknown state : 0x0 + [ 8.555987] GICv3: CPU246: found redistributor 10037 region 1:0x500100f0 + [ 8.562727] [ cut here ] + [ 8.562809] GICv3: CPU246: using allocated LPI pending table @0x08000268 + [ 8.569364] Dying CPU not properly vacated! + [ 16.668834] WARNING: CPU: 0 PID: 1 at kernel/sched/core.c:9215 sched_cpu_dying+0x1d0/0x2a0 + [ 16.681496] Modules linked in: + [ 16.684597] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.0-43-generic #46~20.04.1-Ubuntu + [ 16.693010] pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) + [ 16.700095] pc : sched_cpu_dying+0x1d0/0x2a0 + [ 16.704432] lr : sched_cpu_dying+0x1d0/0x2a0 + [ 16.708770] sp : 8881bbe0 + [ 16.712132] x29: 8881bbe0 x28: cca930eada80 x27: + [ 16.719390] x26: 7395107ce000 x25: 00f6 x24: 403e40ed6728 + [ 16.726651] x23: cca930eb2618 x22: x21: 00f6 + [ 16.733907] x20: cca930719100 x19: 403e40ee7100 x18: 0014 + [ 16.741165] x17: 3836323030303830 x16: 3030303078304020 x15: 656c62617420676e + [ 16.748425] x14: 69646e6570204950 x13: 3030303038363230 x12: 3030383030303030 + [ 16.755683] x11: 78304020656c6261 x10: 7420676e69646e65 x9 : cca92e7e39a0 + [ 16.762940] x8 : 6c6c6120676e6973 x7 : 205d393038323635 x6 : c000fffe + [ 16.770198] x5 : 0017ffe8 x4 : x3 : 8881b8c8 + [ 16.777457] x2 : x1 : x0 : + [ 16.784717] Call trace: + [ 16.787197] sched_cpu_dying+0x1d0/0x2a0 + [ 16.791182] cpuhp_invoke_callback+0x14c/0x5a8 + [ 16.795699] cpuhp_invoke_callback_range+0x5c/0xb8 + [ 16.800568] _cpu_up+0x234/0x360 + [ 16.803844] cpu_up+0xb8/0x110 + [ 16.806945] bringup_nonboot_cpus+0x7c/0xb0 + [ 16.811195] smp_init+0x3c/0x98 + [ 16.814385] kernel_init_freeable+0x1a4/0x39c + [ 16.818813] kernel_init+0x2c/0x158 + [ 16.822359] ret_from_fork+0x10/0x20 + [ 16.825992] ---[ end trace bb9ca924bc23dd10 ]--- + [ 16.830685] CPU246 enqueued tasks (0 total): + [ 16.835356] [ cut here ] + [ 16.835431] GICv3: CPU246: found redistributor 10037 region 1:0x500100f0 + [ 16.840045] Dying CPU not properly vacated! + [ 16.847925] WARNING: CPU: 0 PID: 1 at kernel/sched/core.c:9215 sched_cpu_dying+0x1d0/0x2a + + + == Original Description == + + + When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no output appeared on the console after the EFI stub: Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint A0 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint AD EFI stub: Booting Linux Kernel... EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990294 Title: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..." Status in grub2 package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Bug description: Kernel trace happens when bringing up CPU with focal HWE kernel 5.15.0-43-generic Steps to reproduce: enable earlycon and run reboot loop Expected result: system boots and ready to use Actual result: kerenl trace happens when bringing up CPU. See the call trace below[1]. [1] (copy from comment #7) [ 3.321372] arch_timer: Enabling local workaround for ARM erratum 1418040 [ 3.321394] CPU245: Booted secondary processor 0x0100310100 [0x413fd0c1] [ 8.536939] CPU246: failed to come online [ 8.550338] Detected PIPT I-cache on CPU246 [ 8.555817] CPU246: failed in unknown state : 0x0 [ 8.555987] GICv3: CPU246: found redistributor 10037 region 1:0x500100f0 [ 8.5
[Kernel-packages] [Bug 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."
Similar to comment #6. Here is the log of another Mt. Jade with AltraMax reproducing this issue with Ubuntu kernel. [8.308100] [ cut here ]^M [8.308185] GICv3: CPU248: using allocated LPI pending table @0x0800026a^M [8.314742] Dying CPU not properly vacated!^M [ 16.480898] WARNING: CPU: 0 PID: 1 at kernel/sched/core.c:9215 sched_cpu_dying+0x1d0/0x2a0^M [ 16.493557] Modules linked in:^M [ 16.496658] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.0-43-generic #46~20.04.1-Ubuntu^M [ 16.505065] pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)^M [ 16.512146] pc : sched_cpu_dying+0x1d0/0x2a0^M [ 16.516483] lr : sched_cpu_dying+0x1d0/0x2a0^M [ 16.520822] sp : 8881bbe0^M [ 16.524187] x29: 8881bbe0 x28: c747c462da80 x27: ^M [ 16.531443] x26: 78f67d08a000 x25: 00f8 x24: 403e40f12728^M [ 16.538703] x23: c747c4632618 x22: x21: 00f8^M [ 16.545961] x20: c747c3e99100 x19: 403e40f23100 x18: 0014^M [ 16.553222] x17: 6136323030303830 x16: 3030303078304020 x15: 656c62617420676e^M [ 16.560480] x14: 69646e6570204950 x13: 3030303061363230 x12: 3030383030303030^M [ 16.567738] x11: 78304020656c6261 x10: 7420676e69646e65 x9 : c747c1f639a0^M [ 16.574995] x8 : 6c6c6120676e6973 x7 : 205d353831383033 x6 : c000fffe^M [ 16.582255] x5 : 0017ffe8 x4 : x3 : 8881b8c8^M [ 16.589512] x2 : x1 : x0 : ^M [ 16.596772] Call trace:^M [ 16.599252] sched_cpu_dying+0x1d0/0x2a0^M [ 16.603238] cpuhp_invoke_callback+0x14c/0x5a8^M [ 16.607757] cpuhp_invoke_callback_range+0x5c/0xb8^M [ 16.612627] _cpu_up+0x234/0x360^M [ 16.615904] cpu_up+0xb8/0x110^M [ 16.619003] bringup_nonboot_cpus+0x7c/0xb0^M [ 16.623254] smp_init+0x3c/0x98^M [ 16.626444] kernel_init_freeable+0x1a4/0x39c^M [ 16.630871] kernel_init+0x2c/0x158^M [ 16.634415] ret_from_fork+0x10/0x20^M [ 16.638046] ---[ end trace b4903e61a7ade0b4 ]---^M [ 16.642739] CPU248 enqueued tasks (0 total):^M ** Attachment added: "kopter.log" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+attachment/5640544/+files/kopter.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990294 Title: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..." Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: In Progress Bug description: When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no output appeared on the console after the EFI stub: Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint A0 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint AD EFI stub: Booting Linux Kernel... EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+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 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."
Kernel panic message snippet from the log attachment papat-221211-reboot_mainline-6.0.9-060009-generic_kernel-panic.log: [ 835.504178] [ cut here ] [ 835.504183] kernel BUG at kernel/irq_work.c:235! [ 835.504184] Internal error: Oops - BUG: 0 [#1] SMP [ 835.504186] Modules linked in: [ 835.504187] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GWL 6.0.9-060009-generic #202211161102 [ 835.504189] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 835.504190] pc : irq_work_run_list+0x98/0xa0 [ 835.504194] lr : irq_work_run+0x2c/0x60 [ 835.504196] sp : 8883bc60 [ 835.504197] x29: 8883bc60 x28: 403e40bca798 x27: [ 835.504200] x26: 78e12694f000 x25: x24: [ 835.504202] x23: c75d180f48d4 x22: 02e9 x21: c75d1a27b798 [ 835.504205] x20: 0095 x19: c75d1a287ff0 x18: 8881b050 [ 835.504207] x17: x16: x15: 6765722030303030 [ 835.504209] x14: 0001 x13: 3a296c61746f7420 x12: 302820736b736174 [ 835.504212] x11: x10: x9 : c75d180f48f4 [ 835.504214] x8 : x7 : x6 : [ 835.504217] x5 : x4 : x3 : [ 835.504219] x2 : x1 : x0 : 083e7f10eff8 [ 835.504221] Call trace: [ 835.504222] irq_work_run_list+0x98/0xa0 [ 835.504224] smpcfd_dying_cpu+0x24/0x40 [ 835.504227] cpuhp_invoke_callback+0x230/0x610 [ 835.504229] cpuhp_invoke_callback_range+0xe4/0x11c [ 835.504231] _cpu_up+0x1f4/0x294 [ 835.504233] cpu_up+0xd0/0x13c [ 835.504234] bringup_nonboot_cpus+0x98/0xdc [ 835.504236] smp_init+0x40/0xb8 [ 835.504237] kernel_init_freeable+0x144/0x1c8 [ 835.504240] kernel_init+0x3c/0x180 [ 835.504241] ret_from_fork+0x10/0x20 [ 835.504244] Code: d282 d2800010 d2800011 d65f03c0 (d421) [ 835.504249] ---[ end trace ]--- [ 835.504250] note: swapper/0[1] exited with preempt_count 1 [ 835.504435] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [ 835.504437] SMP: stopping secondary CPUs [ 835.506210] x6 : [ 835.506213] x5 : x4 : x3 : [ 835.506216] x2 : x1 : x0 : 00e0 [ 835.506218] Call trace: [ 835.506219] arch_cpu_idle+0x1c/0x60 [ 835.506221] default_idle_call+0x78/0x1f0 [ 835.506223] cpuidle_idle_call+0x198/0x200 [ 835.506225] do_idle+0xb8/0x120 [ 835.506227] cpu_startup_entry+0x30/0x40 [ 835.506229] secondary_start_kernel+0xf4/0x14c [ 835.506231] __secondary_switched+0xb4/0xb8 [ 835.514617] Call trace: [ 835.518072] arch_cpu_idle+0x1c/0x60 [ 835.525418] default_idle_call+0x78/0x1f0 [ 835.528518] cpuidle_idle_call+0x198/0x200 [ 835.538432] do_idle+0xb8/0x120 [ 835.545516] cpu_startup_entry+0x30/0x40 [ 835.549499] secondary_start_kernel+0xf4/0x14c [ 835.553486] __secondary_switched+0xb4/0xb8 [ 836.948113] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990294 Title: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..." Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: In Progress Bug description: When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no output appeared on the console after the EFI stub: Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint A0 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint AD EFI stub: Booting Linux Kernel... EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+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 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."
I rebooted the system with mainline kernel v6.0.9, and I can similar kernel panic at 302th reboot. See the log attachment papat-221211-reboot_mainline-6.0.9-060009-generic_kernel-panic.log for the kernel panic message. ** Attachment added: "papat-221211-reboot_mainline-6.0.9-060009-generic_kernel-panic.log" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+attachment/5635393/+files/papat-221211-reboot_mainline-6.0.9-060009-generic_kernel-panic.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990294 Title: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..." Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: In Progress Bug description: When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no output appeared on the console after the EFI stub: Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint A0 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint AD EFI stub: Booting Linux Kernel... EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+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 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."
I will process mainline kernel testing. ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990294 Title: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..." Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: In Progress Bug description: When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no output appeared on the console after the EFI stub: Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint A0 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint AD EFI stub: Booting Linux Kernel... EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
The jammy RC (20220418.2) looks good for Ampere Mt. Jade Altra (bizzy). I can pxe install the server successfully. By the way autoinstall of subiquity also works like a charm. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Invalid Status in grub2 source package in Jammy: Fix Released Status in grub2-signed source package in Jammy: Fix Released Status in linux source package in Jammy: Invalid Status in subiquity source package in Jammy: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
Since it seems a grub issue, I reported the issue to qatracker of daily build to make the release team aware of this issue, and hopefully the information will be helpful before releasing RC. http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/246802/testcases/1697/results -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in grub2-unsigned package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+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 1967957] Re: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD
A production taishan2280v2 works with 220405 daily build[1].
We may not need to worry that much with the failure of d06-1 and d06-3
now.
[1]
ubuntu@scobee-jammy-daily-220405:~$ cat /var/log/installer/media-info ; echo ;
uname -a; lsb_release -a; ping -c 4 8.8.8.8; sudo apt update
Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily arm64 (20220405)
Linux scobee-jammy-daily-220405 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30
15:57:31 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
Codename: jammy
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3059ms
[sudo] password for ubuntu:
Hit:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease
Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
Status in linux package in Ubuntu:
Incomplete
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab, which are NOT
production product)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+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 1967957] Re: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD
daily iso (220405) tested on d06 (d06-1)
= log snippet =
Loading the CD via virtual media and drop to the prompt asking "Attempt
interactive netboot from a URL?"
NOTICE: ERR_ADDRL = 0x0
NOTICE: ERR_ADDRH = 0x0
NOTICE: ERR_MISC0L = 0x0
NOTICE: ERR_MISC0H = 0x0
NOTICE: ERR_MISC1L = 0x0
NOTICE: ERR_MISC1H = 0x2ea6f418
NOTICE: [TotemRasIntOemNodeEri]:[1750L]
NOTICE: [RasEriInterrupt]:[117L]NodeTYP2Status = 0x0
ERROR: [FiqInterruptHandler]:[114L] GicInterrupt1 : 0x1cd!!!
[2.400045] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret:
-12
[2.418203] ACPI: IORT: [Firmware Bug]: [map (ptrval)] conflicting
mapping for input ID 0x7c00
[2.427513] ACPI: IORT: [Firmware Bug]: applying workaround.
[2.433174] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret:
-12
[2.441255] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret:
-12
[2.457200] ACPI: IORT: [Firmware Bug]: [map (ptrval)] conflicting
mapping for input ID 0xbc00
[2.466504] ACPI: IORT: [Firmware Bug]: applying workaround.
[5.854360] hisi_sas_v3_hw :74:02.0: 16 hw queues
[5.863968] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret:
-12
[ 19.993752] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret:
-12
mount: mounting /dev/sr0 on /cdrom failed: No such device or address
Unable to find a medium containing a live file system
Attempt interactive netboot from a URL?
yes no (default yes):
Two methods available for IP configuration:
* static: for static IP configuration
* dhcp: for automatic IP configuration
static dhcp (default 'dhcp'):
** Attachment added: "d06-1-vcd-220407-01.log"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1967957/+attachment/5577933/+files/d06-1-vcd-220407-01.log
** Description changed:
= Description =
- Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
+ Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab, which are NOT
production product)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
Status in linux package in Ubuntu:
Incomplete
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab, which are NOT
production product)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
** Summary changed: - jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot + jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Incomplete Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967957] Re: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD
Additional info: in our lab, a taishan2280v2 could install the 220330
iso. (tested by ike)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
Status in linux package in Ubuntu:
Incomplete
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+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 1967961] Re: jammy failed to deploy to Hisilicon D06 with MAAS
In our lab, a production level taishan2280v2 (scobee) and x6000 (saenger) could be deployed by MAAS successfully. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab) Image: Jammy = Steps to Reproduce = 1. Deploy the system with MAAS webUI 2. Wait until everything is ready = Expected Results = After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use. = Actual Results = The system is never ready to be at the login prompt stage, and MAAS deployment timeouts. The console log of the system (see the attachment d06-1.log for the full log): [ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds. [ 366.412566] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds. [ 366.412833] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ** 2167 printk messages dropped ** [ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0] [ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0] [ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0] [ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0] [ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0] [ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0] [*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start [**] (6 of 7) A start job is running for…d Directories (6min 4s / no limit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+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 1967961] Re: jammy failed to deploy to Hisilicon D06 with MAAS
d06-3-maas-220406-02.log is the console log for maas deployment timeout with d06-3. ** Attachment added: "d06-3-maas-220406-02.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+attachment/5577604/+files/d06-3-maas-220406-02.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab) Image: Jammy = Steps to Reproduce = 1. Deploy the system with MAAS webUI 2. Wait until everything is ready = Expected Results = After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use. = Actual Results = The system is never ready to be at the login prompt stage, and MAAS deployment timeouts. The console log of the system (see the attachment d06-1.log for the full log): [ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds. [ 366.412566] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds. [ 366.412833] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ** 2167 printk messages dropped ** [ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0] [ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0] [ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0] [ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0] [ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0] [ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0] [*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start [**] (6 of 7) A start job is running for…d Directories (6min 4s / no limit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+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 1967957] Re: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD
Next from my side: there are new daily build. I may try them as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
Status in linux package in Ubuntu:
Incomplete
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+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 1967957] Re: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD
Redo with d06 (d06-1). This time we have the log of kernel trace. See
d06-1-cd-220406-01.log for the full console log.
[ 652.568681] pstate: 004000c9 (nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 652.575630] pc : irq_work_queue_on+0xa4/0xb0
[ 652.579888] lr : rcu_implicit_dynticks_qs+0x1b8/0x350
[ 652.584928] sp : 8b223c50
[ 652.588229] x29: 8b223c50 x28: 8aa30e00 x27:
[ 652.595354] x26: 003f7fb44025 x25: 0019 x24: 8aa30e00
[ 652.602478] x23: 803f759d9000 x22: 8a906000 x21: 8a16b025
[ 652.609602] x20: x19: 003f7fb43f00 x18: 0102
[ 652.616727] x17: 3330643830383030 x16: 30303820 x15: 3a20307820303030
[ 652.623850] x14: 8a94b760 x13: 8a94b1e8 x12: 0002
[ 652.630974] x11: x10: 0b50 x9 : 882158e4
[ 652.638097] x8 : 002084b42b30 x7 : x6 : 003f7fb44058
[ 652.645221] x5 : x4 : x3 : 003f7fb43140
[ 652.652344] x2 : x1 : 8a90da28 x0 : 0004
[ 652.659469] Call trace:
[ 652.661903] irq_work_queue_on+0xa4/0xb0
[ 652.665813] rcu_implicit_dynticks_qs+0x1b8/0x350
[ 652.670504] force_qs_rnp+0x184/0x340
[ 652.674154] rcu_gp_fqs_loop+0x224/0x394
[ 652.678064] rcu_gp_kthread+0x120/0x164
[ 652.681888] kthread+0x114/0x120
[ 652.685105] ret_from_fork+0x10/0x20
[ 652.688669] ---[ end trace da56ec070b45e740 ]---
** Attachment added: "d06-1-cd-220406-01.log"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1967957/+attachment/5577595/+files/d06-1-cd-220406-01.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
Status in linux package in Ubuntu:
Incomplete
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+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 1967562] Re: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot
log snippet from the attachment "bizzy-maas-220406-01.log" of comment#8 [1.354637] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu [1.362195] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26 [1.374876] Call trace: [1.377310] dump_backtrace+0x0/0x1ec [1.380968] show_stack+0x24/0x30 [1.384272] dump_stack_lvl+0x68/0x84 [1.387929] dump_stack+0x18/0x34 [1.391232] panic+0x18c/0x39c [1.394275] mount_block_root+0x160/0x210 [1.398281] mount_root+0x12c/0x14c [1.401757] prepare_namespace+0x140/0x1a0 [1.405842] kernel_init_freeable+0x1c8/0x214 [1.410187] kernel_init+0x30/0x160 [1.413667] ret_from_fork+0x10/0x20 [1.417235] SMP: stopping secondary CPUs [1.421957] Kernel Offset: 0x34a8864c from 0x8800 [1.428038] PHYS_OFFSET: 0x8000 [1.431514] CPU features: 0x85c1,a3302e42 [1.435859] Memory Limit: none [1.438905] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Incomplete Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot
Redo with the same iso but different downloading url: http://cdimage.ubuntu.com/releases/22.04/beta/ubuntu-22.04-beta-live- server-arm64.iso I can still reproduce the issue. The grub entry looks good (no duplicate ---)[1]. The attachment bizzy-maas-220406-01.log is the corresponding console log. setparams 'Ubuntu Server' set gfxpayload=keep linux/casper/vmlinuz quiet root=/dev/ram0 ramdisk_size=150 ip=dhcp url=http://cdimage.ubuntu.com/releases/22.04/beta/ubuntu-22.04-beta-live-server-arm64.iso autoinstall "ds=nocloud-net;s=http://10.229.56.0/"; --- initrd/casper/initrd ** Attachment added: "bizzy-maas-220406-01.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+attachment/5577564/+files/bizzy-maas-220406-01.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Incomplete Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967961] Re: jammy failed to deploy to Hisilicon D06 with MAAS
Tried to deploy d06-3 with jammy again today. I was dropped to the root username after the ephemeral environment installation reboot[1]. See the attachment "d06-3-maas-220406-01.log" for the full console log. [1] [ OK ] Finished Availability of block devices. root@d06-3:~# root@d06-3:~# ** Attachment added: "d06-3-maas-220406-01.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+attachment/5577537/+files/d06-3-maas-220406-01.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab) Image: Jammy = Steps to Reproduce = 1. Deploy the system with MAAS webUI 2. Wait until everything is ready = Expected Results = After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use. = Actual Results = The system is never ready to be at the login prompt stage, and MAAS deployment timeouts. The console log of the system (see the attachment d06-1.log for the full log): [ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds. [ 366.412566] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds. [ 366.412833] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ** 2167 printk messages dropped ** [ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0] [ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0] [ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0] [ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0] [ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0] [ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0] [*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start [**] (6 of 7) A start job is running for…d Directories (6min 4s / no limit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+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 1967562] Re: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot
** Summary changed: - jammy beta (220330) live server arm64 iso kernel panic during pxe boot + jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Incomplete Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967957] Re: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD
** Summary changed:
- jammy beta (220330) live server arm64 iso failed to boot with virtual CD
+ jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with
virtual CD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
Status in linux package in Ubuntu:
Incomplete
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+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 1967961] Re: jammy beta (220330) live server arm64 iso failed to deploy with MAAS
Please note focal and impish deployment of MAAS do not reproduce this issue. ** Summary changed: - jammy beta (220330) live server arm64 iso failed to deploy with MAAS + jammy failed to deploy with MAAS ** Description changed: = Description = Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab) - Image: Jammy Beta (220330) + Image: Jammy = Steps to Reproduce = 1. Deploy the system with MAAS webUI 2. Wait until everything is ready = Expected Results = After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use. = Actual Results = The system is never ready to be at the login prompt stage, and MAAS deployment timeouts. The console log of the system (see the attachment d06-1.log for the full log): [ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds. [ 366.412566] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds. [ 366.412833] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ** 2167 printk messages dropped ** [ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0] [ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0] [ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0] [ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0] [ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0] [ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0] [*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start [**] (6 of 7) A start job is running for…d Directories (6min 4s / no limit) ** Summary changed: - jammy failed to deploy with MAAS + jammy failed to deploy to d06 with MAAS ** Summary changed: - jammy failed to deploy to d06 with MAAS + jammy failed to deploy to Hisilicon D06 with MAAS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS Status in linux package in Ubuntu: New Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab) Image: Jammy = Steps to Reproduce = 1. Deploy the system with MAAS webUI 2. Wait until everything is ready = Expected Results = After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use. = Actual Results = The system is never ready to be at the login prompt stage, and MAAS deployment timeouts. The console log of the system (see the attachment d06-1.log for the full log): [ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds. [ 366.412566] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds. [ 366.412833] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ** 2167 printk messages dropped ** [ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0] [ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0] [ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0] [ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0] [ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0] [ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0] [*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start [**] (6 of 7) A start job is running for…d Directories (6min 4s / no limit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+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 1967961] [NEW] jammy failed to deploy to Hisilicon D06 with MAAS
Public bug reported: = Description = Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab) Image: Jammy = Steps to Reproduce = 1. Deploy the system with MAAS webUI 2. Wait until everything is ready = Expected Results = After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use. = Actual Results = The system is never ready to be at the login prompt stage, and MAAS deployment timeouts. The console log of the system (see the attachment d06-1.log for the full log): [ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds. [ 366.412566] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds. [ 366.412833] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ** 2167 printk messages dropped ** [ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0] [ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0] [ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0] [ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0] [ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0] [ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0] [*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start [**] (6 of 7) A start job is running for…d Directories (6min 4s / no limit) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "d06-1.log" https://bugs.launchpad.net/bugs/1967961/+attachment/5577401/+files/d06-1.log ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS Status in linux package in Ubuntu: New Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab) Image: Jammy = Steps to Reproduce = 1. Deploy the system with MAAS webUI 2. Wait until everything is ready = Expected Results = After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use. = Actual Results = The system is never ready to be at the login prompt stage, and MAAS deployment timeouts. The console log of the system (see the attachment d06-1.log for the full log): [ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds. [ 366.412566] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds. [ 366.412833] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ** 2167 printk messages dropped ** [ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0] [ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0] [ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0] [ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0] [ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0] [ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0] [*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start [**] (6 of 7) A start job is running for…d Directories (6min 4s / no limit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+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 1967957] Re: jammy beta (220330) live server arm64 iso failed to boot with virtual CD
Similar log from d06 (d06-3), but enabling kernel parameter `debug` (and
remove all `quiet`) at the grub stage.
** Attachment added: "d06-3-debug.log"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1967957/+attachment/5577400/+files/d06-3-debug.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
Status in linux package in Ubuntu:
Incomplete
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+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 1967957] [NEW] jammy beta (220330) live server arm64 iso failed to boot with virtual CD
Public bug reported:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: {^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s! [swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: {^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s! [swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s! [swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic #23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic #23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "d06-3.log"
https://bugs.launchpad.net/bugs/1967957/+attachment/5577398/+files/d06-3.log
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot with virtual
CD
Status in linux package in Ubuntu:
New
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 13
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) live server arm64 iso kernel panic during pxe boot
** Summary changed: - jammy beta (220330) arm iso kernel panic during pxe boot + jammy beta (220330) live server arm64 iso kernel panic during pxe boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) live server arm64 iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Incomplete Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
@Paolo , thanks for verifying. Right, MAAS deployment looks good (see my comment of "Additional Information" in the bug description) as what Dann pointed out. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
@dann , I checked the grub entry prior to filing this bug. For now the pxe server is used for the other purpose. Let me reproduce the post- mortem information later on. Thanks for the tip! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
Attached bizzy-debug.log, which is the console log of the Mt. Jade server (bizzy) with the kernel parameter "debug" enabled. ** Attachment added: "bizzy-debug.log" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1967562/+attachment/5575779/+files/bizzy-debug.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
** Description changed: = Description = - Platforms: Ampere Mt. Jade Altra, Cavium thunderX crb2s + Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: New Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up h
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
bizzy.log is the console log of the Mt. Jade server. The last entry is the kernel panic because of the pxe boot. The last successful deployment in bizzy.log is performed by MAAS. ** Attachment added: "bizzy.log" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1967562/+attachment/5575772/+files/bizzy.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: New Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra, Cavium thunderX crb2s Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967562] [NEW] jammy beta (220330) arm iso kernel panic during pxe boot
Public bug reported: = Description = Platforms: Ampere Mt. Jade Altra, Cavium thunderX crb2s Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: New Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra, Cavium thunderX crb2s Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1
[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
** Changed in: kunpeng920/ubuntu-20.04-hwe Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in kunpeng920 ubuntu-21.10 series: Fix Released Status in kunpeng920 ubuntu-22.04 series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
Focal 5.13.0-30-generic #33~20.04.1-Ubuntu verification passed. ubuntu@segers:~$ uname -a; lsb_release -a; sudo dmesg | grep "fail to alloc uacce" Linux segers 5.13.0-30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:28:43 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-21.10 series: Fix Committed Status in kunpeng920 ubuntu-22.04 series: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
Kernel re-spun. 5.13.0-30 is expected to be released to -updates by 2022/Feb/17[1]. [1] https://lists.ubuntu.com/archives/kernel-sru- announce/2022-February/000198.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-21.10 series: Fix Committed Status in kunpeng920 ubuntu-22.04 series: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
impish 5.13.0-30 verification passed. ubuntu@segers:~$ uname -a; lsb_release -a; sudo dmesg | grep "fail to alloc uacce" Linux segers 5.13.0-30-generic #33-Ubuntu SMP Fri Feb 4 17:05:14 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.10 Release:21.10 Codename: impish ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-21.10 series: Fix Committed Status in kunpeng920 ubuntu-22.04 series: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
The patch is applied https://lists.ubuntu.com/archives/kernel- team/2022-January/127138.html ** Changed in: kunpeng920/ubuntu-20.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-21.10 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-22.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-21.10 series: Fix Committed Status in kunpeng920 ubuntu-22.04 series: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: In Progress Status in linux source package in Jammy: Incomplete Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
Submitted the patch to the kernel team mailing list https://lists.ubuntu.com/archives/kernel-team/2022-January/127109.html for both Impish and Jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in kunpeng920 ubuntu-21.10 series: In Progress Status in kunpeng920 ubuntu-22.04 series: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: In Progress Status in linux source package in Jammy: Incomplete Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
Jammy will release a few months later and we are aware of the development activities of Jammy 5.15 kernel. The patch needs to land Jammy as well to prevent user's dist-upgrade regression. My investigation of the patch, 183b60e00597 crypto: hisilicon/qm - modify the uacce mode check, has clean cherry-pick with Jammy 5.15 master-next, and fixes the issue[1]. Next: Process to merge 183b60e00597 with Jammy 5.15 kernel along with impish 5.13 (for up-coming focal-hwe) [1] Before applying the patch (master-next branch, 5.15.13): ubuntu@segers:~$ sudo ./collect.sh Linux segers 5.15.0-16-generic #16~d20220111t131721~7ec137fc2603 SMP Tue Jan 11 13:18:16 UTC 20 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal [3.408872] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 [ 11.594241] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.636486] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.678612] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.720721] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.762846] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.805032] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.847216] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.889401] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.970515] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 12.067413] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 13.974371] dw_spi_mmio HISI0173:00: DMA init failed [ 19.448332] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 19.820834] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 19.852904] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 20.224761] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 22.956763] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 22.966698] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: -12 [ 22.982319] hisi_sec2 :75:00.0: fail to alloc uacce (-22) [ 22.990846] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 22.14] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: -12 [ 23.010710] hisi_sec2 :b5:00.0: fail to alloc uacce (-22) == [0.00] cma: Reserved 32 MiB at 0x7e00 [0.00] Memory: 131307604K/134213440K available (17280K kernel code, 4572K rwdata, 13820K rodata, 9600K init, 1182K bss, 2873068K reserved, 32768K cma-reserved) [3.408872] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 [ 11.594241] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.636486] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.678612] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.720721] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.762846] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.805032] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.847216] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.889401] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.970515] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 12.067413] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 22.956757] cma_alloc: 10 callbacks suppressed [ 22.956763] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 22.966698] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: -12 [ 22.990846] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 22.14] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: -12 == == [ 22.982319] hisi_sec2 :75:00.0: fail to alloc uacce (-22) [ 23.010710] hisi_sec2 :b5:00.0: fail to alloc uacce (-22) == == == After apply the patch: ubuntu@segers:~$ sudo ./collect.sh Linux segers 5.15.0-16-generic #16~d20220111t123224~c7a448651f57 SMP Tue Jan 11 12:33:20 UTC 20 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal [3.409019] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 [ 11.604567] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.646821] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.688
[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
** Also affects: kunpeng920/ubuntu-22.04 Importance: Undecided Status: New ** Changed in: kunpeng920/ubuntu-21.10 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-22.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-21.10 Assignee: (unassigned) => Taihsiang Ho (taihsiangho) ** Changed in: kunpeng920/ubuntu-22.04 Assignee: (unassigned) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in kunpeng920 ubuntu-21.10 series: In Progress Status in kunpeng920 ubuntu-22.04 series: In Progress Status in linux package in Ubuntu: New Status in linux source package in Impish: In Progress Status in linux source package in Jammy: New Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
** Also affects: kunpeng920/ubuntu-21.10 Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in kunpeng920 ubuntu-21.10 series: New Status in linux package in Ubuntu: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)
** Tags removed: tairadar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1911376
Title:
[ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and
advertise to userspace)
Status in kunpeng920:
In Progress
Status in kunpeng920 ubuntu-18.04 series:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Bug description:
[Impact]
The SSBS patch in 4.14 stable kernel, and mainline kernel adds snippet
into arm64_cpufeatures but in bionic kernel, it is landed into
arm64_elf_hwcaps.
[Fix]
Move SSBS snippet from arm64_elf_hwcaps back to arm64_features
[Test]
No known tool for SSB attack. Regression test only.
[Regression Potential]
Regression might be on all arm64 platforms. Regression test on all arm64
platform we have is recommended.
=
[Bug Description]
ubuntu 18.04.1 fail to enable this SSBS function, this sys log will call
trace as follow:
[0.662089] Call trace:
[0.662870] setup_elf_hwcaps+0xb8/0xd4
[0.664023] setup_cpu_features+0x60/0xf8
[0.665216] smp_cpus_done+0x34/0xa8
[0.666547] smp_init+0x120/0x138
[0.667555] kernel_init_freeable+0xf4/0x260
[0.668860] kernel_init+0x18/0x110
[0.670025] ret_from_fork+0x10/0x18
[Steps to Reproduce]
1) boot this system
2) uname -a
Ubuntu 4.15.0-99.100-generic 4.15.18
[Actual Results]
 boot error:
[0.662089] Call trace:
[0.662870] setup_elf_hwcaps+0xb8/0xd4
[0.664023] setup_cpu_features+0x60/0xf8
[0.665216] smp_cpus_done+0x34/0xa8
[0.666547] smp_init+0x120/0x138
[0.667555] kernel_init_freeable+0xf4/0x260
[0.668860] kernel_init+0x18/0x110
[0.670025] ret_from_fork+0x10/0x18
[Expected Results]
no error
[Reproducibility]
NA
[Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):
arm64: cpufeature: Detect SSBS and advertise to userspace
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d71be2b6c0e19180b5f80a6d42039cc074a693a2
backport this following code into "static const struct
arm64_cpu_capabilities arm64_elf_hwcaps[]" which will be error.
1274 #ifdef CONFIG_ARM64_SSBD
1275 {
1276 .desc = "Speculative Store Bypassing Safe (SSBS)",
1277 .capability = ARM64_SSBS,
1278 .type = ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE,
1279 .matches = has_cpuid_feature,
1280 .sys_reg = SYS_ID_AA64PFR1_EL1,
1281 .field_pos = ID_AA64PFR1_SSBS_SHIFT,
1282 .sign = FTR_UNSIGNED,
1283 .min_field_value = ID_AA64PFR1_SSBS_PSTATE_ONLY,
1284 .cpu_enable = cpu_enable_ssbs,
1285 },
[Resolution]
Can you backport aboving code into "static const struct
arm64_cpu_capabilities arm64_features[] = {"?
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1911376/+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 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
** Tags removed: tairadar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+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 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
Upstream have all the commits including the patch in comment#17[1][2]. [1] the following landed in v5.7. crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM [2] This commit landed in v5.8 modify the SEC probe process -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+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 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
All commits[1] including the patch in comment#17[2] are now in Focal hwe-5.8 tree. According to the above discussion, I would suggest we may re-verify the patch set. [1] Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 74b58db8b7ed crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 2514f5595db7 crypto: hisilicon/sec2 - Update IV and MAC operation Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 8824bc5ed1e7 crypto: hisilicon/sec2 - Add iommu status check Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 a13c97118749 crypto: hisilicon/sec2 - Add workqueue for SEC driver. Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 57ca81245f4d crypto: hisilicon - Use one workqueue per qm instead of per qp Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 b5f13031cd8d crypto: hisilicon - qm depends on UACCE Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 1b44f93eb3e5 crypto: hisilicon - remove redundant assignment of pointer ctx Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 9e00df7156e4 hisilicon - register zip engine to uacce Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 18bead70e991 hisilicon - Remove module_param uacce_mode Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 015d239ac014 uacce: add uacce driver Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 aa017ab97a22 uacce: Add documents for uacce Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 00e62e868ccd crypto: hisilicon - Fix duplicate print when qm occur multiple errors Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 f826e6efb42b crypto: hisilicon - Unify error detect process into qm Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 de3daf4b4ad5 crypto: hisilicon - Configure zip RAS error type Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 eaebf4c3b103 crypto: hisilicon - Unify hardware error init/uninit into QM [2] Ubuntu-hwe-5.8-5.8.0-25.26_20.04.1 18614230f430 modify the SEC probe process ** Changed in: kunpeng920/ubuntu-20.04-hwe Status: New => In Progress ** Changed in: kunpeng920/ubuntu-20.04-hwe Assignee: (unassigned) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in kunpeng920 upstream-kernel series: Incomplete Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+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 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/ubuntu-20.04-hwe Milestone: None => ubuntu-20.04.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 ubuntu-20.04-hwe series: New Status in kunpeng920 upstream-kernel series: Incomplete Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+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 1867588] Re: [SFC-0316]sync mainline kernel 5.7rc1 SFC patchset into ubuntu HWE kernel branch
** Tags removed: tairadar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867588 Title: [SFC-0316]sync mainline kernel 5.7rc1 SFC patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] SFC patchset have merged into mainline 5.7RC1rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] spi: HiSilicon v3xx: Use DMI quirk to set controller buswidth override bits spi: HiSilicon v3xx: Properly set CMD_CONFIG for Dual/Quad modes spi: Allow SPI controller override device buswidth To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867588/+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 1890884] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch
I updated the grub.cfg in comment#6 to be[1]. The changes is the correct
file name initrd --> initrd.gz. And the error message is now:
domain : maas
rootserver: 10.228.68.91 rootpath:
filename : grubnetaa64.efi.signed
mount: mounting /root/cdrom/casper/extras/modules.squashfs-generic on
/root/lib/modules failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /run on /root/run failed: No such file or directory
run-init: current directory on the same filesystem as the root: error 0
Target filesystem doesn't have requested /sbin/init.
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
No init found. Try passing init= bootarg.
BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.2) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
[1]
menuentry "Install Ubuntu Server (18.04.5 subiquity live 20200806.1) " {
set gfxpayload=keep
linux /casper/vmlinuz
url=http://10.228.68.91/bionic-live-server-arm64.iso only-ubiquity ip=dhcp ---
initrd /casper/initrd.gz
}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890884
Title:
kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06
arm64 arch
Status in subiquity:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso
kernel: 4.15.0-112-generic #113-Ubuntu
platform: Hisilicon D06 arm64 arch
[Reproducing Steps]
1. setup pxe boot by following
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
2. pxe boot the machine with the image
[Expected Result]
Boot to subiquity
[Actual Result]
Kernel trace happened during booting process. Reproducing rate: 2 out of 2.
[8.375118] md: ... autorun DONE.
[8.378478] VFS: Cannot open root device "(null)" or unknown-block(0,0):
error -6
[8.385955] Please append a correct "root=" boot option; here are the
available partitions:
[8.394303] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[8.402554] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic
#113-Ubuntu
[8.410369] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 -
V1.20.01 04/26/2019
[8.418879] Call trace:
[8.421316] dump_backtrace+0x0/0x198
[8.424965] show_stack+0x24/0x30
[8.428269] dump_stack+0x98/0xbc
[8.431572] panic+0x128/0x2a4
[8.434615] mount_block_root+0x210/0x2e8
[8.438610] mount_root+0x7c/0x8c
[8.441912] prepare_namespace+0x144/0x1dc
[8.445995] kernel_init_freeable+0x218/0x23c
[8.450341] kernel_init+0x18/0x110
[8.453817] ret_from_fork+0x10/0x18
[8.457486] SMP: stopping secondary CPUs
[8.461836] Kernel Offset: disabled
[8.465312] CPU features: 0x03200a38
[8.468873] Memory Limit: none
[8.473291] Unable to handle kernel paging request at virtual address
09865034
[8.481192] Mem abort info:
[8.483972] ESR = 0x9661
[8.487013] Exception class = DABT (current EL), IL = 32 bits
[8.492918] SET = 0, FnV = 0
[8.495958] EA = 0, S1PTW = 0
[8.499086] Data abort info:
[8.501953] ISV = 0, ISS = 0x0061
[8.505774] CM = 0, WnR = 1
[8.508729] swapper pgtable: 4k pages, 48-bit VAs, pgd = (ptrval)
[8.515502] [09865034] *pgd=0a5fe003,
*pud=0a5fd003, *pmd=0a5f7003, *pte=006894110703
[8.526445] Internal error: Oops: 9661 [#1] SMP
[8.531310] Modules linked in:
[8.534351] Process swapper/0 (pid: 1, stack limit = 0x(ptrval))
[8.541039] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic
#113-Ubuntu
[8.548854] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 -
V1.20.01 04/26/2019
[8.557363] pstate: 60800089 (nZCv daIf -PAN +UAO)
[8.562144] pc : acpi_os_write_memory+0xac/0x158
[8.566749] lr : apei_write+0xb0/0xc0
[8.570397] sp : 09afb900
[8.573698] x29: 09afb900 x28: fffe
[8.578996] x27: x26: ffa5
[8.584294] x25: ffbe x24: 0080
[8.589592] x23: 0005 x22: 0008
[8.594890] x21: 0040 x20: 0010
[8.600188] x19: 94110
[Kernel-packages] [Bug 1890884] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch
uh it's already incomplete. This is a fair status. Let's keep it as is. ** Changed in: subiquity Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890884 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch Status in subiquity: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D06 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [8.375118] md: ... autorun DONE. [8.378478] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [8.385955] Please append a correct "root=" boot option; here are the available partitions: [8.394303] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [8.402554] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.410369] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.418879] Call trace: [8.421316] dump_backtrace+0x0/0x198 [8.424965] show_stack+0x24/0x30 [8.428269] dump_stack+0x98/0xbc [8.431572] panic+0x128/0x2a4 [8.434615] mount_block_root+0x210/0x2e8 [8.438610] mount_root+0x7c/0x8c [8.441912] prepare_namespace+0x144/0x1dc [8.445995] kernel_init_freeable+0x218/0x23c [8.450341] kernel_init+0x18/0x110 [8.453817] ret_from_fork+0x10/0x18 [8.457486] SMP: stopping secondary CPUs [8.461836] Kernel Offset: disabled [8.465312] CPU features: 0x03200a38 [8.468873] Memory Limit: none [8.473291] Unable to handle kernel paging request at virtual address 09865034 [8.481192] Mem abort info: [8.483972] ESR = 0x9661 [8.487013] Exception class = DABT (current EL), IL = 32 bits [8.492918] SET = 0, FnV = 0 [8.495958] EA = 0, S1PTW = 0 [8.499086] Data abort info: [8.501953] ISV = 0, ISS = 0x0061 [8.505774] CM = 0, WnR = 1 [8.508729] swapper pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [8.515502] [09865034] *pgd=0a5fe003, *pud=0a5fd003, *pmd=0a5f7003, *pte=006894110703 [8.526445] Internal error: Oops: 9661 [#1] SMP [8.531310] Modules linked in: [8.534351] Process swapper/0 (pid: 1, stack limit = 0x(ptrval)) [8.541039] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.548854] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.557363] pstate: 60800089 (nZCv daIf -PAN +UAO) [8.562144] pc : acpi_os_write_memory+0xac/0x158 [8.566749] lr : apei_write+0xb0/0xc0 [8.570397] sp : 09afb900 [8.573698] x29: 09afb900 x28: fffe [8.578996] x27: x26: ffa5 [8.584294] x25: ffbe x24: 0080 [8.589592] x23: 0005 x22: 0008 [8.594890] x21: 0040 x20: 0010 [8.600188] x19: 94110034 x18: 0003 [8.605486] x17: x16: 0009 [8.610784] x15: 001f x14: 8205169d4225fc6e [8.616082] x13: 34650f577629d387 x12: 9c021ee3f3d0bcca [8.621380] x11: b1ae83ff50c19148 x10: b6b91ab42ae87562 [8.626678] x9 : f469cb78cb1add9d x8 : a16fcb806efa3dd5 [8.631976] x7 : 0001 x6 : 94110034 [8.637274] x5 : 9411003c x4 : 09639fb8 [8.642571] x3 : x2 : 0034 [8.647869] x1 : 0010 x0 : 09865034 [8.653167] Call trace: [8.655601] acpi_os_write_memory+0xac/0x158 [8.659858] apei_write+0xb0/0xc0 [8.663160] __apei_exec_write_register+0x88/0xb0 [8.667851] apei_exec_write_register_value+0x2c/0x38 [8.672888] __apei_exec_run+0xac/0x108 [8.676711] erst_write+0x154/0x268 [8.680186] erst_writer+0x26c/0x3b0 [8.683751] pstore_dump+0x1b4/0x330 [8.687313] kmsg_dump+0xd0/0x100 [8.690615] panic+0x164/0x2a4 [8.693656] mount_block_root+0x210/0x2e8 [8.697652] mount_root+0x7c/0x8c [8.700953] prepare_namespace+0x144/0x1dc [8.705035] kernel_init_freeable+0x218/0x23c [8.709380] kernel_init+0x18/0x110 [8.712855] ret_from_fork+0x10/0x18 [8.716418] Code: 54000380 710102bf 54000561 d5033e9f (f914) [8.7
[Kernel-packages] [Bug 1890884] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch
@mwhudson Thanks for the hint. I think I did make some mistakes when
setting up the grub parameters for pxe[1] because @dann seemed to
perform a similar test without the same issue in these bug
reports[2][3].
Let me set the status to be invalid until the pxe config is confirmed to
be right.
[1] The grub.cfg snippet I used to reproduce this issue
menuentry "Install Ubuntu Server (18.04.5 subiquity live 20200806.1) (Pull the
iso from lab apache)" {
set gfxpayload=keep
linux /casper/vmlinuz
url=http://10.228.68.91/bionic-live-server-arm64.iso only-ubiquity ip=dhcp ---
initrd /casper/initrd
}
[2] https://bugs.launchpad.net/subiquity/+bug/1891060
[3] https://bugs.launchpad.net/subiquity/+bug/1891059
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890884
Title:
kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06
arm64 arch
Status in subiquity:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso
kernel: 4.15.0-112-generic #113-Ubuntu
platform: Hisilicon D06 arm64 arch
[Reproducing Steps]
1. setup pxe boot by following
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
2. pxe boot the machine with the image
[Expected Result]
Boot to subiquity
[Actual Result]
Kernel trace happened during booting process. Reproducing rate: 2 out of 2.
[8.375118] md: ... autorun DONE.
[8.378478] VFS: Cannot open root device "(null)" or unknown-block(0,0):
error -6
[8.385955] Please append a correct "root=" boot option; here are the
available partitions:
[8.394303] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[8.402554] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic
#113-Ubuntu
[8.410369] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 -
V1.20.01 04/26/2019
[8.418879] Call trace:
[8.421316] dump_backtrace+0x0/0x198
[8.424965] show_stack+0x24/0x30
[8.428269] dump_stack+0x98/0xbc
[8.431572] panic+0x128/0x2a4
[8.434615] mount_block_root+0x210/0x2e8
[8.438610] mount_root+0x7c/0x8c
[8.441912] prepare_namespace+0x144/0x1dc
[8.445995] kernel_init_freeable+0x218/0x23c
[8.450341] kernel_init+0x18/0x110
[8.453817] ret_from_fork+0x10/0x18
[8.457486] SMP: stopping secondary CPUs
[8.461836] Kernel Offset: disabled
[8.465312] CPU features: 0x03200a38
[8.468873] Memory Limit: none
[8.473291] Unable to handle kernel paging request at virtual address
09865034
[8.481192] Mem abort info:
[8.483972] ESR = 0x9661
[8.487013] Exception class = DABT (current EL), IL = 32 bits
[8.492918] SET = 0, FnV = 0
[8.495958] EA = 0, S1PTW = 0
[8.499086] Data abort info:
[8.501953] ISV = 0, ISS = 0x0061
[8.505774] CM = 0, WnR = 1
[8.508729] swapper pgtable: 4k pages, 48-bit VAs, pgd = (ptrval)
[8.515502] [09865034] *pgd=0a5fe003,
*pud=0a5fd003, *pmd=0a5f7003, *pte=006894110703
[8.526445] Internal error: Oops: 9661 [#1] SMP
[8.531310] Modules linked in:
[8.534351] Process swapper/0 (pid: 1, stack limit = 0x(ptrval))
[8.541039] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic
#113-Ubuntu
[8.548854] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 -
V1.20.01 04/26/2019
[8.557363] pstate: 60800089 (nZCv daIf -PAN +UAO)
[8.562144] pc : acpi_os_write_memory+0xac/0x158
[8.566749] lr : apei_write+0xb0/0xc0
[8.570397] sp : 09afb900
[8.573698] x29: 09afb900 x28: fffe
[8.578996] x27: x26: ffa5
[8.584294] x25: ffbe x24: 0080
[8.589592] x23: 0005 x22: 0008
[8.594890] x21: 0040 x20: 0010
[8.600188] x19: 94110034 x18: 0003
[8.605486] x17: x16: 0009
[8.610784] x15: 001f x14: 8205169d4225fc6e
[8.616082] x13: 34650f577629d387 x12: 9c021ee3f3d0bcca
[8.621380] x11: b1ae83ff50c19148 x10: b6b91ab42ae87562
[8.626678] x9 : f469cb78cb1add9d x8 : a16fcb806efa3dd5
[8.631976] x7 : 0001 x6 : 94110034
[8.637274] x5 : 9411003c x4 : 09639fb8
[8.642571] x3 : x2 : 0034
[8.647869] x1 : 0010 x0 : 09865034
[8.653167] Call trace:
[8.655601] acpi_os_write_memory+0xac/0x158
[8.659858] apei_write+0xb0/0xc0
[8.663160] __apei_exec_write_register+0x88/0xb0
[8.667851] apei_exec_write_register_v
[Kernel-packages] [Bug 1890867] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch
Similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890884/comments/6 let me re-visit my pxe configuration and set the status as "incomplete". ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: subiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890867 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Incomplete Bug description: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D05 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [6.643543] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [6.651271] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 [6.657871] Call trace: [6.660308] dump_backtrace+0x0/0x198 [6.663957] show_stack+0x24/0x30 [6.667261] dump_stack+0x98/0xbc [6.670563] panic+0x128/0x2a4 [6.673606] mount_block_root+0x210/0x2e8 [6.677603] mount_root+0x7c/0x8c [6.680904] prepare_namespace+0x144/0x1dc [6.684987] kernel_init_freeable+0x218/0x23c [6.689331] kernel_init+0x18/0x110 [6.692806] ret_from_fork+0x10/0x18 [6.696428] SMP: stopping secondary CPUs [6.700345] Kernel Offset: disabled [6.703821] CPU features: 0x2008 [6.707382] Memory Limit: none [6.710438] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890867/+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 1890884] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch
** Description changed: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D06 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] - Kernel trace happened during booting process. + Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [8.375118] md: ... autorun DONE. [8.378478] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [8.385955] Please append a correct "root=" boot option; here are the available partitions: [8.394303] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [8.402554] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.410369] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.418879] Call trace: [8.421316] dump_backtrace+0x0/0x198 [8.424965] show_stack+0x24/0x30 [8.428269] dump_stack+0x98/0xbc [8.431572] panic+0x128/0x2a4 [8.434615] mount_block_root+0x210/0x2e8 [8.438610] mount_root+0x7c/0x8c [8.441912] prepare_namespace+0x144/0x1dc [8.445995] kernel_init_freeable+0x218/0x23c [8.450341] kernel_init+0x18/0x110 [8.453817] ret_from_fork+0x10/0x18 [8.457486] SMP: stopping secondary CPUs [8.461836] Kernel Offset: disabled [8.465312] CPU features: 0x03200a38 [8.468873] Memory Limit: none [8.473291] Unable to handle kernel paging request at virtual address 09865034 [8.481192] Mem abort info: [8.483972] ESR = 0x9661 [8.487013] Exception class = DABT (current EL), IL = 32 bits [8.492918] SET = 0, FnV = 0 [8.495958] EA = 0, S1PTW = 0 [8.499086] Data abort info: [8.501953] ISV = 0, ISS = 0x0061 [8.505774] CM = 0, WnR = 1 [8.508729] swapper pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [8.515502] [09865034] *pgd=0a5fe003, *pud=0a5fd003, *pmd=0a5f7003, *pte=006894110703 [8.526445] Internal error: Oops: 9661 [#1] SMP [8.531310] Modules linked in: [8.534351] Process swapper/0 (pid: 1, stack limit = 0x(ptrval)) [8.541039] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.548854] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.557363] pstate: 60800089 (nZCv daIf -PAN +UAO) [8.562144] pc : acpi_os_write_memory+0xac/0x158 [8.566749] lr : apei_write+0xb0/0xc0 [8.570397] sp : 09afb900 - [8.573698] x29: 09afb900 x28: fffe - [8.578996] x27: x26: ffa5 - [8.584294] x25: ffbe x24: 0080 - [8.589592] x23: 0005 x22: 0008 - [8.594890] x21: 0040 x20: 0010 - [8.600188] x19: 94110034 x18: 0003 - [8.605486] x17: x16: 0009 - [8.610784] x15: 001f x14: 8205169d4225fc6e - [8.616082] x13: 34650f577629d387 x12: 9c021ee3f3d0bcca - [8.621380] x11: b1ae83ff50c19148 x10: b6b91ab42ae87562 - [8.626678] x9 : f469cb78cb1add9d x8 : a16fcb806efa3dd5 - [8.631976] x7 : 0001 x6 : 94110034 - [8.637274] x5 : 9411003c x4 : 09639fb8 - [8.642571] x3 : x2 : 0034 - [8.647869] x1 : 0010 x0 : 09865034 + [8.573698] x29: 09afb900 x28: fffe + [8.578996] x27: x26: ffa5 + [8.584294] x25: ffbe x24: 0080 + [8.589592] x23: 0005 x22: 0008 + [8.594890] x21: 0040 x20: 0010 + [8.600188] x19: 94110034 x18: 0003 + [8.605486] x17: x16: 0009 + [8.610784] x15: 001f x14: 8205169d4225fc6e + [8.616082] x13: 34650f577629d387 x12: 9c021ee3f3d0bcca + [8.621380] x11: b1ae83ff50c19148 x10: b6b91ab42ae87562 + [8.626678] x9 : f469cb78cb1add9d x8 : a16fcb806efa3dd5 + [8.631976] x7 : 0001 x6 : 94110034 + [8.637274] x5 : 9411003c x4 : 09639fb8 + [8.642571] x3 : x2 : 0034 + [8.647869] x1 : 0010 x0 : 09865034 [8.653167] Call trace: [8.655601] acpi_os_write_memory+0xac/0x158 [8.659858] apei_write+0xb0/0xc0 [8.663160] __apei_exec_write_register+0x88/0xb0 [8.667851] apei_exec_write_register_value+0x2c/0x38 [8.672888] __apei_exec_run+0xac/0x108 [8.676711] erst_
[Kernel-packages] [Bug 1890867] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch
The issue happened at boot stage. apport-collect can't be applied. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890867 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch Status in linux package in Ubuntu: Confirmed Bug description: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D05 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [6.643543] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [6.651271] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 [6.657871] Call trace: [6.660308] dump_backtrace+0x0/0x198 [6.663957] show_stack+0x24/0x30 [6.667261] dump_stack+0x98/0xbc [6.670563] panic+0x128/0x2a4 [6.673606] mount_block_root+0x210/0x2e8 [6.677603] mount_root+0x7c/0x8c [6.680904] prepare_namespace+0x144/0x1dc [6.684987] kernel_init_freeable+0x218/0x23c [6.689331] kernel_init+0x18/0x110 [6.692806] ret_from_fork+0x10/0x18 [6.696428] SMP: stopping secondary CPUs [6.700345] Kernel Offset: disabled [6.703821] CPU features: 0x2008 [6.707382] Memory Limit: none [6.710438] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890867/+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 1890884] [NEW] kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch
Public bug reported: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D06 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. [8.375118] md: ... autorun DONE. [8.378478] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [8.385955] Please append a correct "root=" boot option; here are the available partitions: [8.394303] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [8.402554] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.410369] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.418879] Call trace: [8.421316] dump_backtrace+0x0/0x198 [8.424965] show_stack+0x24/0x30 [8.428269] dump_stack+0x98/0xbc [8.431572] panic+0x128/0x2a4 [8.434615] mount_block_root+0x210/0x2e8 [8.438610] mount_root+0x7c/0x8c [8.441912] prepare_namespace+0x144/0x1dc [8.445995] kernel_init_freeable+0x218/0x23c [8.450341] kernel_init+0x18/0x110 [8.453817] ret_from_fork+0x10/0x18 [8.457486] SMP: stopping secondary CPUs [8.461836] Kernel Offset: disabled [8.465312] CPU features: 0x03200a38 [8.468873] Memory Limit: none [8.473291] Unable to handle kernel paging request at virtual address 09865034 [8.481192] Mem abort info: [8.483972] ESR = 0x9661 [8.487013] Exception class = DABT (current EL), IL = 32 bits [8.492918] SET = 0, FnV = 0 [8.495958] EA = 0, S1PTW = 0 [8.499086] Data abort info: [8.501953] ISV = 0, ISS = 0x0061 [8.505774] CM = 0, WnR = 1 [8.508729] swapper pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [8.515502] [09865034] *pgd=0a5fe003, *pud=0a5fd003, *pmd=0a5f7003, *pte=006894110703 [8.526445] Internal error: Oops: 9661 [#1] SMP [8.531310] Modules linked in: [8.534351] Process swapper/0 (pid: 1, stack limit = 0x(ptrval)) [8.541039] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.548854] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.557363] pstate: 60800089 (nZCv daIf -PAN +UAO) [8.562144] pc : acpi_os_write_memory+0xac/0x158 [8.566749] lr : apei_write+0xb0/0xc0 [8.570397] sp : 09afb900 [8.573698] x29: 09afb900 x28: fffe [8.578996] x27: x26: ffa5 [8.584294] x25: ffbe x24: 0080 [8.589592] x23: 0005 x22: 0008 [8.594890] x21: 0040 x20: 0010 [8.600188] x19: 94110034 x18: 0003 [8.605486] x17: x16: 0009 [8.610784] x15: 001f x14: 8205169d4225fc6e [8.616082] x13: 34650f577629d387 x12: 9c021ee3f3d0bcca [8.621380] x11: b1ae83ff50c19148 x10: b6b91ab42ae87562 [8.626678] x9 : f469cb78cb1add9d x8 : a16fcb806efa3dd5 [8.631976] x7 : 0001 x6 : 94110034 [8.637274] x5 : 9411003c x4 : 09639fb8 [8.642571] x3 : x2 : 0034 [8.647869] x1 : 0010 x0 : 09865034 [8.653167] Call trace: [8.655601] acpi_os_write_memory+0xac/0x158 [8.659858] apei_write+0xb0/0xc0 [8.663160] __apei_exec_write_register+0x88/0xb0 [8.667851] apei_exec_write_register_value+0x2c/0x38 [8.672888] __apei_exec_run+0xac/0x108 [8.676711] erst_write+0x154/0x268 [8.680186] erst_writer+0x26c/0x3b0 [8.683751] pstore_dump+0x1b4/0x330 [8.687313] kmsg_dump+0xd0/0x100 [8.690615] panic+0x164/0x2a4 [8.693656] mount_block_root+0x210/0x2e8 [8.697652] mount_root+0x7c/0x8c [8.700953] prepare_namespace+0x144/0x1dc [8.705035] kernel_init_freeable+0x218/0x23c [8.709380] kernel_init+0x18/0x110 [8.712855] ret_from_fork+0x10/0x18 [8.716418] Code: 54000380 710102bf 54000561 d5033e9f (f914) [8.722499] ---[ end trace 8cc2af9c56a59f43 ]--- [ 38.738914] WARNING: CPU: 32 PID: 9 at /build/linux-WMG2fK/linux-4.15.0/kernel/irq_work.c:102 irq_work_queue_on+0xd4/0xe8 [ 38.749854] Modules linked in: [ 38.752897] CPU: 32 PID: 9 Comm: rcu_sched Tainted: G D 4.15.0-112-generic #113-Ubuntu [ 38.762014] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [ 38.770524] pstate: 60c00089 (nZCv daIf +PAN +UAO) [ 38.775302] pc : irq_work_queue_on+0xd4/0xe8 [ 38.779560] lr : rcu_implicit_dynticks_qs+0x224/0x2c8 [ 38.784597] sp : 09bebd20 [ 38.787897] x29: 09bebd20 x28: ff
[Kernel-packages] [Bug 1890867] [NEW] kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch
Public bug reported: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D05 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [6.643543] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [6.651271] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 [6.657871] Call trace: [6.660308] dump_backtrace+0x0/0x198 [6.663957] show_stack+0x24/0x30 [6.667261] dump_stack+0x98/0xbc [6.670563] panic+0x128/0x2a4 [6.673606] mount_block_root+0x210/0x2e8 [6.677603] mount_root+0x7c/0x8c [6.680904] prepare_namespace+0x144/0x1dc [6.684987] kernel_init_freeable+0x218/0x23c [6.689331] kernel_init+0x18/0x110 [6.692806] ret_from_fork+0x10/0x18 [6.696428] SMP: stopping secondary CPUs [6.700345] Kernel Offset: disabled [6.703821] CPU features: 0x2008 [6.707382] Memory Limit: none [6.710438] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890867 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch Status in linux package in Ubuntu: New Bug description: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D05 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [6.643543] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [6.651271] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 [6.657871] Call trace: [6.660308] dump_backtrace+0x0/0x198 [6.663957] show_stack+0x24/0x30 [6.667261] dump_stack+0x98/0xbc [6.670563] panic+0x128/0x2a4 [6.673606] mount_block_root+0x210/0x2e8 [6.677603] mount_root+0x7c/0x8c [6.680904] prepare_namespace+0x144/0x1dc [6.684987] kernel_init_freeable+0x218/0x23c [6.689331] kernel_init+0x18/0x110 [6.692806] ret_from_fork+0x10/0x18 [6.696428] SMP: stopping secondary CPUs [6.700345] Kernel Offset: disabled [6.703821] CPU features: 0x2008 [6.707382] Memory Limit: none [6.710438] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890867/+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 1866319] Re: reboot crash in qla2x00_shutdown()
I did not reproduce this issue with focal beta iso on scobee. The ephemeral installer environment of focal beta live iso was running 5.4.0-21. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866319 Title: reboot crash in qla2x00_shutdown() Status in subiquity: New Status in linux package in Ubuntu: Incomplete Bug description: focal daily live iso (200227) d06 [Steps to Reproduce] 1. Download the daily live iso over http://www.cdimage.ubuntu.com/ubuntu-server/daily-live/20200227/focal-live-server-arm64.iso and boot from the iso 2. Boot into the installation process by selecting "Install Ubuntu Server" 3. Follow the subiquity instruction and update subiquity at the very beginning of the installation[1] 4. Follow the subiquity instruction to complete the installation on reboot. [1] If you don't update it, it will be this bug LP: #1866318 . Prompt of subiquity installation Version 19.12.2+git49.436ee1d7 of the installer is now available (19.10.2 is currently running). [Expected Result] The system reboots and get ready to use. [Actual Result] The system hangs on reboot. Show some of the messages: [FAILED] Failed unmounting /cdrom. [ 790.782440] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [ 790.790955] pstate: 6049 (nZCv daif +PAN -UAO) [ 790.795747] pc : __free_pages+0x28/0x68 [ 790.799578] lr : __iommu_dma_free_pages+0x38/0x58 [ 790.804271] sp : 11eabb00 [ 790.807575] x29: 11eabb00 x28: 803f7abf8ec0 [ 790.812878] x27: x26: 8a3f7b88e130 [ 790.818180] x25: 11156100 x24: 10e10908 [ 790.823481] x23: x22: 803f515ebc80 [ 790.828783] x21: 0010 x20: [ 790.834084] x19: x18: 0010 [ 790.839386] x17: 8158135c x16: db594df8 [ 790.844688] x15: 803f7abf93e8 x14: [ 790.849989] x13: 91eab827 x12: 11eab82f [ 790.855291] x11: 118ef000 x10: [ 790.860592] x9 : 11ae9000 x8 : 07ad [ 790.865894] x7 : 0017 x6 : 11ae8995 [ 790.871196] x5 : 0007 x4 : [ 790.876497] x3 : 11ae8930 x2 : [ 790.881798] x1 : 0034 x0 : [ 790.887101] Call trace: [ 790.889540] __free_pages+0x28/0x68 [ 790.893020] __iommu_dma_free_pages+0x38/0x58 [ 790.897366] __iommu_dma_free+0xb8/0xf8 [ 790.901192] iommu_dma_free+0x48/0x58 [ 790.904848] dma_free_attrs+0xd4/0xf0 [ 790.908546] qla2x00_free_fw_dump+0x58/0xb8 [qla2xxx] [ 790.913616] qla2x00_shutdown+0xd4/0x160 [qla2xxx] [ 790.918402] pci_device_shutdown+0x44/0x88 [ 790.922494] device_shutdown+0x134/0x240 [ 790.926414] kernel_restart_prepare+0x44/0x50 [ 790.930761] kernel_restart+0x20/0x68 [ 790.934414] __do_sys_reboot+0x100/0x228 [ 790.938327] __arm64_sys_reboot+0x2c/0x38 [ 790.942328] el0_svc_common.constprop.0+0xdc/0x1d8 [ 790.947109] el0_svc_handler+0x34/0x90 [ 790.950847] el0_svc+0x10/0x14 [ 790.953898] Code: d503201f 9100d261 52800020 4b0003e0 (b8e0003e) [ 790.960151] ---[ end trace 37539b75957dd46c ]--- [ 790.970536] Unable to handle kernel paging request at virtual address 10075034 [ 790.978440] Mem abort info: [ 790.981223] ESR = 0x9661 [ 790.984267] Exception class = DABT (current EL), IL = 32 bits [ 790.990175] SET = 0, FnV = 0 [ 790.993218] EA = 0, S1PTW = 0 [ 790.996347] Data abort info: [ 790.999217] ISV = 0, ISS = 0x0061 [ 791.003041] CM = 0, WnR = 1 [ 791.005999] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0125b000 [ 791.012689] [10075034] pgd=0a5ff003, pud=0a5fe003, pmd=0a5fd003, pte=00e894110703 [ 850.657602] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 850.663528] rcu: 61-...0: (7 ticks this GP) idle=33a/1/0x4000 softirq=5287/5287 fqs=5638 [ 850.672833] (detected by 3, t=15005 jiffies, g=81461, q=101) [ 850.678569] Task dump for CPU 61: [ 850.681872] shutdown R running task 0 1 0 0x002a [ 850.688909] Call trace: [ 850.691347] __switch_to+0xe4/0x148 [ 850.694823] 0x25 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1866319/+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 1866319] Re: reboot crash in qla2x00_shutdown()
@Dann the ephemeral installer environment was running 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:34 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux from the daily-live iso (200227 build) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866319 Title: reboot crash in qla2x00_shutdown() Status in subiquity: New Status in linux package in Ubuntu: Incomplete Bug description: focal daily live iso (200227) d06 [Steps to Reproduce] 1. Download the daily live iso over http://www.cdimage.ubuntu.com/ubuntu-server/daily-live/20200227/focal-live-server-arm64.iso and boot from the iso 2. Boot into the installation process by selecting "Install Ubuntu Server" 3. Follow the subiquity instruction and update subiquity at the very beginning of the installation[1] 4. Follow the subiquity instruction to complete the installation on reboot. [1] If you don't update it, it will be this bug LP: #1866318 . Prompt of subiquity installation Version 19.12.2+git49.436ee1d7 of the installer is now available (19.10.2 is currently running). [Expected Result] The system reboots and get ready to use. [Actual Result] The system hangs on reboot. Show some of the messages: [FAILED] Failed unmounting /cdrom. [ 790.782440] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [ 790.790955] pstate: 6049 (nZCv daif +PAN -UAO) [ 790.795747] pc : __free_pages+0x28/0x68 [ 790.799578] lr : __iommu_dma_free_pages+0x38/0x58 [ 790.804271] sp : 11eabb00 [ 790.807575] x29: 11eabb00 x28: 803f7abf8ec0 [ 790.812878] x27: x26: 8a3f7b88e130 [ 790.818180] x25: 11156100 x24: 10e10908 [ 790.823481] x23: x22: 803f515ebc80 [ 790.828783] x21: 0010 x20: [ 790.834084] x19: x18: 0010 [ 790.839386] x17: 8158135c x16: db594df8 [ 790.844688] x15: 803f7abf93e8 x14: [ 790.849989] x13: 91eab827 x12: 11eab82f [ 790.855291] x11: 118ef000 x10: [ 790.860592] x9 : 11ae9000 x8 : 07ad [ 790.865894] x7 : 0017 x6 : 11ae8995 [ 790.871196] x5 : 0007 x4 : [ 790.876497] x3 : 11ae8930 x2 : [ 790.881798] x1 : 0034 x0 : [ 790.887101] Call trace: [ 790.889540] __free_pages+0x28/0x68 [ 790.893020] __iommu_dma_free_pages+0x38/0x58 [ 790.897366] __iommu_dma_free+0xb8/0xf8 [ 790.901192] iommu_dma_free+0x48/0x58 [ 790.904848] dma_free_attrs+0xd4/0xf0 [ 790.908546] qla2x00_free_fw_dump+0x58/0xb8 [qla2xxx] [ 790.913616] qla2x00_shutdown+0xd4/0x160 [qla2xxx] [ 790.918402] pci_device_shutdown+0x44/0x88 [ 790.922494] device_shutdown+0x134/0x240 [ 790.926414] kernel_restart_prepare+0x44/0x50 [ 790.930761] kernel_restart+0x20/0x68 [ 790.934414] __do_sys_reboot+0x100/0x228 [ 790.938327] __arm64_sys_reboot+0x2c/0x38 [ 790.942328] el0_svc_common.constprop.0+0xdc/0x1d8 [ 790.947109] el0_svc_handler+0x34/0x90 [ 790.950847] el0_svc+0x10/0x14 [ 790.953898] Code: d503201f 9100d261 52800020 4b0003e0 (b8e0003e) [ 790.960151] ---[ end trace 37539b75957dd46c ]--- [ 790.970536] Unable to handle kernel paging request at virtual address 10075034 [ 790.978440] Mem abort info: [ 790.981223] ESR = 0x9661 [ 790.984267] Exception class = DABT (current EL), IL = 32 bits [ 790.990175] SET = 0, FnV = 0 [ 790.993218] EA = 0, S1PTW = 0 [ 790.996347] Data abort info: [ 790.999217] ISV = 0, ISS = 0x0061 [ 791.003041] CM = 0, WnR = 1 [ 791.005999] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0125b000 [ 791.012689] [10075034] pgd=0a5ff003, pud=0a5fe003, pmd=0a5fd003, pte=00e894110703 [ 850.657602] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 850.663528] rcu: 61-...0: (7 ticks this GP) idle=33a/1/0x4000 softirq=5287/5287 fqs=5638 [ 850.672833] (detected by 3, t=15005 jiffies, g=81461, q=101) [ 850.678569] Task dump for CPU 61: [ 850.681872] shutdown R running task 0 1 0 0x002a [ 850.688909] Call trace: [ 850.691347] __switch_to+0xe4/0x148 [ 850.694823] 0x25 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1866319/+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 1866319] Re: reboot crash in qla2x00_shutdown()
@Dann Besides, I did not note which d06 I used, and I believe I did not use the production ones. Let me use the beta iso to run again on the production one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866319 Title: reboot crash in qla2x00_shutdown() Status in subiquity: New Status in linux package in Ubuntu: Incomplete Bug description: focal daily live iso (200227) d06 [Steps to Reproduce] 1. Download the daily live iso over http://www.cdimage.ubuntu.com/ubuntu-server/daily-live/20200227/focal-live-server-arm64.iso and boot from the iso 2. Boot into the installation process by selecting "Install Ubuntu Server" 3. Follow the subiquity instruction and update subiquity at the very beginning of the installation[1] 4. Follow the subiquity instruction to complete the installation on reboot. [1] If you don't update it, it will be this bug LP: #1866318 . Prompt of subiquity installation Version 19.12.2+git49.436ee1d7 of the installer is now available (19.10.2 is currently running). [Expected Result] The system reboots and get ready to use. [Actual Result] The system hangs on reboot. Show some of the messages: [FAILED] Failed unmounting /cdrom. [ 790.782440] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [ 790.790955] pstate: 6049 (nZCv daif +PAN -UAO) [ 790.795747] pc : __free_pages+0x28/0x68 [ 790.799578] lr : __iommu_dma_free_pages+0x38/0x58 [ 790.804271] sp : 11eabb00 [ 790.807575] x29: 11eabb00 x28: 803f7abf8ec0 [ 790.812878] x27: x26: 8a3f7b88e130 [ 790.818180] x25: 11156100 x24: 10e10908 [ 790.823481] x23: x22: 803f515ebc80 [ 790.828783] x21: 0010 x20: [ 790.834084] x19: x18: 0010 [ 790.839386] x17: 8158135c x16: db594df8 [ 790.844688] x15: 803f7abf93e8 x14: [ 790.849989] x13: 91eab827 x12: 11eab82f [ 790.855291] x11: 118ef000 x10: [ 790.860592] x9 : 11ae9000 x8 : 07ad [ 790.865894] x7 : 0017 x6 : 11ae8995 [ 790.871196] x5 : 0007 x4 : [ 790.876497] x3 : 11ae8930 x2 : [ 790.881798] x1 : 0034 x0 : [ 790.887101] Call trace: [ 790.889540] __free_pages+0x28/0x68 [ 790.893020] __iommu_dma_free_pages+0x38/0x58 [ 790.897366] __iommu_dma_free+0xb8/0xf8 [ 790.901192] iommu_dma_free+0x48/0x58 [ 790.904848] dma_free_attrs+0xd4/0xf0 [ 790.908546] qla2x00_free_fw_dump+0x58/0xb8 [qla2xxx] [ 790.913616] qla2x00_shutdown+0xd4/0x160 [qla2xxx] [ 790.918402] pci_device_shutdown+0x44/0x88 [ 790.922494] device_shutdown+0x134/0x240 [ 790.926414] kernel_restart_prepare+0x44/0x50 [ 790.930761] kernel_restart+0x20/0x68 [ 790.934414] __do_sys_reboot+0x100/0x228 [ 790.938327] __arm64_sys_reboot+0x2c/0x38 [ 790.942328] el0_svc_common.constprop.0+0xdc/0x1d8 [ 790.947109] el0_svc_handler+0x34/0x90 [ 790.950847] el0_svc+0x10/0x14 [ 790.953898] Code: d503201f 9100d261 52800020 4b0003e0 (b8e0003e) [ 790.960151] ---[ end trace 37539b75957dd46c ]--- [ 790.970536] Unable to handle kernel paging request at virtual address 10075034 [ 790.978440] Mem abort info: [ 790.981223] ESR = 0x9661 [ 790.984267] Exception class = DABT (current EL), IL = 32 bits [ 790.990175] SET = 0, FnV = 0 [ 790.993218] EA = 0, S1PTW = 0 [ 790.996347] Data abort info: [ 790.999217] ISV = 0, ISS = 0x0061 [ 791.003041] CM = 0, WnR = 1 [ 791.005999] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0125b000 [ 791.012689] [10075034] pgd=0a5ff003, pud=0a5fe003, pmd=0a5fd003, pte=00e894110703 [ 850.657602] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 850.663528] rcu: 61-...0: (7 ticks this GP) idle=33a/1/0x4000 softirq=5287/5287 fqs=5638 [ 850.672833] (detected by 3, t=15005 jiffies, g=81461, q=101) [ 850.678569] Task dump for CPU 61: [ 850.681872] shutdown R running task 0 1 0 0x002a [ 850.688909] Call trace: [ 850.691347] __switch_to+0xe4/0x148 [ 850.694823] 0x25 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1866319/+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 1859569] Re: [hns3-0114]net: hns3: fix ETS bandwidth validation bug
** Tags removed: tairadar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859569 Title: [hns3-0114]net: hns3: fix ETS bandwidth validation bug Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Impact] The corresponding ethernet interface could not be up again. [Fix] cherry picked from commit c2d56897819338eb0ba8b93184f7d10329b36653 net: hns3: fix ETS bandwidth validation bug [Test Case] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Steps to Reproduce] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Actual Results] up fail [Expected Results] up ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] This patch fixes it by calling hclge_buffer_alloc to reallocate buffer when pfc_en changes. c2d568978193 net: hns3: fix ETS bandwidth validation bug To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859569/+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 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
** Tags removed: tairadar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+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 1247712] Re: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk
** Also affects: jockey (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: bcmwl (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Saucy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1247712 Title: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk Status in Jockey: Invalid Status in bcmwl package in Ubuntu: Invalid Status in jockey package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: In Progress Status in bcmwl source package in Precise: Invalid Status in jockey source package in Precise: Won't Fix Status in linux-lts-trusty source package in Precise: In Progress Status in bcmwl source package in Saucy: New Status in jockey source package in Saucy: New Status in linux-lts-trusty source package in Saucy: New Status in bcmwl source package in Trusty: Invalid Status in jockey source package in Trusty: In Progress Status in linux-lts-trusty source package in Trusty: In Progress Status in bcmwl package in Baltix: Invalid Bug description: SRU request: Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed. [Impact] Kernel versions higher than 3.8 fail to rebind the Broadcom device to the driver thus compromising system stability. While rebinding is a nice feature it can't come at the cost of system stability. For this reason we'll disable this feature when dealing with Linux >= 3.8 and preserve it in the other cases. [Test Case] Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux- lts-trusty), then use Jockey to install the broadcom wireless driver. Jockey will hang and the system will probably hang on shutdown. [Regression Potential] It should be minimal i.e. there won't be device rebinding on the livecd. This, however, shouldn't be an issue since the open broadcom driver should already work out of the box. Furthermore the test suite now covers this test case. == Description == CID: 201303-13027 Dell Inspiron 5535 CID: 201012-6925 Dell Latitude E6320 CID: 201208-11536 Dell Latitude 6430u Affected chipsets: Broadcom 4365 Broadcom 4313 [14e4:4727] (rev 01) Broadcom 43132 The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on 12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29) Steps: 1. Install Ubuntu 12.04.3 (or 12.04.4) + update 2. Boot to desktop 3. Install the Broadcom STA wireless driver via jockey-gtk Driver cannot be installed, jockey-gtk will stuck at "Downloading and installing driver" The last message from jockey.jog is: unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0 Error message could be found in dmesg: Nov 3 21:34:14 201012-6925 kernel: [ 528.104653] wlc_lcnphy_rx_gain_tbl_free_entry = 5 Nov 3 21:34:14 201012-6925 kernel: [ 528.104863] BUG: unable to handle kernel paging request at a045d020 Nov 3 21:34:14 201012-6925 kernel: [ 528.104906] IP: [] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.104936] PGD 1c0f067 PUD 1c13063 PMD 2ea40067 PTE 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.104967] Oops: 0010 [#1] SMP Nov 3 21:34:14 201012-6925 kernel: [ 528.104988] Modules linked in: lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma] Nov 3 21:34:14 201012-6925 kernel: [ 528.105424] CPU 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105438] Pid: 2695, comm: jockey-backend Tainted: PF O 3.8.0-33-generic #48~precise1-Ubuntu Dell Inc. Latitude E6320/ Nov 3 21:34:14 201012-6925 kernel: [ 528.105493] RIP: 0010:[] [] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.105533] RSP: 0018:88001b405d50 EFLAGS: 00010282 Nov 3 21:34:14 201012-6925 kernel: [ 528.105558] RAX: 0001 RBX: 880031788000 RCX: Nov 3 21:34:14 201012-6925 kernel: [ 528.105590] RDX: RSI: a0861ec0 RDI: 880031788000 Nov 3 21:34:14 201012-6925 kernel: [ 528.105623] RBP: 880
[Kernel-packages] [Bug 1247712] Re: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk
** Changed in: jockey (Ubuntu Precise) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1247712 Title: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk Status in Jockey: Invalid Status in bcmwl package in Ubuntu: Invalid Status in jockey package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: In Progress Status in bcmwl source package in Precise: Invalid Status in jockey source package in Precise: Won't Fix Status in linux-lts-trusty source package in Precise: In Progress Status in bcmwl source package in Trusty: Invalid Status in jockey source package in Trusty: In Progress Status in linux-lts-trusty source package in Trusty: In Progress Status in bcmwl package in Baltix: Invalid Bug description: SRU request: Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed. [Impact] Kernel versions higher than 3.8 fail to rebind the Broadcom device to the driver thus compromising system stability. While rebinding is a nice feature it can't come at the cost of system stability. For this reason we'll disable this feature when dealing with Linux >= 3.8 and preserve it in the other cases. [Test Case] Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux- lts-trusty), then use Jockey to install the broadcom wireless driver. Jockey will hang and the system will probably hang on shutdown. [Regression Potential] It should be minimal i.e. there won't be device rebinding on the livecd. This, however, shouldn't be an issue since the open broadcom driver should already work out of the box. Furthermore the test suite now covers this test case. == Description == CID: 201303-13027 Dell Inspiron 5535 CID: 201012-6925 Dell Latitude E6320 CID: 201208-11536 Dell Latitude 6430u Affected chipsets: Broadcom 4365 Broadcom 4313 [14e4:4727] (rev 01) Broadcom 43132 The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on 12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29) Steps: 1. Install Ubuntu 12.04.3 (or 12.04.4) + update 2. Boot to desktop 3. Install the Broadcom STA wireless driver via jockey-gtk Driver cannot be installed, jockey-gtk will stuck at "Downloading and installing driver" The last message from jockey.jog is: unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0 Error message could be found in dmesg: Nov 3 21:34:14 201012-6925 kernel: [ 528.104653] wlc_lcnphy_rx_gain_tbl_free_entry = 5 Nov 3 21:34:14 201012-6925 kernel: [ 528.104863] BUG: unable to handle kernel paging request at a045d020 Nov 3 21:34:14 201012-6925 kernel: [ 528.104906] IP: [] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.104936] PGD 1c0f067 PUD 1c13063 PMD 2ea40067 PTE 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.104967] Oops: 0010 [#1] SMP Nov 3 21:34:14 201012-6925 kernel: [ 528.104988] Modules linked in: lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma] Nov 3 21:34:14 201012-6925 kernel: [ 528.105424] CPU 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105438] Pid: 2695, comm: jockey-backend Tainted: PF O 3.8.0-33-generic #48~precise1-Ubuntu Dell Inc. Latitude E6320/ Nov 3 21:34:14 201012-6925 kernel: [ 528.105493] RIP: 0010:[] [] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.105533] RSP: 0018:88001b405d50 EFLAGS: 00010282 Nov 3 21:34:14 201012-6925 kernel: [ 528.105558] RAX: 0001 RBX: 880031788000 RCX: Nov 3 21:34:14 201012-6925 kernel: [ 528.105590] RDX: RSI: a0861ec0 RDI: 880031788000 Nov 3 21:34:14 201012-6925 kernel: [ 528.105623] RBP: 88001b405d78 R08: R09: Nov 3 21:34:14 201012-6925 kernel: [ 528.105657] R10: 3684 R11: 0293 R12: 88001b405da0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105690] R13: a08643e0 R14: 880031788098 R15: 8800317880f8 Nov 3 21:34:14 201012-6925 kernel: [
[Kernel-packages] [Bug 1859569] Re: [hns3-0114]net: hns3: fix ETS bandwidth validation bug
Verified via 1. ping and is accessible externally via eth 2. checked the loaded kernel modules and enablement log of dmesg 3. checkbox-cli $ checkbox-cli run com.canonical.certification::ethernet/detect com.canonical.certification::ethernet/info_automated com.canonical.certification::ethernet/info_automated_server Finalizing session that hasn't been submitted anywhere: checkbox-run-2020-03-18T18.30.47 ==[ Results ]=== ☑ : Hardware Manifest ☑ : Detect if at least one ethernet device is detected ☑ : Enumerate available system executables ☑ : Collect information about hardware devices (udev) ☑ : Gather info on current state of network devices ☑ : Provide information about detected ethernet devices ubuntu@scobee:~$ uname -a Linux scobee 4.15.0-92-generic #93-Ubuntu SMP Mon Mar 16 15:40:04 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859569 Title: [hns3-0114]net: hns3: fix ETS bandwidth validation bug Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Impact] The corresponding ethernet interface could not be up again. [Fix] cherry picked from commit c2d56897819338eb0ba8b93184f7d10329b36653 net: hns3: fix ETS bandwidth validation bug [Test Case] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Steps to Reproduce] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Actual Results] up fail [Expected Results] up ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] This patch fixes it by calling hclge_buffer_alloc to reallocate buffer when pfc_en changes. c2d568978193 net: hns3: fix ETS bandwidth validation bug To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859569/+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 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
I also verified 18.04-hwe 5.3.0-42-generic #34~18.04.1-Ubuntu fixes this issue ( 5.3.0-40-generic #32~18.04.1-Ubuntu still has this issue). Verified on d06-1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+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 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
Verified and the bug is fixed. - 4.15.0-92-generic, scobee - 4.15.0-92-generic, d06-2 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+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 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
** Changed in: kunpeng920/ubuntu-18.04 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+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 1859569] Re: [hns3-0114]net: hns3: fix ETS bandwidth validation bug
This patch https://lists.ubuntu.com/archives/kernel- team/2020-March/108124.html has been tested on bionic to look for regression: 1. ping and is accessible externally via eth 2. checked the loaded kernel modules and enablement log of dmesg 3. checkbox-cli ubuntu@scobee:~$ checkbox-cli run com.canonical.certification::ethernet/detect com.canonical.certification::ethernet/info_automated com.canonical.certification::ethernet/info_automated_server Finalizing session that hasn't been submitted anywhere: checkbox-run-2020-03-10T13.13.52 ==[ Results ]=== ☑ : Hardware Manifest ☑ : Detect if at least one ethernet device is detected ☑ : Enumerate available system executables ☑ : Collect information about hardware devices (udev) ☑ : Gather info on current state of network devices ☑ : Provide information about detected ethernet devices ubuntu@scobee:~$ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859569 Title: [hns3-0114]net: hns3: fix ETS bandwidth validation bug Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Impact] The corresponding ethernet interface could not be up again. [Fix] cherry picked from commit c2d56897819338eb0ba8b93184f7d10329b36653 net: hns3: fix ETS bandwidth validation bug [Test Case] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Steps to Reproduce] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Actual Results] up fail [Expected Results] up ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] This patch fixes it by calling hclge_buffer_alloc to reallocate buffer when pfc_en changes. c2d568978193 net: hns3: fix ETS bandwidth validation bug To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859569/+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 1859569] Re: [hns3-0114]net: hns3: fix ETS bandwidth validation bug
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859569 Title: [hns3-0114]net: hns3: fix ETS bandwidth validation bug Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: New Bug description: When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Impact] The corresponding ethernet interface could not be up again. [Fix] cherry picked from commit c2d56897819338eb0ba8b93184f7d10329b36653 net: hns3: fix ETS bandwidth validation bug [Test Case] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Steps to Reproduce] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Actual Results] up fail [Expected Results] up ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] This patch fixes it by calling hclge_buffer_alloc to reallocate buffer when pfc_en changes. c2d568978193 net: hns3: fix ETS bandwidth validation bug To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859569/+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 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
Current upstream status has this fix commit $ git log upstream/master --abbrev-commit --pretty=oneline --grep "net: hns3: pad the short frame before sending to the hardware" 36c67349a1a1 net: hns3: pad the short frame before sending to the hardware $ git tag --list --contains 36c67349a1a1 v5.5 v5.5-rc7 v5.5.1 v5.5.2 v5.5.3 v5.5.4 v5.5.5 v5.5.6 v5.5.7 v5.6-rc1 v5.6-rc2 v5.6-rc3 v5.6-rc4 $ git remote -v upstream git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git (fetch) upstream git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git (push) ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+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 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
The fix is expected to hit eoan 5.3 kernel after this SRU completes $ rmadison -asource linux | grep eoan linux | 5.3.0-18.19| eoan | source linux | 5.3.0-40.32| eoan-security| source linux | 5.3.0-40.32| eoan-updates | source linux | 5.3.0-42.34| eoan-proposed| source $ git log upstream/master-next --abbrev-commit --pretty=oneline --grep "net: hns3: pad the short frame before sending to the hardware" 39d592aa888b net: hns3: pad the short frame before sending to the hardware $ git tag --list --contains 39d592aa888b Ubuntu-5.3.0-41.33 Ubuntu-5.3.0-42.34 Ubuntu-raspi2-5.3.0-1019.21 $ git remote -v upstream git+ssh://taihsian...@git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan (fetch) upstream git+ssh://taihsian...@git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan (push) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+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 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
The fix is expected to land bionic-hwe after this SRU cycle completes --- bionic-hwe kernel tagged Ubuntu-hwe-5.3.0-41.33_18.04.1 and/or Ubuntu- hwe-5.3.0-42.34_18.04.1 have the upstream patch. $ git remote -v lp git+ssh://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic (fetch) lp git+ssh://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic (push) $ git log lp/hwe --abbrev-commit --pretty=oneline --grep "net: hns3: pad the short frame before sending to the hardware" 39d592aa888b net: hns3: pad the short frame before sending to the hardware $ git tag --list --contains 39d592aa888b Ubuntu-hwe-5.3.0-41.33_18.04.1 Ubuntu-hwe-5.3.0-42.34_18.04.1 Ubuntu-raspi2-5.3-5.3.0-1019.21_18.04.1 $ rmadison linux-generic-hwe-18.04 linux-generic-hwe-18.04 | 5.3.0.40.97 | bionic-security | amd64, arm64, armhf, i386, ppc64el, s390x linux-generic-hwe-18.04 | 5.3.0.40.97 | bionic-updates | amd64, arm64, armhf, i386, ppc64el, s390x linux-generic-hwe-18.04 | 5.3.0.42.99 | bionic-proposed | amd64, arm64, armhf, i386, ppc64el, s390x linux-generic-hwe-18.04 | 5.4.0.14.17 | focal | amd64, arm64, armhf, ppc64el, s390x linux-generic-hwe-18.04 | 5.4.0.17.21 | focal-proposed | amd64, arm64, armhf, ppc64el, s390x And "d06-1 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:08:05 UTC 2020" could reproduce this issue. /var/log/syslog will output endless log of message "Mar 3 15:39:35 d06-1 kernel: [ 6305.142251] hns3 :7d:00.2: received event 0x400") -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+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 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
The patch in Eoan is merged over stable channel https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862429 ** Changed in: kunpeng920/upstream-kernel Milestone: linux-v5.3 => linux-v5.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+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 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
** Tags added: tairadar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+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 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
In eoan kernel already.
$ git log --grep="net: hns3: pad the short frame before sending to the hardware"
commit 39d592aa888b3cfe3bca86b524775e4d5b8c96fc
Author: Yunsheng Lin
Date: Wed Jan 15 10:46:45 2020 +0800
net: hns3: pad the short frame before sending to the hardware
BugLink: https://bugs.launchpad.net/bugs/1862429
[ Upstream commit 36c67349a1a1c88b9cf11d7ca7762ababdb38867 ]
The hardware can not handle short frames below or equal to 32
bytes according to the hardware user manual, and it will trigger
a RAS error when the frame's length is below 33 bytes.
This patch pads the SKB when skb->len is below 33 bytes before
sending it to hardware.
Fixes: 76ad4f0ee747 ("net: hns3: Add support of HNS3 Ethernet Driver for
hip08 SoC")
Signed-off-by: Yunsheng Lin
Signed-off-by: Huazhong Tan
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Kamal Mostafa
Signed-off-by: Khalid Elmously
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860320
Title:
[hns3-0120]pad the short frame before sending to the hardware
Status in kunpeng920:
In Progress
Status in kunpeng920 ubuntu-18.04 series:
In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
In Progress
Status in kunpeng920 upstream-kernel series:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
In Progress
Bug description:
The hardware can not handle short frames below or equal to 32
bytes.
[Impact]
The system may hang or endless event log in /var/log/syslog
[Fix]
Cherry-pick or backport the upstream fix
36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before
sending to the hardware
[Test Case]
Send a frame less than 33 bytes.
[Regression Risk]
Low, the patch is only specific to the hns3 driver.
== Original Bug Description ==
[Bug Description]
The hardware can not handle short frames below or equal to 32
bytes according to the hardware user manual, and it will trigger
a RAS error when the frame's length is below 33 bytes.
[Steps to Reproduce]
1.send a frame less than 33 bytes.
[Actual Results]
a RAS occurs
[Expected Results]
no RAS
[Reproducibility]
Inevitably
[Additional information]
Hardware: D06
Firmware: NA
Kernel: NA
[Resolution]
pads the SKB when skb->len is below 33 bytes before sending it to hardware.
net: hns3: pad the short frame before sending to the hardware
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1860320/+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 1854797] Re: bionic/linux-oem: 4.15.0-1066.76 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1854797 Title: bionic/linux-oem: 4.15.0-1066.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Friday, 06. December 2019 22:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854797/+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 1855825] Re: When connecting to wifi with the proposed linux-oem kernel , the system hangs
** Description changed: - Dell XPS 13 7390 (CID 201906-27119) + Dell XPS 13 7390 (CID 201906-27119)(connected with a SAL TBT docking device) Pre-load Ubuntu kernel: linux-oem 4.15.0-1066.76-oem [Description] The system hangs when connecting to wifi [Steps to Reproduce] Connect to bg-wifi over the wifi applet of your desktop. Select the SSID and then being prompted for a password. The system hangs immediately after entering the password. Reproducing Rate: 100% [Expected Result] Wifi works and the system keeps running. [Actual Result] System hangs. [Additional Information] 4.15.0-1066 oem kernel looks good for this test case. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1066.70 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Tue Dec 10 13:47:54 2019 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 +  # This is the distribution channel descriptor for the OEM CDs +  # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor +  canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-10-08 (63 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1855825 Title: When connecting to wifi with the proposed linux-oem kernel , the system hangs Status in linux-meta-oem package in Ubuntu: New Bug description: Dell XPS 13 7390 (CID 201906-27119)(connected with a SAL TBT docking device) Pre-load Ubuntu kernel: linux-oem 4.15.0-1066.76-oem [Description] The system hangs when connecting to wifi [Steps to Reproduce] Connect to bg-wifi over the wifi applet of your desktop. Select the SSID and then being prompted for a password. The system hangs immediately after entering the password. Reproducing Rate: 100% [Expected Result] Wifi works and the system keeps running. [Actual Result] System hangs. [Additional Information] 4.15.0-1066 oem kernel looks good for this test case. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1066.70 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Tue Dec 10 13:47:54 2019 DistributionChannelDescriptor:  # This is the distribution channel descriptor for the OEM CDs  # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor  canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-10-08 (63 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem/+bug/1855825/+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 1855825] Re: When connecting to wifi with the proposed linux-oem kernel , the system hangs
** Attachment added: "var.log.201906-27119-191210tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem/+bug/1855825/+attachment/5311303/+files/var.log.201906-27119-191210tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1855825 Title: When connecting to wifi with the proposed linux-oem kernel , the system hangs Status in linux-meta-oem package in Ubuntu: New Bug description: Dell XPS 13 7390 (CID 201906-27119) Pre-load Ubuntu kernel: linux-oem 4.15.0-1066.76-oem [Description] The system hangs when connecting to wifi [Steps to Reproduce] Connect to bg-wifi over the wifi applet of your desktop. Select the SSID and then being prompted for a password. The system hangs immediately after entering the password. Reproducing Rate: 100% [Expected Result] Wifi works and the system keeps running. [Actual Result] System hangs. [Additional Information] 4.15.0-1066 oem kernel looks good for this test case. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1066.70 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Tue Dec 10 13:47:54 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-10-08 (63 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem/+bug/1855825/+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 1855825] [NEW] When connecting to wifi with the proposed linux-oem kernel , the system hangs
Public bug reported: Dell XPS 13 7390 (CID 201906-27119) Pre-load Ubuntu kernel: linux-oem 4.15.0-1066.76-oem [Description] The system hangs when connecting to wifi [Steps to Reproduce] Connect to bg-wifi over the wifi applet of your desktop. Select the SSID and then being prompted for a password. The system hangs immediately after entering the password. Reproducing Rate: 100% [Expected Result] Wifi works and the system keeps running. [Actual Result] System hangs. [Additional Information] 4.15.0-1066 oem kernel looks good for this test case. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1066.70 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Tue Dec 10 13:47:54 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-10-08 (63 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-oem (Ubuntu) Importance: Undecided Status: New ** Tags: 201906-27119 amd64 apport-bug bionic package-from-proposed taipei-lab uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1855825 Title: When connecting to wifi with the proposed linux-oem kernel , the system hangs Status in linux-meta-oem package in Ubuntu: New Bug description: Dell XPS 13 7390 (CID 201906-27119) Pre-load Ubuntu kernel: linux-oem 4.15.0-1066.76-oem [Description] The system hangs when connecting to wifi [Steps to Reproduce] Connect to bg-wifi over the wifi applet of your desktop. Select the SSID and then being prompted for a password. The system hangs immediately after entering the password. Reproducing Rate: 100% [Expected Result] Wifi works and the system keeps running. [Actual Result] System hangs. [Additional Information] 4.15.0-1066 oem kernel looks good for this test case. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1066.70 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Tue Dec 10 13:47:54 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-10-08 (63 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem/+bug/1855825/+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 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
The dkms fix of LP: 1854156 has been released. We also leveraged some of the previous testing as the result of the comment#9. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852306 Title: xenial/linux: 4.4.0-170.199 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Updates phase-changed: Monday, 02. December 2019 04:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) promote-to-updates: Pending -- ready to copy trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+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 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
** Changed in: oem-priority Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Other Affected Platforms] Dell Inspiron 13-7378 (201605-22329) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.49745
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
A dkms fix in on the way to upload to the archive. It should land in time before the scheduled release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852306 Title: xenial/linux: 4.4.0-170.199 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+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 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
** Description changed: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) - [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) + [Other Affected Platforms] + Dell Inspiron 13-7378 (201605-22329) + + [Additional Info] I was sometimes able to catch the following kernel oops - Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497457] ---[ end trace 87c55fce1375aae8 ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-170-generic 4.4.0-170.199 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Wed Nov 27 20:34:01 2019 DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more
[Kernel-packages] [Bug 1854010] Re: bionic/linux-raspi2: 4.15.0-1052.56 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/raspi2/4.15.0-1052.56/raspi2-4.15-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1854010 Title: bionic/linux-raspi2: 4.15.0-1052.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 27. November 2019 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854009 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854010/+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 1854013] Re: bionic/linux-snapdragon: 4.15.0-1069.76 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/snapdragon/4.15.0-1069.76/snapdragon-4.15-proposed- published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1854013 Title: bionic/linux-snapdragon: 4.15.0-1069.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 27. November 2019 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1854011 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854013/+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 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/eoan/5.3.0-24.26/eoan- proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852232 Title: eoan/linux: 5.3.0-24.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed 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 -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1854020 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1854006 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+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 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852232 Title: eoan/linux: 5.3.0-24.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed 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 -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1854020 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1854006 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+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 1852287] Re: xenial/linux-deeplens: 4.15.0-1013.13 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/deeplens/4.15.0-1013.13 /deeplens-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852287 Title: xenial/linux-deeplens: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854026 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Testing phase-changed: Friday, 22. November 2019 17:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852287/+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 1852233] Re: disco/linux-raspi2: 5.0.0-1023.24 -proposed tracker
The image is not ready. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1852233 Title: disco/linux-raspi2: 5.0.0-1023.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 15. November 2019 08:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852233/+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 1852249] Re: disco/linux-snapdragon: 5.0.0-1027.29 -proposed tracker
The image is not ready. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1852249 Title: disco/linux-snapdragon: 5.0.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 15. November 2019 08:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852249/+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 1854010] Re: bionic/linux-raspi2: 4.15.0-1052.56 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1854010 Title: bionic/linux-raspi2: 4.15.0-1052.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 27. November 2019 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854009 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854010/+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 1852287] Re: xenial/linux-deeplens: 4.15.0-1013.13 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852287 Title: xenial/linux-deeplens: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854026 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Testing phase-changed: Friday, 22. November 2019 17:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852287/+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 1852302] Re: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/snapdragon/4.4.0-1130.138/snapdragon-4.4-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1852302 Title: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1852306 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 20. November 2019 07:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1852301 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852302/+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 1852300] Re: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/raspi2/4.4.0-1126.135/raspi2-4.4-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1852300 Title: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 20. November 2019 02:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852300/+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 1854013] Re: bionic/linux-snapdragon: 4.15.0-1069.76 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1854013 Title: bionic/linux-snapdragon: 4.15.0-1069.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 27. November 2019 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1854011 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854013/+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 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
The following tests were perform: - tested with 4.4.0-169 (Pass) - re-install the system, dist-upgrade, tested with 4.4.0-170 (Fail, still reproducible) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-signed source package in Xenial: New Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 6
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
A potential regression was found https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854156 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852306 Title: xenial/linux: 4.4.0-170.199 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+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 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-genericproposed kernel
component information ubuntu@201701-25364:~$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5918] (rev 05) 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 05) 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) 00:15.0 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 [8086:a160] (rev 31) 00:15.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #2 [8086:a162] (rev 31) 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31) 00:16.3 Serial controller [0700]: Intel Corporation 100 Series/C230 Series Chipset Family KT Redirection [8086:a13d] (rev 31) 00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31) 00:1b.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 [8086:a167] (rev f1) 00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #6 [8086:a115] (rev f1) 00:1c.6 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #7 [8086:a116] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #13 [8086:a11c] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation C236 Chipset LPC/eSPI Controller [8086:a149] (rev 31) 00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] (rev 31) 00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller [8086:a170] (rev 31) 00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] (rev 31) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-LM [8086:15b7] (rev 31) 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100 Mobile] [1002:67c0] 01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 580] [1002:aaf0] 02:00.0 Non-Volatile memory controller [0108]: Toshiba America Info Systems XG4 NVMe SSD Controller [1179:0115] (rev 01) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01) 04:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-genericproposed kernel Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_mid
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-genericproposed kernel
Add var log tarball 201701-25364-191127.tar.gz ** Attachment added: "201701-25364-191127.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854156/+attachment/5308141/+files/201701-25364-191127.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-genericproposed kernel Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x
[Kernel-packages] [Bug 1854156] [NEW] [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-genericproposed kernel
Public bug reported: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497457] ---[ end trace 87c55fce1375aae8 ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-170-generic 4.4.0-170.199 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Wed Nov 27 20:34:01 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2019-11-27 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial
