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.
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
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
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
** 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.
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
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
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
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
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 :
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)
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.
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:~#
**
** 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.
** 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.
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
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
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
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
** 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.
@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.
@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
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
** 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
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"
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
** 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
** 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
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.
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.
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:
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:
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.
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
signee: (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
Ti
** 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.
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
"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
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
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
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]
@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
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]
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
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
** 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
** 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
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
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
** 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
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:
[AC
** 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
** 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
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
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
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
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
@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
** 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
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
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
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
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
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]
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:
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:
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
--
@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]
** 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
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
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:
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
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").
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
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:
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
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
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
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
@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.
@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
** 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:
** 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:
** 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
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
|
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
|
** 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
** 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
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.
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
** 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:
** 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 "
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
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.
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.
** 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
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
** 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
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 |
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
1 - 100 of 1653 matches
Mail list logo
