linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@linux.vnet.ibm.com>
To: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org,
	"nfont >> Nathan Fontenot" <nfont@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: WARN @lib/refcount.c:128 during hot unplug of I/O adapter.
Date: Fri, 7 Apr 2017 10:08:23 +0530	[thread overview]
Message-ID: <D5BDC786-03CF-423C-AFD6-2F8679F465C8@linux.vnet.ibm.com> (raw)
In-Reply-To: <a7a782f2-3783-fd96-eda9-1c7634b2a2e5@linux.vnet.ibm.com>


> On 07-Apr-2017, at 2:14 AM, Tyrel Datwyler <tyreld@linux.vnet.ibm.com> =
wrote:
>=20
> On 04/06/2017 03:27 AM, Sachin Sant wrote:
>> On a POWER8 LPAR running 4.11.0-rc5, a hot unplug operation on
>> any I/O adapter results in the following warning
>=20
> I remember you mentioning this when the issue was brought up for CPUs. =
I
> assume the case is the same here where the issue is only seen with
> adapters that were hot-added after boot (ie. hot-remove of adapter
> present at boot doesn't trip the warning)?
>=20

Correct, can be recreated only with adapters that were hot-added after =
boot.

> -Tyrel
>=20
>>=20
>> Thanks
>> -Sachin
>>=20
>>=20
>=20

      parent reply	other threads:[~2017-04-07  4:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 10:27 WARN @lib/refcount.c:128 during hot unplug of I/O adapter Sachin Sant
2017-04-06 20:44 ` Tyrel Datwyler
2017-04-07  4:04   ` Michael Ellerman
2017-04-10 17:53     ` Tyrel Datwyler
2017-04-11  9:00       ` Michael Ellerman
2017-04-11 17:14         ` Tyrel Datwyler
2017-04-12  2:10           ` Michael Ellerman
2017-04-12 19:41             ` Tyrel Datwyler
2017-04-07  4:38   ` Sachin Sant [this message]

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=D5BDC786-03CF-423C-AFD6-2F8679F465C8@linux.vnet.ibm.com \
    --to=sachinp@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=tyreld@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).