From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [cip-testing] Issue #167 - Build & test iw20gm kernel outside of cip-core/bitbake env
Date: Tue, 20 Mar 2018 18:50:58 +0000 [thread overview]
Message-ID: <1521571858.23626.112.camel@codethink.co.uk> (raw)
In-Reply-To: <CAEss1EK8ZXrCrtB4MxvW5FB0aqjzb7s=xyRcq0sSrx8eNrGvrA@mail.gmail.com>
On Thu, 2018-03-15 at 16:52 +0100, Zoran S wrote:
> Hello to everyone,
>
> I did some testing on this issue: 167, which appear to be a show
> stopper for Renesas iwg20m platform. I did change several times
> shmobile_defconfig in order to build better CIP 4.4.120 kernel.
> Unfortunately, every time (4 in total) I failed.
>
> Both me (testing CIP 4.4.120) and Robert (testing CIP 4.4.112) have
> problems with iwg20m ETH1000 port.
That's interesting. I've also sometimes had trouble getting a reliable
link at 1000 Mbps. When I discussed this with Robert he hadn't yet seen the problem so I though it might be cable-dependent. (We are sharing the board but have used different Ethernet cables.)
When I reconfigured my laptop's Ethernet port to only support 100 Mbps
(ethtool -s <device> speed 100 duplex full) the link became more
reliable.
> I am able to progress up to running the "starting kernel" message,
> then my tests fail (they hang).?
[...]
So u-boot starts the kernel, but you don't get any kernel log messages?
Are you certain that the device tree is loaded successfully? I don't
know whether LAVA checks for error messages from u-boot.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2018-03-20 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 15:52 [cip-dev] [cip-testing] Issue #167 - Build & test iw20gm kernel outside of cip-core/bitbake env Zoran S
2018-03-16 10:07 ` Daniel Wagner
2018-03-20 18:50 ` Ben Hutchings [this message]
2018-03-21 8:36 ` Zoran S
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=1521571858.23626.112.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.