lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQXmO_sSCnd-0NvXKmyeLP0m4XGRRkAgqSiMkfeTcvXs+A@mail.gmail.com>
Date:	Fri, 28 Mar 2014 18:16:49 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Parag Warudkar <parag.lkml@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: BAR 14: can't assign mem (size 0x200000)

On Fri, Mar 28, 2014 at 5:40 PM, Parag Warudkar <parag.lkml@...il.com> wrote:
> No issues with fresh boot, however after resume from suspend I see
> these messages -
>
> [11548.934625] pci_bus 0000:03: Allocating resources
> [11548.934645] pci 0000:02:00.0: bridge window [io  0x1000-0x0fff] to
> [bus 03] add_size 1000
> [11548.934648] pci 0000:02:00.0: bridge window [mem
> 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
> [11548.934650] pci 0000:02:00.0: bridge window [mem
> 0x00100000-0x000fffff] to [bus 03] add_size 200000
> [11548.934653] pci 0000:02:00.0: res[14]=[mem 0x00100000-0x000fffff]
> get_res_add_size add_size 200000
> [11548.934655] pci 0000:02:00.0: res[15]=[mem 0x00100000-0x000fffff
> 64bit pref] get_res_add_size add_size 200000
> [11548.934656] pci 0000:02:00.0: res[13]=[io  0x1000-0x0fff]
> get_res_add_size add_size 1000
> [11548.934659] pci 0000:02:00.0: BAR 14: can't assign mem (size 0x200000)
> [11548.934661] pci 0000:02:00.0: BAR 15: can't assign mem pref (size 0x200000)
> [11548.934662] pci 0000:02:00.0: BAR 13: can't assign io (size 0x1000)
> [11548.934664] pci 0000:02:00.0: BAR 14: can't assign mem (size 0x200000)
> [11548.934666] pci 0000:02:00.0: BAR 15: can't assign mem pref (size 0x200000)
> [11548.934667] pci 0000:02:00.0: BAR 13: can't assign io (size 0x1000)
> [11548.934669] pci 0000:02:00.0: PCI bridge to [bus 03]
> [11548.934697] pci 0000:02:00.0: no hotplug settings from platform
> [11548.934698] pci 0000:02:00.0: using default PCI settings
>

>
> I am running Ubuntu daily mainline build from couple days ago - I
> think it should include the above commit.
>
> Let me know if more info is needed - I don't see any issues because of
> these but that may be because I am not using VTd for anything.

Can you send out whole boot log (include init booting and from resume) and
lspci -tv and lspci -vvxxxx ?

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ