[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161107093148.GA27001@lunn.ch>
Date: Mon, 7 Nov 2016 10:31:48 +0100
From: Andrew Lunn <andrew@...n.ch>
To: kernel test robot <xiaolong.ye@...el.com>
Cc: Raju Lakkaraju <Raju.Lakkaraju@...rosemi.com>,
"David S. Miller" <davem@...emloft.net>,
"Allan W. Nielsen" <allan.nielsen@...rosemi.com>,
LKML <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org,
lkp@...org
Subject: Re: [lkp] [net] af1fee9821:
BUG:spinlock_trylock_failure_on_UP_on_CPU
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
Powered by blists - more mailing lists