** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: kunpeng920/upstream-kernel
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853999
Title:
[sas-1126]scsi: hisi_sas: use wait_for_completion_timeo
** Changed in: kunpeng920/upstream-kernel
Milestone: None => linux-v5.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854550
Title:
[scsi-1130]scsi: scsi_transport_sas: Fix memory leak when rem
ntu-19.10
Milestone: None => ubuntu-19.10-sru-5
** Changed in: kunpeng920/ubuntu-19.10
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: kunpeng920/ubuntu-20.04
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: kunpeng920/ubuntu-20.04
Status: Tria
** Changed in: kunpeng920/ubuntu-19.04
Status: New => Triaged
** Changed in: kunpeng920/ubuntu-19.10
Status: New => Triaged
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: kunpeng920/ubuntu-19.04
Milestone: ubuntu-19.04-sru-11 => ubuntu-19.04-sru-12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853997
Title:
[sas-1126]scsi: hisi_sas: Fix the confli
There is no plan to reapply the kernel side of these fixes ahead of
18.04.4. Introducing the mdadm side of that in 18.04.4 therefore would
cause a regression in functionality:
ubuntu@ip-172-30-0-208:~$ sudo mdadm --create /dev/md0 --run
--metadata=default --level=0 --raid-devices=2 /dev/xvdb /dev/
Adding the block-proposed-* tags as per comment #11.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-disco verification-needed-eoan
** Tags added: block-proposed-bionic block-proposed-disco block-proposed-eoan
verification-done verification-done-bionic verific
** Changed in: kunpeng920
Status: New => Confirmed
** Changed in: qemu (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: qemu (Ubuntu Disco)
Status: New => Confirmed
** Changed in: qemu (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notificat
** Changed in: kunpeng920
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850117
Title:
[hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE
ke
** Changed in: kunpeng920
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854549
Title:
[acc-1130]sync mainline kernel 5.5rc1 acc patchset into ubuntu HWE
ker
@Ike: fyi, I have already prepared a backport for focal here:
https://code.launchpad.net/~dannf/ubuntu/+source/linux/+git/linux/+ref/lp1850117-f
I just didn't have a way to test it. Feel free to start with that (or not) :)
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
[Impact]
USB port unusable and boot time takes ~5 minutes longer to complete.
[Test Case]
dmesg | grep "Cannot enable"
[Fix]
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: Undecided
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
I tested the patch in Comment #34, and it was able to pass 500
iterations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805256
Title:
qemu-img hangs on rcu_call_ready_event logic in Aarch64 when
fyi, what I tested in Comment #35 was upstream QEMU (@ aceeaa69d2) with
a port of the patch in Comment #34 applied. I've attached that patch
here. While it did avoid the issue in my testing, I agree with Rafael's
Comment #36 that it does not appear to address the root cause (as I
understand it), an
git bisect reports:
0b6a70743beacb15516ef9572b40c93b8b3892d3 is the first bad commit
commit 0b6a70743beacb15516ef9572b40c93b8b3892d3
Author: Jan-Marek Glogowski
Date: Fri Feb 1 13:52:31 2019 +0100
usb: handle warm-reset port requests on hub resume
--
You received this bug notification because
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Description changed:
This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
[Impact]
USB port unusable and boot time takes ~5 minutes longer to complete.
+
+ Kernel emits messages like:
+ usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
[Test Case]
dme
Running upstream 5.5-rc2 mainline build:
$ dmesg | grep -e usb -e xhci -e hub
[ 13.482690] usbcore: registered new interface driver usbfs
[ 13.486685] usbcore: registered new interface driver hub
[ 13.490894] usbcore: registered new device driver usb
[ 20.767117] xhci_hcd :00:14.0: xHC
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854207
Title:
Unrevert "arm64: Use firmware to detect CPUs that are not affected by
Public bug reported:
[Impact]
This release contains both bug-fixes, new hardware support, and new features
for users of Mellanox network controllers. The notable ones are:
* bug 1864475 - Add RoCE disable support
[Test Case]
The following development and SRU process will be followed:
https:/
While we are seeking to fix this in bionic/eoan by backporting a new upstream
version (bug 1869441), note that it would have also been possible to backport
the mstreg command (and supporting infrastructure) to bionic's 4.8 version. See:
https://salsa.debian.org/dannf/mstflint/-/commit/261d0e65
** Changed in: mstflint (Ubuntu)
Status: New => Fix Released
** Changed in: mstflint (Ubuntu Bionic)
Status: New => In Progress
** Changed in: mstflint (Ubuntu Eoan)
Status: New => In Progress
** Changed in: mstflint (Ubuntu Bionic)
Assignee: (unassigned
** Also affects: libvirt (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864532
Title:
Incorrect nvram template for secboot firmware
To mana
** Changed in: libvirt (Ubuntu Eoan)
Status: New => Confirmed
** Changed in: libvirt (Ubuntu Eoan)
Importance: Undecided => Low
** Changed in: libvirt (Ubuntu)
Status: Confirmed => In Progress
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => dann fr
** Description changed:
In the ovmf package, /usr/share/OVMF/OVMF_CODE.ms.fd is a symlink to
OVMF_CODE.fd, which is a build of OVMF that does *not* support Secure
Boot. I assume the "ms" stands for Microsoft, whose signing keys are
included in the OVMF_VARS.ms.fd nvram template. If so, sho
** Also affects: edk2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864532
Title:
Incorrect nvram template for secboot firmware
To manage notif
After digging into this today, I'm thinking that I may not be using
OVMF_CODE.secboot.fd as intended. While I initially assumed that
specifying OVMF_CODE.secboot.fd would give you a system with Secure Boot
*active* - it actually just gives you a system where Secure Boot *could*
be activated, if the
** Changed in: edk2 (Ubuntu Bionic)
Status: New => Invalid
** Changed in: edk2 (Ubuntu)
Status: New => In Progress
** Changed in: edk2 (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bu
I've just uploaded the following changes to Debian:
https://salsa.debian.org/qemu-team/edk2/-/commit/1698e2a07e5c8a07ff0d772d2a9377ebe577d544
https://salsa.debian.org/qemu-team/edk2/-/commit/a08b306955cfde78b39028ae8bad44922e0c8e1b
https://salsa.debian.org/qemu-team/edk2/-/commit/e098d8cf95247fe32
I used the attached script to compare the contents of the existing &
proposed versions of this package in eoan and bionic. The output for
each follows. The set of utilities in -proposed is a superset of the
existing version in each release, so I'll check that off in the
validation checklist. Howeve
= Clean upgrade verifications =
== eoan ==
ubuntu@mstflint-eoan:~$ sudo apt install mstflint -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
libfreetype6
Use 'sudo apt a
= Command usage() regression checks =
Here's how I'm comparing the usage output of each command to make sure
no flags were dropped/changed:
$ mkdir cur proposed
$ dpkg -L mstflint | grep ^/usr/bin/ > mstflint.commands
$ for cmd in $(< mstflint.commands); do $cmd -h > cur/$(basename $cmd).usage;
** Patch added: "eoan-usages.diff"
https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1869441/+attachment/5345230/+files/eoan-usages.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869441
** Patch added: "bionic-usages.diff"
https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1869441/+attachment/5345231/+files/bionic-usages.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869
= Command usage analysis =
Summary - the -proposed usage statements all describe a superset of the
commands/arguments in the previous version, with one exception. In bionic,
mstflint's -qq argument used to say it affected both the burn and query
commands - but the -proposed version only claims t
** Changed in: libvirt (Ubuntu)
Status: In Progress => Invalid
** Changed in: libvirt (Ubuntu Eoan)
Status: Confirmed => Invalid
** Changed in: edk2 (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Thanks Jim - given that, I've marked the command line portion of the
testing complete.
** Description changed:
[Impact]
This release contains both bug-fixes, new hardware support, and new features
for users of Mellanox network controllers. The notable ones are:
* bug 1864475 - Add Ro
Also seeing this on a ppc64el system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865959
Title:
plymouth hook hangs waiting for input
To manage notifications about this bug go to:
https://bugs.l
Sorry, posted too quickly. Seen on a ppc64el system while dist-upgrading
after a default MAAS focal install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865959
Title:
plymouth hook hangs waiting
er ppa:ubuntu-s390x-community/mongodb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595242
Title:
mongodb xenial s390x packages are needed (blocks ceilometer)
To manage notifications about this bu
We probably want to do something like this to enable the mongodb charm for z:
https://code.launchpad.net/~dannf/charms/trusty/mongodb/arm64-default-to-ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
@Amr, sorry - my brain replaced "trusty" with "xenial" when I read your
reply. I've pushed a straight backport of the yakkety package to trusty
to ppa:dannf/test if you want to test that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ux (Ubuntu)
Importance: High
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Xenial)
Importance: High
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
**
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584024
Title:
debconf typo "connectivty"
To manage notifications about this bug
With the -proposed version, I'm seeing failures on arm64, apparently due
to the new dependency on containerd.
Starting Docker Socket for the API.
Listening on Docker Socket for the API.
Starting Docker Application Container Engine...
time="2016-07-01T15:45:38.219004000Z" level=info msg="New contai
gcc-5 5.4.0-5ubuntu1~16.04 from ppa:ubuntu-toolchain-r/ppa does accept
vulcan as an -mcpu option, and it does pass the correct -march settings
down to the assembler:
$ gcc -v hello.c -o hello 2>&1 | grep ' as '
as -v -EL -mabi=lp64 -o /tmp/ccgyMnhl.o /tmp/cchw8EFH.s
$ gcc -mcpu=vulcan -v hello.c
For xenial and artful, I have verified by:
1) Deploying an arm64 system (Cavium ThunderX CRB1S), enabling proposed,
installing kdump-tools, rebooting, then triggering a dump.
2) Regression/upgrade tested on x86 by launching a guest, installing
kdump-tools, rebooting, then trigger a dump. Next, e
** Changed in: mozjs24 (Ubuntu Yakkety)
Status: Triaged => Won't Fix
** Changed in: mozjs (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: mozjs (Ubuntu Yakkety)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
(Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: mozjs24 (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
assigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711478
Title:
[FTBFS] arm does not define __NR_migrate_pages
To manage notifications about this bug g
Regression Risk]
Including a new driver is a common practice that should have minimal regression
risk.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767490
Title:
Add d-i
ubuntu@hotdog:~$ sudo perf list | grep thunderx2
thunderx2 imp def:
ubuntu@hotdog:~$ cat /proc/version
Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0
(Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018
** Tags removed: verification-needed-ar
ubuntu@hotdog:~$ dmesg | grep W+X
[ 35.653992] arm64/mm: Found insecure W+X mapping at address
00ac9000/0x00ac9000
[ 36.046414] Checked W+X mappings: FAILED, 12 W+X pages found, 0 non-UXN
pages found
Yep, that's in the userspace mapping.
** Tags removed: verification-needed-
ubuntu@hotdog:~$ cat /proc/version
Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0
(Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018
ubuntu@hotdog:~$ sudo ipmitool lan print
Set in Progress : Set Complete
Auth Type Support : MD5
ubuntu@d05-1:~$ cat /proc/version
Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0
(Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018
ubuntu@d05-1:~$ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
enahisic2i0-tx0
enahisic2i0-tx1
enahisic2
** Changed in: linux-hwe-edge (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699822
Title:
[Regression] Breaks relationship w/ flash-kernel uses wrong versi
Public bug reported:
libnuma from the numactl source package was MIR'd in LP: #891232,
however the numactl binary is still in universe. I'd like to request
that the numactl binary also be considered for main. I work with users
of arm64 server platforms, where NUMA is increasingly common, and they
Should this request be approved, I'd also like to request that it be
considered retroactively for 16.04 so that LTS support is accelerated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700824
Title:
Public bug reported:
I've submitted an MIR for the numactl binary package at: LP: #1700824.
Assuming that is approved, please also include this on the server seed, which I
believe is necessary for it to appear on the ubuntu-server ISOs.
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Sorry, PEBKAC. Looks like the system I was on had both zesty-proposed &
xenial in the sources.list, so the hwe-edge metapackage was trying to
install the *zesty-proposed* deb. But, since zesty wasn't in the
sources.list, there was no new-enough flash-kernel to install.
** Changed in: linux-hwe-edg
** Bug watch added: Debian Bug tracker #800038
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800038
** Also affects: freeipmi (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800038
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** 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 Ubuntu
Bugs
hanged in: freeipmi (Ubuntu Artful)
Assignee: Ike Panhc (ikepanhc) => dann frazier (dannf)
** Changed in: freeipmi (Ubuntu Xenial)
Status: New => Triaged
** Changed in: freeipmi (Ubuntu Yakkety)
Status: New => Triaged
** Changed in: freeipmi (Ubuntu Zesty)
Stat
On Wed, Jun 14, 2017 at 3:13 PM, dann frazier
wrote:
> Cool, yeah - that looks like a more complete solution.
I've tested the latest curtin daily, and found that it does not
address this problem.
While http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/revision/503
seems like a good
** Description changed:
[Impact]
Typically when you install Ubuntu on an EFI system, it installs a new default
EFI boot entry that makes the system reboot directly into the OS. During MAAS
installs, curtin is careful to disable that behavior. MAAS requires the default
boot entry to remain P
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699874
Title:
i386 dumps unusable w/ kernels > 4.4
To manage notifications about
** Description changed:
[Impact]
Booting a Cavium ThunderX node in ACPI mode results in constant messages like
this to the console:
- arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402,
iova=0x0fffc000, fsynr=0x10081, cb=1
+ arm-smmu arm-smmu.1.auto: Unhandled context faul
** 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)
** Summary changed:
- arm64/thunderx: Unhandled cont
** Description changed:
[Impact]
Booting a Cavium ThunderX node in ACPI mode results in constant messages like
this to the console:
arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402,
iova=0x0fffc000, fsynr=0x10081, cb=1
In some configurations, this causes the SATA co
Changing tag to verified as per comments #13 & #14.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
x27;t support) and Cavium ThunderX2 systems that we've
specifically tested upon.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Artful)
Importance: Undecided
Assignee: dann fraz
Is this reproducible w/ the hwe kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630
Title:
aarch64: MSI is not supported by interrupt controller
To manage notifications about this bug go
Public bug reported:
[Impact]
A hardware issue can lead to a kernel crash or unexpected behavior.
[Test Case]
The issue presents itself most commonly as a boot-time crash. It doesn't effect
all Falkor CPUs, and only rarely occurs on CPUs that are effected.
[Regression Risk]
The fix is entirely
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu Zesty)
Importance: Undecide
** Summary changed:
- ThunderX: IPv6 TX failure unless checksum offload disabled
+ ThunderX: TX failure unless checksum offload disabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736593
Title:
cided
Assignee: dann frazier (dannf)
Status: In Progress
** Summary changed:
- hns3 support
+ Hisilicon Network Subsystem Support HNS3
** Summary changed:
- Hisilicon Network Subsystem Support HNS3
+ Hisilicon network subsystem 3 support
** Changed in: linux (Ubuntu)
Status
Public bug reported:
HiSilicon hip08 systems support a cq/rq record feature for RDMA that is
currently not supported by the kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification
e upstream patches.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762758
Title:
10:18 2018 +0100
RDMA/hns: ensure for-loop actually iterates and free's buffers
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
ubuntu@alekhin:~$ cat /proc/version
Linux version 4.13.0-39-generic (buildd@bos02-arm64-024) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #44~16.04.1-Ubuntu SMP Thu Apr
5 16:44:45 UTC 2018
ubuntu@alekhin:~$ dmesg | grep "failed to claim resource for efifb"
** Tags removed:
we have no port).
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Artful)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubu
** Description changed:
[Impact]
There are several stability issues with the i2c-xlp9xxx that cause
communication issues between the host and the BMC, leading to unpredictable
results when the ipmi-ssif module tries to enumerate the device (/dev/ipmi0).
[Test Case]
Reboot the system s
buntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762824
Title:
hisi_sas: Revert and replace SAUCE patches w/ ups
The problem appears to be that acpi=force is being specified on the
command line. Not all arm64 servers support ACPI and, even for the ones
that do, there isn't sufficient support in the 4.4 kernel to support
them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Description changed:
We're carrying a couple SAUCE patches for the hisi_sas driver to enable
- hip08 SoC support. Alternative patches have since landed upstream, which
- are more complete, and will be a better basis for backporting future
- patches to this driver.
+ hip08 SoC support. One of
** Changed in: makedumpfile (Ubuntu Artful)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694859
Title:
arm64 kernel crashdump support
To manage notifica
Public bug reported:
[Impact]
Crash dump support doesn't work by default on any known arm64 platform. Users
have to figure out working incantations for the crashkernel= parameter and the
parameters passed to the crash-dump kernel themselves and manual edit 2
different config files.
[Test Case]
ew => Fix Released
** Changed in: kexec-tools (Ubuntu)
Status: New => Fix Released
** Changed in: kexec-tools (Ubuntu Xenial)
Status: New => In Progress
** Changed in: kexec-tools (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: makedu
** Description changed:
[Impact]
Crash dump support doesn't work by default on any known arm64 platform. Users
have to figure out working incantations for the crashkernel= parameter and the
parameters passed to the crash-dump kernel themselves and manual edit 2
different config files.
+
** Description changed:
[Impact]
Crash dump support doesn't work by default on any known arm64 platform. Users
have to figure out working incantations for the crashkernel= parameter and the
parameters passed to the crash-dump kernel themselves and manual edit 2
different config files.
-
-auto/+bug/1351267/+attachment/5057359/+files/partman-auto.debdiff
** Also affects: partman-auto (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: partman-auto (Ubuntu Xenial)
Status: New => In Progress
** Changed in: partman-auto (Ubuntu Xenial)
Assignee: (unassi
I've tested 3 cases so far in QEMU, using the installer here:
http://ppa.launchpad.net/dannf/diswap/ubuntu/dists/xenial/main/installer-arm64/20101020ubuntu451.20+capminswap.1/
(Sorry it's arm64 only - the amd64 one FTBFS for an unrelated issue)
All tests are with the "All files in one partition" o
Verified:
ubuntu@dawes:~$ dmesg | grep Machine
[0.00] Machine model: Cavium ThunderX CN88XX board
ubuntu@dawes:~$ cat /proc/version
Linux version 4.13.0-36-generic (buildd@bos02-arm64-021) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #40~16.04.1-Ubuntu SMP Fri Feb
On Tue, Feb 20, 2018 at 4:05 AM, Kleber Sacilotto de Souza
wrote:
> Hi,
>
> We have reverted some arm64 patches that were causing boot issues so the
> system should be able to boot now. Could you please verify if you can
> boot the system the latest Artful kernel on -proposed?
LGTM:
ubuntu@grotri
** Changed in: edk2 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: edk2 (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: edk2 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ub
RT filed to collect the uploaded tarball
** Changed in: ibm-java71 (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => dann frazier
(dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Verified: I was able to boot the mini.iso on a Cavium Sabre system from
a USB stick.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
501 - 600 of 3463 matches
Mail list logo
