I've verified that this is resolved in both linux_4.4.0-101.124 and
linux-hwe_4.10.0-40.44~16.04.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/1695093
Title:
arm64: "unsupported RELA
Uploaded qemu_2.8+dfsg-3ubuntu2.8 to unapproved.
--
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/1710019
Title:
support GICv3 ITS save/restore & migration
Status in linux package in Ubun
** Description changed:
[Impact]
Virtual machines on GICv3-based ARM systems cannot be saved/restored or
migrated.
This feature was added in QEMU 2.10.
[Test Case]
ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav
Domain 7936-0 saved to 7936-0.sav
ubuntu@grotrian:~$ sudo
I have a staging PPA that I'm using for testing at ppa:dannf/lp1710019.
The QEMU there is the attached debdiff (trivially) forward-ported to the
latest qemu in updates, and the kernel has the patches I plan to submit
to the kernel team. I've verified that this all works together on a
zesty system.
libvirt's apparmor policy doesn't allow for restoring instances from /tmp, so
I've updated my reproducer tool:
https://code.launchpad.net/~dannf/+git/vm-save-restore
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
I plan to submit my backport to zesty's (4.10) kernel - I haven't yet
investigated the feasibility of backporting this feature to xenial's
virt stack. With respect to QEMU, at this time I'm only requesting that
the backport for zesty be considered.
--
You received this bug notification because yo
@Christian: The blocking issue was with the kernel. It has now been
fixed upstream and I've begun submitting SRU patches for the kernel. +1
from me on proceeding with the QEMU portion.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
ubuntu@starbuck:~$ dmesg --level=err
[2.593406] Error parsing PCC subspaces from PCCT
[2.628707] pci :1f:00.0: BAR 0: failed to claim resource for efifb!
[ 13.457667] Couldn't get size: 0x800e
[ 13.462362] MODSIGN: Couldn't get UEFI db list
[ 13.466810] Couldn't get si
** Changed in: linux (Ubuntu Zesty)
Status: Confirmed => In Progress
--
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/1721365
Title:
ixgbe/PCIe: Allow drivers to use Relaxed Orderin
** Description changed:
[Impact]
A signficant performance gain can be achieved with the iperf benchmark by
allowing the ixgbe driver to take advantage of PCIe Relaxed Ordering, as
observed on the HiSilicon D05 system.
[Test Case]
Setup two servers with dual-port PCIe ixgbe cards, conn
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Zesty)
ing on capable root ports
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
** Description changed:
[Impact]
- A ~12% performance gain can be achieved with the iperf benchmark by allowing
the ixgbe driver to take advantage of PCIe Relaxed Ordering, as observed on the
HiSilicon D05 system.
+ A signficant performance gain can be achieved with the iperf benchmark by
all
** Changed in: linux (Ubuntu Artful)
Status: Confirmed => In Progress
** Description changed:
- I observed this stack trace when attempting to install the 2017.09.26
- daily arm64/artful server ISO:
+ [Impact]
+ I observed this stack trace when attempting to install the 2017.09.26 daily
a
** Changed in: linux (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: linux (Ubuntu Artful)
** Changed in: linux (Ubuntu Artful)
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/1720229
Title:
arm64: usercopy: kernel mem
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: 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/1720229
Title:
arm64: usercopy: kernel memory over
This can be easily reproduced on a running VM with the command:
sudo dmraid -r -c
Bisection shows that this regression was introduced with:
ca18d6f769d22e931d3ba1e8d1ae81953547a417 is the first bad commit
commit ca18d6f769d22e931d3ba1e8d1ae81953547a417
Author: Bart Van Assche
Date: Tue Jun 20
I verified that the kdump failure symptom (Comment #3) has now been
resolved. The crashkernel successfully boots into userspace and is able
to complete the dump collection.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification bec
that is only being distributed for development purposes.
** 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 U
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Zesty)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Using bisection, I've determined that this was introduced in the
following xenial commit:
commit 69747b70c731cc7081e7d13a0f536bb451f5a385
Author: Iyappan Subramanian
Date: Mon Jul 25 17:12:42 2016 -0700
drivers: net: xgene: Enable MDIO driver
--
You received this bug notification because
]
(Still under investigation)
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Fix Released
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux
)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Confirmed
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: linux (Ubuntu Zesty)
Assig
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Description changed:
- We are seeing build failures in ADT when building for an autopkgtest
- profile driven build on armhf.
+ [
** 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/1720229
Title:
arm64: usercopy: kernel memory overwrite attempt detect
Public bug reported:
I observed this stack trace when attempting to install the 2017.09.26
daily arm64/artful server ISO:
[ 107.816592] usercopy: kernel memory overwrite attempt detected to
(null) () (6 bytes)
[ 107.818389] Internal error: Oops - BUG: 0 [#1] SMP
[ 107.819170] Module
Public bug reported:
4.4.0-97-generic #120-Ubuntu
I observed the following failure during autopkgtesting of the linux
package:
The full log is here, and also attached:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l
ubuntu@equal-beetle:~$ cat /proc/version
Linux version 4.10.0-36-generic (buildd@bos01-arm64-013) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #40~16.04.1-Ubuntu SMP Tue
Sep 19 15:20:18 UTC 2017
ubuntu@equal-beetle:~$ sudo dmesg | grep -i arch_timer
[0.00] arch_tim
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member
Public bug reported:
Early silicon in Cavium cn99xx (previously known as Broadcom Vulcan)
systems has an errata that can result in SATA hangs. Since this will be
fixed in later silicon, and the impacted silicon will have a very
limited distribution/life span for non-production scenarios, there is
** Description changed:
- Early silicon in Cavium cn99xx systems requires a PCI quirk for SATA to
- work. Since this will be fixed in later silicon, and the impacted
- silicon will have a very limited distribution/life span for non-
- production scenarios, there is no plan to push a fix upstream.
plan to
push a fix upstream. However, it would be valuable for users evaluating
this silicon if Ubuntu could carry the quirk patch for the 17.10 cycle.
** Affects: linux (Ubuntu)
Importance: High
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You
gcc-5/xenial verified:
ubuntu@neander:~$ cat /proc/version
Linux version 4.4.0-96-generic (buildd@bos01-arm64-013) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #119-Ubuntu SMP Tue Sep 12
15:00:28 UTC 2017
ubuntu@neander:~$ sudo dmesg -c > /dev/null
ubuntu@neander:~$ sudo
** Description changed:
+ [Impact]
+ Certain kernel modules are unloadable (libceph & scsi_debug) due to the
compiler generating unsupported relocations.
+
+ This symptom is similar to LP: #1533009 but, in that case it impacted
+ all modules, and the fix for that appears to remain in place.
+
+
On Wed, Sep 6, 2017 at 2:50 AM, ChristianEhrhardt
<1710...@bugs.launchpad.net> wrote:
> Dann, I don't want to miss the activity here - so the next step you are
> expecting is me to evaluate the diff in detal and prep a qemu SRU?
> Along that you will do regression tests on arm and I could do x86/p
dannf@d05-3:~$ cat /proc/version
Linux version 4.10.0-34-generic (buildd@bos01-arm64-030) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #38~16.04.1-Ubuntu SMP Wed
Aug 30 18:05:59 UTC 2017
dannf@d05-3:~$ ls -l /sys/class/i2c-dev/*/device/firmware_node
lrwxrwxrwx 1 root root
uires errata not having the appropriate workaround applied. (Which are
also the conditions that the suggested backports are attempting to fix).
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) =>
On Wed, Aug 30, 2017 at 12:35 AM, ChristianEhrhardt
<1710...@bugs.launchpad.net> wrote:
> Hi Dann,
> Sorry to ask, really I'm not neglecting all the work you do here.
> But it is a huge set of changes (17 files changed, 929 insertions(+), 46
> deletions(-), and not all arm only) and I wonder as Ze
ubuntu@dawes:~$ sudo apt install kdump-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
binutils crash kexec-tools libdw1 makedumpfile
Suggested packages:
binutils-doc
The following NEW pac
** Description changed:
[Impact]
- cntvct_el0 could be left untrapped if reset with the user access bit set
+ This bug captures a few issues with the ARM arch_timer driver:
+
+ 1) Some arm64 systems have hardware defects in their architected timer
+ implementations that require errata, which we
Public bug reported:
[Impact]
cntvct_el0 could be left untrapped if reset with the user access bit set
[Test Case]
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: Confirmed
** Patch added: "qemu-zesty-gicv3sr.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1710019/+attachment/4940998/+files/qemu-zesty-gicv3sr.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Here's a backport for zesty's QEMU, tested with the 4.13.0-7.8 kernel
from ppa:canonical-kernel-team/unstable w/ the patch from Comment #10
applied.
** Changed in: qemu (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Pa
n: linux (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: linux (Ubuntu Zesty)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: qemu (Ubuntu)
Assignee: dann frazier (dannf) => (unassigned)
I've been able to backport the fixes back as far as 4.7. 4.7 was when
the new vgic reimplementation was merged, and the upstream patchset
would need significant surgery to apply. To fix Ubuntu 16.04's GA kernel
(4.4-based), we'd probably need to develop a new (hopefully simpler)
solution. In the me
Note: in the above:
old = 4.10.0-32.36
new = 4.10.0-33.37
--
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/1708734
Title:
hisi_sas performance improvements
Status in linux package in
For a 1 disk setup, I'm seeing a tiny - possibly insignificant -
improvement. There's no obvious regression, so I'll go ahead and mark
verified.
dannf@d05-3:~$ tail -n2 fio.out.*
==> fio.out.new <==
Disk stats (read/write):
sda: ios=45/80729, merge=0/4929748, ticks=856/3320144, in_queue=3321592,
dannf@d05-3:~$ sudo dmesg -c > /dev/null
[sudo] password for dannf:
dannf@d05-3:~$ sudo ethtool -t enahisic2i1
The test result is PASS
The test extra info:
MacLoopback test 0
Serdes Loopback test 0
PhyLoopback test 0
dannf@d05-3:~$ dmesg
[439684.269761] IPv6: ADDRCONF(NETDEV_U
Regression tested by doing a kernel compile using disk attached to the
hisi_sas controller.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Regression tested by doing a kernel compile using disk attached to the
hisi_sas controller.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The fixed from Debian has now been merged into artful.
** Changed in: makedumpfile (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1676884
Verified w/ remote eyes:
dannf: OK, both are moved, but I don't see link lights yet.
rodsmith: ok - lemme bring them up
dannf: OK, link lights are on.
rodsmith: hot damn! thanks rodsmith!
dannf: Green plus blinking amber.
** Tags removed: verification-needed-zesty
** Tags added: verification
I've ran the vm-start-stop test on a ThunderX system for an hour on the
proposed kernel w/o any issues.
** Tags removed: patch verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
** Attachment added: "dmesg output of proposed kernel collected via ssh over
hns NIC"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704885/+attachment/4933839/+files/dmesg.out
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug
I've tested this kernel and observed no regressions. Updated firmware
has not been released to expose these IDs, so I can't directly test
this. However, it turns out that there is a typo in the ACPI IDs that
has since been fixed upstream, meaning the proposed patches are
insufficient to solve the i
[Regression Risk]
This adds an ID/config for previously unsupported ACPI IDs.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Zesty)
Importance: Undecided
Assignee: dann frazier (dannf
fyi, I have a patch set prepared for this in the Debian bug. I'd like to
see that uploaded in Debian before integrating it in Ubuntu because, if
Debian chooses a different solution, it will be difficult to back that
that out and resync. I've sent a ping to the Debian bug today.
--
You received th
The timeout issue described in comment #8 is being tracked in LP:
#1709727.
** Changed in: gcc-5 (Ubuntu)
Status: New => Triaged
** Changed in: gcc-5 (Ubuntu Xenial)
Status: Confirmed => Triaged
** Changed in: gcc-5 (Ubuntu Yakkety)
Status: New => Won't Fix
** Changed in: g
t; Medium
** Changed in: linux (Ubuntu Zesty)
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/1708734
Title:
hisi_sas performance
improvement.
[Regression Risk]
The fixes are localized to the hisi_sas driver.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: dann frazier (dannf)
Status: Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The fix is localized to a specific driver, and is a clean cherry-pick from
upstream. Regressions would be localized to systems w/ this (onboard) hardware.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ub
** Changed in: linux (Ubuntu Zesty)
Status: Confirmed => In Progress
--
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/1708714
Title:
scsi: hisi_sas: add null check before indirect p
resulting in
corruption, etc).
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Zesty)
Importance: Medium
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ub
ems, it is possible that there are issues that
our test isn't finding, which would likely surface as KVM guest crashes/hangs.
** Changed in: linux (Ubuntu Zesty)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) => dann frazier (dan
** Attachment added: "vm-start-stop.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673564/+attachment/4926651/+files/vm-start-stop.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1708293
Title:
support Hip07/08 I2C controller
Status in linux p
** Description changed:
[Impact]
The i2c driver does not recognize the ACPI IDs for the i2c devices on the
Hip07/08 platforms, making these devices unusable.
[Test Case]
+ ls -l /sys/class/i2c-dev/*/device/firmware_node | grep HISI
+
[Regression Risk]
+ This adds an ID/config for a
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Zesty)
Public bug reported:
[Impact]
The i2c driver does not recognize the ACPI IDs for the i2c devices on the
Hip07/08 platforms, making these devices unusable.
[Test Case]
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Z
** Attachment added: "console.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703437/+attachment/4925349/+files/console.log
--
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/170
Attached is a boot log w/ the fixed kernel that shows the SMMU being
discovered, the system successfully mounting the root disk, etc.
However, the system does seem to hang at the end with the networking
failing to come up.
This is an improvement, and booting in non-ACPI mode shows no
regressions,
htool
funcionality (i.e. workaround for regression would be don't-do-that).
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Zesty)
Importance: Undecided
Assignee: dann frazier (dannf)
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
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/1704146
Title:
hns: under heavy load, NIC may fail and re
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
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/1702749
Title:
arm64: fix crash reading /proc/kcore
Stat
Preemptive verification:
root@d05-3:~# cat /proc/version
Linux version 4.10.0-29-generic (buildd@bos01-arm64-012) (gcc version 6.3.0
20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #33-Ubuntu SMP Wed Jul 19 13:37:12
UTC 2017
root@d05-3:~# cat /proc/kcore > /dev/null&
[1] 9206
root@d05-3:~#
(/proc/k
Preemptive verification:
dannf@xps13:~$ ssh 10.XXX.XXX.XXX cat /proc/version
Warning: Permanently added '10.XXX.XXX.XXX' (ECDSA) to the list of known hosts.
Linux version 4.10.0-29-generic (buildd@bos01-arm64-012) (gcc version 6.3.0
20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #33-Ubuntu SMP Wed Ju
dannf@d05-3:~$ sudo apt install kdump-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
crash kexec-tools makedumpfile
The following NEW packages will be installed:
crash kdump-tools kexec-t
Importance: Medium
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Zesty)
Importance: Medium
Assignee: dann frazier (dannf)
Status: In Progress
** Summary changed:
- 2/4 Hisilicon D05 onboard NIC link indicator LEDs don't
* Changed in: linux (Ubuntu Zesty)
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/1704885
Title:
hns: use after free in hns_nic
** Changed in: makedumpfile (Ubuntu Xenial)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Description changed:
- $ ls arch/
- arm.c ia64.c ppc.c ppc64.c s390x.c x86.c x86_64.c
+ [Impact]
+ kdump
** Also affects: makedumpfile (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1238110
Title:
makedumpfile needs porting
kexec-tools/xenial verification
---
1) MAAS-deployed a clean xenial install
2) Added -proposed to sources.list
3) xenial linux-hwe doesn't yet have arm64/kdump support, so I installed
linux-hwe from ppa:canonical-kernel-team/ppa to get a new enough version.
4) Also in
is specific to a HiSilicon SoC.
Regression risk is mitigated by testing on that system (boot, generating
network activity over a NIC that uses this driver).
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this
kexec-tools/zesty verification
---
1) MAAS-deployed a clean zesty install
2) Added -proposed to sources.list
3) apt update; apt dist-upgrade; apt install kdump-tools
4) Edited /etc/default/grub.d/kdump-tools.cfg and set crashkernel=1G-:512M
(this step is required unti
I uploaded a package w/ the patch from Comment #7 to ppa:dannf/test. Note that
the tests took a *very* long time on arm64, with lots of timeouts:
https://launchpad.net/~dannf/+archive/ubuntu/test/+build/13073558
This was not a problem for other architectures.
I did a local arm64 build of the *c
** Changed in: linux (Ubuntu Zesty)
Status: New => In Progress
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Zesty)
Importance: Undecided => Critical
--
You received this bug notification because you are
ectly test.
** Affects: linux (Ubuntu)
Importance: Critical
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.
https://bugs.launchpad.net/bugs/1704146
Here's a backport of the gcc-6 fix to gcc-5. It includes a backport of
the -mpc-relative-literal-loads option rename change, since it was a
dependent patch, and I'm not comfortable enough w/ gcc development to do
the backport w/o it.
** Patch added: "gcc-5-backport.debdiff"
https://bugs.launch
After update, I verified that the system still survives a 30s iperf run
w/ no performance regression.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
ubuntu@grotrian:~$ cat /proc/version
Linux version 4.10.0-28-generic (buildd@bos01-arm64-012) (gcc version 6.3.0
20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #32-Ubuntu SMP Fri Jun 30 05:33:10
UTC 2017
ubuntu@grotrian:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic
root=UUID=fcf02
ubuntu@d05-3:~$ cat /proc/version
Linux version 4.10.0-28-generic (buildd@bos01-arm64-012) (gcc version 6.3.0
20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #32-Ubuntu SMP Fri Jun 30 05:33:10
UTC 2017
ubuntu@d05-3:~$ sudo stress-ng --class io --sequential 64
stress-ng: info: [7461] rdrand stressor
This is fixed by the following commit in linux-next:
commit 84c24379a783c514e5ff7c8fc8a21cf8d64fd05f
Author: Robin Murphy
Date: Mon Jun 19 16:41:56 2017 +0100
iommu/arm-smmu: Plumb in new ACPI identifiers
--
You received this bug notification because you are a member of Kernel
Packages,
]
The upstream fix is adding support for new device IDs, which were previously
unsupported and would've previously failed to probe w/ -ENODEV.
** Affects: linux (Ubuntu)
Importance: High
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Zesty)
ged in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu Zesty)
Importance: Undecided => High
--
Public bug reported:
[Impact]
Reading /proc/kcore can lead to a crash on arm64 systems.
[Test Case]
# cat /proc/kcore > /dev/null
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Confirmed
** Changed in: linux (Ubu
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1699874
Title:
i386 dumps unusable w/ kernels > 4.4
Status in c
** Changed in: gcc-6 (Ubuntu Xenial)
Status: Confirmed => Invalid
** Also affects: gcc-5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gcc-5 (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Pack
** Description changed:
Note: Updates are being staged at ppa:dannf/arm64-kdump.
[Impact]
It is not possible to collect a kernel crash dump from a crashed arm64 server
for later debugging.
[Test Case]
sudo apt install kdump-tools
(reboot, so crashkernel= is added to the kernel c
1101 - 1200 of 1628 matches
Mail list logo
