Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1019498

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

Show all headers | View raw

Hello,

I applied the fix and built the package. It didn't help. I also built
latest master and I still have this issue.

BTW, the computer is an OptiPlex 7040. Full hwinfo --bios: 
https://lebihan.pl/files/hwinfo-bios.txt

Error trace:
```
root@s217-lab00:~# /dev/shm/efibootmgr/src/efibootmgr -v
BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 0003,0004,0001,0005,000A,0007,0008,0009,0002
Boot0000* Windows Boot ManagerCould not parse device path: Invalid
argument
error trace:
 /build/efivar-yvRv8P/efivar-37/src/include/efivar/efivar-dp.h:1208
efidp_is_valid(): invalid device path node type: Invalid argument
```

Michel Le Bihan

Le lundi 27 juillet 2020 à 15:28 +0000, Limonciello, Mario a écrit :
> > -----Original Message-----
> > From: Michel Le Bihan <michel@lebihan.pl>
> > Sent: Sunday, July 26, 2020 2:58 PM
> > To: 963475@bugs.debian.org
> > Subject: Bug#963475: libefivar1: "efibootmgr -v" fails with "Could
> > not
> > parse device path: Invalid argument"
> > 
> > 
> > [EXTERNAL EMAIL]
> > 
> > Hello,
> > 
> > What's preventing the upstream fix from being applied to this
> > package?
> > 
> > Michel Le Bihan
> 
> I personally can't reproduce the failure on my system's firmware.
> Can you apply the fix locally and confirm it actually helps?

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" "Francesco Poli (wintermute)" <invernomuto@paranoici.org> - 2020-06-22 09:00 +0200
  Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Francesco Poli <invernomuto@paranoici.org> - 2020-06-27 15:40 +0200
  Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-26 22:10 +0200
  Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-27 18:30 +0200
    Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Kevin Locke <kevin@kevinlocke.name> - 2020-07-27 21:00 +0200
  Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-27 19:20 +0200
  Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-27 20:10 +0200
  Bug#963475: Could not parse device path: Invalid argument Omer Ozarslan <omerfaruko@gmail.com> - 2020-07-28 03:20 +0200
  Bug#963475: Could not parse device path: Invalid argument Michel Le Bihan <michel@lebihan.pl> - 2020-07-29 22:50 +0200

csiph-web