From: Oliver Neukum <oneukum@suse.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
LKML <linux-kernel@vger.kernel.org>,
'LinuxSamsung SOC' <linux-samsung-soc@vger.kernel.org>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
netdev@vger.kernel.org
Cc: Dean Jenkins <Dean_Jenkins@mentor.com>
Subject: Re: inconsistent lock state with usbnet/asix usb ethernet and xhci
Date: Tue, 27 Feb 2018 11:37:50 +0100 [thread overview]
Message-ID: <1519727870.18525.4.camel@suse.com> (raw)
In-Reply-To: <c15c90ef-ce1b-4dd7-1d9f-673deb01b6d2@samsung.com>
Am Dienstag, den 27.02.2018, 08:26 +0100 schrieb Marek Szyprowski:
Hi,
> I've noticed that USBnet/ASIX AX88772B USB driver produces deplock kernel
> warning ("inconsistent lock state") on Chromebook2 Peach-PIT board. No
Is that 32 bit?
> special activity is needed to reproduce this issue, it happens almost
> on every boot. ASIX USB ethernet is connected to XHCI USB host controller
> on that board. Is it a known issue? Frankly I have no idea where to look
No, it is not known.
> to fix it. The same adapter connected to EHCI ports on other boards based
> on the same SoC works fine without any warnings.
Odd.
> And the log with mentioned warning:
>
> [ 17.768040] ================================
> [ 17.772239] WARNING: inconsistent lock state
> [ 17.776511] 4.16.0-rc3-next-20180227-00007-g876c53a7493c #453 Not tainted
> [ 17.783329] --------------------------------
> [ 17.787580] inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage.
> [ 17.793607] swapper/0/0 [HC0[0]:SC1[1]:HE1:SE0] takes:
> [ 17.798751] (&syncp->seq#5){?.-.}, at: [<9b22e5f0>]
> asix_rx_fixup_internal+0x188/0x288
Looks like this triggers (in usbnet):
u64_stats_update_begin(&stats64->syncp);
stats64->rx_packets++;
stats64->rx_bytes += skb->len;
u64_stats_update_end(&stats64->syncp);
That I considered to be called under lock.
Could you comment this out for testing?
Regards
Oliver
next prev parent reply other threads:[~2018-02-27 10:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180227072602eucas1p28dcdba711b3153820bd409d838cc63bd@eucas1p2.samsung.com>
2018-02-27 7:26 ` inconsistent lock state with usbnet/asix usb ethernet and xhci Marek Szyprowski
2018-02-27 10:37 ` Oliver Neukum [this message]
2018-02-27 10:59 ` Marek Szyprowski
2018-02-27 14:07 ` Eric Dumazet
2018-02-27 14:07 ` Eric Dumazet
2018-02-27 14:42 ` Marek Szyprowski
2018-02-27 14:42 ` Marek Szyprowski
2018-02-27 15:09 ` Eric Dumazet
2018-02-27 15:09 ` Eric Dumazet
2018-02-27 15:13 ` Eric Dumazet
2018-02-27 15:13 ` Eric Dumazet
2018-02-27 16:07 ` Oliver Neukum
2018-02-27 16:07 ` Oliver Neukum
2018-03-05 7:45 ` Marek Szyprowski
2018-03-05 7:45 ` Marek Szyprowski
2018-03-05 11:46 ` Oliver Neukum
2018-03-05 11:46 ` Oliver Neukum
2018-03-05 19:09 ` Eric Dumazet
2018-03-05 19:09 ` Eric Dumazet
2018-03-05 19:41 [net] net: usbnet: fix potential deadlock on 32bit hosts Eric Dumazet
2018-03-05 19:41 ` [PATCH net] " Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2018-03-07 16:47 [net] " David Miller
2018-03-07 16:47 ` [PATCH net] " David Miller
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=1519727870.18525.4.camel@suse.com \
--to=oneukum@suse.com \
--cc=Dean_Jenkins@mentor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.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 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.