From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Doug Ledford' <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: Bug Report: possible circular locking issue
Date: Mon, 28 Aug 2017 14:44:07 -0500 [thread overview]
Message-ID: <158601d32036$02e2b0d0$08a81270$@opengridcomputing.com> (raw)
In-Reply-To: <1503948482.78641.110.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > > > I ran across this while testing a 4.13-rc7 kernel + the rdma next
> > > > code.
> > >
> > > This reproduces on a stock 4.13-rc7 kernel. But, across all the
> > > stuff
> > > I've booted it on so far, it only shows up on cxgb4 devices, so I
> > > think
> > > this is a cxgb4 specific issue. Steve, can you look into this?
> >
> > Hey Doug. Yes. Is this a regression that shows up now in 4.13-rc
> > but worked in older kernels?
>
> I think so. But I don't update this particular machine every release
> (mainly because it's a contested machine with a unique setup, and the
> last couple kernel releases it's been tied up with rhel testing instead
> of my own, but prior to the last couple kernels I don't recall this
> issue existing).
Do you have other systems that run cxgb4 and do not exhibit this lockdep issue?
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-28 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 16:38 Bug Report: possible circular locking issue Doug Ledford
[not found] ` <1503938316.78641.98.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-28 19:12 ` Doug Ledford
[not found] ` <1503947529.78641.108.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-28 19:18 ` Steve Wise
2017-08-28 19:28 ` Doug Ledford
[not found] ` <1503948482.78641.110.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-28 19:44 ` Steve Wise [this message]
2017-08-28 20:03 ` Doug Ledford
2017-08-31 15:24 ` Potnuri Bharat Teja
[not found] ` <20170831152430.GA15173-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2017-09-05 11:40 ` Potnuri Bharat Teja
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='158601d32036$02e2b0d0$08a81270$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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