mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jlu@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: suddenly, i can't boot barebox on my beagle xM anymore [ISOLATED]
Date: Mon, 03 Dec 2012 09:19:42 +0100	[thread overview]
Message-ID: <1354522782.3772.3.camel@coredoba.hi.pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1212020418020.6898@oneiric>

Hi,

On Sun, 2012-12-02 at 04:24 -0500, Robert P. J. Day wrote:
> i've isolated the commit that introduces the apparent booting
> problem on my xM:
> 
> $ git show 154496f
> commit 154496f736db54123c3f6daaba18809fab54ed9b
> Merge: 05d251f bd6d12b
> Author: Sascha Hauer <s.hauer@pengutronix.de>
> Date:   Fri Nov 16 14:02:49 2012 +0100
> 
>     Merge branch 'for-next/omap'

*snip*

>   so something in that omap merge is causing this.

The merge itself does not actually introduce new code.

Could you try finding the commit with git bisect?

~/git/barebox $ git bisect start
~/git/barebox $ git bisect bad 154496f736db54123c3f6daaba18809fab54ed9b
~/git/barebox $ git bisect good 05d251f
Bisecting: 3 revisions left to test after this (roughly 2 steps)
[663c466794382f803a69414c935cf0a13d4f0761] ARM OMAP4 panda: switch to new environment
~/git/barebox $

Then test this checkout and tell git using "git bisect good" or "git
bisect bad".

Thanks,
Jan
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-12-03  8:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-01 21:18 suddenly, i can't boot barebox on my beagle xM anymore Robert P. J. Day
2012-12-01 22:36 ` Robert P. J. Day
2012-12-02  9:24   ` suddenly, i can't boot barebox on my beagle xM anymore [ISOLATED] Robert P. J. Day
2012-12-03  8:19     ` Jan Lübbe [this message]
2012-12-03  8:31       ` Robert P. J. Day
2012-12-03  8:44         ` Jan Lübbe
2012-12-03  8:48           ` Robert P. J. Day
2012-12-03  8:55           ` Robert P. J. Day
2012-12-03  9:46 ` suddenly, i can't boot barebox on my beagle xM anymore Sascha Hauer
2012-12-03  9:50   ` Robert P. J. Day
2012-12-03  9:56     ` Sascha Hauer
2012-12-03 10:01       ` Robert P. J. Day
2012-12-03 10:04         ` Sascha Hauer
2012-12-03 10:07           ` Robert P. J. Day
2012-12-03 12:02           ` Robert P. J. Day

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=1354522782.3772.3.camel@coredoba.hi.pengutronix.de \
    --to=jlu@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=rpjday@crashcourse.ca \
    /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