From: Goffredo Baroncelli <kreijack@inwind.it>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: GRUB bug with Btrfs multiple devices
Date: Thu, 28 Nov 2019 18:58:12 +0100 [thread overview]
Message-ID: <69aaf772-9eb0-945a-5277-40895e6901de@inwind.it> (raw)
In-Reply-To: <CAJCQCtQF6xtBDWc+i3FezWZUqGsj8hJrAzYpWG+=huFkmOK==g@mail.gmail.com>
On 28/11/2019 01.42, Chris Murphy wrote:
> On Tue, Nov 26, 2019 at 11:07 PM Goffredo Baroncelli <kreijack@inwind.it> wrote:
>>
[...]
>> Could you enable the debug, doing
>>
>> set pager=1
>> set debug=all
>
> I need to narrow the scope. Adding 'set debug=all', there's just way
> too much to video, minutes of pages just holding down space bar full
> time which is even too fast to video. There must be over 1000 pages, a
> tiny minority contain efidisk.c references, the vast majority are
> btrfs.c references. As many pages as there are, I was never able to
> stop right on a boundary between efidisk.c and btrfs.c. So I gave up
> on that approach.
If I remember correctly, in the previous email you reports that even a simple "ls" at the grub prompt raises an error.
So you could watch what happens when doing something simpler like "ls" or "ls (hd0)"
>
> Since the errors happen with efidisk.c I've enabled 'set
> debug=efidisk' and captured 74 photos, available at the link below
> (they are in pager order)
>
>
>
> It does seem that the errors only happen in efidisk.c and only when
> trying to read from what might be phantom devices; I do not know how a
> second device in a Btrfs volume triggers this though. There must be
> some interaction between efidisk.c and btrfs.c? The grubx64.efi,
> grubenv, grub.cfg, and grub modules are all on an HFS+ (no journal)
> file system acting as the EFI System partition (as is the default
> behavior in Fedora on Macs for many years now). Only vmlinuz and
> initramfs are on Btrfs. So I'm not really even sure why btrfs.c gets
> called before the GRUB menu is displayed.
>
> I'll see about reproducing this with a VM using edk2 UEFI and two
> virtio devices, at least get to a cleaner environment so we're not
> confusing multiple system specific weird things. And I can also leave
> this particular Mac laptop as it is for further study.
>
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2019-11-28 17:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 4:05 GRUB bug with Btrfs multiple devices Chris Murphy
2019-11-26 21:11 ` Goffredo Baroncelli
2019-11-26 23:53 ` Chris Murphy
2019-11-27 1:35 ` Chris Murphy
2019-11-27 6:07 ` Goffredo Baroncelli
2019-11-28 0:42 ` Chris Murphy
2019-11-28 17:58 ` Goffredo Baroncelli [this message]
2019-11-28 20:05 ` Chris Murphy
2019-11-28 21:57 ` Goffredo Baroncelli
2019-11-29 17:57 ` Chris Murphy
2019-11-29 19:54 ` Goffredo Baroncelli
2019-11-29 21:17 ` Chris Murphy
2019-11-30 7:33 ` Andrei Borzenkov
2019-11-30 8:12 ` Goffredo Baroncelli
2019-11-30 16:38 ` Chris Murphy
2019-11-27 6:09 ` Goffredo Baroncelli
2019-11-29 20:50 ` Andrei Borzenkov
2019-11-29 21:11 ` Chris Murphy
2019-11-30 7:31 ` Andrei Borzenkov
2019-11-30 16:31 ` Chris Murphy
2019-11-30 17:02 ` Andrei Borzenkov
2019-11-30 17:14 ` Chris Murphy
2019-11-30 17:34 ` Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69aaf772-9eb0-945a-5277-40895e6901de@inwind.it \
--to=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).