** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789227
Title:
nvme devices namespace assigned to the wrong
** Description changed:
[Impact]
The functional change is negligible - the primary goal here is to align our
tree closer to upstream to make future backports cleaner (and therefore safer).
- We are currently carrying 61 SAUCE patches for the hns3 driver. All but
- 6 of these have gone
** Description changed:
[Impact]
The functional change is negligible - the primary goal here is to align our
tree closer to upstream to make future backports cleaner (and therefore safer).
We are currently carrying 61 SAUCE patches for the hns3 driver. All but
6 of these have gone
** Description changed:
[Impact]
- There's no functional impact, this is just an attempt to reconcile the Ubuntu
tree with upstream.
- We are currently carrying 61 SAUCE patches for the hns3 driver. All but 6 of
these have gone upstream in some form. However, some of the patches have
changed
** Description changed:
[Impact]
There's no functional impact, this is just an attempt to reconcile the Ubuntu
tree with upstream.
- We are currently carrying 61 SAUCE patches for the hns3 driver. All but 8 of
these have gone upstream in some form. However, some of the patches have
changed
: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed
** Description changed:
[Impact]
With artful, crashdump worked on the Cavium CRBs, Cavium-based Gigabyte
boards and the Qualcomm Amberwing board, but it no longer works with v4.15.
While possibly not a regression, crashdump also does not currently work with
the HiSilicon D05 board, but
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
[Impact]
With artful, crashdump worked on the Cavium CRBs, Cavium-based Gigabyte boards
and the Qualcomm Amberwing board, but it no longer works with v4.15. While
possibly not a regression, crashdump also does not currently work with the
HiSilicon D05 board, but does with
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1528684
Title:
Error parsing PCC subspaces from PCCT
** Changed in: linux (Ubuntu Cosmic)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu Cosmic)
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: linux (Ubun
84a527a41f38a80353f185d05e41b021e1ff672b
Author: Shaohui Xie
Date: Tue May 10 17:42:26 2016 +0800
net: phylib: fix interrupts re-enablement in phy_start
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: New
** Affects
tty simple/straightforward, and I haven't seen any problems on a system
that uses them w/ the fixes applied.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
** Description changed:
- On a HiSilicon D06 system we noticed that interfaces provided by a plug-
- in "HINIC" network card are not getting assigned predictable names.
- We're getting "ethX" names instead of the expected "enPblah" names.
+ [Impact]
+ Interfaces associated with Huawei "hinic" PCI
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
fyi, this appears to fix the problem for me.
** Patch added:
"0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783138/+attachment/5166848/+files/0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch
** Also
I prepared a ppa build of d-i (ppa:dannf/test) and booted w/ apt-
setup/proposed=true. It resolves the issue I was seeing on a HiSilicon
D05 system w/ disks attached to an mpt3sas controller.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received
Public bug reported:
Testing a bionic build of d-i w/ proposed results in a failure.
>From d-i's /var/log/syslog:
Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected
Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected
Jul 20 20:03:25
Ran the reproducer on both a HiSilicon D05 and D06 and it now passes.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The following hack resolves the issue for me on arm64:
--- build/util/grub-gencfg.orig 2018-07-17 23:19:53.101127509 +
+++ build/util/grub-gencfg 2018-07-17 22:44:09.46019 +
@@ -144,6 +144,7 @@
push @cmdline, @OPTS;
push @cmdline, "rescue/enable=true" if $xattr{Rescue};
I'm investigating an issue we're seeing on a couple ARM servers, and it
looks like this maybe the same issue here. What it looks like is that
the mpt3sas driver is being downloaded/loaded just before the
partitioner starts. Since the kernel is configured to scan for SCSI
devices asynchronously,
** Description changed:
- We applied a partial fix for a regression in LP: #1780137 - that applied
- to inode bitmaps. We also need a fix for block bitmaps.
+ [Impact]
+ The stress-ng mknod/dentry tests can trigger a bug that causes ext4 error
messages:
+ EXT4-fs error (device sda2):
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
We applied a partial fix for a regression in LP: #1780137 - that applied
to inode bitmaps. We also need a fix for block bitmaps.
https://marc.info/?l=linux-ext4=153143692320723=2
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects:
I don't have the configuration to demonstrate the problem - but I have
verified that on an alternate configuration, the output of 'cat
/sys/class/sas_phy/*/sas_address' is the same before and after the
patch, demonstrating a lack of regression.
** Tags removed: verification-needed-bionic
** Tags
Verification results:
ubuntu@d05-6:~$ sudo ./stress
+ umount /tmp/mnt
umount: /tmp/mnt: not mounted.
+ /bin/true
+ mkdir -p /tmp/mnt
+ mkfs.ext4 -F /dev/sda1
mke2fs 1.44.1 (24-Mar-2018)
/dev/sda1 contains a ext4 file system
last mounted on Wed Jul 11 23:26:23 2018
/dev/sda1 alignment is
** Description changed:
[Impact]
A scary-looking message appears in dmesg in several places during boot:
"Error parsing PCC subspaces from PCCT"
+
+ This could cause users to believe they have buggy firmware, in cases
+ where it's actually fine.
[Test Case]
dmesg | grep "Error
n Nvidia DGX system. This is an upstream fix, so any
+ regressions will have upstream support.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
As
Attached is iozone_comparator output showing a positive improvement in
read performance on a D06 system.
** Attachment added: "index.html"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/127/+attachment/5162176/+files/index.html
** Tags removed: verification-needed-bionic
** Tags
** Description changed:
- We're seeing a very reproducible regression in the bionic kernel
- triggered by the stress-ng chdir test performed by the Ubuntu
- certification suite. We see this on both the HiSilicon D05 arm64 server
- and the HiSilicon D06 arm64 server. We have been unable to
@Ike: Let me know if the above sounds plausible. I should also make the
following notes, which may provide evidence counter to my theory of pre-
existing corruption:
It is possible that mkfs.ext4 was ran outside of sudo (e.g. directly in
a root shell), and would therefore not be logged in
Copying over comments from Ike from a different forum:
Ike Panhc (ikepanhc) wrote on 2018-07-09: #42
I build kernel debs based on Ted's response on ext4 mailing list at
http://kernel.ubuntu.com/~ikepanhc/ext4msg61578/
Please also see
https://www.spinics.net/lists/linux-ext4/msg61578.html
I am no longer able to reproduce after applying Ted's patch. I was able
to run my unit test 20 times w/o failing on upstream + patch on d05-6. I
then switched over to the Ubuntu kernel + patch, and it has now passed
64 times (and counting).
I then looked to see why Ike is still observing a
I ran the test case on a D06 system w/ the 4.15.0-26.28 kernel and it
survived.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Smoke tested on D05 and D06 systems.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/134
Title:
Smoke tested on D06 system.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/136
Title:
Upstream thread: https://lkml.org/lkml/2018/7/6/763
--
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/1780137
Title:
[Regression] EXT4-fs error (device sda1):
The significant difference in the cert test wrapper actually appears to
be that it creates a directory in which to run the test, vs. running it
at the root of the mount point. I'm able to reproduce the failure
outside of cert after a fresh reboot with the following script. The fs
.aio-max-nr
** Description changed:
We're seeing a very reproducible regression in the bionic kernel
triggered by the stress-ng chdir test performed by the Ubuntu
- certification suite. Platform is a HiSilicon D05 arm64 server, but we
- don't have reason to believe it is platform specific at this time.
+
On Thu, Jul 5, 2018 at 9:35 AM Colin Ian King
<1780...@bugs.launchpad.net> wrote:
>
> What is the stress-ng command that is being run by /usr/lib/plainbox-
> provider-checkbox/bin/disk_stress_ng - without knowing that it's hard to
> figure out the initial stressor conditions
It runs several
Public bug reported:
We're seeing a very reproducible regression in the bionic kernel
triggered by the stress-ng chdir test performed by the Ubuntu
certification suite. Platform is a HiSilicon D05 arm64 server, but we
don't have reason to believe it is platform specific at this time.
[Test Case]
(Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
which adds a
spin_lock_init() call.
[Regression Risk]
The fix is limited to the hisi_sas driver and is obviously correct.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance
)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status
d to the hisi_sas driver. This driver is only
used by two platforms supported by Ubuntu: HiSilicon D05 and HiSilicon D06. We
will directly verify these fixes on those platforms.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
*
Previously this driver supported one PCI ID (19e5:1822), and this added
a couple more. I don't have one of the *new* devices, but I do have
system with the 19e5:1822, and I can confirm I observe no regressions.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
Verified:
[ 330.966942] EINJ: Error INJection is initialized.
[ 350.598563] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 2
[ 350.598586] {1}[Hardware Error]: It has been corrected by h/w and requires
no further action
[ 350.598589] {1}[Hardware Error]: event
Ran 'iozone -a' to smoke test on a d06 and a d05 w/o any observed
regressions.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Verification:
Since current D06 systems aren't bootable with the previous kernel, I
restricted my regression testing to D05. I ran iozone -a on the current
and -proposed kernels, then compared the results visually using iozone-
results-comparator. While the changes in read performance was all
Passed iozone3 test. I then rebooted w/ the 'break' command line
argument to interrupt boot before mounting the disk, then ran the
following loop:
for i in $(seq 1 10); do modprobe -r hisi_sas_v3_hw; modprobe
hisi_sas_v3_hw; done
It survived, and I was able to boot into the OS from there.
**
= Verification =
== Server Side ==
ubuntu@d06-1:~$ cat /proc/version
Linux version 4.15.0-24-generic (buildd@bos02-arm64-008) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #26-Ubuntu SMP Wed Jun 13 08:44:37 UTC 2018
ubuntu@d06-1:~$ ib_write_bw -n 5 -d hns_2
ubuntu@d06-2:~$ cat /proc/version
Linux version 4.15.0-24-generic (buildd@bos02-arm64-008) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #26-Ubuntu SMP Wed Jun 13 08:44:37 UTC 2018
ubuntu@d06-2:~$ cat /sys/devices/pci\:80/\:80\:08.0/max_link_speed
16 GT/s
** Tags removed:
On Thu, Jun 14, 2018 at 9:51 AM Ard Biesheuvel
wrote:
>
> On 14 June 2018 at 13:02, Brad Figg wrote:
> > This bug is awaiting verification that the kernel in -proposed solves
> > the problem. Please test the kernel and update this bug with the
> > results. If the problem is solved, change the
Verification:
ubuntu@d06-1:~$ cat /proc/version
Linux version 4.15.0-24-generic (buildd@bos02-arm64-008) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #26-Ubuntu SMP Wed Jun 13 08:44:37 UTC 2018
ubuntu@d06-1:~$ lscpu
Architecture:aarch64
Byte Order: Little Endian
CPU(s):
Verified by ssh'ing to the upgraded system over the onboard nic:
$ ssh ubuntu@10.228.68.53 cat /proc/version
Warning: Permanently added '10.228.68.53' (ECDSA) to the list of known hosts.
Linux version 4.15.0-24-generic (buildd@bos02-arm64-008) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3))
is the HiSilicon D05, where we can directly test.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also
** Summary changed:
- Fixes for NIC on socionext board
+ Network installs fail on SocioNext board
--
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/1775884
Title:
Network installs fail on
that is only currently used for the
NIC on this system.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status
*** This bug is a duplicate of bug 1770974 ***
https://bugs.launchpad.net/bugs/1770974
** This bug has been marked a duplicate of bug 1770974
Fix several bugs in RDMA/hns driver
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
[Impact]
- Several issues in the RDMA/hns driver for HiSilicon network adapters have
recently landed upstream.
-
- TBD: Summarize.
+ Several issues and features in the RDMA/hns driver for HiSilicon network
adapters have recently landed upstream. This includes fixes
Driver is now there. Can't verify *it works* yet because I don't have a
card, but vendor tells me it's fine.
ubuntu@d05-1:~$ cat /proc/version
Linux version 4.15.0-23-generic (buildd@bos02-arm64-002) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 17:59:52 UTC 2018
Previous comment was verification w/ the following kernel:
ubuntu@d05-1:~$ cat /proc/version
Linux version 4.15.0-23-generic (buildd@bos02-arm64-002) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 17:59:52 UTC 2018
** Tags removed: verification-needed-bionic
**
ubuntu@d05-1:~$ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
enahisic2i0-tx0
enahisic2i0-tx1
enahisic2i0-tx2
enahisic2i0-tx3
enahisic2i0-tx4
enahisic2i0-tx5
enahisic2i0-tx6
enahisic2i0-tx7
enahisic2i0-tx8
enahisic2i0-tx9
enahisic2i0-tx10
enahisic2i0-tx11
enahisic2i0-tx12
enahisic2i0-tx13
Smoke tested on HiSilicon D05 & D06 systems (I don't have physical
access to yank disks).
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Smoke tested on HiSilicon D05 & D06 systems (I don't have physical
access to do the hot-pull/plug)
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Tested on D05 & D06.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1768974
Title:
Several hisi_sas
> dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
--
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/1774472
Title:
hisi_
Public bug reported:
[Impact]
The way the driver deals with locking the DQ causes performance to suffer.
[Test Case]
Run iozone3 and validate performance is >= previous.
[Fix]
Once a DQ slot is allocated, it must be used. So, currently the driver locks
the DQ while it builds and sends each
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (u
Public bug reported:
[Impact]
Changes in the hisi_sas v3 hardware design require corresponding changes in the
driver.
[Test Case]
I don't have a way to inject these errors, so testing here will be limited to
regression testing on the two Ubuntu-supported platforms that have hisi_sas
/hip07 SoCs, where we have directly tested these
updates.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
[Impact]
Applications, particularly those in the HPC domain (e.g. openmpi), can be
optimized for the processor and cache topology. However, the ARM CPU topology
isn't correctly exposed to userspace.
[Fix]
The ACPI 6.2 specification introduced a Processor
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Description changed:
[Impact]
Applications, particularly those in the HPC domain (e.g. openmpi), can be
optimized for the processor and cache topology. However, the ARM CPU topology
isn't correc
** Description changed:
[Impact]
Applications, particularly those in the HPC domain (e.g. openmpi), can be
optimized for the processor and cache topology. However, the ARM CPU topology
isn't correctly exposed to userspace.
[Fix]
The ACPI 6.2 specification introduced a Processor
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
[Impact]
Applic
** Changed in: linux-meta (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux-meta (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux-meta (Ubuntu Artful)
Assignee: (unassigned) => dann frazier (dannf)
** Changed
Public bug reported:
[Impact]
kdump works fine on arm64 these days, but end users have to manually install
the various packages to make it work vs. just installing linux-crashdump like
on other architectures.
[Test Case]
On an arm64 system:
sudo apt install linux-crashdump
[Fix]
Add the
Verification:
ubuntu@awrep3:~$ cat /proc/version
Linux version 4.15.0-23-generic (buildd@bos02-arm64-002) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 17:59:52 UTC 2018
ubuntu@awrep3:~$ sudo ras-mc-ctl --errors
No Memory errors.
PCIe AER events:
1 2018-05-07
I've smoke-tested the proposed kernel on a system that uses kpti by
default:
ubuntu@awrep3:~$ dmesg | grep -i kpti
[0.074874] CPU features: detected feature: Kernel page table isolation
(KPTI)
ubuntu@awrep3:~$ cat /proc/version
Linux version 4.15.0-23-generic (buildd@bos02-arm64-002) (gcc
I'm unable to explicitly verify this, as we don't have any systems that
support SDEI - and if we did, they'd probably boot in ACPI mode. I have
booted the updated kernel on an arm64 system though, and observed no
regressions.
** Tags removed: verification-needed-bionic
** Tags added:
$ dpkg -c nic-modules-4.15.0-23-generic-di_4.15.0-23.25_arm64.udeb | grep hinic
drwxr-xr-x root/root 0 2018-05-23 10:54
./lib/modules/4.15.0-23-generic/kernel/drivers/net/ethernet/huawei/hinic/
-rw-r--r-- root/root132062 2018-05-23 10:54
ed
16 GT/s
[Fix]
Cherry-pick an upstream commit that supports in-kernel decoding of 16 GT/s link
speed
[Regression Risk]
Trivial fix that just adds an extra case in a switch statement w/ supporting
#defines.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann fraz
** Description changed:
[Impact]
When an ARM-specific platform error (CPER) comes occurs, the kernel will emit
an error with an opaque hex error type. The user would then need to consult the
UEFI specification to decode it. It is far easier for the kernel to do the
decoding itself, and
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
** Description changed:
[Impact]
- When an ARM-specific platform error (CPER) comes occurs, the kernel will emit
an error with an opaque hex
** Description changed:
[Impact]
- TBD
+ When an ARM-specific platform error (CPER) comes occurs, the kernel will emit
an error with an opaque hex error type. The user would then need to consult the
UEFI specification to decode it. It would be better to actually do the decoding
for the user
** Description changed:
[Impact]
The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe
errors to the AER (Advanced Error Reporting) driver, which surfaces them to
userspace. However, we're currently only reporting "recoverable" errors and not
errors of other types
Public bug reported:
[Impact]
Several issues in the RDMA/hns driver for HiSilicon network adapters have
recently landed upstream.
TBD: Summarize.
[Test Case]
TBD
[Regression Risk]
TBD
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status
]
These are previously unsupported devices.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Triaged
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Triaged
** Also affects: linux (Ubuntu
** Changed in: linux (Ubuntu Zesty)
Status: Fix Committed => Won't Fix
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: gcc-6 (Ubuntu Zesty)
Status: Triaged =>
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Description changed:
[Impact]
TBD
[Test Case]
TBD
[Fix]
- TBD
+ c6d8c8ef1d0d94fdae9f5d72982963db89
Public bug reported:
[Impact]
TBD
[Test Case]
TBD
[Fix]
TBD
[Regression Risk]
TBD
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Public bug reported:
[Impact]
The user has to manually load the driver before they can use the RoCE function
of these NICs.
[Test Case]
On a HiSilicon D06 node:
$ lsmod | grep hns-roce-hw-v2
[Fix]
The module is missing the MODULE_DEVICE_TABLE() macro, which exposes the PCI
IDs it is
Public bug reported:
[Impact]
Applications, particularly those in the HPC domain (e.g. openmpi), can be
optimized for the processor and cache topology. However, the ARM CPU topology
isn't correctly exposed to userspace.
[Fix]
The ACPI 6.2 specification introduced a Processor Properties
** Description changed:
[Impact]
When a SATA device, attached to a SAS controller, begins generating errors
(e.g. device failing, or someone yanked it), the SAS error handling will
complete, but may leave zombie ATA commands that never get properly
processed/freed. This can cause some ugly
** Description changed:
[Impact]
Hotplugging a SATA disk into a SAS controller may trigger a NULL pointer
dereference, leading to a crash:
[ 2366.923208] Unable to handle kernel NULL pointer dereference
at virtual address 07b8
...
[ 2368.766334] Call trace:
[ 2368.781712] []
.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bionic
** Description changed:
[Impact]
The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe
errors to the AER (Advanced Error Reporting) driver, which surfaces them to
userspace. However, we're currently only reporting "recoverable" errors and not
errors of other types
e should be an entry for the injected error, as shown below:
No Memory errors.
PCIe AER events:
1 2018-05-07 17:55:46 + Fatal error: Receiver Error
No Extlog errors.
No MCE errors.
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
801 - 900 of 1621 matches
Mail list logo
