IRC logs for #cip for Friday, 2018-05-11

*** vidda_ has joined #cip01:39
*** iwamatsu_ has joined #cip02:55
*** patersonc has joined #cip06:50
*** wagi has joined #cip07:16
wagiIs today the kernel maintainer irc meeting?07:17
*** toscalix has joined #cip07:29
*** toscalix has quit IRC07:30
*** tpollard has joined #cip07:35
*** rajm has joined #cip07:40
szlinwagi: nope, should be yesterday.07:41
wagiszlin: right. just keep forgetting. need something like a reminder. hmm, someone should invent something like this :)07:45
*** rajm has quit IRC07:49
*** toscalix has joined #cip08:27
*** rajm has joined #cip09:07
* rajm gets a renesas healthcheck to run (email->list) - but suspects that's a lucky roll of the dice10:06
*** toscalix_ has joined #cip10:13
*** toscalix has quit IRC10:13
rajmtries with the kernel with CONFIG_DEBUG_RCAR_GEN2_SCIF0 etc and of course that fails (but doubt if it is due to that)10:16
*** toscalix_ has quit IRC10:20
szlinwagi: I've sent the meeting invitation to you11:05
*** vidda_ has quit IRC11:55
*** tpollard has quit IRC12:01
*** toscalix has joined #cip12:34
* rajm copies a test yaml to /var/www/images/kernel-ci/tests and pastes http://localhost:8010/tests/TestName.yaml into submit test in lava and is please to see it submits13:03
wagiszlin: thanks13:11
toscalixcool13:11
rajmthough having checked with both 2017-n and 2018-n the wiki statement 'Click the Submit button. You will see the following message:' appears to be untrue13:22
rajmyou get thrown straight into the job output - if the device is not online (due to the HC not having worked) this doesn't show you much13:23
rajmbut I've verified that the kernel I built with CONFIG_DEBUG_RCAR_GEN2_SCIF0 ... is capable of HC'ing13:25
rajmpatersonc: is the output from that HC ok - I've put it at https://paste.baserock.org/acunepitit or do you need one where it hangs?13:34
*** patersonc has quit IRC13:54
*** patersonc_ has joined #cip13:55
patersonc_Hi rajm13:55
patersonc_That log is good thanks. Do you have one from a case where the board didn't boot?13:55
rajmnothing appears - at least in lava in the not booting case - does the working one show all the output you expect13:56
patersonc_That log seems to be a bit of a mix of Kernel boot log and lava(?) messages? Is that right?13:58
patersonc_E.g. Waiting for the login prompt13:58
rajmyup that's correct14:00
patersonc_Okay14:02
rajmIn the failure case the 'Starting kernel ...' message is followed immediately by 'bootloader-commands timed out after 293 seconds'14:02
patersonc_Nothing from earlyprintk at all? Hmmm14:02
rajmapparently not which is why I thought a comparison within LAVA of the 2 results might be helpful14:03
patersonc_At least with the boot issues I was having there was _some_ output. I've no idea why you'd see nothing!14:05
rajmyes I was assuming LAVA was swallowing it but from the working output it would appear not14:05
patersonc_Have you ever tested the board when not using LAVA?14:06
rajmI'm trying to get it to run with that kernel but am getting 'Bad Linux ARM zImage magic!' maybe I'm missing something in the u-boot sequence, when booting with the installed OS it appears to always work14:09
patersonc_What are you trying to boot over? SD? TFTP/NFS?14:22
rajmtftp14:23
rajmsetting i've used are here https://paste.baserock.org/tabewanipo14:24
patersonc_Do you need to provide an addr location for the zImage as well? (for tftpboot)14:27
patersonc_For uImage I use: tftpboot 0x40007fc0 RZ-G1M/boot/uImage; tftpboot 0x40f00000 RZ-G1M/boot/dtb; bootm 0x40007fc0 - 0x40f0000014:28
rajmjust a mo'....14:28
rajmah! unless the kernel panic I've just got is due to a PEBCAK , I'll pastebin it14:37
rajmKernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)14:40
rajmhttps://paste.baserock.org/avuzesedaf14:40
patersonc_What bootargs are you using?14:46
rajmI copied yours bootz 0x40007fc0 - 0x40f0000014:46
patersonc_Kernel bootargs14:50
patersonc_Oh just seen it, Kernel command line: console=ttySC014:50
patersonc_You need to specify root=14:51
patersonc_Or it doesn't know where to find the RFS14:51
rajmthanks ok14:52
patersonc_For NFS I use: console=ttySC0,115200n8 ignore_loglevel vmalloc=384M rw root=/dev/nfs nfsroot=192.168.1.30:/tftpboot/RZ-G1M ip=192.168.1.33:::::eth0 earlyprintk=serial,ttySC0,115200n814:54
rajmI used bootz 0x40007fc0 - 0x40f00000 earlyprintk=serial,ttySC0,115200n8 console=ttySC0,115200n8 ignore_loglevel vmalloc=384M root=/dev/mmc14:59
rajmblk2p2 copying from printenv settings and still get the panic14:59
patersonc_I believe bootz should be on a different command. I.e...15:05
patersonc_setenv bootargs 'earlyprintk=serial,ttySC0,115200n8 console=ttySC0,115200n8 ignore_loglevel vmalloc=384M root=/dev/mmc'15:05
patersonc_setenv bootcmd 'tftpboot 0x40007fc0 RZ-G1M/boot/uImage; tftpboot 0x40f00000 RZ-G1M/boot/dtb; bootm 0x40007fc0 - 0x40f00000'15:05
patersonc_You can see your Kernel args aren't getting passed to the Kernel by this line in your log:15:06
patersonc_Kernel command line: console=ttySC015:06
patersonc_rajm: I'm afraid I have to leave the office now, and I'm away next week :( I'll try and keep an eye on emails in case you get stuck.15:07
rajmOK thanks - have a good week!15:07
patersonc_Thanks!15:08
*** patersonc_ has quit IRC15:17
rajmI made bootargs setenv bootargs 'earlyprintk=serial,ttySC0,115200n8 console=ttySC0,115200n8 ignore_loglevel vmalloc=384M root=/dev/mmcblk2p2 rootwait rootfstype=ext3 rw'15:26
rajmand it's now hanging at waiting for root device15:26
rajmoutput is now at https://paste.baserock.org/ikavamusek15:43
*** toscalix has quit IRC15:56
* rajm has merged https://gitlab.com/cip-project/cip-testing/board-at-desk-single-dev/merge_requests/59 thanks bwh 16:36
*** rajm has quit IRC16:43

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!