xenial verification
ubuntu@ubuntu:~$ apt show linux-tools-common
Package: linux-tools-common
Version: 4.4.0-195.227
Priority: optional
Section: kernel
Source: linux
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 715 kB
Provides: linu
= focal verification =
ubuntu@ubuntu:~$ cat /proc/version
Linux version 5.4.0-55-generic (buildd@lcy01-amd64-013) (gcc version 9.3.0
(Ubuntu 9.3.0-17ubuntu1~20.04)) #61-Ubuntu SMP Mon Nov 9 20:49:56 UTC 2020
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars/ | grep FOO
FOO!BAR-8ed72b3f-ad26-4d5c-aa36-
= groovy verification =
ubuntu@ubuntu:~$ cat /proc/version
Linux version 5.8.0-30-generic (buildd@lgw01-amd64-009) (gcc (Ubuntu
10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #32-Ubuntu
SMP Mon Nov 9 21:03:15 UTC 2020
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars | grep FOO
FO
= bionic verification =
ubuntu@ubuntu:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-125-generic
root=UUID=9e45081a-7e2b-4294-8b2f-4ccb8139ed67 ro console=tty1 console=ttyS0
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars/ | grep FOO
FOO!BAR-8ed72b3f-ad26-4d5c-aa36-38689635cac3
** Tags remo
= xenial verification -
ubuntu@ubuntu:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.4.0-195-generic
root=UUID=6f35ed47-31af-4f66-b33f-5863971f8df0 ro console=tty1 console=ttyS0
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars/ | grep FOO
FOO!BAR-8ed72b3f-ad26-4d5c-aa36-38689635cac3
** Tags remov
I've tested the update for each series in an x86 VM in both Secure Boot
and non-Secure Boot modes and observed no regressions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900774
Title:
[arm64] EF
= groovy verification =
error: no suitable video mode found.
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
[0.00] Booting Lin
= focal verification =
error: no suitable video mode found.
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
[0.00] Booting Linu
= bionic verification =
error: no suitable video mode found.
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, KASLR will be disabled
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
[0.00] Booting Lin
= xenial verification =
error: no suitable video mode found.
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, KASLR will be disabled
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
[0.00] Booting Lin
** Changed in: grub2 (Ubuntu Groovy)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: grub2 (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: grub2 (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: grub
** Changed in: grub2 (Ubuntu Groovy)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: grub2 (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: grub2 (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: grub
= groovy verification =
GNU GRUB GNU GRUB version 2.04buntu3.29
Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device or file completions.
What's the symptom?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907156
Title:
Unable to run 4.14 stable kernel in 20.04 user space
To manage notifications about this bug go to:
https://bugs.laun
Note that we did switch to lz4 compression starting in 19.10. This is
configurable via /etc/initramfs-tools/initramfs.conf, so you could
workaround it by returning to gzip. Why 4.14.y would be a snowflake here
isn't clear.
--
You received this bug notification because you are a member of Ubuntu
B
I think this is a firmware issue. Normally you should see something
like:
288 bytes read in 34 ms (7.8 KiB/s)
## Executing script at 400400
10741547 bytes read in 323 ms (31.7 MiB/s) <- This is loading the kernel
64692535 bytes read in 1672 ms (36.9 MiB/s)<- This is loading the initramfs
A workaround might be to have flash-kernel automatically defrag files it
generates on ext4, so adding a task for it.
** Changed in: flash-kernel (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Not sure if we still care, it's the old moonshot ARM64 node.
-
Issue found on ARM64 node ms10-35-mcdivittb0-kernel with F-5.8.
Install the plymouth package from proposed will cause system failed to boot,
with error message:
Wrong Ramdisk Image Format
Ramdisk
It works fine for me:
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.14.211 #3 SMP Wed Dec 9 00:40:44 UTC 2020 x86_64 x86_64 x86_64
GNU/Linux
I kept the default initramfs.conf w/ COMPRESS=lz4. I started with a
defconfig and added what I needed to boot my (EFI-based) VM.
ubuntu@ubuntu:~$ sudo file /bo
Here's a patch for flash-kernel that works around the issue.
** Summary changed:
- plymouth in proposed cause F-5.8 unable to boot on moonshot ARM64 "Wrong
Ramdisk Image Format"
+ Moonshot ProLiant m400 fails to boot "Wrong Ramdisk Image Format"
** Patch added: "flash-kernel-e4defrag.patch"
ACK, I'll go ahead and close this bug then, but still happy to help if I can :)
I'd suggest adding some debugging command line arguments (debug,
initcall_debug, etc) to see if you can get any more info about where it's
hanging.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
them. Issues could
include kernel oopses, corruption, etc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu
** Changed in: apt (Ubuntu Focal)
Status: Fix Released => Triaged
** Changed in: apt (Ubuntu Groovy)
Status: Fix Released => Triaged
** Changed in: apt (Ubuntu Bionic)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I noticed that the Built-Using control field is no longer being
generated for linux-modules-nvidia- packages... well, except for the aws
ones, which still have it.
For example:
$ apt show linux-modules-nvidia-440-5.3.0-51-generic | grep Built-Using
Built-Using: nvidia-dkms-
** Changed in: edk2 (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: edk2 (Ubuntu)
Status: New => 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/1
** Attachment added: "focal-mce-auto-reboot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908294/+attachment/5443914/+files/focal-mce-auto-reboot.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
[Impact]
When rebooting with the focal kernel, my system always MCEs. Installing an
nvidia driver - or simply blacklisting the nouveau driver - avoids the issue.
Sometimes it hard hangs the system, requiring a manual power cycle:
[ OK ] Reached target Reboot.
[ 402.48975
** Attachment added: "reboot-mce-hang.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908294/+attachment/5443915/+files/reboot-mce-hang.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
The latest available firmware still has the problem, so looks like we'll
need to workaround it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900796
Title:
Moonshot ProLiant m400 fails to boot "Wro
Updating the statuses. This is Fix Released in groovy (patches were
later applied, per Comment #2), and marking Focal as NEW as some patches
are coming into focal/master-next via stable after the initial "Won't
Fix" decision. It needs to be investigated whether that unblocks the
remaining patches.
@kaihengfeng - It is unclear where the issue lies. If it turns out to be
a driver bug, and we find an SRUable fix, then I'd like to see it SRU'd.
The issue is still reproducible with latest upstream kernels.
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Als
Yes it is reproducible w/ the IOMMU disabled (intel_iommu=off). See
attached log.
** Attachment added: "repro-with-intel_iommu=off.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908294/+attachment/5444656/+files/repro-with-intel_iommu%3Doff.log
--
You received this bug notificati
** Also affects: flash-kernel (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: plymouth (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: flash-kernel (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: plymouth (Ubu
Closing as Invalid, as I believe the problem is in firmware. Will reopen
if that proves false.
** Changed in: linux (Ubuntu Artful)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Invalid
--
You received this bug notification because you are a me
** Description changed:
Seen on a Cavium CRB1S a couple of times while running the
- com.canonical.certification::disk/disk_stress_ng_sda kernel from the
+ com.canonical.certification::disk/disk_stress_ng_sda testcase from the
canonical-certification-server test suite:
[ 1823.116031] Unab
These observations were on a system in our lab called "seuss". My
suggestions for next steps would be:
1) Determine how reliable this failure is.
a) Deploy xenial/hwe on seuss, and downgrade the kernel to the version in the
crash log (4.13.0-36-generic #40~16.04.1-Ubuntu).
b) Run the com.canoni
** Summary changed:
- arm64 - stress_ng triggers panic on crypted lvm
+ kernel BUG at
/build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I believe this occurred while running disk/disk_stress_ng_dm-1 from the
certification test suite on the system in our lab called "seuss", which
had been installed manually w/ d-i, using LVM w/ crypted home. (I dug
that info out of LP: #1749040, from whence this bug was spawned).
Since this crash o
Ignore comment #4 - was meant for a different bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747523
Title:
support thunderx2 vendor pmu events
To manage notifications about this bug go to:
htt
public bug 1760712
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747523
Title:
support thunderx2 vendor pmu events
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
]
This teaches existing code about a new SoC, which should mitigate regressions
for all other platforms.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Artful)
Importance: Undecided
Assignee
Since this appears to be a hardware issue, I'll mark Invalid. fyi, we're
working with the vendor to figure out next steps for lundmark.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Note that with the HWE kernel, this also requires vga=efifb:off (see LP:
#1755304). As this is working as designed, I'm going to close as
Invalid.
** Changed in: debian-installer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Yeah - I verified it on the arm64 ISOs, and it was good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700826
Title:
please include numactl on the ubuntu-server iso
To manage notifications about t
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]
/1800664/comments/3
[Test Case]
iperf -c 192.168.99.1 -P5
[Fix]
Revert the offending patch.
[Regression Risk]
This is reverting a patch, returning the driver to 18.10 GA behavior.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In
** Description changed:
[Impact]
Bug 1800664 introduced checksum offload and TSO support for HiNIC adapters.
While that did improve performance in short iperf runs, longer runs were later
found to show a significant regression in performance:
- https://bugs.launchpad.net/ubuntu/+source/lin
Thanks Radoslaw! I've created PPAs for the rocky & queens ubuntu cloud
archives w/ your v2 patches integrated for testing.
ppa:dannf/queens-arm64
ppa:dannf/rocky-arm64
I plan to keep this up to date as your patch set iterates, as well as
rebasing on latest QEMU until merged in mainline and backpo
ilable soon after HWE kernel is available and
before second point release."
-dann
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804306
Title:
Move supported arm64 server list to
reasons for these
changes are clarified.
** Changed in: ubuntu-z-systems
Status: Triaged => Incomplete
** Changed in: ubuntu-z-systems
Assignee: dann frazier (dannf) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
Upstream bug: https://bugs.openjdk.java.net/browse/JDK-8211105
Reference (w/ workaround):
http://mail.openjdk.java.net/pipermail/jdk-updates-dev/2018-September/000155.html
$ cat LogTest.java
public class LogTest {
public static void main(String[] args) {
k_unmap()
[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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806488
T
Public bug reported:
[Impact]
kdump support isn't usable on HiSilicon D05 systems. This previously worked in
bionic.
[Test Case]
sudo apt install linux-crashdump
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT
crashkernel=512M"' | \
sudo tee /etc/default/grub.d/kdump-tools.cfg
s
ll
memreserve config table").
+
+ Risk mitigated by testing on both x86 ARM and EFI systems.
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Cosmic)
In theory, you should *never* have an "ubuntu" entry in efibootmgr when
MAAS-deployed. I'm guessing this is a dup of the following bug, for which a fix
has not been backported to trusty:
https://bugs.launchpad.net/maas/+bug/1642298
--
You received this bug notification because you are a membe
** Attachment removed: "arm64-hisilicon-d05-18.04-blurry-screenshot.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5183108/+files/arm64-hisilicon-d05-18.04-blurry-screenshot.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is definitely reproducible on a D05 (arm64) with 18.04 running
wayland, and the symptoms look identical. I re-tested with the 18.04.1
ISO and confirmed.
** Attachment added: "arm64-hisilicon-d05-18.04-blurry-syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachm
The smartpqi driver is included in the linux-modules deb. If you are
trying to build/use an out-of-tree smartpqi driver (which your taint
flags suggest), please be clear about that. It could quite likely be a
bug in that out-of-tree driver vs. a bug with Ubuntu.
--
You received this bug notificat
@Mao: correct, I do not observe screen blur in d-i on D05.
btw, note also bug 1780076
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940
Title:
Ubuntu 18.04 d-i install screen becomes blurry on
I tracked down why libvirt generates the message "internal error: The PF
device for VF XXX has no network device name" on startup when built in
bionic, but not in xenial. When populating device capabilities, we see:
virNetDevGetFeatures():
virNetDevSwitchdevFeature():
virNetDevGetPhysicalFun
Public bug reported:
[Impact]
If an admin uses ethtool to change the link speed or duplex setting while the
hardware is still processing packets, a hardware hang may result.
[Test Case]
While traffic is in-progress, use ethtool to change link speed/duplex.
[Fix]
Fixes have been applied upstream
signed) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
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/1792209
Title:
net: hns: Avoid hang
** Description changed:
[Impact]
MSI-X configuration is hardcoded in the hns3 driver, but the actual
configuration may change across revisions. Query firmware for the MSI-X
offset/numbers instead.
[Test Case]
- Regression testing: Confirm that, on existing hardware, the same MSIs are
a
Verified - has survived several minutes of:
while :; do
sudo ethtool -s enahisic2i1 speed 1000 duplex full
sudo service systemd-networkd restart
sleep 5
sudo ethtool -s enahisic2i1 speed 10 duplex half
sudo service systemd-networkd restart
sleep 5
done
With ping/iperf still responding
tly tested.
** 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)
There was no v4.6-yakkety build for arm64, but v4.8 booted fine. I
further bisected this down to:
0cb0786bac159 ARM64: PCI: Support ACPI-based PCI host controller
Presumably nova in newer OpenStack releases has made changes to the
libvirt xml it generates that requires additional kernel support.
I've backported the necessary fixes and verified that the result does solve the
problem:
https://git.launchpad.net/~dannf/ubuntu/+source/linux/+git/linux?h=xenial-arm64-acpi-pci
That being said, the changes are not particularly isolated, so it will
require careful review and testing for regres
** Changed in: ubuntu-z-systems
Status: Triaged => 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/1798312
Title:
LP1792533 : [Comm] IBM JDK 8.0.5.22 integration into Ubuntu
To man
Reviewd & uploaded to SRU queue.
** Changed in: ubuntu-z-systems
Assignee: dann frazier (dannf) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798312
Title:
LP1792533
f no model string is found.
If something is buggy with this patch, it could lead to installer crashes.
** Affects: parted (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: parted (Ubuntu Bionic)
Importance: Undecided
Assi
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** Changed in: debian-installer (Ubuntu)
Status: New => Fix Released
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Changed in: debian-installer (Ubuntu Bionic)
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Ubuntu Package Archive Administrators
(ubuntu-archive)
** Changed in: ibm-java71 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
cosmic verification:
ubuntu@d05-4:~$ sudo parted -s /dev/nvme0n1 -- print | grep Model
Model: Force MP300 (nvme)
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Also affects: openjdk-lts (Ubuntu Cosmic)
Importance: Critical
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/1796982
Title:
[Regression] AArch64: log and cos/sin intrinsics
bionic verification:
ubuntu@d05-4:~$ sudo parted -s /dev/nvme0n1 -- print | grep Model
Model: Force MP300 (nvme)
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug n
cosmic verification:
ubuntu@d06-3:~$ cat /proc/version
Linux version 4.18.0-11-generic (buildd@bos02-arm64-030) (gcc version 8.2.0
(Ubuntu 8.2.0-7ubuntu1)) #12-Ubuntu SMP Tue Oct 23 19:24:51 UTC 2018
ubuntu@d06-3:~$ sudo ethtool -s enp125s0f2 speed 100 duplex half autoneg off
ubuntu@d06-3:~$ sudo
bionic verification:
ubuntu@d06-3:~$ cat /proc/version
Linux version 4.15.0-39-generic (buildd@bos02-arm64-010) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #42-Ubuntu SMP Tue Oct 23 15:43:48 UTC 2018
ubuntu@d06-3:~$ sudo ethtool -s enp125s0f2 speed 100 duplex half autoneg off
ubuntu@d06-3
@rbiernacki I just wanted to check - do you still have plans to propose
your "fast fix" upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
[bionic] libvirtError: Node device not
.
+ [Impact]
+ on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail
to launch as they drop to the busybox prompt after booting.
- Dann F believes this may be related to the xenial image not containing
- appropriate acpi modifications.
+ [Test Case]
+ Deploy rocky-bionic OpenStack
Regression tested on ThunderX/X-Gene, which I believe were the only 2
arm64 servers supported by the 4.4 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797092
Title:
xenial guest on arm64 dr
Assignee: dann frazier (dannf)
Status: In Progress
** 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
Retested with 2.02-2ubuntu8.6:
dannf@mdraid:~$ sudo grub-reboot 0
WARNING: Detected GRUB environment block on diskfilter device
0 will remain the default boot entry until manually cleared with:
grub-editenv /boot/grub/grubenv unset next_entry
--
You received this bug notification because yo
Public bug reported:
Upstream bug: https://bugs.openjdk.java.net/browse/JDK-8211105
$ cat LogTest.java
public class LogTest {
public static void main(String[] args) {
double x = 4.9E-324;
System.out.println(Math.log(x));
System.out.println(StrictMath.log(x));
}
}
Verification (regression test only - we don't yet have the hw that
supports the feature):
ubuntu@d06-3:~$ cat /proc/version
Linux version 4.15.0-37-generic (buildd@bos02-arm64-015) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #40-Ubuntu SMP Tue Oct 2 15:36:22 UTC 2018
$ sudo ethtool -K en
@rbiernacki: Thanks for commenting here - and sorry for my delayed
response as I was out on PTO. While I haven't tested it in our setup, I
agree that your [4] is likely a better/more generic "fast fix" solution
than what I prepared. Feel free to CC me on your RFC.
--
You received this bug notific
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802023
Title:
hns3: map tx ring to tc
To manage notifications abou
Smoke tested both bionic-proposed & cosmic-proposed.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802023
Title:
** Changed in: linux (Ubuntu Cosmic)
Status: New => Fix Released
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Fix Released
** Changed in: linux-raspi2 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: linux-raspi2 (Ubuntu Cosmic)
Status: New => Fix Rel
Verified - see attached dmesg.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/bionic/+source/linux-snapdragon/+bug/1797092/+attachment/5214304/+files/dmesg
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notificati
Ike has since done some more extensive testing, and found that
performance actually *drops* with longer iperf runs. With a 900s run,
he's seeing it go down to ~200Mbps, while the kernel emits messages like
these:
[ 1070.047048] ITS queue timeout (65440 65504 1120)
[ 1070.051658] ITS cmd it
** Tags removed: verification-done-cosmic
** Tags added: verification-failed-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800664
Title:
Add checksum offload and TSO support for HiNIC adapte
Public bug reported:
$ apt showsrc openjdk-lts | grep -e ^Version -e ^Vcs-
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Version: 11~28-3ubuntu2
Vcs-Browser: https://code.launchpad.net/~openjdk/openjdk/openjdk11
Vcs-Bzr: http://bazaar.launchpad.net/~openjdk/open
** Also affects: installation-guide (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: installation-guide (Ubuntu Disco)
Importance: Undecided
Assignee: Ike Panhc (ikepanhc)
Status: New
** Also affects: installation-guide (Ubuntu Bionic)
Importance: Und
** Description changed:
- For some platform we need Ubuntu LTS point release with HWE kernel. It
- is necessary to mention that so that user can download correct LTS
- binaries and power up their machine.
-
[Impact]
-
- * Installation-guide does not mention HWE kernel and point release. User
** Description changed:
+ For some platform we need Ubuntu LTS point release with HWE kernel. It
+ is necessary to mention that so that user can download correct LTS
+ binaries and power up their machine.
+
[Impact]
- The installation guide currently has a static list of supported arm64 server
Public bug reported:
[Impact]
The installation guide currently has a static list of supported arm64 server
platforms. This is a cumbersome way to store this information as it is
constantly changing, and these systems are becoming sufficiently standardized
as to not require platform-specific ins
** Changed in: installation-guide (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: installation-guide (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: installation-guide (Ubuntu Disco)
Status: In Progress => 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/1730322
Title:
Add HWE kernel and point release URL for new
** Changed in: installation-guide (Ubuntu Disco)
Status: In Progress => 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/1804306
Title:
Move supported arm64 server list to wiki
To
Fixed upstream in version 1.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/509425
Title:
svn-load can't connect to my repository
To manage notifications about this bug go to:
https://bugs.launchpa
201 - 300 of 3463 matches
Mail list logo
