[Kernel-packages] [Bug 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash
https://lists.cs.columbia.edu/pipermail/kvmarm/2020-September/042543.html this patch will slove this bug。 Can you test it？ ** Changed in: linux (Ubuntu) Status: Expired => New ** Also affects: kunpeng920 Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in kunpeng920: New Status in linux package in Ubuntu: New Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1869763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
** Also affects: kunpeng920/ubuntu-20.04-hwe Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 ubuntu-20.04-hwe series: New Status in kunpeng920 upstream-kernel series: Incomplete Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
pls refer to this follow link issue: https://bugs.launchpad.net/kunpeng920/+bug/1859756 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in kunpeng920: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 :7d:00.0: inform reset to vf(2) failed -5! [80001.276902] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to V
[Kernel-packages] [Bug 1867900] Re: CPU stress test fails with focal kernel
=》Patch to disable hisi_sec2 temporarily sent.
=》https://lists.ubuntu.com/archives/kernel-team/2020-June/110647.html
Can you test this following patch which have sent this lkml to enable
sec2 driver for ubuntu verson?
[PATCH] crypto: hisilicon - update SEC driver module parameter
As stress-ng running SEC engine on the Ubuntu OS,
we found that SEC only supports two threads each with one TFM
based on the default module parameter 'ctx_q_num'.
If running more threads, stress-ng will fail since it cannot
get more TFMs.
In order to fix this, we adjusted the default values
of the module parameters to support more TFMs.
Signed-off-by: Longfang Liu
Signed-off-by: Zaibo Xu
---
drivers/crypto/hisilicon/sec2/sec_main.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/crypto/hisilicon/sec2/sec_main.c
b/drivers/crypto/hisilicon/sec2/sec_main.c
index a4cb58b..57de51f 100644
--- a/drivers/crypto/hisilicon/sec2/sec_main.c
+++ b/drivers/crypto/hisilicon/sec2/sec_main.c
@@ -30,9 +30,9 @@
#define SEC_SQE_SIZE 128
#define SEC_SQ_SIZE(SEC_SQE_SIZE * QM_Q_DEPTH)
-#define SEC_PF_DEF_Q_NUM 64
+#define SEC_PF_DEF_Q_NUM 256
#define SEC_PF_DEF_Q_BASE 0
-#define SEC_CTX_Q_NUM_DEF 24
+#define SEC_CTX_Q_NUM_DEF 2
#define SEC_CTX_Q_NUM_MAX 32
#define SEC_CTRL_CNT_CLR_CE0x301120
@@ -191,7 +191,7 @@ static const struct kernel_param_ops sec_ctx_q_num_ops = {
};
static u32 ctx_q_num = SEC_CTX_Q_NUM_DEF;
module_param_cb(ctx_q_num, &sec_ctx_q_num_ops, &ctx_q_num, 0444);
-MODULE_PARM_DESC(ctx_q_num, "Queue num in ctx (24 default, 2, 4, ..., 32)");
+MODULE_PARM_DESC(ctx_q_num, "Queue num in ctx (2 default, 2, 4, ..., 32)");
static const struct kernel_param_ops vfs_num_ops = {
.set = vfs_num_set,
--
2.8.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1867900
Title:
CPU stress test fails with focal kernel
Status in kunpeng920:
Incomplete
Status in kunpeng920 ubuntu-18.04-hwe series:
Incomplete
Status in kunpeng920 ubuntu-20.04 series:
Incomplete
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
[Impact]
We have several crypto accelerators for Hisilicon 1620 but unfortunately one
of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2
makes kernel to run crypto functions without accelerator.
[Fix]
Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver.
[Test]
$ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz
--times --af-alg 0
$ echo $?
[Regression Potential]
This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other
platform.
==
[Bug Description]
CPU stress test fails with focal kernel
[Steps to Reproduce]
1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable
2) sudo apt-add-repository -y ppa:hardware-certification/public
3) sudo apt install -y canonical-certification-server
4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux
5) Run CPU stress test with `sudo certify-advanced`
[Actual Results]
Failed with
stress-ng: fail: [6118] stress-ng-af-alg: bind failed, errno=19 (No such
device)
[Expected Results]
Passed
[Reproducibility]
100%
[Additional information]
Same test with bionic-update kernel passed
[Resolution]
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1867900/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
this following patch will fix sec2 boot bug: crypto: hisilicon/sec2 - modify the SEC probe process https://www.spinics.net/lists/linux-crypto/msg47550.html can you open CONFIG_CRYPTO_TEST=m and CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=m to test acc driver? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867587] Re: [sas-0316]sync mainline kernel 5.6rc1 sas patchset into ubuntu HWE kernel branch
** Summary changed: - [sas-0316]sync mainline kernel 5.6rc1 roce patchset into ubuntu HWE kernel branch + [sas-0316]sync mainline kernel 5.6rc1 sas patchset into ubuntu HWE kernel branch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867587 Title: [sas-0316]sync mainline kernel 5.6rc1 sas patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Committed Bug description: [Bug Description] SAS patchset have merged into mainline 5.6rc1 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] scsi: hisi_sas: Rename hisi_sas_cq.pci_irq_mask scsi: hisi_sas: Add prints for v3 hw interrupt converge and automatic affinity scsi: hisi_sas: Modify the file permissions of trigger_dump to write only scsi: hisi_sas: Replace magic number when handle channel interrupt scsi: hisi_sas: replace spin_lock_irqsave/spin_unlock_restore with spin_lock/spin_unlock scsi: hisi_sas: use threaded irq to process CQ interrupts To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
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. this aboving sec2 optimize code have a small bug, we have fixing it and can you revert aboving four patches? 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 this aboving 11 ACC patches is not problem and you merge it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
from log: Hardware name: Huawei XA320 V2 /BC82HPNB, BIOS 0.95 08/15/2019 this server is x6000, I think that it is not enabled sec driver. Can you provide this lscpi information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859269] Re: [roce-0111]sync mainline kernel 5.5rc6 roce patchset into ubuntu HWE kernel branch
I have confirmed that our internal test team have completed 28 testcases and not find any bug. now also are adding some testcase to test this Roce module. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859269 Title: [roce-0111]sync mainline kernel 5.5rc6 roce patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.5rc6 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] RDMA/hns: Delete unnecessary callback functions for cq RDMA/hns: Rename the functions used inside creating cq RDMA/hns: Redefine the member of hns_roce_cq struct RDMA/hns: Redefine interfaces used in creating cq IB/umem: remove the dmasync argument to ib_umem_get RDMA/hns: Modify appropriate printings RDMA/hns: Fix non-standard error codes RDMA/hns: Modify hns_roce_hw_v2_get_cfg to simplify the code RDMA/hns: Simplify doorbell initialization code RDMA/hns: Replace not intuitive function/macro names RDMA/hns: Modify fields of struct hns_roce_srq RDMA/hns: Delete unnecessary uar from hns_roce_cq RDMA/hns: Remove unnecessary structure hns_roce_sqp RDMA/hns: Delete unnecessary variable max_post RDMA/hns: Remove unsupported modify_port callback RDMA: Connect between the mmap entry and the umap_priv structure RDMA/hns: Fix build error again RDMA/hns: Fix memory leak on 'context' on error return path RDMA/hns: Bugfix for qpc/cqc timer configuration RDMA/hns: Fix to support 64K page for srq RDMA/hns: Delete BITS_PER_BYTE redefinition RDMA/hns: Prevent undefined behavior in hns_roce_set_user_sq_size() RDMA/hns: Release qp resources when failed to destroy qp RDMA/hns: Fix a spelling mistake in a macro RDMA/hns: Modify return value of restrack functions RDMA/hns: Modify variable/field name from vlan to vlan_id RDMA/hns: Fix wrong parameters when initial mtt of srq->idx_que RDMA/hns: remove a redundant le16_to_cpu RDMA/hns: Prevent memory leaks of eq->buf_list RDMA/hns: Correct the value of srq_desc_size RDMA/hns: Correct the value of HNS_ROCE_HEM_CHUNK_LEN RDMA/hns: Add support for reporting wc as software mode RDMA/hns: Bugfix for posting a wqe with sge RDMA/hns: Fix coding style issues RDMA/hns: Replace custom macros HNS_ROCE_ALIGN_UP RDMA/hns: Remove redundant print information RDMA/hns: Delete unnessary parameters in hns_roce_v2_qp_modify() RDMA/hns: Update the value of qp type RDMA/hns: Remove unused function hns_roce_init_eq_table() RDMA/hns: Avoid printing address of mtt page RDMA/hns: Simplify the calculation and usage of wqe idx for post verbs update 01120 RDMA/hns: Get pf capabilities from firmware RDMA/hns: Add interfaces to get pf capabilities from firmware RDMA/hns: Remove some redundant variables related to capabilities RDMA/hns: Add support for extended atomic in userspace [Status] (In Progress): RDMA/hns: Delete unnecessary callback functions for cq (In Progress): RDMA/hns: Rename the functions used inside creating cq (In Progress): RDMA/hns: Redefine the member of hns_roce_cq struct (In Progress): RDMA/hns: Redefine interfaces used in creating cq (In Progress): IB/umem: remove the dmasync argument to ib_umem_get (In Progress): RDMA/hns: Modify appropriate printings (In Progress): RDMA/hns: Fix non-standard error codes (In Progress): RDMA/hns: Modify hns_roce_hw_v2_get_cfg to simplify the code (In Progress): RDMA/hns: Simplify doorbell initialization code (In Progress): RDMA/hns: Replace not intuitive function/macro names (In Progress): RDMA/hns: Modify fields of struct hns_roce_srq (In Progress): RDMA/hns: Delete unnecessary uar from hns_roce_cq (In Progress): RDMA/hns: Remove unnecessary structure hns_roce_sqp (In Progress): RDMA/hns: Delete unnecessary variable max_post (In Progress): RDMA/hns: Remove unsupported modify_port callback (In Progress): RDMA: Connect between the mmap entry and the umap_priv structure (Fix committed): RDMA/hns: Fix build error again (Fix committed): RDMA/hns: Fix memory leak on 'context' on error return path (Fix committed): RDMA/hns: Bugfix for qpc/cqc timer configuration (Fix committed): RDMA/hns: Fix to support 64K page for srq (In Progress): RDMA/hns: Delete BITS_PER_BYTE redefinition (Fix committed): RDMA/hns: Prevent undefined behavior in hns_roce_set_user_sq_size() (Fix committed): RDMA/hns: Release q
[Kernel-packages] [Bug 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
ubuntu@ubuntu:~$ dmesg | grep sfc [ 29.360735] hisi-sfc-v3xx HISI0341:00: hw version 0x351 ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.4.0-14-generic #17~d20200214t082755~5d13e758ee67~lp1860401 SMP Fri Feb 14 08:28 aarch64 aarch64 aarch64 GNU/Linux ubuntu@ubuntu:~$ cat /proc/mtd dev:size erasesize name mtd0: 0100 1000 "spi-PRP0001:00" ubuntu@ubuntu:~$ lsmod | grep sfc spi_hisi_sfc_v3xx 16384 0 ubuntu@ubuntu:~$ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
I use your provided deb to test this sfc driver. this sfc driver have been enabled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
net: hns3: refactor the notification scheme of PF reset net: hns3: refactor the procedure of VF FLR net: hns3: modify hclge_func_reset_sync_vf()'s return type to void net: hns3: enlarge HCLGE_RESET_WAIT_CNT net: hns3: refactor the precedure of PF FLR net: hns3: split hclgevf_reset() into preparing and rebuilding part net: hns3: schedule hclgevf_service by using delayed workqueue net: hns3: modify an unsuitable reset level for hardware error net: hns3: replace an unsuitable variable type in hclge_inform_reset_assert_to_vf() net: hns3: add protection when get SFP speed as 0 net: hns3: modify the IRQ name of misc vectors net: hns3: modify an unsuitable log in hclge_map_ring_to_vector() net: hns3: modify the IRQ name of TQP vector net: hns3: re-organize vector handle net: hns3: add trace event support for HNS3 driver net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure in hns3_nic_uninit_vector_data() net: hns3: add some VF VLAN information for command "ip link show" net: hns3: implement ndo_features_check ops for hns3 driver net: hns3: get FD rules location before dump in debugfs net: hns3: optimization for CMDQ uninitialization net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev net: hns3: check FE bit before calling hns3_add_frag() net: hns3: do not schedule the periodic task when reset fail net: hns3: allocate WQ with WQ_MEM_RECLAIM flag net: hns3: remove unnecessary work in hclgevf_main net: hns3: remove mailbox and reset work in hclge_main net: hns3: schedule hclgevf_service by using delayed workqueue pls ensuring this aboving patchset will merge into ubuntu 20.04 kernel verison. thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859261 Title: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: [Bug Description] hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: support tx-scatter-gather-fraglist feature net: hns3: add support for configuring VF MAC from the host net: hns3: add support for configuring bandwidth of VF on the host net: hns3: add support for setting VF trust net: hns3: add support for spoof check setting net: hns3: add support for setting VF link status on the host net: hns3: make array tick_array static, makes object smaller net: hns3: fix a wrong reset interrupt status mask net: hns3: cleanup of stray struct hns3_link_mode_mapping net: hns3: fix ETS bandwidth validation bug net: hns3: reallocate SSU' buffer size when pfc_en changes net: hns3: add compatible handling for MAC VLAN switch parameter configuration net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE net: hns3: remove unused macros net: hns3: Use the correct style for SPDX License Identifier net: hns3: cleanup byte order issues when printed net: hns3: cleanup some print format warning net: hns3: add or modify some comments net: hns3: optimize local variable initialization net: hns3: cleanup a format-truncation warning net: hns3: cleanup some coding style issues net: hns3: cleanup some magic numbers net: hns3: add struct netdev_queue debug info for TX timeout net: hns3: dump some debug information when reset fail treewide: Use sizeof_member() macro net: hns3: log and clear hardware error after reset complete net: hns3: do not allocate linear data for fraglist skb net: hns3: minor cleanup for hns3_handle_rx_bd() net: hns3: make struct hns3_enet_ring cacheline aligned net: hns3: introduce ring_to_netdev() in enet module net: hns3: minor optimization for barrier in IO path net: hns3: optimized MAC address in management table. net: hns3: remove struct hns3_nic_ring_data in hns3_enet module net: hns3: fix mis-counting IRQ vector numbers issue net: hns3: fix VF ID issue for setting VF VLAN net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() net: hns3: fix for TX queue not restarted problem net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure i
[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
I can not find "treewide: Use sizeof_member() macro but found a similiar. Do you mean this patch? commit c593642c8be046915ca3a4a300243a68077cd207 Author: Pankaj Bharadiya Date: Mon Dec 9 10:31:43 2019 -0800 treewide: Use sizeof_field() macro Replace all the occurrences of FIELD_SIZEOF() with sizeof_field() except at places where these are defined. Later patches will remove the unused definition of FIELD_SIZEOF(). you can ignore this patchset -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859261 Title: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: [Bug Description] hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: support tx-scatter-gather-fraglist feature net: hns3: add support for configuring VF MAC from the host net: hns3: add support for configuring bandwidth of VF on the host net: hns3: add support for setting VF trust net: hns3: add support for spoof check setting net: hns3: add support for setting VF link status on the host net: hns3: make array tick_array static, makes object smaller net: hns3: fix a wrong reset interrupt status mask net: hns3: cleanup of stray struct hns3_link_mode_mapping net: hns3: fix ETS bandwidth validation bug net: hns3: reallocate SSU' buffer size when pfc_en changes net: hns3: add compatible handling for MAC VLAN switch parameter configuration net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE net: hns3: remove unused macros net: hns3: Use the correct style for SPDX License Identifier net: hns3: cleanup byte order issues when printed net: hns3: cleanup some print format warning net: hns3: add or modify some comments net: hns3: optimize local variable initialization net: hns3: cleanup a format-truncation warning net: hns3: cleanup some coding style issues net: hns3: cleanup some magic numbers net: hns3: add struct netdev_queue debug info for TX timeout net: hns3: dump some debug information when reset fail treewide: Use sizeof_member() macro net: hns3: log and clear hardware error after reset complete net: hns3: do not allocate linear data for fraglist skb net: hns3: minor cleanup for hns3_handle_rx_bd() net: hns3: make struct hns3_enet_ring cacheline aligned net: hns3: introduce ring_to_netdev() in enet module net: hns3: minor optimization for barrier in IO path net: hns3: optimized MAC address in management table. net: hns3: remove struct hns3_nic_ring_data in hns3_enet module net: hns3: fix mis-counting IRQ vector numbers issue net: hns3: fix VF ID issue for setting VF VLAN net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() net: hns3: fix for TX queue not restarted problem net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure in hns3_nic_uninit_vector_data() net: hns3: add some VF VLAN information for command "ip link show" net: hns3: implement ndo_features_check ops for hns3 driver net: hns3: get FD rules location before dump in debugfs net: hns3: optimization for CMDQ uninitialization net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev net: hns3: check FE bit before calling hns3_add_frag() net: hns3: do not schedule the periodic task when reset fail net: hns3: allocate WQ with WQ_MEM_RECLAIM flag net: hns3: remove unnecessary work in hclgevf_main net: hns3: remove mailbox and reset work in hclge_main net: hns3: schedule hclgevf_service by using delayed workqueue net: hns3: refactor the notification scheme of PF reset net: hns3: refactor the procedure of VF FLR net: hns3: modify hclge_func_reset_sync_vf()'s return type to void net: hns3: enlarge HCLGE_RESET_WAIT_CNT net: hns3: refactor the precedure of PF FLR net: hns3: split hclgevf_reset() into preparing and rebuilding part net: hns3: split hclge_reset() into preparing and rebuilding part net: hns3: modify an unsuitable reset level for hardware error net: hns3: replace an unsuitable variable type in hclge_inform_reset_assert_to_vf() net: hns3: add protection when get SFP speed as 0 net: hns3: modify the IRQ name of misc vectors net: hns3: modify an unsuitable log in hclge_map_ring_to_vector() net: hns3: modify the IRQ name of TQP vec
[Kernel-packages] [Bug 1861976] Re: [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch
** Summary changed: - [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch + [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861976 Title: [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] acc patchset have merged into mainline 5.5rc6 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon - fix spelling mistake "disgest" -> "digest" crypto: hisilicon - add branch prediction macro crypto: hisilicon - adjust hpre_crt_para_get crypto: hisilicon - Fixed some tiny bugs of HPRE crypto: hisilicon - Bugfixed tfm leak crypto: hisilicon - Add aead support on SEC2 crypto: hisilicon - redefine skcipher initiation crypto: hisilicon - Add branch prediction macro crypto: hisilicon - Add callback error check crypto: hisilicon - Adjust some inner logic crypto: hisilicon - Update QP resources of SEC V2 crypto: hisilicon - Update some names on SEC V2 crypto: hisilicon - fix print/comment of SEC V2 crypto: hisilicon - Update debugfs usage of SEC V2 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
thank you! I will test it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
** Description changed: [Bug Description] hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: support tx-scatter-gather-fraglist feature net: hns3: add support for configuring VF MAC from the host net: hns3: add support for configuring bandwidth of VF on the host net: hns3: add support for setting VF trust net: hns3: add support for spoof check setting net: hns3: add support for setting VF link status on the host net: hns3: make array tick_array static, makes object smaller net: hns3: fix a wrong reset interrupt status mask net: hns3: cleanup of stray struct hns3_link_mode_mapping net: hns3: fix ETS bandwidth validation bug net: hns3: reallocate SSU' buffer size when pfc_en changes net: hns3: add compatible handling for MAC VLAN switch parameter configuration net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE net: hns3: remove unused macros net: hns3: Use the correct style for SPDX License Identifier net: hns3: cleanup byte order issues when printed net: hns3: cleanup some print format warning net: hns3: add or modify some comments net: hns3: optimize local variable initialization net: hns3: cleanup a format-truncation warning net: hns3: cleanup some coding style issues net: hns3: cleanup some magic numbers net: hns3: add struct netdev_queue debug info for TX timeout net: hns3: dump some debug information when reset fail treewide: Use sizeof_member() macro net: hns3: log and clear hardware error after reset complete net: hns3: do not allocate linear data for fraglist skb net: hns3: minor cleanup for hns3_handle_rx_bd() net: hns3: make struct hns3_enet_ring cacheline aligned net: hns3: introduce ring_to_netdev() in enet module net: hns3: minor optimization for barrier in IO path net: hns3: optimized MAC address in management table. net: hns3: remove struct hns3_nic_ring_data in hns3_enet module net: hns3: fix mis-counting IRQ vector numbers issue net: hns3: fix VF ID issue for setting VF VLAN net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() net: hns3: fix for TX queue not restarted problem net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure in hns3_nic_uninit_vector_data() net: hns3: add some VF VLAN information for command "ip link show" net: hns3: implement ndo_features_check ops for hns3 driver net: hns3: get FD rules location before dump in debugfs net: hns3: optimization for CMDQ uninitialization net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev net: hns3: check FE bit before calling hns3_add_frag() net: hns3: do not schedule the periodic task when reset fail net: hns3: allocate WQ with WQ_MEM_RECLAIM flag net: hns3: remove unnecessary work in hclgevf_main net: hns3: remove mailbox and reset work in hclge_main net: hns3: schedule hclgevf_service by using delayed workqueue net: hns3: refactor the notification scheme of PF reset net: hns3: refactor the procedure of VF FLR net: hns3: modify hclge_func_reset_sync_vf()'s return type to void net: hns3: enlarge HCLGE_RESET_WAIT_CNT net: hns3: refactor the precedure of PF FLR net: hns3: split hclgevf_reset() into preparing and rebuilding part net: hns3: split hclge_reset() into preparing and rebuilding part net: hns3: modify an unsuitable reset level for hardware error net: hns3: replace an unsuitable variable type in hclge_inform_reset_assert_to_vf() net: hns3: add protection when get SFP speed as 0 net: hns3: modify the IRQ name of misc vectors net: hns3: modify an unsuitable log in hclge_map_ring_to_vector() net: hns3: modify the IRQ name of TQP vector net: hns3: re-organize vector handle net: hns3: add trace event support for HNS3 driver + update 0120 + net: hns3: pad the short frame before sending to the hardware + + [Status] (In Progress): net: hns3: support tx-scatter-gather-fraglist feature (In Progress): net: hns3: add support for configuring VF MAC from the host (In Progress): net: hns3: add support for configuring bandwidth of VF on the host (In Progress): net: hns3: add support for setting VF trust (In Progress): net: hns3: add support for spoof check setting (In Progress): net: hns3: add support for setting VF link status on the host (In Progress): net: hns3: make array tick_array static, makes object smaller (Fix committed): net: hns3: fix a wrong reset interrupt status mask (Fix committed): net: hns3: cleanup of stray struct hns3_link_mode_mapping (Fix committed): net: hns3: fix ETS bandwidth validation bug (Fix committed): net: hns3: reallocate SSU' buffer size when p
[Kernel-packages] [Bug 1853997] Re: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset
=>Is this bug duplicate of bug 1853999? No, it should inject diff error type. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853997 Title: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset Status in kunpeng920: Triaged Status in kunpeng920 ubuntu-18.04 series: Triaged Status in kunpeng920 ubuntu-18.04-hwe series: Triaged Status in kunpeng920 ubuntu-19.04 series: Triaged Status in kunpeng920 ubuntu-19.10 series: Triaged Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Triaged Status in linux source package in Disco: Triaged Status in linux source package in Eoan: Triaged Status in linux source package in Focal: Fix Released Bug description: "[Steps to Reproduce] 1. Close all the PHYS; 2. Inject error; 3. Open one PHY; [Actual Results] Some disk will be lost [Expected Results] No disk will be lost [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA+I59 Kernel: NA [Resolution] When init device for SAS disks, it will send TMF IO to clear disks. At that time TMF IO is broken by some operations such as injecting controller reset from HW RAs event, the TMF IO will be timeout, and at last device will be gone. Print is as followed: hisi_sas_v3_hw :74:02.0: dev[240:1] found ... hisi_sas_v3_hw :74:02.0: controller resetting... hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11 hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11 hisi_sas_v3_hw :74:02.0: controller reset complete hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done hisi_sas_v3_hw :74:02.0: dev[240:1] is gone sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d, error:5 To improve the reliability, retry TMF IO max of 3 times for SAS disks which is the same as softreset does." scsi: hisi_sas: Fix the conflict between device gone and host reset To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854550] Re: [scsi-1130]scsi: scsi_transport_sas: Fix memory leak when removing devices
if this patch merge into this linus 5.5 version, whether we can backport ubuntu 18.04.4 update version or not? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854550 Title: [scsi-1130]scsi: scsi_transport_sas: Fix memory leak when removing devices Status in kunpeng920: Triaged Status in kunpeng920 ubuntu-18.04 series: Invalid Status in kunpeng920 ubuntu-18.04-hwe series: Triaged Status in kunpeng920 ubuntu-19.04 series: Won't Fix Status in kunpeng920 ubuntu-19.10 series: Won't Fix Status in kunpeng920 ubuntu-20.04 series: Triaged Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Triaged Bug description: "[Steps to reproduce] Enable memleak, and do as follows: root@(none)$ echo 0 > /sys/devices/platform/HISI0162:01/host0/port-0:0/expander-0:0/port-0:0:10/phy-0:0:10/sas_phy/phy-0:0:10/enable [ 79.857888] hisi_sas_v2_hw HISI0162:01: dev[7:1] is gone root@(none)$ echo scan > /sys/kernel/debug/kmemleak [ 131.656603] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) root@(none)$ more /sys/kernel/debug/kmemleak unreferenced object 0x041da5c66000 (size 256): comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s) hex dump (first 32 bytes): 00 5e c6 a5 1d 04 ff ff 01 00 00 00 00 00 00 00 .^.. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [<(ptrval)>] kmem_cache_alloc+0x188/0x260 [<(ptrval)>] bsg_setup_queue+0x48/0x1a8 [<(ptrval)>] sas_rphy_add+0x108/0x2d0 [<(ptrval)>] sas_probe_devices+0x168/0x208 [<(ptrval)>] sas_discover_domain+0x660/0x9c8 [<(ptrval)>] process_one_work+0x3f8/0x690 [<(ptrval)>] worker_thread+0x70/0x6a0 [<(ptrval)>] kthread+0x1b8/0x1c0 [<(ptrval)>] ret_from_fork+0x10/0x18 unreferenced object 0x041d8c075400 (size 128): comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s) hex dump (first 32 bytes): 00 40 25 97 1d 00 ff ff 00 00 00 00 00 00 00 00 .@%. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [<(ptrval)>] __kmalloc_node+0x1a8/0x2c8 [<(ptrval)>] blk_mq_realloc_tag_set_tags.part.70+0x48/0xd8 [<(ptrval)>] blk_mq_alloc_tag_set+0x1dc/0x530 [<(ptrval)>] bsg_setup_queue+0xe8/0x1a8 [<(ptrval)>] sas_rphy_add+0x108/0x2d0 [<(ptrval)>] sas_probe_devices+0x168/0x208 [<(ptrval)>] sas_discover_domain+0x660/0x9c8 [<(ptrval)>] process_one_work+0x3f8/0x690 [<(ptrval)>] worker_thread+0x70/0x6a0 [<(ptrval)>] kthread+0x1b8/0x1c0 [<(ptrval)>] ret_from_fork+0x10/0x18 unreferenced object 0x041da5c65e00 (size 256): comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [<(ptrval)>] __kmalloc_node+0x1a8/0x2c8 [<(ptrval)>] blk_mq_alloc_tag_set+0x254/0x530 [<(ptrval)>] bsg_setup_queue+0xe8/0x1a8 [<(ptrval)>] sas_rphy_add+0x108/0x2d0 [<(ptrval)>] sas_probe_devices+0x168/0x208 [<(ptrval)>] sas_discover_domain+0x660/0x9c8 [<(ptrval)>] process_one_work+0x3f8/0x690 [<(ptrval)>] worker_thread+0x70/0x6a0 [<(ptrval)>] kthread+0x1b8/0x1c0 [<(ptrval)>] ret_from_fork+0x10/0x18 root@(none)$ [solution] Fix by doing the queue removal in one place - in sas_rphy_remove() - instead of unregistering the queue in sas_rphy_remove() and finally cleaning up the queue in calling blk_cleanup_queue() from sas_end_device_release() or sas_expander_release(). Function bsg_remove_queue() can handle a NULL pointer q, so remove the precheck in sas_rphy_remove(). " scsi: scsi_transport_sas: Fix memory leak when removing devices To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1854550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
I find this "Mellonox 25Gigabit-64bit-SFP28-2port– PCIe3.0 X8–15B3-1015-2" card can require 260M CMA memory. If we insert 2 or 3...4 Mellonox card, this card will fail to init it, so we should disable this cma config or set 1024M or above CMA memory. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Confirmed Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
hi daniel
this bug also affect this ubuntu 18.04.0 version which using bionic
kernel branch(kernel 4.15), because this patchset have merged into
mainline linus kernel 4.16rc1 (after kernel 4.15).
I want to add this bionic tag, but i fail it. Can you add this bionic
tag to merge this patchset into bionic branch.
thank you
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738334
Title:
hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
io_mem_pfn callback")
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Artful:
Fix Released
Bug description:
[SRU Justification]
[Impact]
On Artful kernels, X fails to start and a kernel splat is printed.
This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
incomplete: the hisilicon hibmc driver does not contain the callback
and so the kernel tries to execute code at NULL.
[Fix]
There is a discussion and potential fix at
https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The
fix hasn't landed yet and it looks like they're going to re-engineer the entire
section instead.
Rather than wait for that and deal with the massive regression
potential, the fix I have picked to submit is very very minimal and
touches only hibmc.
[Regression Potential]
Minimal - fix only touches hibmc driver. Tested on D05 board.
[Testcase]
Install patched kernel, try to start X. If it succeeds, the fix works. If
there's a kernel splat, the fix does not work.
[Notes]
HiSilicon would really like this fix in Artful in such time so that when the
next 16.04 point release ships in February, the HWE kernel will work with Xorg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738334
Title:
hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
io_mem_pfn callback")
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Artful:
Fix Released
Bug description:
[SRU Justification]
[Impact]
On Artful kernels, X fails to start and a kernel splat is printed.
This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
incomplete: the hisilicon hibmc driver does not contain the callback
and so the kernel tries to execute code at NULL.
[Fix]
There is a discussion and potential fix at
https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The
fix hasn't landed yet and it looks like they're going to re-engineer the entire
section instead.
Rather than wait for that and deal with the massive regression
potential, the fix I have picked to submit is very very minimal and
touches only hibmc.
[Regression Potential]
Minimal - fix only touches hibmc driver. Tested on D05 board.
[Testcase]
Install patched kernel, try to start X. If it succeeds, the fix works. If
there's a kernel splat, the fix does not work.
[Notes]
HiSilicon would really like this fix in Artful in such time so that when the
next 16.04 point release ships in February, the HWE kernel will work with Xorg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
whether this patchset will merge into ubuntu 16.04.4 version or not? this
patchset will important for our DO5 board, Can you check it please?
thank you
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738334
Title:
hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
io_mem_pfn callback")
Status in linux package in Ubuntu:
Confirmed
Bug description:
[SRU Justification]
[Impact]
On Artful kernels, X fails to start and a kernel splat is printed.
This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
incomplete: the hisilicon hibmc driver does not contain the callback
and so the kernel tries to execute code at NULL.
[Fix]
There is a discussion and potential fix at
https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The
fix hasn't landed yet and it looks like they're going to re-engineer the entire
section instead.
Rather than wait for that and deal with the massive regression
potential, the fix I have picked to submit is very very minimal and
touches only hibmc.
[Regression Potential]
Minimal - fix only touches hibmc driver. Tested on D05 board.
[Testcase]
Install patched kernel, try to start X. If it succeeds, the fix works. If
there's a kernel splat, the fix does not work.
[Notes]
HiSilicon would really like this fix in Artful in such time so that when the
next 16.04 point release ships in February, the HWE kernel will work with Xorg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738334/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
hi daniel: whether this following mainline patchset have merge into this artful branch or not? If do not merge this patchset, this xwindow function will fail it. Can you confirm it and provide this artful branch in order to test it for me 505a1b5 vgaarb: Factor out EFI and fallback default device selection a37c0f4 vgaarb: Select a default VGA device even if there's no legacy VGA -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698700 Title: hibmc driver does not include "pci:" prefix in bus ID Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: SRU Justification [Impact] On the HiSilicon D05 (arm64) board, X crashes when started. [0] [Fix] The crash is attributable to the bus ID that the hibmc driver reports for the hibmc graphics card on the board. In particular, the bus id is missing the "pci:" prefix that most other cards provide: [1] - The busid reported on the arm64 system is "0007:a1:00.0" - The busid reported on a amd64 system is "pci::00:02.0" X tests for this prefix. A missing prefix for PCI cards leads to an Xorg crash. Fix this by using the set_pci_busid function from the DRM core. [Testcase] Successfully tested on a D05 board. [2] [Regression Potential] Changes are limited to the hibmc driver, so any regression should also be limited to that driver. [Notes] I submitted the patch upstream. However, upstream is refactoring the drm core, and set_busid is going away. That does fix this issue but the regression potential of the refactor is enormous, so this seems like the wiser approach. [3] [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16 [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29 [3]: https://www.spinics.net/lists/dri-devel/msg143831.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
this patch will solve commit #10 bug, please merge this patch. thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698700 Title: hibmc driver does not include "pci:" prefix in bus ID Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Incomplete Bug description: SRU Justification [Impact] On the HiSilicon D05 (arm64) board, X crashes when started. [0] [Fix] The crash is attributable to the bus ID that the hibmc driver reports for the hibmc graphics card on the board. In particular, the bus id is missing the "pci:" prefix that most other cards provide: [1] - The busid reported on the arm64 system is "0007:a1:00.0" - The busid reported on a amd64 system is "pci::00:02.0" X tests for this prefix. A missing prefix for PCI cards leads to an Xorg crash. Fix this by using the set_pci_busid function from the DRM core. [Testcase] Successfully tested on a D05 board. [2] [Regression Potential] Changes are limited to the hibmc driver, so any regression should also be limited to that driver. [Notes] I submitted the patch upstream. However, upstream is refactoring the drm core, and set_busid is going away. That does fix this issue but the regression potential of the refactor is enormous, so this seems like the wiser approach. [3] [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16 [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29 [3]: https://www.spinics.net/lists/dri-devel/msg143831.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
hi daniel please take care of this following patchset, other distro exist some xwindow crash issue. https://lists.freedesktop.org/archives/dri- devel/2017-November/159002.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698700 Title: hibmc driver does not include "pci:" prefix in bus ID Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Incomplete Bug description: SRU Justification [Impact] On the HiSilicon D05 (arm64) board, X crashes when started. [0] [Fix] The crash is attributable to the bus ID that the hibmc driver reports for the hibmc graphics card on the board. In particular, the bus id is missing the "pci:" prefix that most other cards provide: [1] - The busid reported on the arm64 system is "0007:a1:00.0" - The busid reported on a amd64 system is "pci::00:02.0" X tests for this prefix. A missing prefix for PCI cards leads to an Xorg crash. Fix this by using the set_pci_busid function from the DRM core. [Testcase] Successfully tested on a D05 board. [2] [Regression Potential] Changes are limited to the hibmc driver, so any regression should also be limited to that driver. [Notes] I submitted the patch upstream. However, upstream is refactoring the drm core, and set_busid is going away. That does fix this issue but the regression potential of the refactor is enormous, so this seems like the wiser approach. [3] [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16 [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29 [3]: https://www.spinics.net/lists/dri-devel/msg143831.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
Starting Hostname Service... Ubuntu 17.10 ubuntu ttyAMA0 [ 68.535458] Internal error: Attempting to execute userspace memory: 8604 [#1] SMP [ 68.543288] Modules linked in: nls_iso8859_1 joydev input_leds shpchp ipmi_ssif ipmi_si ipmi_devintf ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ppdev lp parport ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure hid_generic usbhid hid marvell hibmc_drm ttm aes_ce_blk drm_kms_helper aes_ce_cipher crc32_ce syscopyarea crct10dif_ce sysfillrect sysimgblt ghash_ce fb_sys_fops sha2_ce sha1_ce drm hisi_sas_v2_hw hisi_sas_main megaraid_sas libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk crypto_simd cryptd [ 68.607986] CPU: 39 PID: 2746 Comm: llvmpipe-1 Not tainted 4.13.0-16-generic #19-Ubuntu [ 68.615975] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.29 07/17/2017 [ 68.622576] task: 8013b88ecb00 task.stack: 8013b8dc4000 [ 68.628485] PC is at 0x0 [ 68.631026] LR is at ttm_bo_vm_fault+0x218/0x520 [ttm] [ 68.636151] pc : [<>] lr : [] pstate: 00400145 [ 68.643533] sp : 8013b8dc7ac0 [ 68.646834] x29: 8013b8dc7ac0 x28: [ 68.652134] x27: 0cb63000 x26: [ 68.657434] x25: 0208 x24: [ 68.662734] x23: 8013dd0e5240 x22: 8013dd0e50b0 [ 68.668034] x21: 0cb53000 x20: 8013b324d518 [ 68.67] x19: 093b8c08 x18: [ 68.678633] x17: x16: [ 68.683933] x15: x14: [ 68.689232] x13: x12: 8013ddcadc00 [ 68.694531] x11: x10: 8013e5f62900 [ 68.699831] x9 : 001000eb x8 : 01dd85b8 [ 68.705130] x7 : x6 : 8013b8dc7bf8 [ 68.710430] x5 : x4 : 0008 [ 68.715730] x3 : 0cb53000 x2 : [ 68.721029] x1 : x0 : 8013ddcadc00 [ 68.726329] Process llvmpipe-1 (pid: 2746, stack limit = 0x8013b8dc4000) [ 68.733364] Stack: (0x8013b8dc7ac0 to 0x8013b8dc8000) [ 68.739098] 7ac0: 8013b8dc7c00 082585a4 8013b8dc7cc0 0d73 [ 68.746914] 7ae0: 8013b324d518 08e2 8013b958bfe0 8013b888a580 [ 68.754731] 7b00: 8013b324d518 8013b888a5e8 0003 [ 68.762547] 7b20: 8013ddcadc00 8013ddcadc00 0cb53000 0cd5b000 [ 68.770363] 7b40: 8013b35824b0 8013b3582ed8 8013b35824d0 [ 68.778180] 7b60: 00b53000 8013b888a580 00680f4f [ 68.785996] 7b80: 140440fb 8013bd2908f0 [ 68.793813] 7ba0: 001002f2 8013b324d590 8013b324d590 [ 68.801629] 7bc0: 01dd85b8 001000eb 8013e5f62900 [ 68.809445] 7be0: 8013ddcadc00 00040d00 [ 68.817262] 7c00: 8013b8dc7c30 0825ca7c 8013b8dc7cc0 0d73 [ 68.825078] 7c20: 8013b8dc7c70 0825e628 [ 68.832894] 7c40: 0065 093b8000 8013b324d518 0825e52c [ 68.840710] 7c60: 0065 08165b38 8013b8dc7d30 0825eaac [ 68.848527] 7c80: 0054 8013b324d518 0cb53000 0040 [ 68.856343] 7ca0: 8013b888a580 0054 [ 68.864160] 7cc0: 8013b324d518 014200ca0054 001000eb 0cb53000 [ 68.871976] 7ce0: 8013b8625328 8013b958bfe0 [ 68.879792] 7d00: [ 68.887609] 7d20: 00040d00 8013b8dc7d60 08a80e10 [ 68.895425] 7d40: 8013b8dc7ec0 8013b88ecb00 0cb53000 9206 [ 68.903241] 7d60: 8013b8dc7dc0 08a81054 0cb53000 9206 [ 68.911058] 7d80: 8013b8dc7ec0 8013b8dc7ec0 08a97238 0024 [ 68.918874] 7da0: 9206 0cb53000 8013b88ecb00 [ 68.926690] 7dc0: 8013b8dc7df0 08081244 093b8000 9206 [ 68.934507] 7de0: 0cb53000 00040d00 08083508 [ 68.942323] 7e00: 8017f2d1b000 0d939338 [ 68.950139] 7e20: 2000 0200 8017fbce8090 fbcec080 [ 68.957955] 7e40: 08083930 8017f2d1b000 [ 68.965771] 7e60
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
I use this following 17.10 ISO to test this xwindow for D05 board. http://cdimage.ubuntu.com/releases/17.10/release/ubuntu-17.10-server- arm64.iso Then set this next step: sudo apt install ubuntu-desktop sudo reboot. this desktop will crash. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698700 Title: hibmc driver does not include "pci:" prefix in bus ID Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Incomplete Bug description: SRU Justification [Impact] On the HiSilicon D05 (arm64) board, X crashes when started. [0] [Fix] The crash is attributable to the bus ID that the hibmc driver reports for the hibmc graphics card on the board. In particular, the bus id is missing the "pci:" prefix that most other cards provide: [1] - The busid reported on the arm64 system is "0007:a1:00.0" - The busid reported on a amd64 system is "pci::00:02.0" X tests for this prefix. A missing prefix for PCI cards leads to an Xorg crash. Fix this by using the set_pci_busid function from the DRM core. [Testcase] Successfully tested on a D05 board. [2] [Regression Potential] Changes are limited to the hibmc driver, so any regression should also be limited to that driver. [Notes] I submitted the patch upstream. However, upstream is refactoring the drm core, and set_busid is going away. That does fix this issue but the regression potential of the refactor is enormous, so this seems like the wiser approach. [3] [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16 [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29 [3]: https://www.spinics.net/lists/dri-devel/msg143831.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698700 Title: hibmc driver does not include "pci:" prefix in bus ID Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Incomplete Bug description: SRU Justification [Impact] On the HiSilicon D05 (arm64) board, X crashes when started. [0] [Fix] The crash is attributable to the bus ID that the hibmc driver reports for the hibmc graphics card on the board. In particular, the bus id is missing the "pci:" prefix that most other cards provide: [1] - The busid reported on the arm64 system is "0007:a1:00.0" - The busid reported on a amd64 system is "pci::00:02.0" X tests for this prefix. A missing prefix for PCI cards leads to an Xorg crash. Fix this by using the set_pci_busid function from the DRM core. [Testcase] Successfully tested on a D05 board. [2] [Regression Potential] Changes are limited to the hibmc driver, so any regression should also be limited to that driver. [Notes] I submitted the patch upstream. However, upstream is refactoring the drm core, and set_busid is going away. That does fix this issue but the regression potential of the refactor is enormous, so this seems like the wiser approach. [3] [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16 [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29 [3]: https://www.spinics.net/lists/dri-devel/msg143831.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
