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
> function
> [ 72.778123] ftrace: far branches to multiple entry points unsupported
> inside a single module
>
> ^ I
Does this fix the issue?
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h
=for-next/fixes&id=5a3ae7b314a2259b1188b22b392f5eba01e443ee
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Thanks Dann.
I can HTTP boot that mini.iso fine on my rev 0.2 Developerbox.
** 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.ne
On 14 June 2018 at 13:02, Brad Figg wrote:
> This bug is awaiting verification that the kernel in -proposed solves
> the problem. Please test the kernel and update this bug with the
> results. If the problem is solved, change the tag 'verification-needed-
> bionic' to 'verification-done-bionic'. I
Bug is fixed on zesty with package version 3.5.6-4ubuntu4.3
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707172
Ti
On 2 September 2017 at 16:22, Julian Andres Klode
wrote:
> Thanks Ard.
>
> Fixes for both artful and zesty are uploaded now.
>
Great! Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707172
Ti
On 2 September 2017 at 15:49, Julian Andres Klode
wrote:
> @ard Are released older than zesty affected as well? I don't have a
> machine to test this, I'm just uploading the fix for zesty and artful.
>
No, the issue appeared only after upgrading to Zesty.
--
You received this bug notification b
On 1 September 2017 at 14:32, Julian Andres Klode
wrote:
> Ah, https://gitlab.com/gnutls/gnutls/issues/204 has more details.
>
> ** Description changed:
>
> + [Impact]
> + AES256-GCM ciphertext is all zero on arm64 with hardware acceleration,
> breaking gnome-terminal and xfce4-terminal which use
On 1 September 2017 at 14:10, Julian Andres Klode
wrote:
> Do we have a reproducible test case for an SRU?
>
Doesn't the debian bug report have one?
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1707172
>
> Title:
>
Actually, it appears this issue is caused by a bug in libgnutls:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867581
** Bug watch added: Debian Bug tracker #867581
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867581
--
You received this bug notification because you are a member of
Public bug reported:
The following Debian issue exists in the Ubuntu package as well
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867581
It breaks gnome-terminal and xfce4-terminal on arm64 machines.
The issue is fixed upstream in 3.5.13, and the fix was backported to
Debian stretch as wel
Public bug reported:
On an arm64 system (Cortex-A57 based AMD Overdrive), dumping a lot of
data to a gnome-terminal window crashes the gnome-terminal-server
process.
For instance, doing something like
$ hexdump -C /dev/urandom
will crash within a matter of seconds with the following backtrace
Previous kernels produced a crash like this one:
Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
console [ttyS0] disabled
Unable to handle kernel paging request at virtual address 7dfffee0004e
pgd = 1f2542365000
[7dfffee0004e] *pgd=00013745c003, *pud=00013745d003,
*pm
For the record, DT boot is equally affected, even though the fix
mentions ACPI _HIDs etc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692548
Title:
Marvell MacchiatoBin crashes in fintek_8250_prob
This may be related to issues we encountered with LTO. Could you use the
GCC49 profile instead? The only difference between GCC49 and GCC5 is
whether LTO is enabled, they can both be used with a GCC that is in fact
6.x
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
When Clang itself is built with GCC 5 or later, it may crash when
building for the aarch64 architecture if the following patch is not
applied
https://www.marc.info/?l=llvm-commits&m=142918476428427&w=4
This applies to wily only: vivid uses GCC 4.9, and xenial already has
the
Public bug reported:
EFISTUB zImages for ARM64 contain two sections, a dummy .reloc section
and a .text sections covering the entire payload.
When attempting to sign such a zImage, sbsign fails in the
image_find_regions() like so
Starting program: /home/ard/build/sbsigntool-0.6/src/sbsign --key
Hi Riku,
I am in touch with the OpenSSL maintainer who authored most of the
assembler code in OpenSSL (for all architectures).
ARMv8 versions will likely be done in collaboration with him, including
(NEON) accelerated versions of SHA and AES (as the crypto extensions on
v8 are optional). I will k
In fact, this still does not look correct: it should read
SIXTY_FOUR_BIT_LONG not SIXTY_FOUR_BIT (the latter is intended for Win64
style LLP64 model)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/11021
19 matches
Mail list logo
