All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 2/2] PCI: Only enable realloc auto when root bus has 64bit mmio
Date: Thu, 25 Sep 2014 11:49:12 -0400	[thread overview]
Message-ID: <54243978.3030501@canonical.com> (raw)
In-Reply-To: <CAE9FiQX1pfciTcuF3_eggQLCn=LvTSLTT0UZxTb+z_RaLHwgJQ@mail.gmail.com>

On 09/16/2014 06:27 PM, Yinghai Lu wrote:
> On Tue, Sep 16, 2014 at 1:21 PM, Joseph Salisbury
> <joseph.salisbury@canonical.com> wrote:
>> A new bug[0] was opened due to enabling PCI_REALLOC_ENABLE_AUTO, which
>> is similar to the original bug[1] we discussed.
>>
>> Just wondering if there have been any additional ideas on realloc since
>> this was last discussed?
>>
>> [0] http://pad.lv/1363313
>> [1] http://pad.lv/1245938
> This one looks different, that LSI card support SRIOV, but BIOS does not
> allocate resource to SRIOV bar.
> We release old resource and ...reallocate resource to them with two retries.
>
> [    0.321983] pci_bus 0000:00: max bus depth: 1 pci_try_num: 2
> [    0.322010] pci 0000:00:03.0: BAR 15: assigned [mem
> 0xef800000-0xef8fffff pref]
> [    0.322025] pci 0000:01:00.0: reg 0x174: [mem 0x00000000-0x00003fff 64bit]
> [    0.322033] pci 0000:01:00.0: reg 0x17c: [mem 0x00000000-0x0003ffff 64bit]
> [    0.322040] pci 0000:01:00.0: reg 0x174: [mem 0x00000000-0x00003fff 64bit]
> [    0.322042] pci 0000:01:00.0: BAR 6: assigned [mem
> 0xef800000-0xef87ffff pref]
> [    0.322051] pci 0000:01:00.0: reg 0x17c: [mem 0x00000000-0x0003ffff 64bit]
> [    0.322053] pci 0000:01:00.0: BAR 9: can't assign mem (size 0x400000)
> [    0.322061] pci 0000:01:00.0: reg 0x174: [mem 0x00000000-0x00003fff 64bit]
> [    0.322063] pci 0000:01:00.0: BAR 7: assigned [mem
> 0xfbd00000-0xfbd3ffff 64bit]
> [    0.322070] pci 0000:00:03.0: PCI bridge to [bus 01]
> [    0.322073] pci 0000:00:03.0:   bridge window [io  0xc000-0xcfff]
> [    0.322077] pci 0000:00:03.0:   bridge window [mem 0xfbd00000-0xfbdfffff]
> [    0.322080] pci 0000:00:03.0:   bridge window [mem
> 0xef800000-0xef8fffff pref]
> [    0.322142] pci_bus 0000:00: No. 2 try to assign unassigned res
> [    0.322143] release child resource [mem 0xfbd00000-0xfbd3ffff 64bit]
> [    0.322144] release child resource [mem 0xfbd80000-0xfbdbffff 64bit]
> [    0.322145] release child resource [mem 0xfbdfc000-0xfbdfffff 64bit]
> [    0.322147] pci 0000:00:03.0: resource 14 [mem
> 0xfbd00000-0xfbdfffff] released
> [    0.322148] pci 0000:00:03.0: PCI bridge to [bus 01]
> [    0.322156] pci 0000:00:03.0: bridge window [mem
> 0x00100000-0x001fffff] to [bus 01] add_size 500000
> [    0.322174] pci 0000:00:03.0: res[14]=[mem 0x00100000-0x001fffff]
> get_res_add_size add_size 500000
> [    0.322176] pci 0000:00:03.0: BAR 14: assigned [mem 0xefb00000-0xf00fffff]
> [    0.322185] pci 0000:01:00.0: reg 0x174: [mem 0xfbd00000-0xfbd03fff 64bit]
> [    0.322192] pci 0000:01:00.0: reg 0x17c: [mem 0x00000000-0x0003ffff 64bit]
> [    0.322194] pci 0000:01:00.0: res[9]=[mem
> 0x00000000-0xffffffffffffffff 64bit] get_res_add_size add_size 400000
> [    0.322196] pci 0000:01:00.0: res[7]=[mem
> 0x00000000-0xffffffffffffffff 64bit] get_res_add_size add_size 40000
> [    0.322198] pci 0000:01:00.0: BAR 3: assigned [mem
> 0xefb00000-0xefb3ffff 64bit]
> [    0.322211] pci 0000:01:00.0: reg 0x17c: [mem 0x00000000-0x0003ffff 64bit]
> [    0.322212] pci 0000:01:00.0: BAR 9: assigned [mem
> 0xefb40000-0xeff3ffff 64bit]
> [    0.322219] pci 0000:01:00.0: BAR 1: assigned [mem
> 0xeff40000-0xeff43fff 64bit]
> [    0.322232] pci 0000:01:00.0: reg 0x174: [mem 0xfbd00000-0xfbd03fff 64bit]
> [    0.322234] pci 0000:01:00.0: BAR 7: assigned [mem
> 0xeff44000-0xeff83fff 64bit]
> [    0.322241] pci 0000:00:03.0: PCI bridge to [bus 01]
> [    0.322244] pci 0000:00:03.0:   bridge window [io  0xc000-0xcfff]
> [    0.322248] pci 0000:00:03.0:   bridge window [mem 0xefb00000-0xf00fffff]
> [    0.322251] pci 0000:00:03.0:   bridge window [mem
> 0xef800000-0xef8fffff 64bit pref]
>
> So the resource realloc do work as expected. but LSI firmware has some
> problem again?
>
> We may need to add command after the reset the bridge resource.
>
> Can you get bootlog with "pci=earlydump"?
>
> Thanks
>
> Yinghai
Hi Yinghai,

The user collected earlydump data, which can be found here:
https://launchpadlibrarian.net/185141163/dmesg-pci%3Dearlydump

  parent reply	other threads:[~2014-09-25 15:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-08 23:54 [PATCH 0/2] PCI: Don't enable realloc automatically when above 4g 64bit mmio is not supported Yinghai Lu
2013-12-08 23:54 ` [PATCH 1/2] PCI: pcibus address to resource converting take bus instead of dev Yinghai Lu
2013-12-09 17:52   ` Bjorn Helgaas
2013-12-09 19:21     ` Yinghai Lu
2013-12-09 20:03       ` Yinghai Lu
2013-12-09 20:43         ` Greg KH
2013-12-09 20:47           ` Yinghai Lu
2013-12-09 21:06             ` Bjorn Helgaas
2013-12-08 23:54 ` [PATCH 2/2] PCI: Only enable realloc auto when root bus has 64bit mmio Yinghai Lu
2013-12-09 17:54   ` Bjorn Helgaas
2013-12-09 19:20     ` Yinghai Lu
2013-12-09 19:42       ` Bjorn Helgaas
2013-12-09 20:10         ` Yinghai Lu
2013-12-09 20:20           ` Bjorn Helgaas
2013-12-09 20:44             ` Yinghai Lu
2013-12-09 21:05               ` Bjorn Helgaas
2013-12-11 19:19           ` Joseph Salisbury
2013-12-11 19:55             ` Yinghai Lu
2014-01-08 16:38               ` Joseph Salisbury
2014-01-10 16:19               ` Joseph Salisbury
2014-01-10 17:13                 ` Yinghai Lu
2014-01-10 21:54                   ` Joseph Salisbury
2014-01-10 23:12                     ` Yinghai Lu
2014-09-16 20:21                   ` Joseph Salisbury
2014-09-16 22:27                     ` Yinghai Lu
2014-09-17  7:46                       ` Yinghai Lu
2014-09-24 23:48                         ` Bjorn Helgaas
2014-09-25 18:19                         ` Joseph Salisbury
2014-09-25 18:24                           ` Yinghai Lu
2014-09-25 15:49                       ` Joseph Salisbury [this message]
2014-09-25 16:04                         ` Bjorn Helgaas
2014-09-25 18:04                           ` Joseph Salisbury
2014-09-25 18:23                         ` Yinghai Lu

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=54243978.3030501@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=stable@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.