On Thu, Jan 09, 2020 at 03:55:17PM -0600, Bjorn Helgaas wrote: > On Thu, Jan 09, 2020 at 06:31:57PM +0800, Yicong Yang wrote: > > On 2020/1/9 12:27, Bjorn Helgaas wrote: > > > [+cc Nicholas, who is working in this area] > > > > > > On Thu, Jan 09, 2020 at 11:35:09AM +0800, Yicong Yang wrote: > > >> Hi, > > >> > > >> recently I met a problem with pci bus resource allocation. The allocation strategy > > >> makes me confused and leads to a wrong allocation results. > > >> > > >> There is a hisilicon network device with four functions under one root port. The > > >> original bios resources allocation looks like: > > > What kernel is this? Can you collect the complete dmesg log? > > > > The kernel version is 5.4.0. > > Good; at least we know this isn't related to Nicholas' new resource > code that's in -next right now. It is not in next - it is in the release candidates, right? > > > the dmesg log is like: > > The below is not the complete dmesg log. I don't know what your > system is, but the complete log might be in /var/log/dmesg, or maybe > you could capture it with the "ignore_loglevel" kernel parameter and a > serial console? > > > [ 496.598130] hns3 0000:7d:00.3 eth11: net stop > > ... Yicong, please provide the full outputs of: "dmesg" and "sudo lspci -xxxx" and "sudo cat /proc/iomem" in a location that is publicly accessible so that anybody reading this email can find it. Kind regards, Nicholas
