mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: am335x: baltos
Date: Tue, 5 Jul 2022 10:52:17 +0200	[thread overview]
Message-ID: <20220705085217.GC5208@pengutronix.de> (raw)
In-Reply-To: <CAGm1_kss73npzzCzoD44kO4C24PNwPHZcOV_nZWwq_sW12zxww@mail.gmail.com>

Hi Yegor,

On Mon, Jul 04, 2022 at 02:54:48PM +0200, Yegor Yefremov wrote:
> am335x-baltos got broken between 2022.06 and the current master. The
> symptoms: no barebox console output at all i.e. the system freezes.
> 
> Here is git bisect log but I don't really see the reason for the failure:
> 
> # first bad commit: [8828e1226981b6a31b12a643768cac63fae3576e] Merge
> branch 'for-next/imx'

There's nothing in this branch that is even compiled on your board, so I
would guess that you gave a wrong answer somewhere during bisecting.
Apart from bisecting again you could enable some debugging:

[*] Low level debug messages (read help)
    Kernel low-level debugging port (AM33XX Debug UART)  --->
    (0) OMAP Debug UART Port Selection
    [*] Trace initcalls

Regards,
  Sascha
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2022-07-05  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 12:54 Yegor Yefremov
2022-07-05  8:52 ` Sascha Hauer [this message]
2022-07-05 12:51   ` Yegor Yefremov

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=20220705085217.GC5208@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=yegorslists@googlemail.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