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

2020-07-27 Thread Michel Le Bihan 
I added a comment under the existing closed issue: 
https://github.com/rhboot/efibootmgr/issues/133#issuecomment-664549236

Le lundi 27 juillet 2020 à 17:54 +, Limonciello, Mario a écrit :
> In that case, would you mind reporting a bug to upstream efibootmgr?
> It seems
> to me that your Boot entry can't be properly parsed.  You may
> need to also
> attach it to your bug report.
> 
> > -Original Message-
> > From: Michel Le Bihan 
> > Sent: Monday, July 27, 2020 12:16 PM
> > To: Limonciello, Mario; 963...@bugs.debian.org
> > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with
> > "Could not
> > parse device path: Invalid argument"
> > 
> > 
> > [EXTERNAL EMAIL]
> > 
> > It was efibootmgr and efivar master.
> > 
> > Le lundi 27 juillet 2020 à 16:46 +, Limonciello, Mario a écrit
> > :
> > > Was that just efibootmgr master?
> > > If possible, can you move up to *both* efivar master and
> > > efibootmgr
> > > master and try again?
> > > 
> > > > -Original Message-
> > > > From: Michel Le Bihan 
> > > > Sent: Monday, July 27, 2020 11:25 AM
> > > > To: Limonciello, Mario; 963...@bugs.debian.org
> > > > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with
> > > > "Could not
> > > > parse device path: Invalid argument"
> > > > 
> > > > 
> > > > [EXTERNAL EMAIL]
> > > > 
> > > > 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
> > > > Boot* 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 +, Limonciello, Mario a
> > > > écrit
> > > > :
> > > > > > -Original Message-
> > > > > > From: Michel Le Bihan 
> > > > > > Sent: Sunday, July 26, 2020 2:58 PM
> > > > > > To: 963...@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?

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

2020-07-27 Thread Michel Le Bihan 
It was efibootmgr and efivar master.

Le lundi 27 juillet 2020 à 16:46 +, Limonciello, Mario a écrit :
> Was that just efibootmgr master?
> If possible, can you move up to *both* efivar master and efibootmgr
> master and try again?
> 
> > -Original Message-
> > From: Michel Le Bihan 
> > Sent: Monday, July 27, 2020 11:25 AM
> > To: Limonciello, Mario; 963...@bugs.debian.org
> > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with
> > "Could not
> > parse device path: Invalid argument"
> > 
> > 
> > [EXTERNAL EMAIL]
> > 
> > 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
> > Boot* 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 +, Limonciello, Mario a écrit
> > :
> > > > -Original Message-
> > > > From: Michel Le Bihan 
> > > > Sent: Sunday, July 26, 2020 2:58 PM
> > > > To: 963...@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?

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

2020-07-27 Thread Limonciello, Mario 
I would suggest a new issue linking to that one instead so it's not lost.

> -Original Message-
> From: Michel Le Bihan 
> Sent: Monday, July 27, 2020 1:01 PM
> To: Limonciello, Mario; 963...@bugs.debian.org
> Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not
> parse device path: Invalid argument"
> 
> 
> [EXTERNAL EMAIL]
> 
> I added a comment under the existing closed issue:
> https://github.com/rhboot/efibootmgr/issues/133#issuecomment-664549236
> 
> Le lundi 27 juillet 2020 à 17:54 +, Limonciello, Mario a écrit :
> > In that case, would you mind reporting a bug to upstream efibootmgr?
> > It seems
> > to me that your Boot entry can't be properly parsed.  You may
> > need to also
> > attach it to your bug report.
> >
> > > -Original Message-
> > > From: Michel Le Bihan 
> > > Sent: Monday, July 27, 2020 12:16 PM
> > > To: Limonciello, Mario; 963...@bugs.debian.org
> > > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with
> > > "Could not
> > > parse device path: Invalid argument"
> > >
> > >
> > > [EXTERNAL EMAIL]
> > >
> > > It was efibootmgr and efivar master.
> > >
> > > Le lundi 27 juillet 2020 à 16:46 +, Limonciello, Mario a écrit
> > > :
> > > > Was that just efibootmgr master?
> > > > If possible, can you move up to *both* efivar master and
> > > > efibootmgr
> > > > master and try again?
> > > >
> > > > > -Original Message-
> > > > > From: Michel Le Bihan 
> > > > > Sent: Monday, July 27, 2020 11:25 AM
> > > > > To: Limonciello, Mario; 963...@bugs.debian.org
> > > > > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with
> > > > > "Could not
> > > > > parse device path: Invalid argument"
> > > > >
> > > > >
> > > > > [EXTERNAL EMAIL]
> > > > >
> > > > > 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
> > > > > Boot* 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 +, Limonciello, Mario a
> > > > > écrit
> > > > > :
> > > > > > > -Original Message-
> > > > > > > From: Michel Le Bihan 
> > > > > > > Sent: Sunday, July 26, 2020 2:58 PM
> > > > > > > To: 963...@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?

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

2020-07-27 Thread Michel Le Bihan 
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
Boot* 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 +, Limonciello, Mario a écrit :
> > -Original Message-
> > From: Michel Le Bihan 
> > Sent: Sunday, July 26, 2020 2:58 PM
> > To: 963...@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?

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

2020-07-27 Thread Kevin Locke 
On Mon, 2020-07-27 at 18:24 +0200, Michel Le Bihan wrote:
> Le lundi 27 juillet 2020 à 15:28 +, Limonciello, Mario a écrit :
>>> On Sun, 2020-07-26 at 14:58, Michel Le Bihan wrote:
>>> What's preventing the upstream fix from being applied to this
>>> package?
>> 
>> I personally can't reproduce the failure on my system's firmware.
>> Can you apply the fix locally and confirm it actually helps?
> 
> I applied the fix and built the package. It didn't help. I also built
> latest master and I still have this issue.

FWIW, I'm also experiencing the issue that efibootmgr -v produces the
error "Could not parse device path: Invalid argument" with libefiboot1
37-2.1, but not 37-2.  Building libefiboot1 with fdb8034 and 4e04afc
added to debian/patches does solve the issue for me.

https://github.com/rhboot/efivar/commit/fdb803402fb32fa6d020bac57a40c7efe4aabb7d.patch
https://github.com/rhboot/efivar/commit/4e04afc2df9bbc26e5ab524b53a6f4f1e61d7c9e.patch

Best,
Kevin

P.S. I had to build using GCC 9 due to
https://github.com/rhboot/efivar/issues/156

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

2020-07-27 Thread Limonciello, Mario 
In that case, would you mind reporting a bug to upstream efibootmgr? It seems
to me that your Boot entry can't be properly parsed.  You may need to also
attach it to your bug report.

> -Original Message-
> From: Michel Le Bihan 
> Sent: Monday, July 27, 2020 12:16 PM
> To: Limonciello, Mario; 963...@bugs.debian.org
> Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not
> parse device path: Invalid argument"
> 
> 
> [EXTERNAL EMAIL]
> 
> It was efibootmgr and efivar master.
> 
> Le lundi 27 juillet 2020 à 16:46 +, Limonciello, Mario a écrit :
> > Was that just efibootmgr master?
> > If possible, can you move up to *both* efivar master and efibootmgr
> > master and try again?
> >
> > > -Original Message-
> > > From: Michel Le Bihan 
> > > Sent: Monday, July 27, 2020 11:25 AM
> > > To: Limonciello, Mario; 963...@bugs.debian.org
> > > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with
> > > "Could not
> > > parse device path: Invalid argument"
> > >
> > >
> > > [EXTERNAL EMAIL]
> > >
> > > 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
> > > Boot* 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 +, Limonciello, Mario a écrit
> > > :
> > > > > -Original Message-
> > > > > From: Michel Le Bihan 
> > > > > Sent: Sunday, July 26, 2020 2:58 PM
> > > > > To: 963...@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?

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

2020-07-27 Thread Limonciello, Mario 
> -Original Message-
> From: Michel Le Bihan 
> Sent: Sunday, July 26, 2020 2:58 PM
> To: 963...@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?

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

2020-07-27 Thread Limonciello, Mario 
Was that just efibootmgr master?
If possible, can you move up to *both* efivar master and efibootmgr master and 
try again?

> -Original Message-
> From: Michel Le Bihan 
> Sent: Monday, July 27, 2020 11:25 AM
> To: Limonciello, Mario; 963...@bugs.debian.org
> Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not
> parse device path: Invalid argument"
> 
> 
> [EXTERNAL EMAIL]
> 
> 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
> Boot* 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 +, Limonciello, Mario a écrit :
> > > -Original Message-
> > > From: Michel Le Bihan 
> > > Sent: Sunday, July 26, 2020 2:58 PM
> > > To: 963...@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?

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

2020-07-26 Thread Michel Le Bihan 
Hello,

What's preventing the upstream fix from being applied to this package?

Michel Le Bihan

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

2020-06-27 Thread Francesco Poli 
On Mon, 22 Jun 2020 08:46:14 +0200 Francesco Poli (wintermute) wrote:

[...]
> I searched the web and found a github [issue], that claims the
> problem is in efivar, mentioning a [commit] that is supposed
> to fix it.
> But it seems to me that the [code] currently in Debian unstable
> does not include this fix.
> 
> [issue]: 
> [commit]: 
> 
> [code]: 
> 
> I hope I am not completely off-track...   :-p
> 
> Could you please investigate the issue and cherrypick the patch,
> if appropriate?

I tried to downgrade from libefiboot1/37-2.1 to libefiboot1/37-2 and I
can confirm that the problem vanishes after the downgrade.

Is there any news on your side?
Please let me know, thanks for your time!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpbiDJ7ggoT6.pgp
Description: PGP signature

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

2020-06-22 Thread Francesco Poli (wintermute) 
Package: libefivar1
Version: 37-2.1
Severity: important

Hello!

One week ago I had no issues in running:

  $ efibootmgr -v

but today, I get:

  $ efibootmgr -v
  BootCurrent: 0001
  Timeout: 1 seconds
  BootOrder: 0001,
  Boot* debianCould not parse device path: Invalid argument

Please note that (luckily!) the system is able to boot and reboot,
and that the non-verbose output is:

  $ efibootmgr
  BootCurrent: 0001
  Timeout: 1 seconds
  BootOrder: 0001,
  Boot* debian
  Boot0001* debian2

I searched the web and found a github [issue], that claims the
problem is in efivar, mentioning a [commit] that is supposed
to fix it.
But it seems to me that the [code] currently in Debian unstable
does not include this fix.

[issue]: 
[commit]: 

[code]: 

I hope I am not completely off-track...   :-p

Could you please investigate the issue and cherrypick the patch,
if appropriate?

Thanks for your time.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libefivar1 depends on:
ii  libc6  2.30-8

libefivar1 recommends no packages.

libefivar1 suggests no packages.

-- no debconf information