bugs.debian.org; Bernhard Übelacker
> Subject: Bug#977043: fwupdmgr[1191] trap invalid opcode ip:4247d0 sp:bf98504c
> error:0 in fwupdmgr[423000+15000]
>
>
> [EXTERNAL EMAIL]
>
> ke 10. maalisk. 2021 klo 13.08 Julien Cristau (jcris...@debian.org) kirjoitti:
> >
> >
Martin-Éric Racine
> Sent: Wednesday, March 10, 2021 10:25
> To: Limonciello, Mario
> Cc: 977...@bugs.debian.org; Julien Cristau; Bernhard Übelacker
> Subject: Re: Bug#977043: fwupdmgr[1191] trap invalid opcode ip:4247d0
> sp:bf98504c error:0 in fwupdmgr[423000+15000]
>
>
arch 10, 2021 5:14
> > To: Julien Cristau
> > Cc: 977...@bugs.debian.org; Bernhard Übelacker
> > Subject: Bug#977043: fwupdmgr[1191] trap invalid opcode ip:4247d0
> > sp:bf98504c
> > error:0 in fwupdmgr[423000+15000]
> >
> >
> > [EXTERNAL EMAIL]
> >
Hello Martin-Éric,
without being involved in packaging fwupd I tried to
have a look at this issue.
I could not reproduce it inside a i386 qemu VM (not even
with "-cpu pentium"). Have not tested on real hardware.
Looking up the endbr32 instruction, it seems it belongs to something
called
ke 10. maalisk. 2021 klo 13.08 Julien Cristau (jcris...@debian.org) kirjoitti:
>
> On Wed, Mar 10, 2021 at 01:01:30PM +0200, Martin-Éric Racine wrote:
> > This could indeed be it. The baseline for Bullseye still is a basic
> > 686. Additionally, the lowest Linux kernel for i386 is linux-image-686
On Wed, Mar 10, 2021 at 01:01:30PM +0200, Martin-Éric Racine wrote:
> This could indeed be it. The baseline for Bullseye still is a basic
> 686. Additionally, the lowest Linux kernel for i386 is linux-image-686
> which is configured for Geode. Still, the bug just appeared a few days
> ago when the
This could indeed be it. The baseline for Bullseye still is a basic
686. Additionally, the lowest Linux kernel for i386 is linux-image-686
which is configured for Geode. Still, the bug just appeared a few days
ago when the package in Testing was updated. This seems like a
regression.
$ lscpu
This looks relevant: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84148
Cheers,
Julien
On Wed, Mar 10, 2021 at 11:20:25AM +0100, Bernhard Übelacker wrote:
> Hello Martin-Éric,
> without being involved in packaging fwupd I tried to
> have a look at this issue.
>
> I could not reproduce it inside
Package: fwupd
Version: 1.5.1-5
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
$ sudo invoke-rc.d fwupd restart
Job for fwupd.service failed because a fatal signal was delivered causing the
control process to dump core.
See "systemctl status fwupd.service" and "journalctl
9 matches
Mail list logo
