** 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/1845820
Title:
arm64: loop on boot after installing linux-generic-
@rafaeldtinoco: Also, I wonder if it wouldn't make sense to submit your patch
upstream?
https://github.com/hreinecke/sg3_utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833618
Title:
failing
I MAAS deployed an impacted system w/ the attached preseed to include
your PPA, and curtin successfully installed. Afterward, the system
entered a deploy loop, but there's no sign that this was related to your
fix - rather, it may just be a boot order issue. Interrupting the loop
and telling it to
On Thu, Oct 3, 2019 at 4:42 AM Rafael David Tinoco
wrote:
>
> Hey Dann, nope, the file changed is Debian related only.
hmm.. I see the file in the upstream source, and Debian hasn't patched
it. But, perhaps you mean that upstream is not impacted. And yeah, I
can see that this may
A follow-up on comment #47 - I've proven that the reboot loop had
nothing to do with your change, I just missed a required section of the
preseed. Updated file attached just as an fyi.
** Attachment added:
"curtin_userdata_ubuntu_arm64_generic_disco_seidel-FLAKYMEMORY"
https://bugs.launchpad.
** Also affects: kunpeng920
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/1805256
Title:
qemu-img hangs on rcu_call_ready_event logic in Aarch64 when
co
rgc=, argv=) at qemu-img.c:2520
#7 0xb7ce1e54 in main (argc=8, argv=) at qemu-img.c:5097
> > I've tried to verify me theory with this patch and didn't run into the
> > issue for ~500 iterations (usually I would trigger the issue ~20
> > iter
** Also affects: kunpeng920
Importance: Undecided
Status: New
** Changed in: kunpeng920
Status: New => 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/1845355
Title:
Su
Verification:
ubuntu@kreiken:~$ cat /proc/version
Linux version 5.0.0-32-generic (buildd@bos02-arm64-021) (gcc version 7.4.0
(Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #34~18.04.1-Ubuntu SMP Wed Oct 2
22:12:13 UTC 2019
ubuntu@kreiken:~$ dmesg | grep zip
[ 30.558846] hisi_zip :75:00.0: enablin
Upstream thread: https://lists.openwall.net/linux-ext4/2019/08/30/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847340
Title:
ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
And the precursor to that the upstream thread in comment #1:
https://www.spinics.net/lists/linux-fsdevel/msg151486.html
And here's a captured filesystem image (referenced in above thread):
https://people.canonical.com/~dannf/md2.e2ic.qcow2
--
You received this bug notification because you ar
Public bug reported:
[Impact]
In the event of a loss of power, ext4 filesystems mounted w/
data=journal,journal_checksum are subject to a corruption issue that requires a
fsck to recover. This is exacerbated by installations by curtin that set
passno=0 in /etc/fstab, preventing fsck from runnin
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Ff-series)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance:
** 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I confirmed that if we compress the kernel (as Seth's patch does), the
5.0 kernel would boot fine on the HP m400[*]. I chatted w/ apw about
this and we agreed that a respin isn't necessary because LP showed that
there is no current linux-hwe-edge package in bionic, and therefore
introducing one sho
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:
** 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
** Description changed:
- This issue was limited to Moonshost ARM64 node, ThunderX works fine.
+ This issue was limited to Moonshot ARM64 node, ThunderX works fine.
After the node was deployed with 4.15 Bionic, it will install linux-
generic-hwe-18.04-edge package and reboot.
However,
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
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775732
Title:
a
** Changed in: linux-hwe-edge (Ubuntu)
Status: New => Fix Committed
** Changed in: linux-hwe-edge (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux-hwe-edge (Ubuntu)
Status: Fix Committed => 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/1828553
Title:
Unable to boot Bionic 5.0 linux-hwe-edge kernel on AR
** Changed in: linux-hwe-edge (Ubuntu)
Status: Fix Released => 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/1828553
Title:
Unable to boot Bionic 5.0 linux-hwe-edge kernel on AR
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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
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
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
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
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
[
@Riccardo: I found some time to try and reproduce the ipxe issue again
today but, unfortunately, I don't remember what the failure looked like
and the logs in comment #6 are no longer accessible. Would you be able
to attach some logs here?
--
You received this bug notification because you are a m
Thanks Riccardo. I'm still unable to reproduce, but I'm not sure I'm
doing the right thing. Can you elaborate on how iPXE is getting loaded
in the "good" case? i.e. are you loading it from disk, or chainloading
to it from OVMF's built-in PXE client? In your "bad" logs, it looks like
you are booting
On Mon, May 20, 2019 at 2:15 AM Riccardo Pittau
<1821...@bugs.launchpad.net> wrote:
>
> Hi Dann,
>
> Please find recent logs here:
>
> This is the correct output on bionic using virtio + ovmf package from xenial:
> http://logs.openstack.org/90/644590/8/gate/ironic
Public bug reported:
Adding passthrough devices to a guest introduces a boot delay of > 17
minutes. During this time libvirt reports the guest to be "paused". The
delay does not seem to scale with the # of hostdevs - that is, 1 hostdev
causes about a 17min delay, while 16 only bumps that up to ~18
Here's a perf report of a 'sudo perf record -p 6949 -a -F 25000 -e
cycles', after libvirt spawned qemu w/ pid 6949.
** Attachment added: "perf.report"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575/+attachment/5280233/+files/perf.report
--
You received this bug notification beca
** Attachment added: "sample xml w/ devices passed through"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575/+attachment/5280232/+files/config5-new.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
Introduced by the fixes for bug 1823753.
[Impact]
Crashes (as observed on a nigrogen8m device), and a potential memory leak.
[Test Case]
Regression tested only.
[Fix]
f46cc0152501e dma-contiguous: page-align the size in dma_free_contiguous()
c6622a425acd1 dma-contiguous: do
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Disco)
Assignee: (u
On Wed, Aug 14, 2019 at 1:25 PM Terry Rudd <1829...@bugs.launchpad.net> wrote:
>
> Dann, is this still planned for Eoan?
This change is upstream in v5.1.
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Released
--
You received this bug notification be
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
)
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)
--
** Changed in: linux-hwe-edge (Ubuntu)
Status: Fix Committed => 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/1828553
Title:
Unable to boot Bionic 5.0 linux-hwe-edge kernel on AR
MA issue at all was by turning
on DMA_CMA on arm64 for the RPi3 (bug 1803206) - so I'd at least like
to get some regression testing on that platform. And, obviously such
relatively lowmem platforms make me want to be rather conservative
about bumping up CMA sizes.
-dann
--
You received
** 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:
Patch submitted upstream:
https://www.spinics.net/lists/netdev/msg571753.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829652
Title:
Kernel panic upon resetting ixgbe SR-IOV VFIO virtual funct
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
be good to know the results w/ cma=64M on the
cmdline.
-dann
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823753
Title:
arm64: cma_alloc errors at boot
To manage notifications about this b
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823753
Title:
arm64: cma_alloc errors at boot
To manage notifications
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
** 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
** Description changed:
[Impact]
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
involved, id
linux (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => High
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => dann
(initramfs) modprobe -r hisi_sas_v3_hw
[ 70.546285] hisi_sas_v3_hw :74:02.0: dev[4:1] is gone
[ 70.552479] sd 3:0:1:0: [sdc] Synchronizing SCSI cache
[ 70.561963] sd 3:0:1:0: [sdc] Stopping disk
[ 71.161605] hisi_sas_v3_hw :74:02.0: dev[3:5] is gone
[ 71.168193] sd 3:0:0:0: [sdb]
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: New =>
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- On some arm64 systems[*] we are seeing a spew of messages on the
- console:
+ [Impact]
+ We enabled CONFIG_DMA_CMA to fix bug 1803206, but that led to a regression
+ where other systems began spewing on the order of 10K of these messages on
boot:
[ 19.534097] cma:
** Description changed:
[Impact]
We enabled CONFIG_DMA_CMA to fix bug 1803206, but that led to a regression
on other arm64 systems that began spewing these messages on boot - sometimes
> 10K of them:
[ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
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:
te sas port if expander discover failed
[Regression Risk]
Restricted to libsas-based drivers.
** Affects: linux (Ubuntu)
Importance: High
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Disco)
Importance: High
Assignee: dann frazier (dannf)
Ubuntu has sync'd a Debian version with the fix for focal, so marking
that task Fix Released.
** Also affects: slurm-llnl (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: slurm-llnl (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: slurm-llnl (
** Attachment added: "lspci.uefi.pci=realloc,pci=nocrs"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1849563/+attachment/5305739/+files/lspci.uefi.pci%3Drealloc%2Cpci%3Dnocrs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Attaching a boot log using an OVMF built w/ DEBUG enabled, which adds
some more runes, such as:
PciBus: HostBridge->NotifyPhase(AllocateResources) - Out of Resources
PciBus: [01|00|00] was rejected due to resource confliction.
** Attachment added: "uefi boot log w/ OVMF DEBUG enabled"
https:
** Attachment added: "lspci.uefi"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1849563/+attachment/5305738/+files/lspci.uefi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849563
Title:
U
** Attachment added: "lspci.seabios"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1849563/+attachment/5305737/+files/lspci.seabios
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849563
Titl
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852723
Title:
[Regression] Bionic kernel 4.15.0-71.80 can not boot on Thunder
With earlycon on, I am able to get more output. This looks like a
smoking gun:
[0.460249] CPU features: CPU1: Detected conflict for capability 11
(Virtualization Host Extensions), System: 0, CPU: 1
git blame for this error message points at:
e988af0188e30 arm64: capabilities: Unify the verifi
Discussion thread on edk2 list:
https://edk2.groups.io/g/discuss/topic/ovmf_resource_assignment/59340711?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,59340711
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
My bisect landed on:
628859e8621cb arm64: capabilities: Change scope of VHE to Boot CPU feature
I'm doing a build w/ that patch reverted to verify.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/185272
Yes, reverting just that change seems to fix it for me on a Sabre board.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852723
Title:
[Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
Thanks for testing. I've uploaded a new version to the PPA (+snakeoil.3)
that fixes a few issues:
- Fixes a typo (s/--no-defaults/--no-default/). Because of this the
build was importing the MS keys into the DB instead of the snakeoil key.
Now the same snakeoil key is in PK/KEK and DB, and no MS k
While the autopkgtest for eoan still fails, it now fails with 2 errors
instead of 3. I confirmed from the logs[*] that the no-longer-failing
test is the one this upload addressed.
[*] Compare the "2019-11-14 11:09:47 UTC" vs. "2019-11-19 19:32:01 UTC" logs at:
https://autopkgtest.ubuntu.com/packag
Public bug reported:
The security uploads for apport (2.20.11-0ubuntu8.2 for eoan,
2.20.10-0ubuntu27.2 for disco, and 2.20.9-0ubuntu7.8 for bionic - and
maybe those for older releases as well) have caused the
test_add_proc_info test to start failing[1]. The pattern changed after
the subsequent upl
The autopkgtests for bionic and disco also continue to fail w/ the
upload in -proposed. However, as was the case for eoan, the failure that
the uploads for this bug targeted has gone away. The remaining failures
appear to be a regression(s) introduced by previous security uploads.
I've reported bug
How frequently does this occur? Are the backtraces always the same?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853485
Title:
Bionic kernel panic on Cavium ThunderX CN88XX
To manage notification
disco verification:
GNU GRUB version 2.02
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.
bionic verification:
GNU GRUB version 2.02
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. ESC at any time exits.
Verification:
ubuntu@bionic:~$ sudo kexec -p /boot/vmlinuz-`uname -r`
--initrd=/boot/initrd.img-`uname -r` --reuse-cmdline
ubuntu@bionic:~$ echo 1 | sudo tee /proc/sys/kernel/sysrq
1
ubuntu@bionic:~$ echo c | sudo tee /proc/sysrq-trigger
c
[ 164.962517] sysrq: SysRq : Trigger a crash
[ 164.96
** Tags added: dgx2-performance-regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853927
Title:
Stream Scale Time is 12% higher in 4.15.0-70.77 than 4.15.0-68.75
To manage notifications abo
** Tags added: dgx2-performance-regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853928
Title:
Stream Scale Rate Test shows -11.99% lower for Config 1 in
4.15.0-70.77 than 4.15.0-68.75
T
** Tags added: dgx2-performance-regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853930
Title:
io RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows
-11.23 % drop in 4.15.0-7
Public bug reported:
We reverted a couple changes in 4.15.0-72.81 because they were causing a
regression (bug 1853326) that was not understood at press time:
b042ff6848684 Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"
5f395b984282e Revert "arm64: Use firmware to detect CPUs that are not a
Tracking the reapplication of the reverted patches in bug 1854207.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853326
Title:
[Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
To m
** Description changed:
[Impact]
- After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
- on breakpoint when running a 32-bit application (on 64-bit Ubuntu).
+ After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
+ on breakpoint when running a 32-bit
Unreproducible w/ >= disco versions, so marking them Invalid.
** Changed in: gdb (Ubuntu Disco)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848200
Title:
gdb not st
Public bug reported:
I'm having issues passing Nvidia Tesla GPUs to an OVMF-mode guest. While
I can passthrough other devices to an OVMF-mode guest w/o a problem
(e.g. Mellanox Connect-X 5 VFs), I'm seeing a couple different failure
modes when passing through a GPU:
1) No output:
-
$ vir
** Attachment added: "dmesg when booting in non-UEFI mode (OK)"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1849563/+attachment/5299616/+files/dmesg.seabios
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "dmesg of guest after hitting issue #2 (invalid I/O
region)"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1849563/+attachment/5299615/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Attachment added: "guest XML (hits issue #1, no output)"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1849563/+attachment/5299614/+files/foo.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
)
Importance: Critical
Assignee: dann frazier (dannf)
Status: Confirmed
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Focal)
Importance
cpaelzer recommends that we retest w/ the q35 machine type as a next
step.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849563
Title:
Unable to passthrough GPUs to guest
To manage notifications a
OK - this is a messy one. It is due to the backport of this:
https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9
Reverting that is probably not the right answer because the point of it
is to avoid corruption. But this is a pretty serious usability issue. It
is not at
** Description changed:
- [Impact]
- After installing the 4.15.0-67.76 kernel from bionic-proposed, our Nvidia
DGX2 system is no longer bootable.
+ Users of RAID0 arrays are susceptible to a corruption issue if:
+ - The members of the RAID array are not all the same size[*]
+ - Data has been wr
** Description changed:
Users of RAID0 arrays are susceptible to a corruption issue if:
- - The members of the RAID array are not all the same size[*]
- - Data has been written to the array while running kernels < 3.14 and >=
3.14.
+ - The members of the RAID array are not all the same size[
** Description changed:
Users of RAID0 arrays are susceptible to a corruption issue if:
- The members of the RAID array are not all the same size[*]
- Data has been written to the array while running kernels < 3.14 *and* >=
3.14.
- Upstream is dealing with this by adding a versioned la
I've proposed changing the error message to point to a webpage w/ a better
explanation:
https://marc.info/?l=linux-raid&m=157196348406853&w=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849682
T
Sorry, that was my fault. I added the dyndbg= parameter to our MAAS
cmdlines to try and get some more debug info for bug 1849682.
Unfortunately, the way this ended up getting quoted screwed up the
parsing in grub.cfg. I've removed it now.
** Changed in: ubuntu-kernel-tests
Status: New => In
This appears to be a new driver, so backporting it should not be a
significant regression risk.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Im
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: kunpeng920/upstream-kernel
Status: New => Triaged
** Also affects: kunpeng920/ubu
701 - 800 of 3463 matches
Mail list logo
