netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyler Baker <tyler.baker@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "David S. Miller" <davem@davemloft.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Fugang Duan <B38611@freescale.com>,
	"Kevin's boot bot" <khilman@kernel.org>,
	Olof Johansson <olof@lixom.net>, netdev <netdev@vger.kernel.org>,
	Shawn Guo <shawn.guo@linaro.org>
Subject: re: net: fec: Ensure clocks are enabled while using mdio bus
Date: Fri, 10 Jul 2015 12:07:29 -0700	[thread overview]
Message-ID: <CANMBJr7XML6v5_75LmD7ARMHaAJo9YBodv13jCcdN2mL7Vu0ZQ@mail.gmail.com> (raw)

Hi Andrew,

The kernelci.org system reported[1][2][3] new imx6 boot failures in
next-20150710. I've bisected[4] these failures to 6c3e921b18ed "net:
fec: Ensure clocks are enabled while using mdio bus". Reverting this
commit on top of next-20150710, resolves the boot failures. I have not
investigated any further, but did add the imx maintainer to the CC
list. Apologies in advanced for not replying to the original thread,
as I was not subscribed to the netdev list until now.

Any chance you can confirm this regression on your end?

Cheers,

Tyler

[1] http://kernelci.org/boot/all/job/next/kernel/next-20150710/
[2] http://storage.kernelci.org/next/next-20150710/arm-multi_v7_defconfig/lab-collabora/boot-imx6q-sabrelite.html
[3] http://storage.kernelci.org/next/next-20150710/arm-imx_v6_v7_defconfig/lab-tbaker/boot-imx6q-cm-fx6.html
[4] http://hastebin.com/uzofovupey.pas

             reply	other threads:[~2015-07-10 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 19:07 Tyler Baker [this message]
2015-07-13  7:40 ` net: fec: Ensure clocks are enabled while using mdio bus Shawn Guo

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=CANMBJr7XML6v5_75LmD7ARMHaAJo9YBodv13jCcdN2mL7Vu0ZQ@mail.gmail.com \
    --to=tyler.baker@linaro.org \
    --cc=B38611@freescale.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=khilman@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=shawn.guo@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).