All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Jarvis <James.Jarvis@ed.ac.uk>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: echo and hello bug
Date: Wed, 17 Jun 2009 16:24:39 +0100	[thread overview]
Message-ID: <4A390AB7.5070609@ed.ac.uk> (raw)
In-Reply-To: <d7ead6de0906160934r6172026t532b9f1cbcb4643a@mail.gmail.com>

Vladimir 'phcoder' Serbinenko wrote:
>
>
> On Tue, Jun 16, 2009 at 4:09 PM, James Jarvis <James.Jarvis@ed.ac.uk 
> <mailto:James.Jarvis@ed.ac.uk>> wrote:
>
>     Vladimir 'phcoder' Serbinenko wrote:
>
>             tried this module list in grub-mkimage on 2282 but it hung!
>                
>
>         I think you have a problem with you building system. If you
>         want ping
>         me (phcoder) on IRC and I'll compile for you
>          
>
>     Shamed me into looking deeper! I discover that by listing hello
>     and echo first in the grub-mkimage command they both work as
>     expected. Not sure why this occurs - is there a file detailing
>     module dependencies one can look at?
>
> You have probably hit a memory access bug in a secondary module. Post 
> the list of modules you integrate and try removing some of these modules
It appears that if the "echo" and "hello" modules are in the efi image 
before the "kernel" module they work but if after they don't.

Moving "kernel" to the end means that "echo" "hello" and "ls" work 
correctly. I need kernel so I just need to remember to put it as the 
last module. Presumably I am not the first to come across this problem 
but it was not one that came up easily in searches. I'll add to the bug 
report.

James


-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.




  reply	other threads:[~2009-06-17 15:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 11:34 echo and hello bug James Jarvis
2009-06-08 11:42 ` Vladimir 'phcoder' Serbinenko
2009-06-08 13:39   ` James Jarvis
2009-06-09  3:47     ` Peter Cros
2009-06-09 14:43       ` James Jarvis
2009-06-09 15:01         ` Vladimir 'phcoder' Serbinenko
2009-06-16 14:09           ` James Jarvis
2009-06-16 16:07             ` Felix Zielcke
2009-06-16 16:34             ` Vladimir 'phcoder' Serbinenko
2009-06-17 15:24               ` James Jarvis [this message]
2009-06-17 16:07                 ` Vladimir 'phcoder' Serbinenko

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=4A390AB7.5070609@ed.ac.uk \
    --to=james.jarvis@ed.ac.uk \
    --cc=grub-devel@gnu.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.