grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Jeff Chua <jeff.chua.linux@gmail.com>
Subject: Re: Fwd: boot/i386/pc/startup_raw.S:115: Error: attempt to move .org backwards
Date: Thu, 01 Dec 2011 08:47:07 +0100	[thread overview]
Message-ID: <4ED730FB.30002@gmail.com> (raw)
In-Reply-To: <CAAJw_ZunpsF-oLZt-a7VK2_SbpxFD+KoakVgEi+22tbghEixdA@mail.gmail.com>

On 01.12.2011 08:21, Jeff Chua wrote:
> 2011/11/25 Vladimir 'φ-coder/phcoder' Serbinenko<phcoder@gmail.com>:
>
>> That's pretty weird since no recent changes to reiserfs or msdos part but I
>> can attempt to recreate. Could you perhaps try to bisect to get exact
>> faulting revision? Your range spans 20 intensive commits. Bisecting it is at
>> most 5 attempts but will simplify the debugging greately.
> I bisect it down further. Still workd at rev 3588. Couldn't compile
> 3589. Doesn't work at rev 3590.
>
Thanks. It should help although I'm still scratching my head on this one.
> It seems even on 32-bit, it's not 100% reliable. Works 99% of the
> time, but hangs occasionally when I copy a new boot file to the
> reiserfs partition.
>
What do you mean by "copying boot file"?
> Jeff
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



  reply	other threads:[~2011-12-01  7:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 14:46 boot/i386/pc/startup_raw.S:115: Error: attempt to move .org backwards Jeff Chua
2011-11-14 14:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-14 16:27 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17  0:29   ` Jeff Chua
2011-11-17  0:44     ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17  0:47       ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17  5:23       ` Jeff Chua
2011-11-17 10:13         ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 15:38           ` Jeff Chua
2011-11-17 16:15             ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 16:30               ` Jeff Chua
2011-11-17 16:33                 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 17:40                   ` Jeff Chua
2011-11-17 17:52                     ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 18:07                       ` Jeff Chua
2011-11-17 18:17                         ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 18:36                           ` Jeff Chua
2011-11-17 19:15                             ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-18  0:04                               ` Jeff Chua
2011-11-21  7:32                               ` Jeff Chua
2011-11-21 22:22                                 ` Jeff Chua
2011-11-21 22:42                                   ` Fwd: " Jeff Chua
2011-11-25 13:29                                     ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-12-01  7:21                                       ` Jeff Chua
2011-12-01  7:47                                         ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-12-23  9:26                                     ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17  9:25     ` Vladimir 'φ-coder/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=4ED730FB.30002@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=jeff.chua.linux@gmail.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).