From: "Allan W. Nielsen" <allan.nielsen@microsemi.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: kernel test robot <xiaolong.ye@intel.com>,
Raju Lakkaraju <Raju.Lakkaraju@microsemi.com>,
"David S. Miller" <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<lkp@01.org>
Subject: Re: [lkp] [net] af1fee9821: BUG:spinlock_trylock_failure_on_UP_on_CPU
Date: Mon, 7 Nov 2016 10:55:32 +0100 [thread overview]
Message-ID: <20161107095532.GD16599@microsemi.com> (raw)
In-Reply-To: <20161107093148.GA27001@lunn.ch>
Hi,
I'm quite surprised too.
I asked Raju to see if he can re-produce, and then try again with the
microsemi_phy disabled and see it that makes a difference.
If Raju gets stuck on this, then I will try to help our during the after-noon.
/Allan
On 07/11/16 10:31, Andrew Lunn wrote:
> EXTERNAL EMAIL
>
>
> On Mon, Nov 07, 2016 at 10:26:28AM +0800, kernel test robot wrote:
> >
> > FYI, we noticed the following commit:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> > commit af1fee98219992ba2c12441a447719652ed7e983 ("net: phy: Add support for Microsemi VSC 8530/40 Fast Ethernet PHY")
>
> Humm, interesting. I've no idea how this patch can trigger such a
> warning. The USB gadget does not have an Ethernet PHY, let alone a
> Microsemi 8530/40 Fast Ethernet PHY this patch adds.
>
> However, it seems nicely documented how to reproduce this. Allan, can
> you setup such a system? Reproduce it, then revert the change and see
> if it still happens.
>
> Andrew
next prev parent reply other threads:[~2016-11-07 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 2:26 [net] af1fee9821: BUG:spinlock_trylock_failure_on_UP_on_CPU kernel test robot
2016-11-07 2:26 ` [lkp] " kernel test robot
2016-11-07 9:31 ` Andrew Lunn
2016-11-07 9:31 ` [lkp] " Andrew Lunn
2016-11-07 9:55 ` Allan W. Nielsen [this message]
2016-11-07 13:27 ` Allan W. Nielsen
2016-11-07 17:34 ` Andrew Lunn
2016-11-07 17:34 ` [lkp] " Andrew Lunn
2016-11-08 2:01 ` Ye Xiaolong
2016-11-08 2:01 ` [lkp] " Ye Xiaolong
2016-11-08 8:11 ` Allan W. Nielsen
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=20161107095532.GD16599@microsemi.com \
--to=allan.nielsen@microsemi.com \
--cc=Raju.Lakkaraju@microsemi.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=netdev@vger.kernel.org \
--cc=xiaolong.ye@intel.com \
/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.