Hi Nagendra,

I suspect the auto-login action functionality. Please try to test by avoiding auto-login functionality.

We can nail down/avoid the auto-login functionality issue like below.

Steps:
######
1. Boot the target manually and login
2. Make sure you will get login prompt
3. Run reset/reboot command
4. Check whether we will get to see the console log in the LAVA result page.

Best of luck!

Note:
1. You can use below "-boot" section

"
 - boot:
    timeout:
      minutes: 2
    method: minimal
    soft_reboot: ["reset;pwd;reset"]
    parameters:
      shutdown-message: ["< Please mention shutdown message > "]
      boot-message: [" < Please mention boot message "]
"

Regards,
Koti
On Thu, 22 Apr 2021 at 21:33, <lava-users-request@lists.lavasoftware.org> wrote:
Send Lava-users mailing list submissions to
        lava-users@lists.lavasoftware.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.lavasoftware.org/mailman/listinfo/lava-users
or, via email, send a message with subject or body 'help' to
        lava-users-request@lists.lavasoftware.org

You can reach the person managing the list at
        lava-users-owner@lists.lavasoftware.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lava-users digest..."


Today's Topics:

   1. Unable to get kernel boot messages in to lava job while using
      lava framework & telnet (Nagendra Singamsetti)
   2. Notify on finish does not hold duration (Westermann, Oliver)


----------------------------------------------------------------------

Message: 1
Date: Thu, 22 Apr 2021 17:53:31 +0530
From: Nagendra Singamsetti <nag.singam91@gmail.com>
To: lava-users@lists.lavasoftware.org
Subject: [Lava-users] Unable to get kernel boot messages in to lava
        job while using lava framework & telnet
Message-ID:
        <CAFhg_Wste+2=zO51aA3GOq-BjwbUx76rms=gF8Rv-hKNCOeQVQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi ,

I am trying to automate the linux boot functionality on my custom boards
using LAVA framework. Previously I have done it on Renesas board using LAVA
it works fine.I got linux boot messages on lava job whereas i am not
getting with customised board.

*Issue:   *I am using trace32 debugger to flash images onto the board
(working fine).  After that i am calling minimal method in pipeline job  to
get prompt strings/login
But i am not getting the linux boot messages on the job. always stucks at
the following:
[common] connect-device Connecting to device using 'telnet 10.10.0.18 4000'
<http://10.10.0.69/scheduler/job/789#L136>Setting prompt string to
['lava-test: # '] <http://10.10.0.69/scheduler/job/789#L137>end: 2.3
connect-device (duration 00:00:00) [common]
<http://10.10.0.69/scheduler/job/789#L138>end: 2 boot-trace32-image
(duration 00:00:28) [common]
<http://10.10.0.69/scheduler/job/789#action_3>start:
3 minimal-boot (timeout 00:03:00) [common]
<http://10.10.0.69/scheduler/job/789#action_3-1>start: 3.1 connect-device
(timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#L141>Already
connected <http://10.10.0.69/scheduler/job/789#L142>end: 3.1 connect-device
(duration 00:00:00) [common]
<http://10.10.0.69/scheduler/job/789#action_3-2>start: 3.2
auto-login-action (timeout 00:03:00) [common]
<http://10.10.0.69/scheduler/job/789#L144>Setting prompt string to
['Booting Linux'] <http://10.10.0.69/scheduler/job/789#L145>auto-login-action:
Wait for prompt ['Booting Linux'] (timeout 00:03:00)
<http://10.10.0.69/scheduler/job/789#L146>Trying 10.10.0.18...
<http://10.10.0.69/scheduler/job/789#L147>Connected to 10.10.0.18.
<http://10.10.0.69/scheduler/job/789#L148>Escape character is '^]'.
<http://10.10.0.69/scheduler/job/789#L149>
<http://10.10.0.69/scheduler/job/789#L150>alif_asic01 4000 [115200 N81]
<http://10.10.0.69/scheduler/job/789#L151>
<http://10.10.0.69/scheduler/job/789#L152>auto-login-action timed out after
180 seconds <http://10.10.0.69/scheduler/job/789#L153>end: 3.2
auto-login-action (duration 00:03:00) [common]

*Both telnet & serial server(ser2net) is configured.*
*Uart cable attached with serial server:
usb-Profolic_Technology_Inc._Usb-serial_Controller-ifoo-port0*

i am getting boot log messages using telnet manually but not with lava.

*Manual log with telnet:*
$ telnet 10.10.0.18 4000
Trying 10.10.0.18...
Connected to 10.10.0.18.
Escape character is '^]'.

alif_asic01 4000 [115200 N81]

Booting Linux on physical CPU 0x0
Linux version 5.4.25-00024-g9283a6810958-dirty (nishit@alif) (gcc version
9.2.0 (GCC)) #72 Tue Apr 20 15:41:31 IST 2021
#HGG1
CPU: ARMv8-a aarch32 Processor [411fd010] revision 0 (ARMv8), cr=50c5383d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
#HGG1.1
OF: fdt: Machine model: corstone700

[PFA] yaml job

thanks

Regards
Nagendra S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lavasoftware.org/pipermail/lava-users/attachments/20210422/64057c21/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sample_job.yaml
Type: application/octet-stream
Size: 383 bytes
Desc: not available
URL: <http://lists.lavasoftware.org/pipermail/lava-users/attachments/20210422/64057c21/attachment-0001.obj>

------------------------------

Message: 2
Date: Thu, 22 Apr 2021 16:03:34 +0000
From: "Westermann, Oliver" <Oliver.Westermann@cognex.com>
To: "lava-users@lists.lavasoftware.org"
        <lava-users@lists.lavasoftware.org>
Subject: [Lava-users] Notify on finish does not hold duration
Message-ID:
        <MN2PR06MB65739A1747A4848D80CF8F5986469@MN2PR06MB6573.namprd06.prod.outlook.com>

Content-Type: text/plain; charset="us-ascii"

Hey,

I'm using the 'notify by mail' option for our setup. It's setup as

criteria:
    status: finished

But when the mail is send, it seems the the job is not really finished yet, as the mail do contain timestamps for submitted and started, but not for finished. This also results in Duration being None.

Also I noticed that the "Device Details" and "Job Details" elements are empty for me.

Is this "expected" behavior or is my setup wrong?

(Using LAVA 2021.03.post1, but existed on 2021.1 as well)

Best regards, Olli



------------------------------

Subject: Digest Footer

_______________________________________________
Lava-users mailing list
Lava-users@lists.lavasoftware.org
https://lists.lavasoftware.org/mailman/listinfo/lava-users


------------------------------

End of Lava-users Digest, Vol 32, Issue 12
******************************************