From: peppe.cavallaro@st•com (Giuseppe CAVALLARO)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 0/8] arm64: rockchip: Initial GeekBox enablement
Date: Wed, 9 Mar 2016 10:52:19 +0100 [thread overview]
Message-ID: <56DFF253.9050208@st.com> (raw)
In-Reply-To: <CAAObsKBr9SXg1-wr9O-ypR8JozdGpeAwfDLMeUKi8ozxkKyTXg@mail.gmail.com>
On 3/9/2016 10:42 AM, Tomeu Vizoso wrote:
> On 9 March 2016 at 10:00, Giuseppe CAVALLARO <peppe.cavallaro@st•com> wrote:
>> On 3/9/2016 9:56 AM, Giuseppe CAVALLARO wrote:
>>>
>>> Hello
>>>
>>> On 3/9/2016 9:35 AM, Tomeu Vizoso wrote:
>>>>
>>>>
>>>> in order to get the onboard network on the Radxa Rock2 to work at all
>>>> on today's linux-next, I had to revert both commits:
>>>>
>>>> * "stmmac: Fix 'eth0: No PHY found' regression" for the drivers to
>>>> probe and the link to come up, and
>>>
>>>
>>> I've just sent two patches (on top of net.git) to fix this problem
>>> pls let me know if these help on your side too.
>>>
>>>>
>>>> * "stmmac: first frame prep at the end of the xmit routine" for the
>>>> network interface to work at all.
>>>
>>>
>>> I cannot reproduce it right now but I am looking at this again and let
>>> you know.
>>> I will check your output file too
>>
>>
>> hmm, I think that the problem is around the "normal descriptor"
>> management that is configured on the boxes where the driver is
>> failing now. Using enhanced descriptors the network is ok.
>> I will keep you up-to-date.
>
> Hi,
>
> I have done some tests and these are the results:
>
> * net.git (133800d1f028): probe failed
ok, failure due to the "stmmac: Fix 'eth0: No PHY found' regression"
>
> * net.git (133800d1f028) + revert: everything fine
ok that is expected but the fixed-link will be NOK
>
> * net.git (133800d1f028) + revert + "stmmac: fix MDIO settings": everything fine
thx for having tested it. So it works on real transceiver (tested by
you) and with the fixed-link (tested by me).
>
> * today's linux-next: probe failed
>
> * today's linux-next + revert of 88f8b1bb41c6 stmmac: Fix 'eth0: No
> PHY found' regression: probe succeeded but no network at all
>
> * today's linux-next + revert of 88f8b1bb41c6 (stmmac: Fix 'eth0: No
> PHY found' regression) + revert of 0e80bdc9a72d (stmmac: first frame
> prep at the end of xmit routine): probe succeeded, dhcp succeeds and
> nfsroot works for a few seconds before timing out
ok, I was looking at this problem now that seems to related
the "stmmac: first frame prep at the end of xmit routine"
that, at first glance, is breaking the gmac 3.50 with normal descriptor.
> Btw, could you CC LKML on future patches that need testing?
sure
peppe
>
> Thanks,
>
> Tomeu
>
>> peppe
>>
>>
>>>
>>> Regards
>>> peppe
>>>
>>>
>>>> But a few seconds into the nfsroot boot I start getting:
>>>>
>>>> [ 9.136701] systemd[1]: Started Load Kernel Modules.
>>>> [ 18.116321] nfs: server 10.42.0.1 not responding, still trying
>>>> [ 18.516224] ------------[ cut here ]------------
>>>> [ 18.521024] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:303
>>>> dev_watchdog+0x284/0x288
>>>> [ 18.529456] NETDEV WATCHDOG: eth0 (rk_gmac-dwmac): transmit queue 0
>>>> timed out
>>>>
>>>> I'm attaching the full boot log.
>>>>
>>>> Regards,
>>>>
>>>> Tomeu
>>>>
>>>
>>>
>>
>
>
next prev parent reply other threads:[~2016-03-09 9:52 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1457294038-14243-1-git-send-email-afaerber@suse.de>
2016-03-06 19:53 ` [PATCH v3 2/8] Documentation: devicetree: rockchip: Document GeekBox Andreas Färber
2016-03-06 19:53 ` [PATCH v3 3/8] arm64: dts: rockchip: Add GeekBox config Andreas Färber
2016-03-06 19:53 ` [PATCH v3 5/8] arm64: dts: rockchip: Clean up gpio-keys nodes Andreas Färber
2016-03-06 19:53 ` [PATCH v3 6/8] arm64: dts: rockchip: Add power key to GeekBox Andreas Färber
2016-03-10 23:04 ` Julien Chauveau
2016-03-16 10:58 ` Andreas Färber
2016-03-16 13:52 ` Andreas Färber
2016-03-10 23:09 ` Julien Chauveau
2016-03-06 19:53 ` [PATCH v3 7/8] Documentation: devicetree: rockchip: Document Landingship Andreas Färber
2016-03-17 14:46 ` Rob Herring
2016-03-06 19:53 ` [PATCH v3 8/8] arm64: dts: rockchip: Add Landingship config Andreas Färber
2016-03-07 12:17 ` [PATCH v3 0/8] arm64: rockchip: Initial GeekBox enablement Andreas Färber
2016-03-07 12:24 ` Heiko Stübner
2016-03-07 12:35 ` Andreas Färber
2016-03-07 13:26 ` Giuseppe CAVALLARO
2016-03-07 14:27 ` Andreas Färber
2016-03-07 15:09 ` Giuseppe CAVALLARO
2016-03-07 15:46 ` Andreas Färber
2016-03-07 15:52 ` Giuseppe CAVALLARO
2016-03-07 17:15 ` Andreas Färber
2016-03-07 23:22 ` Dinh Nguyen
2016-03-08 7:24 ` Giuseppe CAVALLARO
2016-03-08 15:45 ` Dinh Nguyen
2016-03-09 7:24 ` Giuseppe CAVALLARO
2016-03-09 8:35 ` Tomeu Vizoso
2016-03-09 8:56 ` Giuseppe CAVALLARO
2016-03-09 9:00 ` Giuseppe CAVALLARO
2016-03-09 9:42 ` Tomeu Vizoso
2016-03-09 9:52 ` Giuseppe CAVALLARO [this message]
2016-03-09 10:27 ` Giuseppe CAVALLARO
2016-03-09 10:53 ` Tomeu Vizoso
2016-03-09 14:31 ` Giuseppe CAVALLARO
2016-03-09 14:53 ` Giuseppe CAVALLARO
2016-03-09 16:31 ` Dinh Nguyen
2016-03-10 9:13 ` Giuseppe CAVALLARO
2016-03-10 16:47 ` Dinh Nguyen
2016-03-11 9:09 ` Giuseppe CAVALLARO
2016-03-14 11:43 ` Tomeu Vizoso
2016-03-14 16:20 ` Giuseppe CAVALLARO
2016-03-15 7:23 ` Tomeu Vizoso
2016-03-15 12:36 ` Giuseppe CAVALLARO
2016-03-30 16:44 ` Dinh Nguyen
2016-03-31 7:53 ` Giuseppe CAVALLARO
2016-03-08 10:03 ` Gabriel Fernandez
2016-03-08 10:24 ` Giuseppe CAVALLARO
2016-03-08 10:33 ` Gabriel Fernandez
2016-03-11 12:12 ` Michael Trimarchi
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=56DFF253.9050208@st.com \
--to=peppe.cavallaro@st$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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