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]
Date:	Mon, 12 Oct 2015 23:19:49 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Meelis Roos <mroos@...ux.ee>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: 4.3-rc3 BAR allocation problems on multiple machines

On Mon, Oct 12, 2015 at 10:06 PM, Meelis Roos <mroos@...ux.ee> wrote:
>> >> > sparc64 machines:
>
> Updated on V210 - the others were more recent. Now I get more BAR
> warning there too:
>
> http://kodu.ut.ee/~mroos/dm/dm.v210+patches

other warning:

[   38.829890] pci 0001:00:07.0: can't claim BAR 2 [mem
0x7ff00000000-0x7ff000fffff]: address conflict with 0001:00:07.0 [mem
0x7ff00000000-0x7ff000fffff]
[   38.829924] pci 0001:00:06.0: can't claim BAR 0 [io
0x7fe01000000-0x7fe0100000f]: address conflict with 0001:00:07.0 [io
0x7fe01000000-0x7fe0100ffff]
[   38.829957] pci 0001:00:0d.0: can't claim BAR 0 [io
0x7fe01000900-0x7fe01000907]: address conflict with 0001:00:07.0 [io
0x7fe01000000-0x7fe0100ffff]
[   38.829988] pci 0001:00:0d.0: can't claim BAR 1 [io
0x7fe01000918-0x7fe0100091f]: address conflict with 0001:00:07.0 [io
0x7fe01000000-0x7fe0100ffff]
[   38.830019] pci 0001:00:0d.0: can't claim BAR 2 [io
0x7fe01000910-0x7fe01000917]: address conflict with 0001:00:07.0 [io
0x7fe01000000-0x7fe0100ffff]
[   38.830050] pci 0001:00:0d.0: can't claim BAR 3 [io
0x7fe01000908-0x7fe0100090f]: address conflict with 0001:00:07.0 [io
0x7fe01000000-0x7fe0100ffff]
[   38.830081] pci 0001:00:0d.0: can't claim BAR 4 [io
0x7fe01000920-0x7fe0100092f]: address conflict with 0001:00:07.0 [io
0x7fe01000000-0x7fe0100ffff]

are real overlapping
1. between BAR1 and BAR2 for 0001:00:07.0.
2. between BAR from 0001:00:07.0 and 0001:00:06.0 io.

I would suspect 00001:00:07.0 is not assigned by firmware.


[   38.830112] PCI: /pci@1e,600000 can't claim Video RAM area [mem
0x7ff000a0000-0x7ff000bffff]: address conflict with 0001:00:07.0 [mem
0x7ff00000000-0x7ff000fffff]
[   38.830150] PCI: /pci@1e,600000 can't claim System ROM [mem
0x7ff000f0000-0x7ff000fffff]: address conflict with 0001:00:07.0 [mem
0x7ff00000000-0x7ff000fffff]
[   38.830187] PCI: /pci@1e,600000 can't claim Video ROM [mem
0x7ff000c0000-0x7ff000c7fff]: address conflict with 0001:00:07.0 [mem
0x7ff00000000-0x7ff000fffff]

those are intended.

Anyway OBP does not assign resource to 00001:00:07.0 ?

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