On Tue, Oct 29, 2024 at 10:41 AM Sweta Ghosh sweta.ghosh@nagarro.com wrote:
The whole welcome is of 27 lines but for trouble shooting i have reduced it to only 1 line in /etc/issue in test image with which I am currently testing: System Info:
The actual welcome messages will look like this: |_ _ / __ \ / ____| | | | | | | (___ | | | | | |___ \ _| | | |__| |____) | |_____ ____/|_____/
System Info: Version.....: Debian OS Type......: Linux
Interfaces: eth0.......:192.168.1.10
Instruction:
- welcome to console
- login with user and password
Alternative :
- Make sure network interface is up of eth0 network
- Open a browser and type "http://192.168.1.10"
You are currently connected via:ttyS0 (115200)
device-mgmt login:
Output of /etc/issue
|_ _ / __ \ / ____| | | | | | | (___ | | | | | |___ \ _| | | |__| |____) | |_____ ____/|_____/ System : Version.....: \S{VALUE} Type......: \S{NAME} Interfaces: abc : \e{green}\4{interface}\e{reset} Instruction:
- welcome to console
- login with user and password
\e{darkgray}Alternative :
- Make sure network interface is up of \4{interface}'s network
- Open a browser and type "http://%5C4%7Binterface%7D%22%5Ce%7Breset%7D
You are currently connected via: \l (\b)
The only suspect there is "login", but I don't think this is an issue. You mentioned that you reduced it to one line just for testing and it still fails. This is interesting. Let's see if the problem doesn't start earlier than that. First "prompt" LAVA is looking for is loading kernel. Example here: https://lava.infra.foundries.io/scheduler/job/54785#L565
auto-login-action: Wait for prompt ['Linux version [0-9]'] (timeout 00:08:00)
Do you have this in your log?
Then you should also see the list of prompts that LAVA is looking for: https://lava.infra.foundries.io/scheduler/job/54785#L713
['-\[ cut here \]', 'Unhandled fault', 'BUG: KCSAN:', 'BUG: KASAN:', 'BUG: KFENCE:', 'Oops(?: -|:)', 'WARNING:', '(kernel BUG at|BUG:)', 'invalid opcode:', 'Kernel panic - not syncing', 'fio@am62xx-evm', 'Password:', 'root@am62xx-evm', 'login:', 'Login incorrect']
Do you have these in your log?
Best Regards, Milosz