All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Javier Martinez Canillas <fmartine@redhat.com>,
	The development of GNU GRUB <grub-devel@gnu.org>,
	Daniel Kiper <dkiper@net-space.pl>
Cc: Sergei Trofimovich <slyfox@gentoo.org>,
	debian-ia64 <debian-ia64@lists.debian.org>,
	Peter Jones <pjones@redhat.com>,
	Michael Karcher <debian@mkarcher.dialup.fu-berlin.de>
Subject: Re: GRUB error: unknown filesystem on ia64
Date: Sat, 10 Apr 2021 11:40:33 +0200	[thread overview]
Message-ID: <5b041746-09e9-0557-9f2a-ac3b37837728@physik.fu-berlin.de> (raw)
In-Reply-To: <e504dcd3-ea25-41a2-a859-8b5608bc9ad2@physik.fu-berlin.de>

On 4/8/21 7:30 PM, John Paul Adrian Glaubitz wrote:
> On 4/8/21 7:10 PM, Javier Martinez Canillas wrote:
>>> Any news on this? I assume this should be trivial to fix when considering just the
>>
>> Not yet, sorry. I discussed a little bit with Peter yesterday but it's strange
>> that only affects ia64 and not x64. I'll try to take a look at this next week.
> 
> It's probably caused by different natural alignment which causes the code on x86_64
> to land at the right position automatically.

OK, so I had another discussion with Michael Karcher who analyzed the bug and the
problem is apparently that after the change, mkimage adds an alignment to the module
address which it did not before the change.

And the suspicion why this affects ia64 and not x86_64 could be that the module data
is properly aligned as mkimage expects while it's not on ia64.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



  reply	other threads:[~2021-04-10  9:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 18:22 GRUB error: unknown filesystem on ia64 John Paul Adrian Glaubitz
2021-03-26 18:01 ` Daniel Kiper
2021-03-26 18:28   ` John Paul Adrian Glaubitz
2021-03-26 18:43     ` Daniel Kiper
2021-04-08 16:45       ` John Paul Adrian Glaubitz
2021-04-08 17:10         ` Javier Martinez Canillas
2021-04-08 17:30           ` John Paul Adrian Glaubitz
2021-04-10  9:40             ` John Paul Adrian Glaubitz [this message]
2021-04-12  6:21               ` Javier Martinez Canillas
2021-04-12  6:57                 ` John Paul Adrian Glaubitz
2021-04-16 15:21                   ` Javier Martinez Canillas
2021-04-16 16:43                     ` John Paul Adrian Glaubitz
2021-04-16 16:55                       ` John Paul Adrian Glaubitz
2021-04-16 20:14                         ` Javier Martinez Canillas
2021-04-16 20:32                           ` John Paul Adrian Glaubitz
2021-04-16 21:32                             ` Javier Martinez Canillas
2021-04-19 15:33                               ` John Paul Adrian Glaubitz
2021-04-19 17:56                                 ` Javier Martinez Canillas
2021-04-21 17:54                                   ` Javier Martinez Canillas
2021-04-16 15:21                   ` Javier Martinez Canillas
2021-06-16 14:22 Javier Martinez Canillas

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=5b041746-09e9-0557-9f2a-ac3b37837728@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=debian-ia64@lists.debian.org \
    --cc=debian@mkarcher.dialup.fu-berlin.de \
    --cc=dkiper@net-space.pl \
    --cc=fmartine@redhat.com \
    --cc=grub-devel@gnu.org \
    --cc=pjones@redhat.com \
    --cc=slyfox@gentoo.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.