From: Nathan Lynch <Nathan_Lynch@mentor.com>
To: Martin Fuzzey <mfuzzey@parkeon.com>
Cc: <netdev@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>, <festevam@gmail.com>
Subject: Re: [Regression] FEC: Panic on suspend in 3.16
Date: Wed, 6 Aug 2014 10:09:25 -0500 [thread overview]
Message-ID: <53E24525.2020809@mentor.com> (raw)
In-Reply-To: <53E24147.4050304@parkeon.com>
On 08/06/2014 09:52 AM, Martin Fuzzey wrote:
> Hi all,
>
> I am using the fec ethernet driver on a i.MX53 SoC.
>
> All was working fine on 3.13 but, after upgrading to 3.16 I now get a
> panic on suspend:
Same issue reported here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-August/277728.html
a71e3c37960c (net: phy: Set the driver when registering an MDIO bus
device) has been implicated; try reverting that.
next prev parent reply other threads:[~2014-08-06 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 14:52 [Regression] FEC: Panic on suspend in 3.16 Martin Fuzzey
2014-08-06 15:09 ` Nathan Lynch [this message]
2014-08-06 15:32 ` Stefano Babic
2014-08-06 15:43 ` Nathan Lynch
2014-08-06 15:47 ` Russell King - ARM Linux
2014-08-06 15:52 ` Stefano Babic
2014-08-06 16:01 ` Fabio Estevam
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=53E24525.2020809@mentor.com \
--to=nathan_lynch@mentor.com \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mfuzzey@parkeon.com \
--cc=netdev@vger.kernel.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).