Fixed in upstream 1.4
** Changed in: svn-load (Ubuntu)
Status: Confirmed => 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/889860
Title:
svn -load gives python error
To manage n
Actually, that should've been fixed in 1.3. Please reopen if that's not
the case.
** Changed in: svn-load (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
[Impact]
Ubuntu does not currently support SecureBoot for UEFI systems on arm64
platforms.
[Test Case]
See: https://wiki.ubuntu.com/UEFI/SecureBoot/Testing
[Fix]
- Introduce shim-signed for arm64
- Introduce grub-signed for arm64
- Produce signed linux kernels
[Regression
** Bug watch added: Debian Bug tracker #910768
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910768
** Also affects: svn-load (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910768
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
hanged in: shim (Ubuntu Cosmic)
Status: New => Fix Released
** Changed in: shim (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => d
I'm not aware of any armhf hardware that has PCI and was supported by
the 4.4 kernel. Calxeda gear maybe - but that was never officially
released and I don't have access to it anyway.
I did regression test using the virt model in QEMU. System still boots, lspci
smoke tests OK:
ubuntu@ubuntu:~$ ls
** Description changed:
[Impact]
- on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail
to launch as they drop to the busybox prompt after booting.
+ on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail
to launch as they drop to the busybox promp
** Summary changed:
- xenial guest on arm64 drops to busybux under openstack bionic-rocky
+ xenial guest on arm64 drops to busybox under openstack bionic-rocky
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
I can't tell if this is the same root cause as bug 1765668 - if it is,
please feel free to dup.
I'm able to launch/boot bionic/arm64 guests in disco, but not xenial. I took a
look as to why, and it appears that we are using the wrong base image. arm64
requires UEFI images.
** 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) {
only.
[Fix]
1c77215480bcf net: hns3: Set tx ring' tc info when netdev is up
[Regression Risk]
Restricted to a single driver, which has been tested on the target SoC.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affe
The system was set to boot from PXE by default, at least before MAAS deployed
it:
Feb 22 03:28:41 lodygin cloud-init[3447]: + echo before grub-install efiboot
settings
Feb 22 03:28:41 lodygin cloud-init[3447]: before grub-install efiboot settings
Feb 22 03:28:41 lodygin cloud-init[3447]: + efiboo
** Also affects: grub2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: grub2 (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubunt
** Description changed:
- Binary package hint: grub-pc
+ [Impact]
+ The grub-reboot manpage says it will "Set the default boot menu entry for
GRUB, for the next boot only." But, that's a promise it cannot keep when GRUB
cannot write to the environment block, such as when it is stored on Linux
s
Now in 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/1792533
Title:
[Comm] IBM JDK 8.0.5
I was able to successfully capture a kernel crash dump file from a
ThunderX-based Gigabyte R120.
** 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
Verified - ran this over an ssh connection over the hns3 nic:
ubuntu@d06-3:~$ cat /proc/version
Linux version 4.15.0-35-generic (buildd@bos02-arm64-013) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #38-Ubuntu SMP Wed Sep 12 10:35:16 UTC 2018
** Tags removed: verification-needed-bionic
**
** Changed in: grub2 (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[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
allocated befo
@Andrew: thanks. Hard to tell what the root cause is there - might need
more logs. The only obvious concern I see here is:
[0.062805] acpi PNP0A08:00: Bus :00 not present in PCI namespace
Would you mind trying a newer guest (bionic/cosmic) and seeing if that
is any better? The xenial GA k
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dan
cided
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)
Importance: Undecided
Status: New
** Changed in:
]
Localized to a single driver, tested on the one SoC that includes this device.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf
Public bug reported:
[Impact]
If something goes wrong during phy initialization, the device may fail to come
up.
[Test Case]
I don't have a way to inject a FIS error, so this will be smoke tested for
regressions only.
Needs to be tested on both D05 and D06 systems, since it touches code on both
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned
fects: 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)
Importance: Unde
buntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Attachment added: "fio"
https://bugs.launchpad.net/bugs/1794165/+att
use it implements a
previously-unsupported feature. However, there are 2 changesets that refactor
reset code ahead that are required before the above fix, and that refactoring
has a risk of introducing a regression.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier
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)
Importance: Unde
** Description changed:
[Impact]
Newer revisions of hns3 support toggling the rx-vlan-filter feature, but the
driver does not allow it.
[Test Case]
Currently the command:
- $ sudo strace ethtool -K rx-vlan-filter off
+ $ sudo ethtool -K rx-vlan-filter off
reports:
- Could no
Verification:
On a system w/ /boot on an md device:
dannf@mdraid:~$ sudo grub-reboot 0
[sudo] password for dannf:
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
With 18.04 UEFI on x86, does passing the kernel parameter
"video=efifb:off" make a difference?
--
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 bl
Now that testing is looking good, here's a cleaned-up debdiff that is
hopefully more suitable for carrying. It is as used in the cosmic build
in ppa:dannf/test. This is still just the simple hack though (vs. a new
config) - just with improved function name/return type and w/ a DEP-3
header.
** Pat
My original intent was to just carry it until there's a proper fix
upstream, and we can evaluate that for backporting. But, if you think
generic black-listing is a desired feature upstream (but w/ e.g.
configurable ids), I can take a look at implementing that. However,
that'll take some time, so I'
Marking "In Progress" for disco, as a patch was submitted:
https://lists.ubuntu.com/archives/kernel-team/2019-March/099315.html
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Verification: Ran netperf between 2 D06 hosts, one running the bionic-
proposed kernel, the other the cosmic-proposed kernel, w/o error.
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bu
Verified - boot tested both cosmic & bionic proposed kernels on a D06
system.
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-don-bionic verification-done-cosmic
** Tags removed: verification-don-bionic
** Tags added: verification-done-bionic
--
@Riccardo: The PPA builds I provided had both a fix for this issue and
some security issues, some related to networking code. To help determine
if it is the security fixes or the fix for this bug causing your iPXE
regression, I've uploaded new packages *without* the security fix. Could
you test tho
Public bug reported:
On some arm64 systems[*] we are seeing a spew of messages on the
console:
[ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534113] cma: cma_alloc: alloc failed, req-size:
This was not an issue prior to v4.20. Bisection identified the following commit:
886643b766321 arm64: use the generic swiotlb_dma_ops
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823753
Title:
a
The disco kernel uses CONFIG_CMA_SIZE_MBYTES=16, while the arm64
defconfig sets it to 32. I tried bumping up this setting by powers of 2
until the messages went away, and it finally did at 128, which seems
extreme. Need to figure out what is attempting these allocations, and
why they are failing.
I enabled CMA_DEBUG & CMA_DEBUGFS and booted w/ cma=128M so that we can
see the CMA state when no allocations fail.
root@d06-4:/sys/kernel/debug/cma/cma-reserved# cat count
32768
root@d06-4:/sys/kernel/debug/cma/cma-reserved# cat used
15630
Looks like we're actually using ~61M - and perhaps the
** 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/1823753
Title:
arm64: cma_alloc errors at boot
To manage notifications about this
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
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/bug
It appears that linux-signed-hwe-edge does not yet have the arm64
support we added to linux-signed.
** Summary changed:
- not able to install linux-generic-hwe-18.04-edge/bionic-proposed
+ arm64: not able to install linux-generic-hwe-18.04-edge/bionic-proposed
--
You received this bug notifica
Public bug reported:
[Impact]
The Build-Using control file field is incorrect for linux-signed-hwe &
linux-signed-hwe-edge. They claim they were built against the "linux" package,
but should be linux-hwe/linux-hwe-edge respectively.
[Test Case]
Look at the Packages file.
[Fix]
Detect and inser
** Also affects: linux-signed (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-edge (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affec
** Summary changed:
- Build-Using incorrect
+ Built-Using incorrect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824016
Title:
Built-Using incorrect
To manage notifications about this bug go to:
I have a fix staged for this, but it relies on published signed binaries
that aren't present.
dannf, ok the signing component appears in rejected ...
will try and get to the bottom of why that happened
So assigning to apw for now...
** Changed in: linux (Ubuntu)
Status: Incomplete => In
tu Cosmic)
Status: New => Invalid
** Changed in: linux-signed (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux-signed (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux-signed (Ubuntu Bionic)
Status: New => In Pr
Yeah, no crash anymore - thanks Ard!
ubuntu@d06-4:~$ echo function | sudo tee
/sys/kernel/debug/tracing/current_tracer
function
[ 72.778123] ftrace: far branches to multiple entry points unsupported inside
a single module
^ I assume this is expected
--
You received this bug notification bec
[ 72.778123] ftrace: far branches to multiple entry points unsupported inside
a single module
[ 72.786657] WARNING: CPU: 121 PID: 3299 at
/home/ubuntu/linux-5.0.0/kernel/trace/ftrace.c:2008 ftrace_bug+0xb0/0x2b0
[ 72.786662] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds
tpm_
off
ifconfig enp129s0f0 mtu 1501
iperf -c -l 64K -t 3
[Fix]
5f543a54eec08 net: hns3: fix for not calculating tx bd num correctly
[Regression Risk]
Fix is restricted to a driver only used in Hi1620 SoC-based systems.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann
** 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/1822871
Title:
enabling ftrace on Hi1620 CS causes an Oops
To man
On Wed, Apr 10, 2019 at 11:01 AM Ard Biesheuvel
wrote:
>
> On Tue, 9 Apr 2019 at 16:30, dann frazier wrote:
> >
> > Yeah, no crash anymore - thanks Ard!
> >
> > ubuntu@d06-4:~$ echo function | sudo tee
> > /sys/kernel/debug/tracing/current_tracer
> &g
I tried installing ubuntu-desktop on a sabre, but I was still unable to
reproduce. That's still my best hypothesis (Comment #4), but I think
we're stuck here w/o more info from Naresh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Changed in: mstflint (Ubuntu)
Status: New => 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/1863483
Title:
Mstflint package update to 4.13.3-2
To manage notifications about th
Public bug reported:
Today I noticed that the software manager is telling me there's a juju
update available (2.7.1), with an option to update. When I click update,
it says "Unable to update juju: snap has no updates available". Sure
enough, `snap info` confirms that I'm already on 2.7.*2*:
chann
Public bug reported:
[Impact]
Older versions of libvirt, such as the one in bionic, have an nvram variable in
/etc/libvirt/qemu.conf that pairs firmware images with the corresponding nvram
template files:
#nvram = [
# "/usr/share/OVMF/OVMF_CODE.fd:/usr/share/OVMF/OVMF_VARS.fd",
# "/usr/shar
Public bug reported:
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, shouldn't
OVMF
Thanks Steve. At this time I'm leaning more towards removing the link
vs. changing what it points to. AFAICT, the link really just serves as a
hint that it should be paired with OVMF_VARS.ms.fd. But IMHO, that's
better clarified for humans in documentation, which we now have in
/usr/share/doc/ovmf/
I dug up my arm64/disco VM that I had hacked up to test this shim build
before MS had signed it:
ubuntu@disco:~$ sudo mokutil --sb-state
SecureBoot enabled
So what's the relevant difference between this working config and the
broken one?
Looks like I had set it up following:
https://wiki.archl
It does not appear to be an issue with the signed kernel - the same one
that fails to build in my focal/MS-signed VM does boot when installed in
the disco/self-signed VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
The issue seems to be related to GRUB. If I upgrade my working-in-SB-
disco VM to focal's grub-efi-arm64-signed, it now fails. If I downgrade
my *not*-working-in-SB-focal VM to disco's grub-efi-arm64-signed, it now
boots in SB mode.
** Also affects: grub2 (Ubuntu)
Importance: Undecided
S
Upstream GRUB 2.02 also fails - so there's likely something in the disco
patchset that is required.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm64 Secure Boot fails w/ "error: ca
@juliank: The shim build is the same in both cases. The only difference
is that one is signed by MS, the other self-signed. I did notice that
key enrollment didn't work in my guest, which maybe a failure to execute
mma64.efi, and therefore maybe related to bug 1864223.
My hypothesis is that the SB
Thanks Timo. We could argue for introducing mlxreg in an SRU as being
hardware enablement (SRU team would be the judge), as long as we could
clearly demonstrate a negligible regression risk in doing so. I took a
stab at a backport to gauge that feasibility. Unfortunately, I found
that this is non-t
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
I've got a hacked together focal-based GRUB I created by replacing some
patches w/ updated versions from the rhboot repository. It still need
quite a bit of cleanup though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I've compared the list of patches squashed into the ubuntu-
linuxefi.patch we have in focal with the current set of patches in the
fedora-32 branch of https://github.com/rhboot/grub2, which is the
upstream for our SB patches AIUI. There has been some rework of the
linuxefi command since the version
While trying to create a backport of mlxreg - without touching other
parts of mstflint - I hit an incompatibility. See below. Does mlxreg
require the new version of mget_max_reg_size(), or can it be made to
work with the 4.8 version? The supports_reg_accces_gmp() interface will
likely need to be ad
]
The fix is a quirk restricted to specific SoCs. It does rely on firmware
behaving (overloading the desired_perf register w/ a correct actual perf
value), so changes in firmware could lead to regressions.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf
** Description changed:
[Impact]
- Some HiSilicon SoCs do not implement registers that the cpufreq subsystem
uses to calculate current performance. This can result in undefined data being
used in internal calculations, and being exposed to userspace via sysfs.
+ Some HiSilicon SoCs do not imp
** Description changed:
[Impact]
SATA disks may be unusable
will not be usable when:
- - The disk is connected through a SAS expander
- - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
- - link rate between expander & disk is greater than link between controller
and exp
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (u
Please provide the console log and libvirt xml for a failing VM.
** Changed in: edk2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821729
Title:
UEFI in o
On Wed, Mar 27, 2019 at 9:35 AM Janåke Rönnblom wrote:
>
> Can the edk2/ovmf package for Bionic be updated to the latest version?
>
> 0~20190309.89910a39-1ubuntu1
Sorry, no. Our policy is to backport the fixes instead.
-dann
--
You received this bug notification because you are
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Xenial)
Status: New => Won't Fix
** Description changed:
[Impact]
SATA disks may be unusable
will n
@Riccardo: Thanks, I can reproduce by using machine='pc-1.0' in my XML
(pc-i440fx-2.12 worked fine). I also found that the version of ovmf in
disco works w/ pc-1.0, so I'll try to bisect down what fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: linux (Ubuntu Cosmic)
Status: New => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821620
Title:
Ad
Bisection led me to the following fix:
https://github.com/tianocore/edk2/commit/272658b9971865812f70e494d0198f13df8b841b
I've uploaded test kernels to a PPA, can you verify that the 18.04 ('bionic')
one fixes the problem for you?
https://launchpad.net/~dannf/+archive/ubuntu/test
** Also affe
)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a mem
** Changed in: gnu-efi (Ubuntu)
Status: Confirmed => Invalid
** Changed in: shim (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: shim-signed (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bug
** Changed in: shim-signed (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: shim (Ubuntu)
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/1811901
: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Description changed:
[Impact]
+ Driver will report TX errors
+
[Test Case]
+
[Fix]
5f543a54eec08 net: hns3: fix for not calculating tx bd num correctly
+
[Regression Risk]
+ Restricted to hns3 driver, only used for HiSilicon ARM SoCs.
--
You received this bug notification because
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a me
@Riccardo: Sorry, I'm not sure how to read your update. Are you stating
that you are unable to reproduce the panic *after installing a PPA
build*, or for some other reason?
Can you confirm that the ipxe thing is a separate issue? If so, please
file a new bug for that instead of overloading this on
On Mon, Apr 1, 2019 at 9:50 AM Riccardo Pittau
<1821...@bugs.launchpad.net> wrote:
>
> @Dann: what I'm saying is that I can't reproduce the kernel panic after
> installing a PPA build because it doesn't load from ipxe anymore.
>
> I can't confirm or deny th
cided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
[Impact]
- Driver will report TX errors
+
[Test Case]
+
[Fix]
5f543a54eec08 net: hns3: fix for not calculating tx bd num correctly
[Regression Risk]
Restricted to hns3 driver, only used for HiSilicon ARM SoCs.
--
You received this bug notification b
Public bug reported:
[Impact]
Attempting to enable the function tracer causes an Oops. This impacts the
current disco kernel, as well as latest upstream
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).
[Test Case]
$ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer
[ 3125.651453] k
Bisection led to the following commit:
# first bad commit: [bdb85cd1d20669dfae813555dddb745ad09323ba]
arm64/module: switch to ADRP/ADD sequences for PLT entries
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Summary changed:
- enabling ftrace on Hi1620 causes an Oops
+ enabling ftrace on Hi1620 CS causes an Oops
** Description changed:
[Impact]
Attempting to enable the function tracer causes an Oops. This impacts the
current disco kernel, as well as latest upstream
(@5e7a8ca319268a70a6c7c3c
** 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/1822871
Title:
enabling ftrace on Hi1620 CS causes an Oops
To manage notifications
hns_roce_v2_modify_qp
[Regression Risk]
Driver is only for HNS nics on HiSilicon SoCs
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: lin
** Also affects: linux (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/1813847
Title:
af-alg stressor triggers modprobe throttling
To manage notif
** Bug watch added: Debian Bug tracker #891256
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891256
** Also affects: kexec-tools (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891256
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
just work.
Kernel support is a different question - if you know what patches are
required for that, please open a bug against the kernel w/ that info.
-dann
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
[x0]
> > >
> > > ...but if I bump notify_me size to uint64_t the issue goes away.
> >
> > Ouch. :) Is this with or without my patch(es)?
> >
> > Also, what if you just add a dummy uint32_t after notify_me?
>
> With the dummy the testcase also runs
301 - 400 of 3463 matches
Mail list logo
