Re: BAR 14: can't assign mem (size 0x200000)

2014-04-11 Thread Parag Warudkar
e_on_node+0x190/0x190 [ 339.143061] ---[ end trace d0c4e4d8d8734d92 ]--- [ 339.143064] pci 0000:02:00.0: BAR 14: can't assign mem (size 0x20) [ 339.143066] pci :02:00.0: BAR 15: can't assign mem pref (size 0x20) [ 339.143068] pci :02:00.0: BAR 13: can't assign io (size

Re: BAR 14: can't assign mem (size 0x200000)

2014-04-10 Thread Parag Warudkar
On Thu, 10 Apr 2014, Bjorn Helgaas wrote: > On Sat, Mar 29, 2014 at 6:14 PM, Parag Warudkar wrote: > >> On Sat, Mar 29, 2014 at 09:41:20AM -0700, Linus Torvalds wrote: > > > >>> Parag, can you add a WARN_ON_ONCE() to that message, so that we see > >>> what the call chain is for it. > > Parag,

Re: BAR 14: can't assign mem (size 0x200000)

2014-04-10 Thread Bjorn Helgaas
On Sat, Mar 29, 2014 at 6:14 PM, Parag Warudkar wrote: >> On Sat, Mar 29, 2014 at 09:41:20AM -0700, Linus Torvalds wrote: > >>> Parag, can you add a WARN_ON_ONCE() to that message, so that we see >>> what the call chain is for it. Parag, did you ever try this? > ... > Not sure if Ubuntu includes

Re: BAR 14: can't assign mem (size 0x200000)

2014-03-29 Thread Parag Warudkar
On Sat, Mar 29, 2014 at 1:19 PM, Bjorn Helgaas wrote: > [+cc Rafael, linux-pci, linux-acpi] > > On Sat, Mar 29, 2014 at 09:41:20AM -0700, Linus Torvalds wrote: >> Parag, can you add a WARN_ON_ONCE() to that message, so that we see >> what the call chain is for it. > > I think we likely get a Bus

Re: BAR 14: can't assign mem (size 0x200000)

2014-03-29 Thread Bjorn Helgaas
[+cc Rafael, linux-pci, linux-acpi] On Sat, Mar 29, 2014 at 09:41:20AM -0700, Linus Torvalds wrote: > On Sat, Mar 29, 2014 at 12:11 AM, Yinghai Lu wrote: > > > > Later during resuming, kernel try to assign resource 02:00.0 but it will > > fail > > as parent bridge 00:1c.3 has no resource. > > (N

Re: BAR 14: can't assign mem (size 0x200000)

2014-03-29 Thread Linus Torvalds
On Sat, Mar 29, 2014 at 12:11 AM, Yinghai Lu wrote: > > Later during resuming, kernel try to assign resource 02:00.0 but it will fail > as parent bridge 00:1c.3 has no resource. > (Not sure how pci_configure_slot get called with this resume path). I think that last comment is the most pertinent o

Re: BAR 14: can't assign mem (size 0x200000)

2014-03-29 Thread Parag Warudkar
On Sat, Mar 29, 2014 at 3:11 AM, Yinghai Lu wrote: > > For the boot path, kernel is right. > BIOS does not assign resource for > 00:1c.0, (io, mmio, mmio pref), 00:1c.3(io, mmio, mmio pref), 00:1c.4 (io). > > but 00:1c.0 00:1c.4 support hotplug either in acpiphp or pcie slot cap. > > [0.263398

Re: BAR 14: can't assign mem (size 0x200000)

2014-03-29 Thread Yinghai Lu
no resource. (Not sure how pci_configure_slot get called with this resume path). so you will have [11548.934659] pci :02:00.0: BAR 14: can't assign mem (size 0x20) [11548.934661] pci :02:00.0: BAR 15: can't assign mem pref (size 0x20) [11548.934662] pci :02:00.0: B

Re: BAR 14: can't assign mem (size 0x200000)

2014-03-28 Thread Yinghai Lu
1548.934659] pci 0000:02:00.0: BAR 14: can't assign mem (size 0x20) > [11548.934661] pci :02:00.0: BAR 15: can't assign mem pref (size 0x20) > [11548.934662] pci :02:00.0: BAR 13: can't assign io (size 0x1000) > [11548.934664] pci :02:00.0: BAR 14: can&#x

BAR 14: can't assign mem (size 0x200000)

2014-03-28 Thread Parag Warudkar
0x0010-0x000f 64bit pref] get_res_add_size add_size 20 [11548.934656] pci :02:00.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000 [11548.934659] pci :02:00.0: BAR 14: can't assign mem (size 0x20) [11548.934661] pci :02:00.0: BAR 15: can't assign mem