** Description changed:
[Impact]
- TBD
+ Sync up the hns drivers with the 5.2 merge window.
+
+ (Cut & paste from bug 1819535)
+ Drivers for the HiSilicon Hi1620 SoC continue to be under active development,
including both hardware enablement and bug fix patches. With the amount of flux
involv
Public bug reported:
[Impact]
TBD
[Test Case]
TBD
[Fix]
TBD
[Regression Risk]
TBD
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: dann frazier
I forgot to enable CMA_DEBUGFS in those builds, so I've uploaded another
(cma.3)
--
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
dev 500e004aaa1f response:
0x0 status 0x2
(initramfs) cat negotiated_linkrate
12.0 Gbit
[Regression Risk]
Impact is limited to drivers built on top of libsas.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You recei
On Thu, May 23, 2019 at 8:31 AM Paolo Pisati <1823...@bugs.launchpad.net> wrote:
>
> Yes, i have all the hardware to do some testing, prepare some kernels
> and we can take it from there.
Thanks Paolo. I pushed a test build to ppa:dannf/cma. This bumps cma
to 32M, but would also be good to know th
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: linux (Ubuntu Cosmic)
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.
Patch submitted upstream:
https://www.spinics.net/lists/netdev/msg571753.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/1829652
Title:
Kernel panic upon resetting ixgbe SR-IOV VFIO
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Confirmed
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status:
On Wed, May 22, 2019 at 8:41 AM Paolo Pisati <1823...@bugs.launchpad.net> wrote:
>
> I realize this is just a workaround (and the above 31M cma memory
> fragmentation is ugly), but we should definitely bump CMA allocation
> space: definitely 32M (since that's what upstream default to) but if 64M
>
)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => dann frazier (dannf)
--
Public bug reported:
[Impact]
Performance is degraded when a guest is booted w/ vgic v4 support enabled.
[Test Case]
I used a HiSilicon D06 system w/ an Intel 82599 10Gbps NIC. I passed through a
VF to a guest, and ran "netperf -H " against a 10Gbps-capable target.
With vgic v4 support, I'm on
disco verification:
ubuntu@d06-4:~$ cat /proc/version
Linux version 5.0.0-16-generic (buildd@bos02-arm64-013) (gcc version 8.3.0
(Ubuntu/Linaro 8.3.0-6ubuntu1)) #17-Ubuntu SMP Wed May 15 10:54:19 UTC 2019
ubuntu@d06-4:~$ dmesg | grep cma
[0.00] cma: Reserved 16 MiB at 0x7f00
[
disco verification:
ubuntu@d06-4:~$ cat /proc/version
Linux version 5.0.0-16-generic (buildd@bos02-arm64-013) (gcc version 8.3.0
(Ubuntu/Linaro 8.3.0-6ubuntu1)) #17-Ubuntu SMP Wed May 15 10:54:19 UTC 2019
ubuntu@d06-4:~$ sudo dmesg -c > /dev/null
ubuntu@d06-4:~$ echo function | sudo tee
/sys/kern
Bionic verification:
(initramfs) cat /proc/version
Linux version 4.15.0-51-generic (buildd@bos02-arm64-037) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #55-Ubuntu SMP Wed May 15 14:27:56 UTC 2019
(initramfs) modprobe -r hisi_sas_v3_hw
[ 217.311945] systemd-udevd[1224]: passed device to ne
Verification:
ubuntu@d06-2:~$ cat /proc/version
Linux version 4.15.0-51-generic (buildd@bos02-arm64-037) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #55-Ubuntu SMP Wed May 15 14:27:56 UTC 2019
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You re
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
o the Hi1620 device and other users of the marvell phy.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Ryan: Is this still a problem w/ 4.15? Do you need a full OpenStack
setup to reproduce it, or is just a single node nova model enough?
--
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/177573
The hisi_sas maintainer is experimenting with a patch that will change
the driver's 33 page allocations to single page allocations. If there is
no significant performance impact, that could be a way forward to deal
with the fragmentation issue costing us up to 31M of CMA.
In addition, there is DMA
** Description changed:
[Impact]
The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3
ARM systems.
[Test Case]
sudo apt install linux-crashdump
Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as
appropriate (for D06, crashkernel=512M)
s
cided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in:
Marking critical, as this prevents X-Gene/uboot systems from booting
** Changed in: linux-signed-hwe-edge (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 Ubu
Marking critical, as this prevents X-Gene/uboot systems from booting
** Changed in: linux-signed-hwe-edge (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
** Also affects: linux-signed-hwe-edge (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-signed-hwe-edge (Ubuntu Cosmic)
Status: New => Invalid
** Changed in: linux-signed-hwe-edge (Ubuntu Disco)
Status: New => Invalid
** Changed in: linux-signed-hwe-edge (U
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Disco)
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.
I've split the ratelimiting topic out to bug 1828092 so to keep this one
open while we continue to try and solve the underlying cause of the
messages.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Public bug reported:
[Impact]
As described in bug 1823753, failures to allocate DMA out of CMA space can
result in ~10K cma_alloc() error messages. While non-fatal (the code falls back
to allocating memory out of non-CMA space), the error messages themselves can
be a problem - esp. for systems
Why would it fail to init? If CMA allocation fails, the kernel will
fulfill the request using alloc_pages_node():
struct page *__dma_direct_alloc_pages(struct device *dev, size_t size,
dma_addr_t *dma_handle, gfp_t gfp, unsigned long attrs)
{
[...]
/* CMA can be used only i
As per Seth's suggestion, I tried ratelimiting the cma_alloc messages:
diff --git a/mm/cma.c b/mm/cma.c
index c7b39dd3b4f6..56d2a046f689 100644
--- a/mm/cma.c
+++ b/mm/cma.c
@@ -477,7 +477,7 @@ struct page *cma_alloc(struct cma *cma, size_t count,
unsigned int align,
page_
Note that in current disco things have gotten worse - our single page
allocations have blown up to 11753:
$ cat cma.disco.dmesg | grep "cma: cma_alloc(cma" | sed -r 's/.*count
([0-9]+)\,.*/\1/' | sort -n | uniq -c
11753 1
3 2
3 4
234 8
32 16
2 24
4 32
256 33
The culprit for the 256 33 page allocations (that causes the
fragmentation mentioned in comment #8) is the hisi_sas_v3_hw driver:
[ 21.220867] Call trace:
[ 21.223301] dump_backtrace+0x0/0x1b0
[ 21.226948] show_stack+0x24/0x30
[ 21.230251] dump_stack+0x90/0xb4
[ 21.233554] cma_alloc+
To try to understand how the CMA is allocated - and what the problem
might be - I booted a HiSilicon D06 w/ plenty of cma cushion (cma=128M),
and looked at cma debugfs. In the upstream thread, Robin asked if this
was potentially an issue with lots of 1 page allocations - something for
which patches
nassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Cosmic)
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/1827437
Tit
Public bug reported:
[Impact]
Potential memory corruption.
[Test Case]
I've not seen a failure in practice (well, it's easy to crash 5.0 but, as the
commit message notes, that's because it includes an additional patch that
happens to "tickle" this. But to regression test, I boot a HiSilicon D06
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because y
Just to add a tag back, this fix is causing regressions on some server
platforms in bug 1823753
--
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/1803206
Title:
Please enable CONFIG_DMA_CMA
nly used on ARM servers based on the
Hi1616 SoC.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bio
** Description changed:
[Impact]
Attempting to enable the function tracer causes an Oops. This impacts the
current disco kernel, as well as latest upstream
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).
This is 100% reproducible on D06 CS systems, but not reproducible on D06
ES systems
Note that this appears to be a regression introduced by bug 1803206.
Disabling DMA_CMA avoids it - but obviously would regress bug 1803206.
--
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/18
Upstream thread:
http://lists.infradead.org/pipermail/linux-arm-kernel/2019-April/647345.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/1823753
Title:
arm64: cma_alloc errors at b
On Tue, Apr 16, 2019 at 1:26 PM Jo Shields wrote:
>
> I'm an idiot and should have been trying the version from -proposed, of
> course. Working on it
Whups, yeah - so was I :) I thought for sure I had enabled -proposed
on my D05
Anyway, I was also an idiot and didn't realize I could just chec
On Tue, Apr 16, 2019 at 1:50 PM Jo Shields wrote:
>
> OK, yes, confirmed I have ethernet with 4.15.0-48.51
Awesome, thanks!
--
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/1818294
Title:
@directhex: Are you able to test this on your XR320? I've regression
tested on a HiSilicon D05 which uses the same driver (it worked before,
still works now).
ubuntu@d05-5:~$ cat /proc/version
Linux version 4.15.0-47-generic (buildd@bos02-arm64-022) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubunt
This patch resolves the problem for me, thx Ard!
https://patchwork.kernel.org/patch/10899313/
--
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/1822871
Title:
enabling ftrace on Hi1620 CS
On Wed, Apr 10, 2019 at 11:01 AM Ard Biesheuvel
wrote:
>
> On Tue, 9 Apr 2019 at 16:30, dann frazier wrote:
> >
> > Yeah, no crash anymore - thanks Ard!
> >
> > ubuntu@d06-4:~$ echo function | sudo tee
> > /sys/kernel/debug/tracing/current_tracer
> &g
** Changed in: linux (Ubuntu)
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/1822871
Title:
enabling ftrace on Hi1620 CS causes
off
ifconfig enp129s0f0 mtu 1501
iperf -c -l 64K -t 3
[Fix]
5f543a54eec08 net: hns3: fix for not calculating tx bd num correctly
[Regression Risk]
Fix is restricted to a driver only used in Hi1620 SoC-based systems.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann
[ 72.778123] ftrace: far branches to multiple entry points unsupported inside
a single module
[ 72.786657] WARNING: CPU: 121 PID: 3299 at
/home/ubuntu/linux-5.0.0/kernel/trace/ftrace.c:2008 ftrace_bug+0xb0/0x2b0
[ 72.786662] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds
tpm_
Yeah, no crash anymore - thanks Ard!
ubuntu@d06-4:~$ echo function | sudo tee
/sys/kernel/debug/tracing/current_tracer
function
[ 72.778123] ftrace: far branches to multiple entry points unsupported inside
a single module
^ I assume this is expected
--
You received this bug notification bec
I have a fix staged for this, but it relies on published signed binaries
that aren't present.
dannf, ok the signing component appears in rejected ...
will try and get to the bottom of why that happened
So assigning to apw for now...
** Changed in: linux (Ubuntu)
Status: Incomplete => In
tu Cosmic)
Status: New => Invalid
** Changed in: linux-signed (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux-signed (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux-signed (Ubuntu Bionic)
Status: New => In Pr
** Summary changed:
- Build-Using incorrect
+ Built-Using incorrect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1824016
Title:
Built-Using incorrect
Status in linux-signed pa
** Also affects: linux-signed (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-edge (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affec
Public bug reported:
[Impact]
The Build-Using control file field is incorrect for linux-signed-hwe &
linux-signed-hwe-edge. They claim they were built against the "linux" package,
but should be linux-hwe/linux-hwe-edge respectively.
[Test Case]
Look at the Packages file.
[Fix]
Detect and inser
It appears that linux-signed-hwe-edge does not yet have the arm64
support we added to linux-signed.
** Summary changed:
- not able to install linux-generic-hwe-18.04-edge/bionic-proposed
+ arm64: not able to install linux-generic-hwe-18.04-edge/bionic-proposed
--
You received this bug notifica
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823753
Title:
arm64: cma_alloc errors at boot
Status in linux packag
I enabled CMA_DEBUG & CMA_DEBUGFS and booted w/ cma=128M so that we can
see the CMA state when no allocations fail.
root@d06-4:/sys/kernel/debug/cma/cma-reserved# cat count
32768
root@d06-4:/sys/kernel/debug/cma/cma-reserved# cat used
15630
Looks like we're actually using ~61M - and perhaps the
This was not an issue prior to v4.20. Bisection identified the following commit:
886643b766321 arm64: use the generic swiotlb_dma_ops
--
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/182375
The disco kernel uses CONFIG_CMA_SIZE_MBYTES=16, while the arm64
defconfig sets it to 32. I tried bumping up this setting by powers of 2
until the messages went away, and it finally did at 128, which seems
extreme. Need to figure out what is attempting these allocations, and
why they are failing.
Public bug reported:
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:
Verification: Ran netperf between 2 D06 hosts, one running the bionic-
proposed kernel, the other the cosmic-proposed kernel, w/o error.
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bu
Verified - boot tested both cosmic & bionic proposed kernels on a D06
system.
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-don-bionic verification-done-cosmic
** Tags removed: verification-don-bionic
** Tags added: verification-done-bionic
--
Marking "In Progress" for disco, as a patch was submitted:
https://lists.ubuntu.com/archives/kernel-team/2019-March/099315.html
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which
hns_roce_v2_modify_qp
[Regression Risk]
Driver is only for HNS nics on HiSilicon SoCs
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: lin
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822871
Title:
enabling ftrace on Hi1620 CS causes an Oops
Status in
** Summary changed:
- enabling ftrace on Hi1620 causes an Oops
+ enabling ftrace on Hi1620 CS causes an Oops
** Description changed:
[Impact]
Attempting to enable the function tracer causes an Oops. This impacts the
current disco kernel, as well as latest upstream
(@5e7a8ca319268a70a6c7c3c
Bisection led to the following commit:
# first bad commit: [bdb85cd1d20669dfae813555dddb745ad09323ba]
arm64/module: switch to ADRP/ADD sequences for PLT entries
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
Public bug reported:
[Impact]
Attempting to enable the function tracer causes an Oops. This impacts the
current disco kernel, as well as latest upstream
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).
[Test Case]
$ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer
[ 3125.651453] k
** Description changed:
[Impact]
- Driver will report TX errors
+
[Test Case]
+
[Fix]
5f543a54eec08 net: hns3: fix for not calculating tx bd num correctly
[Regression Risk]
Restricted to hns3 driver, only used for HiSilicon ARM SoCs.
--
You received this bug notification b
cided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Kern
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are
** Description changed:
[Impact]
+ Driver will report TX errors
+
[Test Case]
+
[Fix]
5f543a54eec08 net: hns3: fix for not calculating tx bd num correctly
+
[Regression Risk]
+ Restricted to hns3 driver, only used for HiSilicon ARM SoCs.
--
You received this bug notification because
: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Kernel
Packages, wh
)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a mem
** Changed in: linux (Ubuntu Cosmic)
Status: New => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821620
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Xenial)
Status: New => Won't Fix
** Description changed:
[Impact]
SATA disks may be unusable
will n
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (u
** Description changed:
[Impact]
SATA disks may be unusable
will not be usable when:
- - The disk is connected through a SAS expander
- - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
- - link rate between expander & disk is greater than link between controller
and exp
** Description changed:
[Impact]
- Some HiSilicon SoCs do not implement registers that the cpufreq subsystem
uses to calculate current performance. This can result in undefined data being
used in internal calculations, and being exposed to userspace via sysfs.
+ Some HiSilicon SoCs do not imp
]
The fix is a quirk restricted to specific SoCs. It does rely on firmware
behaving (overloading the desired_perf register w/ a correct actual perf
value), so changes in firmware could lead to regressions.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf
This change should qualify for an SRU. However, Canonical does not have
the described hardware. We will need help from Huawei to test the SRU.
Can Huawei commit to the following steps?
1) Test a PPA build with this fix (both 4.15 and 4.18) by 2019-03-27.
Canonical can prepare this PPA.
2) After
; statement that meets these restrictions.
A bug in this code could possibly reduce the speed of an otherwise working disk
connection.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Xenial)
Importance: Un
Sorry, previous one was bionic. This is cosmic:
ubuntu@d06-2:~$ cat /proc/version
Linux version 4.18.0-17-generic (buildd@bos02-arm64-075) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:57 UTC
2019
ubuntu@d06-2:~$ sudo ethtool enp125s0f1
Settings for e
cosmic verification:
ubuntu@d06-2:~$ cat /proc/version
Linux version 4.15.0-47-generic (buildd@bos02-arm64-022) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #50-Ubuntu SMP Wed Mar 13 10:42:02 UTC 2019
ubuntu@d06-2:~$ sudo ethtool enp125s0f1
Settings for enp125s0f1:
Supported ports:
signed) => 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/1821064
Title:
hns3: fix oops in hns3_clean_rx_ring()
Status in linux package in Ubuntu:
Fix Released
Status
adds a new read
barrier, there is a potential performance regression risk.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: High
Assignee: dann frazier (
Sorry, I'm unable to verify this for xenial. I submitted it as an SRU
back to 4.4 because it had already landed in the stable queue for 4.4,
and is a trivial change[*]. I think we'd need a system that either uses
mvsas or aix94xx to actually exercise this libsas code on 4.4.
I do have a system tha
= cosmic verification =
After running cert:
ubuntu@d06-4:~$ cat /proc/version
Linux version 4.18.0-17-generic (buildd@bos02-arm64-075) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:57 UTC
2019
ubuntu@d06-4:~$ dmesg | grep CMD_SYNC
** Tags removed: v
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
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/1818747
Title:
Crash in nvme_irq_check() when using thr
** 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/1818747
Title:
Crash in nvme_irq_check() when using thr
cosmic verification:
ubuntu@d06-1:~$ cat /proc/version
Linux version 4.18.0-17-generic (buildd@bos02-arm64-075) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:57 UTC
2019
ubuntu@d06-1:~$ ls -l /dev/disk/by-path
total 0
lrwxrwxrwx 1 root root 9 Mar 19
= bionic verification =
After running cert:
ubuntu@d06-4:~$ cat /proc/version
Linux version 4.15.0-47-generic (buildd@bos02-arm64-022) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #50-Ubuntu SMP Wed Mar 13 10:42:02 UTC 2019
ubuntu@d06-4:~$ dmesg | grep CMD_SYNC
ubuntu@d06-4:~$
** Tags rem
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1817969
Title:
hns3 nic speed may not match optical port spe
Verified - I was able to successfully crash dump a cosmic system.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
edium
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Cosmic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects:
ying and cherry-picking individual patches
would be more error prone then re-syncing with current upstream.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification because you are a member of Ke
** Description changed:
[Impact]
Per https://patchwork.kernel.org/cover/10737541/ :
"Every controller HW version has had bugs. These bugs have been very
painful to debug. One useful tool to debug these is being able to capture
and export HW registers and driver control structures at p
** Description changed:
[Impact]
Per https://patchwork.kernel.org/cover/10737541/ :
"Every controller HW version has had bugs. These bugs have been very
painful to debug. One useful tool to debug these is being able to capture
and export HW registers and driver control structures at p
and device debugfs directories
[Regression Risk]
Code changes are restricted to the on-chip SAS controller on hi1620 SoCs.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification because you are a
On Fri, Mar 8, 2019 at 2:00 PM Jo Shields wrote:
>
> This'll filter through to the HWE kernel in Xenial without needing to be
> individually tracked in this bug (or a new one), right?
That is correct.
--
You received this bug notification because you are a member of Kernel
Packages, which is su
601 - 700 of 1626 matches
Mail list logo
