From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] B@D run on Renesas board - issue
Date: Thu, 16 Nov 2017 17:54:27 +0900 [thread overview]
Message-ID: <009c01d35eb8$82d1b050$887510f0$@toshiba.co.jp> (raw)
In-Reply-To: <d279e51b2e1b4d6394b0d77606efac0b@RVC-EX13-M02.rvc.renesas.com>
Dear Trung san
> -----Original Message-----
> From: Trung. Huynh [mailto:trung.huynh.uw at rvc.renesas.com]
> Sent: Thursday, November 16, 2017 5:49 PM
> To: Daniel Sangorrin; 'Robert Marshall'; Binh Thanh. Nguyen
> Cc: O365-Toru Oishi; 'Chris Paterson'; cip-dev at lists.cip-project.org
> Subject: RE: B at D run on Renesas board - issue
>
> Dear Daniel,
>
> Thank for your reply.
> The log in attachment is took from lava for easily observing instead of html page.
> Regarding deploy section, YES, as you can see the log showing that has passed over it already to get into test section.
>
> Is there anything going wrong?
> Looking for your feedback
>
It seems that you are not booting from a ramdisk, but rather the rootfs installed on the eMMC or SD Card.
Regards,
Daniel
> Best Regards,
> Trung
>
> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> Sent: Thursday, November 16, 2017 3:11 PM
> To: Trung. Huynh <trung.huynh.uw@rvc.renesas.com>; 'Robert Marshall' <robert.marshall@codethink.co.uk>; Binh Thanh. Nguyen
> <binh.nguyen.uw@rvc.renesas.com>
> Cc: O365-Toru Oishi <toru.oishi.zj@renesas.com>; 'Chris Paterson' <Chris.Paterson2@renesas.com>; cip-dev at lists.cip-project.org
> Subject: RE: B at D run on Renesas board - issue
>
> Dear Trung san,
>
> > -----Original Message-----
> > From: Trung. Huynh [mailto:trung.huynh.uw at rvc.renesas.com]
> > Sent: Wednesday, November 15, 2017 7:21 PM
> > To: Daniel Sangorrin; 'Robert Marshall'; Binh Thanh. Nguyen
> > Cc: O365-Toru Oishi; 'Chris Paterson'; cip-dev at lists.cip-project.org
> > Subject: RE: B at D run on Renesas board - issue
> >
> > Hi Daniel, Robert,
> >
> > We got into test section already, but have no idea why it attempts to execute the thing non-exist at all:
> > # /lava-237/bin/lava-test-runner /lava-237/0 as you can see our error
> > log in attachment.
> > I also take example log over here https://gitlab.com/snippets/1679749
> > to see that it can create a directory by mkdir /lava-1
> >
> > Could you please tell us what does it make scene? How can we fix it?
> > Thank you.
>
> Please could you send the complete log?
>
> > P/S: healthcheck script same as Binh-san attached to you before
>
> Did you make sure to uncomment the deploy section?
>
> Regards,
> Daniel
>
> >
> > Best Regards,
> > Trung
> >
> > -----Original Message-----
> > From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> > Sent: Monday, November 6, 2017 9:19 AM
> > To: 'Robert Marshall' <robert.marshall@codethink.co.uk>; Binh Thanh.
> > Nguyen <binh.nguyen.uw@rvc.renesas.com>
> > Cc: O365-Toru Oishi <toru.oishi.zj@renesas.com>; 'Chris Paterson'
> > <Chris.Paterson2@renesas.com>; Trung. Huynh
> > <trung.huynh.uw@rvc.renesas.com>; cip-dev at lists.cip-project.org
> > Subject: RE: B at D run on Renesas board - issue
> >
> > Hello Binh-san,
> >
> > > -----Original Message-----
> > > From: Robert Marshall [mailto:robert.marshall at codethink.co.uk]
> > > Sent: Saturday, November 04, 2017 1:05 AM
> > > To: Binh Thanh. Nguyen
> > > Cc: Daniel Sangorrin; O365-Toru Oishi; Chris Paterson; Trung. Huynh;
> > > cip-dev at lists.cip-project.org
> > > Subject: Re: B at D run on Renesas board - issue
> > >
> > > "Binh Thanh. Nguyen" <binh.nguyen.uw@rvc.renesas.com> writes:
> > >
> > > > Hello Daniel, Robert,
> > > >
> > > > We are facing an issue when trying to run healthcheck using B at D on Renesas board.
> > > > I would like to attach the log and the healthcheck script (we
> > > > modified the healthcheck from Daniel)
> > > >
> > > > The boot action was passed, but after that, look like LAVA cannot
> > > > send command to Board, only send "#" (it supposed to be "uname").
> > > > I wonder if you met same issue before?
> > > > And if possible, please give us any hints you may have for debugging this issue!
> > > >
> > > > Best regards,
> > > > Binh Nguyen
> > >
> > > Thanh
> > >
> > > Sorry for the delay in responding!
> > >
> > > That test is missing a deploy section (all commented out) are you
> > > trying to make the test too minimal? LAVA tends to swallow output if
> > > it is what is expected.
> > >
> > > Robert
> >
> > As Robert said, please do not comment out the deploy section. LAVA
> > does not just deploy the binaries as they are, it also copies some scripts (LAVA Test shell) into the ramdisk (or network filesystem).
> > # LAVA does not use scp (or a serial protocol) to copy them into the
> > target
> >
> > For deploying you need a PDU (remote power switch). If you don't have
> > one you need to buy one and then add the corresponding commands.
> > # Note: I use an IP Power 9258 remote PDU.
> > # Note: do not think you can get around without a PDU*
> >
> > Thanks,
> > Daniel
> >
> > *There are ways to do it but they have limitations
> > https://validation.linaro.org/static/docs/v2/dispatcher-design.html#pr
> > imary-
> > connection
> >
> >
> >
> >
>
>
next prev parent reply other threads:[~2017-11-16 8:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 10:05 [cip-dev] B@D run on Renesas board - issue Binh Thanh. Nguyen
2017-11-03 16:04 ` Robert Marshall
2017-11-06 2:18 ` Daniel Sangorrin
2017-11-08 7:26 ` Binh Thanh. Nguyen
2017-11-15 10:21 ` Trung. Huynh
2017-11-15 13:59 ` Robert Marshall
2017-11-16 8:11 ` Daniel Sangorrin
2017-11-16 8:48 ` Trung. Huynh
2017-11-16 8:54 ` Daniel Sangorrin [this message]
2017-11-17 9:18 ` Robert Marshall
2017-11-27 10:45 ` Trung. Huynh
2017-11-30 7:53 ` Daniel Sangorrin
2017-11-30 9:09 ` Robert Marshall
2017-11-30 19:42 ` Agustin Benito Bethencourt
2017-12-05 9:09 ` Trung. Huynh
2017-12-11 6:46 ` Daniel Sangorrin
2017-12-11 9:54 ` Trung. Huynh
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='009c01d35eb8$82d1b050$887510f0$@toshiba.co.jp' \
--to=daniel.sangorrin@toshiba.co.jp \
--cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox