[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967957 Title: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967957 Title: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967957 Title: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967957 Title: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967957 Title: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967957 Title: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot with virtual
CD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) live server arm64 iso kernel panic during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940112] Re: missing dependency of qemu-efi-aarch64 when testing arm platforms
** Changed in: plainbox-provider-checkbox Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940112 Title: missing dependency of qemu-efi-aarch64 when testing arm platforms To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1940112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 [
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946773] Re: "An error occurred. Press enter to start a shell"
var log collected with impish rc image (211013) with mt. jade (howzit). ** Attachment added: "var-log-impish-rc-20211013-bmc-vmedia.tar.gz" https://bugs.launchpad.net/subiquity/+bug/1946773/+attachment/5532831/+files/var-log-impish-rc-20211013-bmc-vmedia.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946773 Title: "An error occurred. Press enter to start a shell" To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1946773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946773] Re: "An error occurred. Press enter to start a shell"
"20211012 arm64 ISO" could reproduce the same issue with Mt. Jade (howzit) var/log/installer/subiquity-server-debug.log shows subiquity timeout: 2021-10-13 12:47:18,086 ERROR subiquity.server.server:391 top level error Traceback (most recent call last): File "/snap/subiquity/2824/lib/python3.8/site-packages/subiquity/server/server.py", line 579, in start await self.wait_for_cloudinit() File "/snap/subiquity/2824/lib/python3.8/site-packages/subiquity/server/server.py", line 487, in wait_for_cloudinit status_cp = await asyncio.wait_for(status_coro, 600) File "/snap/subiquity/2824/usr/lib/python3.8/asyncio/tasks.py", line 501, in wait_for raise exceptions.TimeoutError() asyncio.exceptions.TimeoutError ** Attachment added: "var_log.tar.gz" https://bugs.launchpad.net/subiquity/+bug/1946773/+attachment/5532478/+files/var_log.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946773 Title: "An error occurred. Press enter to start a shell" To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1946773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945012] Re: [Impish Beta][arm64] installer has python traceback
Hi Michael. Yes I am OK. Thank you for your time and effort! I will re- open the issue and provide more comprehensive log files when the issue shows up again. Please feel free to close it now. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945012 Title: [Impish Beta][arm64] installer has python traceback To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1945012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945012] Re: [Impish Beta][arm64] installer has python traceback
I did not manage to reproduce this issue with both iso (2 out of 2 passed via vMedia) and pxe (1 out of 1 passed) installation. My hypothesis: The boot process on the day I raised this issue at the bios stage of my machine (kreiken) is much slower than today, and it (the bios) seemed to check some usb block device several times. I did not notice this kind of usb block device bios check today. Maybe a flaky block device was re-formatted later for maas deployment or something, so subiquity is happy with the block device. Or the block device is just dead, so the block detection simply ignores to use it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945012 Title: [Impish Beta][arm64] installer has python traceback To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1945012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945012] Re: [Impish Beta][arm64] installer has python traceback
I think I could collect the log via the console message redirection. I will update the information later on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945012 Title: [Impish Beta][arm64] installer has python traceback To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1945012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945012] Re: [Impish Beta][arm64] installer has python traceback
@dbungert did you suggest any way to pull full /var/log/installer/subiquity-server-debug.log ? I tried scp (to copy the target to my local) and pastebinit (to upload the log file), but they both did not manage to do it. I could only remotely access the machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945012 Title: [Impish Beta][arm64] installer has python traceback To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1945012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945012] Re: [Impish Beta][arm64] installer has python traceback
I used maas 2.9 snap (2.9.3~beta2 (9200-g.43e4a0607) to deploy the same machine, and it could successfully deploy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945012 Title: [Impish Beta][arm64] installer has python traceback To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1945012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945012] Re: [Impish Beta][arm64] installer has python traceback
I tried to pxe installation by following this steps https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via- uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 and it brought up similar error. Reproducing rate: 5 out of 5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945012 Title: [Impish Beta][arm64] installer has python traceback To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1945012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945012] [NEW] [Impish Beta][arm64] installer has python traceback
Public bug reported: iso: impish beta http://cdimage.ubuntu.com/releases/21.10/beta/ubuntu-21.10-beta-live-server-arm64.iso hardware: taishan2280v2 (kreiken) == Steps to Reproduce == 1. Boot impish beta with the iso (via vMedia of BMC) 2. subiquity shows up. Answer questions. == Expected Result == I can walk through all questions == Actual Result == Traceback shows up (maybe in right after answering locale or right before block device detection) and the installer prompt re-spawns. === message snippet from /var/log/installer/subiquity-server- debug.log.3844 of the installer shell === After the installer prompt re-spawned, I use "Enter shell" to dump the log shown below. 2021-09-24 19:09:59,880 INFO root:39 finish: subiquity/Meta/client_variant_POST: SUCCESS: 200 null 2021-09-24 19:09:59,881 INFO aiohttp.access:206 [24/Sep/2021:19:09:59 +] "POST /meta/client_variant?variant=%22server%22 HTTP/1.1" 200 195 "-" "Python/3.6 aiohttp/3.7.4.post0" 2021-09-24 19:09:59,882 INFO root:39 start: subiquity/Meta/status_GET: 2021-09-24 19:09:59,883 DEBUG root:39 start: subiquity/Locale/GET: 2021-09-24 19:09:59,883 DEBUG root:39 finish: subiquity/Locale/GET: SUCCESS: 200 "en_GB.UTF-8" 2021-09-24 19:09:59,883 INFO aiohttp.access:206 [24/Sep/2021:19:09:59 +] "GET /locale HTTP/1.1" 200 205 "-" "Python/3.6 aiohttp/3.7.4.post0" 2021-09-24 19:10:00,123 INFO root:39 finish: subiquity/Meta/status_GET: SUCCESS: 500 Traceback (most recent call last): File "/snap/subiquity/2654/lib/python3.6... 2021-09-24 19:10:00,124 DEBUG subiquity.server.server:369 request to /meta/status?cur=%22ERROR%22 crashed Traceback (most recent call last): File "/snap/subiquity/2654/lib/python3.6/site-packages/subiquity/common/api/server.py", line 123, in handler result = await implementation(**args) File "/snap/subiquity/2654/lib/python3.6/site-packages/subiquity/server/server.py", line 87, in status_GET await self.app.state_event.wait() File "/snap/subiquity/2654/usr/lib/python3.6/asyncio/locks.py", line 283, in wait yield from fut concurrent.futures._base.CancelledError 2021-09-24 19:10:00,124 ERROR aiohttp.server:393 Error handling request Traceback (most recent call last): File "/snap/subiquity/2654/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 422, in _handle_request resp = await self._request_handler(request) File "/snap/subiquity/2654/lib/python3.6/site-packages/aiohttp/web_app.py", line 499, in _handle resp = await handler(request) File "/snap/subiquity/2654/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 119, in impl return await handler(request) File "/snap/subiquity/2654/lib/python3.6/site-packages/subiquity/server/server.py", line 375, in middleware ErrorReportRef, report.ref()) AttributeError: 'NoneType' object has no attribute 'ref' ProblemType: Bug DistroRelease: Ubuntu 21.10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri Sep 24 19:15:55 2021 Snap: subiquity 21.08.2 () Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: subiquity Importance: Undecided Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-bug arm64 impish uec-images ** Also affects: subiquity Importance: Undecided Status: New ** Description changed: iso: impish beta http://cdimage.ubuntu.com/releases/21.10/beta/ubuntu-21.10-beta-live-server-arm64.iso - hardware: taishan2280v2 + hardware: taishan2280v2 (kreiken) == Steps to Reproduce == 1. Boot impish beta with the iso (via vMedia of BMC) 2. subiquity shows up. Answer questions. == Expected Result == I can walk through all questions == Actual Result == Traceback shows up (maybe in right after answering locale or right before block device detection) and the installer prompt re-spawns. - - === message snippet from /var/log/installer/subiquity-server-debug.log.3844 of the installer shell === + === message snippet from /var/log/installer/subiquity-server- + debug.log.3844 of the installer shell === After the installer prompt re-spawned, I use "Enter shell" to dump the log shown below. 2021-09-24 19:09:59,880 INFO root:39 finish: subiquity/Meta/client_variant_POST: SUCCESS: 200 null 2021-09-24 19:09:59,881 INFO aiohttp.access:206 [24/Sep/2021:19:09:59 +] "POST /meta/client_variant?variant=%22server%22 HTTP/1.1" 200 195 "-" "Python/3.6 aiohttp/3.7.4.post0" 2021-09-24 19:09:59,882 INFO root:39 start: subiquity/Meta/status_GET: 2021-09-24 19:09:59,883 DEBUG root:39 start: subiquity/Locale/GET: 2021-09-24 19:09:59,883 DEBUG root:39 finish: subiquity/Locale/GET: SUCCESS: 200 "en_GB.UTF-8" 2021-09-24 19:09:59,883 INFO aiohttp.access:206 [24/Sep/2021:19:09:59 +] "GET /locale HTTP/1.1" 200 205 "-" "Python/3.6
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911376 Title: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace) To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1911376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858590] Re: fwupdaa64.efi crashes on startup
A quick note of the current status: on bionic (4.15 kernel) we are still looking forward to bionic re-uploading if possible because the uploaded version[1] could still reproduce this issue. [1] 1.2.10-1ubuntu2~ubuntu18.04.5 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858590 Title: fwupdaa64.efi crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1858590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858590] Re: fwupdaa64.efi crashes on startup
** Summary changed: - fwupaa64.efi crashes on startup + fwupdaa64.efi crashes on startup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858590 Title: fwupdaa64.efi crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1858590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867588 Title: [SFC-0316]sync mainline kernel 5.7rc1 SFC patchset into ubuntu HWE kernel branch To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900773] Re: ARM servers timeout downloading initrd
Groovy rc 20201022 daily image could reproduce on d05 (d05-1) and d06 (kreiken). Besides, the lz workaround still works on both of the platforms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900773 Title: ARM servers timeout downloading initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1900773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900773] Re: thunderx CRB systems tftp timeout downloading initrd
Repacking initrd as initrd.lz is a working workaround on d05. By using initrd.lz, I could not reproduce this issue on d05-4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900773 Title: thunderx CRB systems tftp timeout downloading initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1900773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900773] Re: thunderx CRB systems tftp timeout downloading initrd
My apologies. The comment#9 https://bugs.launchpad.net/ubuntu/+source /livecd-rootfs/+bug/1900773/comments/9 used the grubnetaa64.efi from focal http://ports.ubuntu.com/ubuntu- ports/dists/focal/main/uefi/grub2-arm64/current/grubnetaa64.efi.signed If d05 (d05-4) uses the groovy grub, it COULD reproduce this issue as well. So I would say the testing result of d05 is the same as d06 by @Ike. - grub from focal ---> not reproduce this issue - grub from groovy --> able to reproduce this issue My next will be: - hide comment#9 to not confuse people - also try the initrd.lzma workaround -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900773 Title: thunderx CRB systems tftp timeout downloading initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1900773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900773] Re: thunderx CRB systems tftp timeout downloading initrd
I tried 20201021 Groovy daily live with Hisilicon d05 via PXE, and I did NOT reproduce this issue. [Post-installation Information] ubuntu@d05-4-20-10-rc-102021-pxe-tai-1:~$ cat /var/log/installer/media-info ; echo ; uname -a; lsb_release -a Ubuntu-Server 20.10 "Groovy Gorilla" - Release arm64 (20201021) Linux d05-4-20-10-rc-102021-pxe-tai-1 5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:33:30 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.10 Release:20.10 Codename: groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900773 Title: thunderx CRB systems tftp timeout downloading initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1900773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895922] Re: maas could not deploy a kvm-based vm via virsh
@Patricia I also tried to deploy scalebot charm and use some VMs (scalebot-dev-controller2 and 3). They are able to deploy now. Thanks for looking this issue, and thanks @Ryan for your helpful information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895922 Title: maas could not deploy a kvm-based vm via virsh To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1895922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895922] Re: maas could not deploy a kvm-based vm via virsh
** Description changed:
Curtin process failed during MaaS deployment. The infrastructure worked
well until ~3 weeks ago.
-
[Steps to Reproduce]
1. Enlist and commission a KVM-based VM in MaaS 2.8.2 (8577-g.a3e674063)
2. Deploy the VM node
+
+ reproducing environment: nodes named after "scalebot-dev-controller"
+ prefix in tremont lab maas.
+
[Expected Result]
1. The VM is deployed
[Actual Result]
Curtin failed during the deployment
Here is the error message:
+ Generating grub debconf_selections for devices=['/dev/vda'] uefi=False
+ finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: FAIL:
installing grub to target devices
+ finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: FAIL:
configuring target system bootloader
+ finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL:
curtin command curthooks
+ Traceback (most recent call last):
+ File "/curtin/curtin/commands/main.py", line 202, in main
+ ret = args.func(args)
+ File "/curtin/curtin/commands/curthooks.py", line 1770, in curthooks
+ builtin_curthooks(cfg, target, state)
+ File "/curtin/curtin/commands/curthooks.py", line 1736, in
builtin_curthooks
+ setup_grub(cfg, target, osfamily=osfamily)
+ File "/curtin/curtin/commands/curthooks.py", line 689, in setup_grub
+ configure_grub_debconf(instdevs, target, uefi_bootable)
+ File "/curtin/curtin/commands/curthooks.py", line 509, in
configure_grub_debconf
+ link = block.disk_to_byid_path(dev)
+ File "/curtin/curtin/block/__init__.py", line 869, in
disk_to_byid_path
+ mapping = get_dev_disk_byid()
+ File "/curtin/curtin/block/__init__.py", line 861, in
get_dev_disk_byid
+ return _get_dev_disk_by_prefix('/dev/disk/by-id')
+ File "/curtin/curtin/block/__init__.py", line 846, in
_get_dev_disk_by_prefix
+ for path in os.listdir(prefix)]
+ FileNotFoundError: [Errno 2] No such file or directory:
'/dev/disk/by-id'
+ [Errno 2] No such file or directory: '/dev/disk/by-id'
- Generating grub debconf_selections for devices=['/dev/vda'] uefi=False
- finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: FAIL:
installing grub to target devices
- finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: FAIL:
configuring target system bootloader
- finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL:
curtin command curthooks
- Traceback (most recent call last):
- File "/curtin/curtin/commands/main.py", line 202, in main
- ret = args.func(args)
- File "/curtin/curtin/commands/curthooks.py", line 1770, in curthooks
- builtin_curthooks(cfg, target, state)
- File "/curtin/curtin/commands/curthooks.py", line 1736, in
builtin_curthooks
- setup_grub(cfg, target, osfamily=osfamily)
- File "/curtin/curtin/commands/curthooks.py", line 689, in setup_grub
- configure_grub_debconf(instdevs, target, uefi_bootable)
- File "/curtin/curtin/commands/curthooks.py", line 509, in
configure_grub_debconf
- link = block.disk_to_byid_path(dev)
- File "/curtin/curtin/block/__init__.py", line 869, in
disk_to_byid_path
- mapping = get_dev_disk_byid()
- File "/curtin/curtin/block/__init__.py", line 861, in
get_dev_disk_byid
- return _get_dev_disk_by_prefix('/dev/disk/by-id')
- File "/curtin/curtin/block/__init__.py", line 846, in
_get_dev_disk_by_prefix
- for path in os.listdir(prefix)]
- FileNotFoundError: [Errno 2] No such file or directory:
'/dev/disk/by-id'
- [Errno 2] No such file or directory: '/dev/disk/by-id'
-
-
- VM kernel: Linux scalebot-dev-controller5 4.15.0-117-generic #118-Ubuntu SMP
Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
+ VM kernel: Linux scalebot-dev-controller5 4.15.0-117-generic #118-Ubuntu
+ SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: curtin (not installed)
ProcVersionSignature: User Name 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
Date: Thu Sep 17 04:38:32 2020
SourcePackage: curtin
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
Curtin process failed during MaaS deployment. The infrastructure worked
well until ~3 weeks ago.
[Steps to Reproduce]
1. Enlist and commission a KVM-based VM in MaaS 2.8.2 (8577-g.a3e674063)
2. Deploy the VM node
- reproducing environment: nodes named after
[Bug 1895922] Re: maas could not deploy a kvm-based vm via virsh
There were deployed kvm nodes and they are running well, so I inclined to think the kvm host and its communication with maas are both good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895922 Title: maas could not deploy a kvm-based vm via virsh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1895922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895922] Re: maas could not deploy a kvm-based vm via virsh
More logs from curtin and /var/log ** Attachment added: "lp1895922-01.tar.gz" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1895922/+attachment/5411540/+files/lp1895922-01.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895922 Title: maas could not deploy a kvm-based vm via virsh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1895922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895922] Re: maas could not deploy a kvm-based vm via virsh
The log file from comment1 was fetched in the vm node by logging into the target deployment node. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895922 Title: maas could not deploy a kvm-based vm via virsh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1895922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895922] Re: maas could not deploy a kvm-based vm via virsh
I did see the /dev/disk/by-id folder. However, there is /dev/disk/by- uuid in the vm node instead: ubuntu@scalebot-dev-controller5:~$ ls /dev/ blockecryptfs initctl loop2 mem ppp shm tty1 tty17 tty24 tty31 tty39 tty46 tty53 tty60 ttyS1 ttyS17 ttyS24 ttyS31 uhid vcs5 vcsa6 zfs btrfs-controlfd input loop3 memory_bandwidthpsaux snapshot tty10 tty18 tty25 tty32 tty4 tty47 tty54 tty61 ttyS10 ttyS18 ttyS25 ttyS4 uinput vcs6 vda bus full kmsg loop4 mqueue ptmx snd tty11 tty19 tty26 tty33 tty40 tty48 tty55 tty62 ttyS11 ttyS19 ttyS26 ttyS5 urandom vcsa vda1 char fuse lightnvm loop5 net pts stderrtty12 tty2 tty27 tty34 tty41 tty49 tty56 tty63 ttyS12 ttyS2 ttyS27 ttyS6 vcs vcsa1 vfio console hpet log loop6 network_latency random stdin tty13 tty20 tty28 tty35 tty42 tty5 tty57 tty7 ttyS13 ttyS20 ttyS28 ttyS7 vcs1 vcsa2 vga_arbiter core hugepages loop-control loop7 network_throughput rfkill stdouttty14 tty21 tty29 tty36 tty43 tty50 tty58 tty8 ttyS14 ttyS21 ttyS29 ttyS8 vcs2 vcsa3 virtio-ports cpu_dma_latency hwrng loop0 mapper nullrtc tty tty15 tty22 tty3 tty37 tty44 tty51 tty59 tty9 ttyS15 ttyS22 ttyS3 ttyS9 vcs3 vcsa4 vport0p1 disk i2c-0 loop1 mcelog portrtc0 tty0 tty16 tty23 tty30 tty38 tty45 tty52 tty6 ttyS0 ttyS16 ttyS23 ttyS30 ttyprintk vcs4 vcsa5 zero ubuntu@scalebot-dev-controller5:~$ ls /dev/disk by-label by-partuuid by-path by-uuid ubuntu@scalebot-dev-controller5:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895922 Title: maas could not deploy a kvm-based vm via virsh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1895922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895922] [NEW] maas could not deploy a kvm-based vm via virsh
Public bug reported:
Curtin process failed during MaaS deployment. The infrastructure worked
well until ~3 weeks ago.
[Steps to Reproduce]
1. Enlist and commission a KVM-based VM in MaaS 2.8.2 (8577-g.a3e674063)
2. Deploy the VM node
[Expected Result]
1. The VM is deployed
[Actual Result]
Curtin failed during the deployment
Here is the error message:
Generating grub debconf_selections for devices=['/dev/vda'] uefi=False
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub:
FAIL: installing grub to target devices
finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: FAIL:
configuring target system bootloader
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin
command curthooks
Traceback (most recent call last):
File "/curtin/curtin/commands/main.py", line 202, in main
ret = args.func(args)
File "/curtin/curtin/commands/curthooks.py", line 1770, in curthooks
builtin_curthooks(cfg, target, state)
File "/curtin/curtin/commands/curthooks.py", line 1736, in
builtin_curthooks
setup_grub(cfg, target, osfamily=osfamily)
File "/curtin/curtin/commands/curthooks.py", line 689, in setup_grub
configure_grub_debconf(instdevs, target, uefi_bootable)
File "/curtin/curtin/commands/curthooks.py", line 509, in
configure_grub_debconf
link = block.disk_to_byid_path(dev)
File "/curtin/curtin/block/__init__.py", line 869, in
disk_to_byid_path
mapping = get_dev_disk_byid()
File "/curtin/curtin/block/__init__.py", line 861, in
get_dev_disk_byid
return _get_dev_disk_by_prefix('/dev/disk/by-id')
File "/curtin/curtin/block/__init__.py", line 846, in
_get_dev_disk_by_prefix
for path in os.listdir(prefix)]
FileNotFoundError: [Errno 2] No such file or directory:
'/dev/disk/by-id'
[Errno 2] No such file or directory: '/dev/disk/by-id'
VM kernel: Linux scalebot-dev-controller5 4.15.0-117-generic #118-Ubuntu SMP
Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: curtin (not installed)
ProcVersionSignature: User Name 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
Date: Thu Sep 17 04:38:32 2020
SourcePackage: curtin
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic uec-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895922
Title:
maas could not deploy a kvm-based vm via virsh
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1895922/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890884
Title:
kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06
arm64 arch
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1890884/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890884 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1890884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890867 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890884
Title:
kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06
arm64 arch
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1890884/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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]
[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:
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890867 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890867 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873489] Re: lscpu cache information is incorrect with focal on arm 64-bit platform (ThunderX2)
Hi Mauricio, thank you for providing the information that I was not aware of. It's very clear and helpful for me. Because the ThunderX2 is unavailable for me currently, I verified the output format with Focal on an arm d06 cpu, which is able to reproduce the "issue" (my own host name "scobee"). It is exactly what you have said. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873489 Title: lscpu cache information is incorrect with focal on arm 64-bit platform (ThunderX2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1873489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873489] [NEW] lscpu cache information is incorrect with focal on arm 64-bit platform (ThunderX2)
Public bug reported: Platform: Cavium Sabre Marvell ThunderX2 The L1/L2/L3 cache output by "lscpu" is incorrect, and differes from the output with bionic. [Steps to Reproduce] 1. Install ubuntu server (focal) on Sabre 2. lspci [Expected Result] L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:32768K [Actual Result] L1d cache: 1.8 MiB L1i cache: 1.8 MiB L2 cache:14 MiB L3 cache:64 MiB [More Information] 1. eoan could reproduce this issue. 2. bionic-hwe could not reproduce this issue (5.3.0-46-generic #38~18.04.1-Ubuntu) 3. with focal, check the cpu cache directly from the virtual devices and the cache information looks good: $ cat /sys/devices/system/cpu/cpu0/cache/index0/level /sys/devices/system/cpu/cpu0/cache/index0/size 1 32K 4. More information about the system which could reproduce the issue: ubuntu@apollo:~$ cat /sys/devices/system/cpu/cpu0/cache/index0/level /sys/devices/system/cpu/cpu0/cache/index0/size 1 32K ubuntu@apollo:~$ uname -a Linux apollo 5.4.0-24-generic #28-Ubuntu SMP Thu Apr 9 22:17:51 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ubuntu@apollo:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal ubuntu@apollo:~$ dpkg -l util-linux Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii util-linux 2.34-0.1ubuntu9 arm64miscellaneous system utilities ubuntu@apollo:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: util-linux 2.34-0.1ubuntu9 ProcVersionSignature: User Name 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic aarch64 ApportVersion: 2.20.11-0ubuntu26 Architecture: arm64 CasperMD5CheckResult: skip Date: Fri Apr 17 16:00:13 2020 SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873489 Title: lscpu cache information is incorrect with focal on arm 64-bit platform (ThunderX2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1873489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
Marking as "won't fix" because the getconf and the kernel are working as expected. (Please refer to comment 11 for details) ** Changed in: kunpeng920 Status: In Progress => Won't Fix ** Changed in: kunpeng920/ubuntu-18.04 Status: In Progress => Won't Fix ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: New => Won't Fix ** Changed in: kunpeng920/ubuntu-20.04 Status: New => Won't Fix ** Changed in: glibc (Ubuntu) Status: New => Won't Fix ** Changed in: kunpeng920/upstream-kernel Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
eoan on scobee could reproduce this issue: ubuntu@scobee:~$ apt-cache policy libc-bin; uname -a; lsb_release -a; getconf LEVEL1_ICACHE_SIZE libc-bin: Installed: 2.30-0ubuntu2.1 Candidate: 2.30-0ubuntu2.1 Version table: *** 2.30-0ubuntu2.1 500 500 http://ports.ubuntu.com/ubuntu-ports eoan-updates/main arm64 Packages 100 /var/lib/dpkg/status 2.30-0ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports eoan/main arm64 Packages Linux scobee 5.3.0-46-generic #38-Ubuntu SMP Fri Mar 27 17:32:45 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
focal on scobee could reproduce this issue: ubuntu@scobee:~$ apt-cache policy libc-bin libc-bin: Installed: 2.31-0ubuntu7 Candidate: 2.31-0ubuntu7 Version table: *** 2.31-0ubuntu7 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages 100 /var/lib/dpkg/status ubuntu@scobee:~$ uname -a; lsb_release -a; getconf LEVEL1_ICACHE_SIZE Linux scobee 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:12:38 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
This is not a kernel issue. I would suggest "won't fix" for this issue from technical point of view: 1) This is not a bug but a feature restriction of the tool getconf[1]. We could only retrieve the cpu cache information in another way, which is not what getconf is using now. Because the upstream does not update the retrieve method, we could not avoid to re-implement the retrieve method. Besides, 0 in this case is expected because it means "no information available".[2] 2) This is not a kernel issue because kernel still provides the corresponding cpu information. lscpu could get the expected information because lscpu retrives the cache information in another way. lspcu gets the information via Linux virtual filesystem, including /proc/cpuinfo and /sys/devices/system/cpu, and these virtual devices/files provided by Linux kernel show the corresponding kernel is working and working well. I would suggest to use lscpu in your case to retrieve L2/L3 cache information instead of getconf. [1] According to the source code where getconf retrieves cpu cache information sysdeps/unix/sysv/linux/aarch64/sysconf.c:__sysconf /* Unfortunately, the registers that contain the actual cache info (CCSIDR_EL1, CLIDR_EL1, and CSSELR_EL1) are protected by the Linux kernel (though they need not have been). However, CTR_EL0 contains the *minimum* linesize in the entire cache hierarchy, and is accessible to userland, for use in __aarch64_sync_cache_range, and it is a reasonable assumption that the L1 cache will have that minimum line size. */ [2] Please refer to the comments in this source file ./sysdeps/posix/sysconf.c:__sysconf case _SC_LEVEL1_ICACHE_SIZE: case _SC_LEVEL1_ICACHE_ASSOC: case _SC_LEVEL1_ICACHE_LINESIZE: case _SC_LEVEL1_DCACHE_SIZE: case _SC_LEVEL1_DCACHE_ASSOC: case _SC_LEVEL1_DCACHE_LINESIZE: case _SC_LEVEL2_CACHE_SIZE: case _SC_LEVEL2_CACHE_ASSOC: case _SC_LEVEL2_CACHE_LINESIZE: case _SC_LEVEL3_CACHE_SIZE: case _SC_LEVEL3_CACHE_ASSOC: case _SC_LEVEL3_CACHE_LINESIZE: case _SC_LEVEL4_CACHE_SIZE: case _SC_LEVEL4_CACHE_ASSOC: case _SC_LEVEL4_CACHE_LINESIZE: /* In general we cannot determine these values. Therefore we return zero which indicates that no information is available. */ return 0; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866319 Title: reboot crash in qla2x00_shutdown() To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1866319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866319 Title: reboot crash in qla2x00_shutdown() To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1866319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866319 Title: reboot crash in qla2x00_shutdown() To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1866319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859569 Title: [hns3-0114]net: hns3: fix ETS bandwidth validation bug To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
** Changed in: kunpeng920 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04 Assignee: (unassigned) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
Reproducible with the following conditions (bionic-5.3): ubuntu@saenger:~$ uname -a Linux saenger 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:43:38 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ubuntu@saenger:~$ dpkg -l libc-bin Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===-=== ii libc-bin 2.27-3ubuntu1 arm64 GNU C Library: Binaries ubuntu@saenger:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
Reproducible with the following conditions: ubuntu@saenger:~$ uname -a Linux saenger 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:10:16 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ubuntu@saenger:~$ dpkg -l libc-bin Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===-=== ii libc-bin 2.27-3ubuntu1 arm64 GNU C Library: Binaries ubuntu@saenger:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/jockey/+bug/1247712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/jockey/+bug/1247712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
kernel used for the comment #3 : 5.3.0-42-generic #34~18.04.1-Ubuntu so I am keen to know which kernel/hardware combination it could really reproduce this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
I tested the command on bionic (ubuntu-mate) and it returns: GNU_LIBPTHREAD_VERSION NPTL 2.27 POSIX2_SYMLINKS1 LEVEL1_ICACHE_SIZE 32768 LEVEL1_ICACHE_ASSOC8 LEVEL1_ICACHE_LINESIZE 64 LEVEL1_DCACHE_SIZE 32768 LEVEL1_DCACHE_ASSOC8 LEVEL1_DCACHE_LINESIZE 64 LEVEL2_CACHE_SIZE 262144 LEVEL2_CACHE_ASSOC 4 LEVEL2_CACHE_LINESIZE 64 LEVEL3_CACHE_SIZE 6291456 LEVEL3_CACHE_ASSOC 12 LEVEL3_CACHE_LINESIZE 64 LEVEL4_CACHE_SIZE 0 LEVEL4_CACHE_ASSOC 0 LEVEL4_CACHE_LINESIZE 0 and $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 142 Model name: Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz Stepping:11 CPU MHz: 800.013 CPU max MHz: 3900. CPU min MHz: 400. BogoMIPS:3600.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:6144K NUMA node0 CPU(s): 0-7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
** Tags added: tairadar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868028] Re: L2\L3 cache display error for using "getconf -a" command"
** Changed in: kunpeng920 Assignee: (unassigned) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868028 Title: L2\L3 cache display error for using "getconf -a" command" To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1868028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859569 Title: [hns3-0114]net: hns3: fix ETS bandwidth validation bug To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859569 Title: [hns3-0114]net: hns3: fix ETS bandwidth validation bug To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859569 Title: [hns3-0114]net: hns3: fix ETS bandwidth validation bug To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
