public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@linux.intel.com>
To: Alex Williamson <alex.williamson@redhat.com>,
	Joerg Roedeljoro <joro@8bytes.org>
Cc: 范冬冬 <fandd@inspur.com>, 刘长生 <liuchangsheng@inspur.com>,
	iommu <iommu@lists.linux-foundation.org>,
	"jiang.liu@intel.com" <jiang.liu@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	闫晓峰 <yanxiaofeng@inspur.com>, "Roland Dreier" <roland@kernel.org>
Subject: Re: Panic when cpu hot-remove
Date: Thu, 18 Jun 2015 13:40:13 +0800	[thread overview]
Message-ID: <558259BD.7080402@linux.intel.com> (raw)
In-Reply-To: <1434551800.5628.5.camel@redhat.com>

On 2015/6/17 22:36, Alex Williamson wrote:
> On Wed, 2015-06-17 at 13:52 +0200, Joerg Roedeljoro wrote:
>> On Wed, Jun 17, 2015 at 10:42:49AM +0000, 范冬冬 wrote:
>>> Hi maintainer,
>>>
>>> We found a problem that a panic happen when cpu was hot-removed. We also trace the problem according to the calltrace information.
>>> An endless loop happen because value head is not equal to value tail forever in the function qi_check_fault( ).
>>> The location code is as follows:
>>>
>>>
>>> do {
>>>         if (qi->desc_status[head] == QI_IN_USE)
>>>         qi->desc_status[head] = QI_ABORT;
>>>         head = (head - 2 + QI_LENGTH) % QI_LENGTH;
>>>     } while (head != tail);
>>
>> Hmm, this code interates only over every second QI descriptor, and tail
>> probably points to a descriptor that is not iterated over.
>>
>> Jiang, can you please have a look?
> 
> I think that part is normal, the way we use the queue is to always
> submit a work operation followed by a wait operation so that we can
> determine the work operation is complete.  That's done via
> qi_submit_sync().  We have had spurious reports of the queue getting
> impossibly out of sync though.  I saw one that was somehow linked to the
> I/O AT DMA engine.  Roland Dreier saw something similar[1].  I'm not
> sure if they're related to this, but maybe worth comparing.  Thanks,
Thanks, Alex and Joerg!

Hi Dongdong,
	Could you please help to give some instructions about how to
reproduce this issue? I will try to reproduce it if possible.
Thanks!
Gerry

> 
> Alex
> 
> [1] http://lists.linuxfoundation.org/pipermail/iommu/2015-January/011502.html
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

  reply	other threads:[~2015-06-18  5:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 10:42 Panic when cpu hot-remove 范冬冬
2015-06-17 11:52 ` Joerg Roedeljoro
2015-06-17 14:36   ` Alex Williamson
2015-06-18  5:40     ` Jiang Liu [this message]
     [not found]       ` <558272E3.4000504@inspur.com>
2015-06-18  7:54         ` fandongdong
2015-06-25  8:11           ` Jiang Liu
2015-06-25 10:46             ` fandongdong
2015-11-09 20:21             ` Guenter Roeck

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=558259BD.7080402@linux.intel.com \
    --to=jiang.liu@linux.intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=fandd@inspur.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jiang.liu@intel.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuchangsheng@inspur.com \
    --cc=roland@kernel.org \
    --cc=yanxiaofeng@inspur.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