Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1515942 > unrolled thread

Re: [lkp] [net] af1fee9821: BUG:spinlock_trylock_failure_on_UP_on_CPU

Started byAndrew Lunn <andrew@lunn.ch>
First post2016-11-07 10:40 +0100
Last post2016-11-08 03:10 +0100
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [lkp] [net]  af1fee9821:  BUG:spinlock_trylock_failure_on_UP_on_CPU Andrew Lunn <andrew@lunn.ch> - 2016-11-07 10:40 +0100
    Re: [lkp] [net]  af1fee9821:  BUG:spinlock_trylock_failure_on_UP_on_CPU Andrew Lunn <andrew@lunn.ch> - 2016-11-07 18:40 +0100
    Re: [lkp] [net]  af1fee9821:  BUG:spinlock_trylock_failure_on_UP_on_CPU Ye Xiaolong <xiaolong.ye@intel.com> - 2016-11-08 03:10 +0100

#1515942 — Re: [lkp] [net] af1fee9821: BUG:spinlock_trylock_failure_on_UP_on_CPU

FromAndrew Lunn <andrew@lunn.ch>
Date2016-11-07 10:40 +0100
SubjectRe: [lkp] [net] af1fee9821: BUG:spinlock_trylock_failure_on_UP_on_CPU
Message-ID<sAOzf-1fr-1@gated-at.bofh.it>
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

[toc] | [next] | [standalone]


#1516368

FromAndrew Lunn <andrew@lunn.ch>
Date2016-11-07 18:40 +0100
Message-ID<sAW3M-6lw-35@gated-at.bofh.it>
In reply to#1515942
On Mon, Nov 07, 2016 at 02:27:14PM +0100, Allan W. Nielsen wrote:
> Hi,
> 
> I tried to get this "lkp" up and running, but I had some troubles gettting
> these scripts to work.
> 
> But it seems like it can be reproduced using th eprovided config file, and qemu.
> 
> Here is what I did:
> 
> # reproduce original bug
> git reset --hard af1fee98219992ba2c12441a447719652ed7e983
> mkdir bug-build
> cp config-4.8.0-14895-gaf1fee9 bug-build/.config
> make O=bug-build oldconfig
> make O=bug-build -j8
> qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -m 4G -kernel \
>     ../net-next/bug-build/arch/x86_64/boot/bzImage -nographic
> <see-output-1-below>
> # bug seemed to be re-produced
> 
> 
> # Try previous version
> git reset --hard 32ab0a38f0bd554cc45203ff4fdb6b0fdea6f025
> make O=bug-build oldconfig
> make O=bug-build -j8
> qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -m 4G -kernel \
>     ../net-next/bug-build/arch/x86_64/boot/bzImage -nographic
> <see-output-2-below>
> # bug seemed to disappear
> 
> 
> # Try the buggy revision again - but without MICROSEMI_PHY
> git reset --hard af1fee98219992ba2c12441a447719652ed7e983
> sed -e "/MICROSEMI_PHY/d" -i bug-build/.config
> make O=bug-build oldconfig
> cat bug-build/.config | grep MICROSEMI_PHY
> qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -m 4G -kernel \
>     ../net-next/bug-build/arch/x86_64/boot/bzImage -nographic
> <see-output-3-below>
> # bug still seem to be there...
> 
> 
> Not sure what this tells me, any hints are more than welcome.

If the bug happens without your code being compiled, it cannot be your
code. It suggests the patch is moving code around in such a way to
trigger the issue, but it is not the source of the issue itself. To me
it seems like memory corruption or uninitialised variables in some
other code, or maybe DMA from the stack, which was never allowed but
mostly work on some platforms, but the recent change to virtual mapped
stacks as broken.

Your code is off the hook, thanks for the testing you did.

     Andrew

[toc] | [prev] | [next] | [standalone]


#1516734

FromYe Xiaolong <xiaolong.ye@intel.com>
Date2016-11-08 03:10 +0100
Message-ID<sB41j-366-13@gated-at.bofh.it>
In reply to#1515942
On 11/07, Allan W. Nielsen wrote:
>Hi,
>
>I tried to get this "lkp" up and running, but I had some troubles gettting
>these scripts to work.

Hi, Allan

Could you tell us what troubles you have met when trying the "lkp qemu"
tool, it would be better if you could paste some log so we can help to
improve it.

Thanks,
Xiaolong

>
>But it seems like it can be reproduced using th eprovided config file, and qemu.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web