[tbot] How to debug acquire_linux

Harald Seiler hws at denx.de
Fri Nov 23 11:32:51 UTC 2018

On Thu, 2018-11-22 at 19:24 +0100, Stefano Babic wrote:
> Hi,
> I have a board that cannot be got in linux. It looks like that
> tbot.acquire_linux() hangs forever (can I set a tiimeout ?)
> I ran a testcase that works fine for another board - I guess that the
> issue is due to the fact that this board has a lot of output in part
> caused by systemd and in part due to kernel messages that are printed to
> the console. When I start the testcase, tbot remains in <board>-linux. I
> can understand that board is up and works because software activates
> some relays, but it is not recognized by tbot.
> The weird thing is that "interactive_linux" works.

I overlooked this previously ... `interactive_linux` works?  That's not
possible, it uses the *exact same* code-path ... Is this a consistent

> How can I debug this? 

I pushed changes to the development branch that allow deeper introspection by showing
all data sent and received ...

> Or do we have to block kernel messages to the console via kernel
> parameter ?
> Bye,
> Stefano

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-62  Fax: +49-8142-66989-80   Email: hws at denx.de

More information about the tbot mailing list