All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yijing Wang <wangyijing@huawei.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	PCI <linux-pci@vger.kernel.org>,
	"Herui (Ray)" <Ray.herui@huawei.com>
Subject: Re: Assign mem resource fail after remove and rescan
Date: Thu, 2 Apr 2015 16:35:59 +0800	[thread overview]
Message-ID: <551CFF6F.8050000@huawei.com> (raw)
In-Reply-To: <CAE9FiQUQ_Kz8sNzu9RmOfoe4xEwfZ3atGcfQ39UAp4dRz2rRFA@mail.gmail.com>

On 2015/4/2 6:21, Yinghai Lu wrote:
> On Mon, Mar 30, 2015 at 11:38 PM, Yijing Wang <wangyijing@huawei.com> wrote:
>> On 2015/3/29 14:18, Yinghai Lu wrote:
>>> On Sat, Mar 28, 2015 at 3:02 AM, Yijing Wang <wangyijing@huawei.com> wrote:
>>>> ...
>>>>
>>>> I compared above log and found after we did remove and rescan, the bridge requested resource size extended to 0x06000000,
>>>> and when system boot up, it requested only 0x4800000.
>>>>
>>    I tested it, remove and rescan 05:19.0 device is ok now, but
>> if do the operations for the parent device of 05:19.0, the result is
>> still fail.
> 
> Found the problem, attached patch should fix the problem.

Thanks, will test soon.

> 
> Thanks
> 
> Yinghai
> 


-- 
Thanks!
Yijing


  reply	other threads:[~2015-04-02  8:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28 10:02 Assign mem resource fail after remove and rescan Yijing Wang
2015-03-29  6:18 ` Yinghai Lu
2015-03-30  4:05   ` Yijing Wang
2015-03-31  6:38   ` Yijing Wang
2015-04-01 22:21     ` Yinghai Lu
2015-04-02  8:35       ` Yijing Wang [this message]
2015-04-09 11:12       ` Yijing Wang
2015-05-05 19:07       ` Bjorn Helgaas
2015-06-25  1:59         ` Yijing Wang
2015-06-25  7:05           ` Yinghai Lu
2015-06-25  7:25             ` Yijing Wang

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=551CFF6F.8050000@huawei.com \
    --to=wangyijing@huawei.com \
    --cc=Ray.herui@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=yinghai@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.