Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1241282 > unrolled thread

4.3-rc3 BAR allocation problems on multiple machines

Started byMeelis Roos <mroos@linux.ee>
First post2015-10-07 11:30 +0200
Last post2015-10-08 16:50 +0200
Articles 17 — 3 participants

Back to article view | Back to linux.kernel

Contents

  4.3-rc3 BAR allocation problems on multiple machines Meelis Roos <mroos@linux.ee> - 2015-10-07 11:30 +0200
    Re: 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu <yinghai@kernel.org> - 2015-10-08 00:50 +0200
      Re: 4.3-rc3 BAR allocation problems on multiple machines Meelis Roos <mroos@linux.ee> - 2015-10-12 15:10 +0200
        Re: 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu <yinghai@kernel.org> - 2015-10-13 01:00 +0200
          Re: 4.3-rc3 BAR allocation problems on multiple machines Meelis Roos <mroos@linux.ee> - 2015-10-13 07:10 +0200
            Re: 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu <yinghai@kernel.org> - 2015-10-13 07:50 +0200
              Re: 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu <yinghai@kernel.org> - 2015-10-13 08:30 +0200
              Re: 4.3-rc3 BAR allocation problems on multiple machines Meelis Roos <mroos@linux.ee> - 2015-10-13 09:40 +0200
                Re: 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu <yinghai@kernel.org> - 2015-10-13 21:40 +0200
                Re: 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu <yinghai@kernel.org> - 2015-10-13 21:50 +0200
                  Re: 4.3-rc3 BAR allocation problems on multiple machines Meelis Roos <mroos@linux.ee> - 2015-10-13 22:40 +0200
                    Re: 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu <yinghai@kernel.org> - 2015-10-14 02:50 +0200
                      Re: 4.3-rc3 BAR allocation problems on multiple machines Meelis Roos <mroos@linux.ee> - 2015-10-14 09:40 +0200
                        Re: 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu <yinghai@kernel.org> - 2015-10-14 23:50 +0200
            Re: 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu <yinghai@kernel.org> - 2015-10-13 08:20 +0200
    Re: 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu <yinghai@kernel.org> - 2015-10-08 01:20 +0200
      Re: 4.3-rc3 BAR allocation problems on multiple machines Bjorn Helgaas <helgaas@kernel.org> - 2015-10-08 16:50 +0200

#1241282 — 4.3-rc3 BAR allocation problems on multiple machines

FromMeelis Roos <mroos@linux.ee>
Date2015-10-07 11:30 +0200
Subject4.3-rc3 BAR allocation problems on multiple machines
Message-ID<qgTcR-DX-17@gated-at.bofh.it>
First I noticed that on Sun Netra t1-150 (sparc64 CPU), PCI allocation 
was failing for qla1280 scsi driver. Reading dmesg uncovered "can't 
claim BAR" errors. Looking for this in my other test machines I see more 
of them - on many sparc64 machines and some on x86.

In another thread for "Resource allocation cleanup for v4.4", Yinghai Lu 
asked for full dmesg to solve another similar case. So to help 
understanding this one, here are the dmesgs of my machines:

sparc64 machines:

http://kodu.ut.ee/~mroos/dm/dm.t1-105
http://kodu.ut.ee/~mroos/dm/dm.t1-200
http://kodu.ut.ee/~mroos/dm/dm.v120
http://kodu.ut.ee/~mroos/dm/dm.v210
http://kodu.ut.ee/~mroos/dm/dm.v240
http://kodu.ut.ee/~mroos/dm/dm.sb100

amd64 machine:

http://kodu.ut.ee/~mroos/dm/dm.x2100

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

[toc] | [next] | [standalone]

#1241836

FromYinghai Lu <yinghai@kernel.org>
Date2015-10-08 00:50 +0200
Message-ID<qh5H4-1L2-15@gated-at.bofh.it>
In reply to#1241282
On Wed, Oct 7, 2015 at 2:25 AM, Meelis Roos <mroos@linux.ee> wrote:
> First I noticed that on Sun Netra t1-150 (sparc64 CPU), PCI allocation
> was failing for qla1280 scsi driver. Reading dmesg uncovered "can't
> claim BAR" errors. Looking for this in my other test machines I see more
> of them - on many sparc64 machines and some on x86.
>
> In another thread for "Resource allocation cleanup for v4.4", Yinghai Lu
> asked for full dmesg to solve another similar case. So to help
> understanding this one, here are the dmesgs of my machines:
>
> sparc64 machines:
>
> http://kodu.ut.ee/~mroos/dm/dm.t1-105
> http://kodu.ut.ee/~mroos/dm/dm.t1-200
> http://kodu.ut.ee/~mroos/dm/dm.v120
> http://kodu.ut.ee/~mroos/dm/dm.v210
> http://kodu.ut.ee/~mroos/dm/dm.v240
> http://kodu.ut.ee/~mroos/dm/dm.sb100

Please try

git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
for-pci-v4.4-next

It should fix some "no compatible bridge window"

Thanks

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

[toc] | [prev] | [next] | [standalone]

#1244672

FromMeelis Roos <mroos@linux.ee>
Date2015-10-12 15:10 +0200
Message-ID<qiL1w-8hA-7@gated-at.bofh.it>
In reply to#1241836
> > sparc64 machines:
> >
> > http://kodu.ut.ee/~mroos/dm/dm.t1-105
> > http://kodu.ut.ee/~mroos/dm/dm.t1-200
> > http://kodu.ut.ee/~mroos/dm/dm.v120
> > http://kodu.ut.ee/~mroos/dm/dm.v210
> > http://kodu.ut.ee/~mroos/dm/dm.v240
> > http://kodu.ut.ee/~mroos/dm/dm.sb100
> 
> Please try
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
> for-pci-v4.4-next
> 
> It should fix some "no compatible bridge window"

Blade 100: still has 2 address conflicts:
http://kodu.ut.ee/~mroos/dm/dm.sb100+patch

V240: still has a lot of address conflicts:
http://kodu.ut.ee/~mroos/dm/dm.v240+patch

V210: fixes the line
pci 0001:00:07.0: can't claim BAR 0 [io  0x7fe01000000-0x7fe0100ffff]: address conflict with 0001:00:06.0 [io  0x7fe01000600-0x7fe0100061f]

These lines are still present:

pci 0001:00:07.0: can't claim BAR 1 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]
pci 0001:00:07.0: can't claim BAR 2 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]

V120: all messages gone, used to have
[   46.962673] pci 0000:00:01.0: can't claim BAR 8 [mem 0x1ff00000000-0x1ffbfffffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000]
[   46.962794] pci 0000:02:08.0: can't claim BAR 1 [mem 0x1ff00002000-0x1ff00003fff]: no compatible bridge window
[   46.962856] pci 0000:02:08.0: can't claim BAR 3 [mem 0x1ff00004000-0x1ff00005fff]: no compatible bridge window
[   46.962917] pci 0000:02:08.1: can't claim BAR 1 [mem 0x1ff00006000-0x1ff00007fff]: no compatible bridge window
[   46.962976] pci 0000:02:08.1: can't claim BAR 3 [mem 0x1ff00008000-0x1ff00009fff]: no compatible bridge window

T1-200: all messages gone, used to have
[   41.606858] pci 0000:00:01.0: can't claim BAR 8 [mem 0x1ff00000000-0x1ffbfffffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000]
[   41.606981] pci 0000:02:08.0: can't claim BAR 1 [mem 0x1ff00002000-0x1ff00003fff]: no compatible bridge window
[   41.607043] pci 0000:02:08.0: can't claim BAR 3 [mem 0x1ff00004000-0x1ff00005fff]: no compatible bridge window
[   41.607174] pci 0000:02:08.1: can't claim BAR 1 [mem 0x1ff00006000-0x1ff00007fff]: no compatible bridge window
[   41.607236] pci 0000:02:08.1: can't claim BAR 3 [mem 0x1ff00008000-0x1ff00009fff]: no compatible bridge window
[   41.607298] pci 0000:02:05.0: can't claim BAR 1 [mem 0x1ff0000a000-0x1ff0000bfff]: no compatible bridge window
[   41.607358] pci 0000:02:05.0: can't claim BAR 6 [mem 0x1ff00020000-0x1ff0003ffff]: no compatible bridge window

T1-105: all messages are gone, qla1280 works. used to have 
[   21.107754] pci 0000:00:01.0: can't claim BAR 8 [mem 0x1ff00000000-0x1ffbfffffff]: address conflict with Video RAM area [??? 0x1ff000a0000-0x1ff000bffff flags 0x80000000]
[   21.107856] pci 0000:02:01.0: can't claim BAR 8 [mem 0x1ff00100000-0x1ff028fffff]: no compatible bridge window
[   21.107926] pci 0000:03:0f.0: can't claim BAR 8 [mem 0x1ff00100000-0x1ff028fffff]: no compatible bridge window
[   21.107993] pci 0000:04:00.0: can't claim BAR 0 [mem 0x1ff01000000-0x1ff01ffffff]: no compatible bridge window
[   21.108058] pci 0000:04:00.0: can't claim BAR 1 [mem 0x1ff02000000-0x1ff027fffff]: no compatible bridge window
[   21.108124] pci 0000:04:00.1: can't claim BAR 0 [mem 0x1ff02800000-0x1ff0280702f]: no compatible bridge window
[   21.108190] pci 0000:04:04.0: can't claim BAR 1 [mem 0x1ff02808000-0x1ff02808fff]: no compatible bridge window
[   21.108256] pci 0000:04:04.0: can't claim BAR 6 [mem 0x1ff02810000-0x1ff0281ffff]: no compatible bridge window
...
[   53.649523] qla1280 0000:04:04.0: can't ioremap BAR 1: [mem size 0x00001000]
[   53.742379] qla1280: Unable to map I/O memory


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

[toc] | [prev] | [next] | [standalone]

#1245202

FromYinghai Lu <yinghai@kernel.org>
Date2015-10-13 01:00 +0200
Message-ID<qiUeu-4ES-11@gated-at.bofh.it>
In reply to#1244672
On Mon, Oct 12, 2015 at 6:04 AM, Meelis Roos <mroos@linux.ee> wrote:
>> > sparc64 machines:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
>> for-pci-v4.4-next
>>
>> It should fix some "no compatible bridge window"
>
> Blade 100: still has 2 address conflicts:
> http://kodu.ut.ee/~mroos/dm/dm.sb100+patch
>
> V240: still has a lot of address conflicts:
> http://kodu.ut.ee/~mroos/dm/dm.v240+patch
>
> V210: fixes the line
> pci 0001:00:07.0: can't claim BAR 0 [io  0x7fe01000000-0x7fe0100ffff]: address conflict with 0001:00:06.0 [io  0x7fe01000600-0x7fe0100061f]
>
> These lines are still present:
>
> pci 0001:00:07.0: can't claim BAR 1 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]
> pci 0001:00:07.0: can't claim BAR 2 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]
>
you should not have those.

Looks like you are using old branch before 2015-10-05.

If you use the git directly, please update the branch to local again.

Thanks

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

[toc] | [prev] | [next] | [standalone]

#1245339

FromMeelis Roos <mroos@linux.ee>
Date2015-10-13 07:10 +0200
Message-ID<qj00x-4Ug-3@gated-at.bofh.it>
In reply to#1245202
> >> > sparc64 machines:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
> >> for-pci-v4.4-next
> >>
> >> It should fix some "no compatible bridge window"
> >
> > Blade 100: still has 2 address conflicts:
> > http://kodu.ut.ee/~mroos/dm/dm.sb100+patch
> >
> > V240: still has a lot of address conflicts:
> > http://kodu.ut.ee/~mroos/dm/dm.v240+patch
> >
> > V210: fixes the line
> > pci 0001:00:07.0: can't claim BAR 0 [io  0x7fe01000000-0x7fe0100ffff]: address conflict with 0001:00:06.0 [io  0x7fe01000600-0x7fe0100061f]
> >
> > These lines are still present:
> >
> > pci 0001:00:07.0: can't claim BAR 1 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]
> > pci 0001:00:07.0: can't claim BAR 2 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]
> >
> you should not have those.
> 
> Looks like you are using old branch before 2015-10-05.
> 
> If you use the git directly, please update the branch to local again.

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

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

[toc] | [prev] | [next] | [standalone]

#1245357

FromYinghai Lu <yinghai@kernel.org>
Date2015-10-13 07:50 +0200
Message-ID<qj0Dg-5EA-13@gated-at.bofh.it>
In reply to#1245339
On Mon, Oct 12, 2015 at 10:06 PM, Meelis Roos <mroos@linux.ee> wrote:
>> >> > sparc64 machines:
>> >>
>> >> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
>> >> for-pci-v4.4-next
>> >>
>> >> It should fix some "no compatible bridge window"
>> >
>> > Blade 100: still has 2 address conflicts:
>> > http://kodu.ut.ee/~mroos/dm/dm.sb100+patch
>> >
>> > V240: still has a lot of address conflicts:
>> > http://kodu.ut.ee/~mroos/dm/dm.v240+patch
>> >
>> > V210: fixes the line
>> > pci 0001:00:07.0: can't claim BAR 0 [io  0x7fe01000000-0x7fe0100ffff]: address conflict with 0001:00:06.0 [io  0x7fe01000600-0x7fe0100061f]
>> >
>> > These lines are still present:
>> >
>> > pci 0001:00:07.0: can't claim BAR 1 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]
>> > pci 0001:00:07.0: can't claim BAR 2 [mem 0x7ff00000000-0x7ff000fffff]: address conflict with Video RAM area [??? 0x7ff000a0000-0x7ff000bffff flags 0x80000000]
>> >
>> you should not have those.
>>
>> Looks like you are using old branch before 2015-10-05.
>>
>> If you use the git directly, please update the branch to local again.
>
> 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
>

interesting, mem and mem64 is overlapping.

[   38.824625] /pci@1f,700000: TOMATILLO PCI Bus Module ver[4:0]
[   38.824654] /pci@1f,700000: PCI IO [io
0x7f601000000-0x7f601ffffff] offset 7f601000000
[   38.824680] /pci@1f,700000: PCI MEM [mem
0x7f700000000-0x7f7ffffffff] offset 7f700000000
[   38.824704] /pci@1f,700000: PCI MEM64 [mem
0x7f700000000-0x7f7ffffffff] offset 7f700000000
[   38.826310] PCI: Scanning PBM /pci@1f,700000
[   38.826479] schizo f0069c00: PCI host bridge to bus 0000:00
[   38.826506] pci_bus 0000:00: root bus resource [io
0x7f601000000-0x7f601ffffff] (bus address [0x0000-0xffffff])
[   38.826536] pci_bus 0000:00: root bus resource [mem
0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff])
[   38.826565] pci_bus 0000:00: root bus resource [mem
0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff])

We need to add more sanitary checking.

Can you send boot log after booting with "debug ignore_loglevel ofpci_debug=1" ?

Thanks

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

[toc] | [prev] | [next] | [standalone]

#1245372

FromYinghai Lu <yinghai@kernel.org>
Date2015-10-13 08:30 +0200
Message-ID<qj1fX-6Co-7@gated-at.bofh.it>
In reply to#1245357

[Multipart message — attachments visible in raw view] — view raw

On Mon, Oct 12, 2015 at 10:43 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> On Mon, Oct 12, 2015 at 10:06 PM, Meelis Roos <mroos@linux.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
>>
>
> interesting, mem and mem64 is overlapping.
>
> [   38.824625] /pci@1f,700000: TOMATILLO PCI Bus Module ver[4:0]
> [   38.824654] /pci@1f,700000: PCI IO [io
> 0x7f601000000-0x7f601ffffff] offset 7f601000000
> [   38.824680] /pci@1f,700000: PCI MEM [mem
> 0x7f700000000-0x7f7ffffffff] offset 7f700000000
> [   38.824704] /pci@1f,700000: PCI MEM64 [mem
> 0x7f700000000-0x7f7ffffffff] offset 7f700000000
> [   38.826310] PCI: Scanning PBM /pci@1f,700000
> [   38.826479] schizo f0069c00: PCI host bridge to bus 0000:00
> [   38.826506] pci_bus 0000:00: root bus resource [io
> 0x7f601000000-0x7f601ffffff] (bus address [0x0000-0xffffff])
> [   38.826536] pci_bus 0000:00: root bus resource [mem
> 0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff])
> [   38.826565] pci_bus 0000:00: root bus resource [mem
> 0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff])
>

For overlapping, please check attached patch that should fix the problem.

Thanks

Yinghai

[toc] | [prev] | [next] | [standalone]

#1245409

FromMeelis Roos <mroos@linux.ee>
Date2015-10-13 09:40 +0200
Message-ID<qj2lI-8ci-1@gated-at.bofh.it>
In reply to#1245357
> > 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
> >
> 
> interesting, mem and mem64 is overlapping.
> 
> [   38.824625] /pci@1f,700000: TOMATILLO PCI Bus Module ver[4:0]
> [   38.824654] /pci@1f,700000: PCI IO [io
> 0x7f601000000-0x7f601ffffff] offset 7f601000000
> [   38.824680] /pci@1f,700000: PCI MEM [mem
> 0x7f700000000-0x7f7ffffffff] offset 7f700000000
> [   38.824704] /pci@1f,700000: PCI MEM64 [mem
> 0x7f700000000-0x7f7ffffffff] offset 7f700000000
> [   38.826310] PCI: Scanning PBM /pci@1f,700000
> [   38.826479] schizo f0069c00: PCI host bridge to bus 0000:00
> [   38.826506] pci_bus 0000:00: root bus resource [io
> 0x7f601000000-0x7f601ffffff] (bus address [0x0000-0xffffff])
> [   38.826536] pci_bus 0000:00: root bus resource [mem
> 0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff])
> [   38.826565] pci_bus 0000:00: root bus resource [mem
> 0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff])
> 
> We need to add more sanitary checking.
> 
> Can you send boot log after booting with "debug ignore_loglevel ofpci_debug=1" ?

http://kodu.ut.ee/~mroos/dm/dm.v210+patch+debug

Applied the fix_mem_mem64_overlapping.patch and retested. The BAR 
allocation problems are still there:

http://kodu.ut.ee/~mroos/dm/dm.v210+patch+mem64patch+debug

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

[toc] | [prev] | [next] | [standalone]

#1246075

FromYinghai Lu <yinghai@kernel.org>
Date2015-10-13 21:40 +0200
Message-ID<qjdAu-7Oi-15@gated-at.bofh.it>
In reply to#1245409
On Tue, Oct 13, 2015 at 12:32 AM, Meelis Roos <mroos@linux.ee> wrote:

> Applied the fix_mem_mem64_overlapping.patch and retested. The BAR
> allocation problems are still there:
>
> http://kodu.ut.ee/~mroos/dm/dm.v210+patch+mem64patch+debug

Good, now MEM64 is gone.

[   34.145275] /pci@1f,700000: TOMATILLO PCI Bus Module ver[4:0]
[   34.145304] /pci@1f,700000: PCI IO [io
0x7f601000000-0x7f601ffffff] offset 7f601000000
[   34.145330] /pci@1f,700000: PCI MEM [mem
0x7f700000000-0x7f7ffffffff] offset 7f700000000
[   34.146938] PCI: Scanning PBM /pci@1f,700000
[   34.147104] schizo f0069c00: PCI host bridge to bus 0000:00
[   34.147132] pci_bus 0000:00: root bus resource [io
0x7f601000000-0x7f601ffffff] (bus address [0x0000-0xffffff])
[   34.147162] pci_bus 0000:00: root bus resource [mem
0x7f700000000-0x7f7ffffffff] (bus address [0x00000000-0xffffffff])
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1246091

FromYinghai Lu <yinghai@kernel.org>
Date2015-10-13 21:50 +0200
Message-ID<qjdKb-80D-51@gated-at.bofh.it>
In reply to#1245409
On Tue, Oct 13, 2015 at 12:32 AM, Meelis Roos <mroos@linux.ee> wrote:
>>
>> Can you send boot log after booting with "debug ignore_loglevel ofpci_debug=1" ?
>
> http://kodu.ut.ee/~mroos/dm/dm.v210+patch+debug

Firmware does reported overlapped resources.

[   34.150035] PCI: scan_bus[/pci@1e,600000] bus no 0
[   34.150050]   * /pci@1e,600000/isa@7
[   34.150085]     create device, devfn: 38, type:
[   34.150114]     class: 0x60100 device name: 0001:00:07.0
[   34.150129]     parse addresses (60 bytes) @ fff000123fe92b40
[   34.150144]   start: 7fe01000000, end: 7fe0100ffff, i: 10 ==========
[   34.150159]   start: 7ff00000000, end: 7ff000fffff, i: 14
[   34.150174]   start: 7ff00000000, end: 7ff000fffff, i: 18
[   34.150188]     adding to system ...
[   34.150333] PCI: dev header type: 0
[   34.150348]   * /pci@1e,600000/pmu@6
[   34.150386]     create device, devfn: 30, type:
[   34.150409]     class: 0x0 device name: 0001:00:06.0
[   34.150424]     parse addresses (20 bytes) @ fff000123fe7d080
[   34.150439]   start: 7fe01000000, end: 7fe0100000f, i: 10 =============
[   34.150453]     adding to system ...
[   34.150582] PCI: dev header type: 0
[   34.150596]   * /pci@1e,600000/usb@a
[   34.150630]     create device, devfn: 50, type:
[   34.150655]     class: 0xc0310 device name: 0001:00:0a.0
[   34.150670]     parse addresses (20 bytes) @ fff000123fe7aec0
[   34.150686]   start: 7ff01000000, end: 7ff01ffffff, i: 10
[   34.150699]     adding to system ...
[   34.150727] pci 0001:00:0a.0: PME# supported from D3cold
[   34.150888] PCI: dev header type: 0
[   34.150902]   * /pci@1e,600000/ide@d
[   34.150932]     create device, devfn: 68, type: ide
[   34.150959]     class: 0x101ff device name: 0001:00:0d.0
[   34.150976]     parse addresses (100 bytes) @ fff000123fe79900
[   34.150991]   start: 7fe01000900, end: 7fe01000907, i: 10 =============
[   34.151006]   start: 7fe01000918, end: 7fe0100091f, i: 14 =============
[   34.151021]   start: 7fe01000910, end: 7fe01000917, i: 18 ==============
[   34.151035]   start: 7fe01000908, end: 7fe0100090f, i: 1c ============
[   34.151050]   start: 7fe01000920, end: 7fe0100092f, i: 20 =============


can you send out output for
lspci -vvxxx
lspci -tv

Thanks

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

[toc] | [prev] | [next] | [standalone]

#1246122

FromMeelis Roos <mroos@linux.ee>
Date2015-10-13 22:40 +0200
Message-ID<qjewy-LU-7@gated-at.bofh.it>
In reply to#1246091
> >> Can you send boot log after booting with "debug ignore_loglevel ofpci_debug=1" ?
> >
> > http://kodu.ut.ee/~mroos/dm/dm.v210+patch+debug
> 
> Firmware does reported overlapped resources.
[...] 
> can you send out output for
> lspci -vvxxx
> lspci -tv

Here you are.

0000:00:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
	Subsystem: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (16000ns min), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 6
	Region 0: Memory at 00200000 (64-bit, non-prefetchable) [size=2M]
	Region 2: Memory at 00110000 (64-bit, non-prefetchable) [size=64K]
	Region 4: [virtual] Memory at fffff80900000000 (32-bit, non-prefetchable)
	Region 5: [virtual] Memory at fffff80900000000 (32-bit, non-prefetchable)
	Expansion ROM at fffff80900000000 [disabled]
	Capabilities: [40] PCI-X non-bridge device
		Command: DPERE- ERO+ RBC=512 OST=1
		Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz-
	Capabilities: [48] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [50] Vital Product Data
		Not readable
	Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
		Address: 2d92e07bc876dbd0  Data: 0c1b
	Kernel driver in use: tg3
00: e4 14 48 16 06 00 b0 02 00 00 00 02 10 40 80 00
10: 04 00 20 00 00 00 00 00 04 00 11 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 e4 14 48 16
30: 00 00 81 2b 40 00 00 00 00 00 00 00 a3 01 40 00
40: 07 48 02 00 f8 ff 43 04 01 50 02 40 00 20 00 00
50: 03 58 00 00 3b 79 48 4b 05 00 86 00 d0 db 76 c8
60: 7b e0 92 2d 1b 0c 00 00 98 02 03 20 00 00 3f 76
70: ee 00 00 00 c4 00 00 80 4c 5b 03 00 00 00 00 00
80: 00 00 00 00 00 59 b0 00 36 00 13 04 82 90 20 02
90: 09 97 00 01 01 00 00 00 00 00 00 00 f5 01 00 00
a0: 00 00 00 00 2d 01 00 00 00 00 00 00 e3 01 00 00
b0: 00 00 00 00 00 00 00 71 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0000:00:02.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
	Subsystem: Oracle/SUN Device 1648
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (16000ns min), Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 7
	Region 0: Memory at 00400000 (64-bit, non-prefetchable) [size=2M]
	Region 2: Memory at 00120000 (64-bit, non-prefetchable) [size=64K]
	Region 4: [virtual] Memory at fffff80900000000 (32-bit, non-prefetchable)
	Region 5: [virtual] Memory at fffff80900000000 (32-bit, non-prefetchable)
	[virtual] Expansion ROM at fffff80900000000 [disabled]
	Capabilities: [40] PCI-X non-bridge device
		Command: DPERE- ERO+ RBC=512 OST=1
		Status: Dev=ff:1f.1 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz-
	Capabilities: [48] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [50] Vital Product Data
		Not readable
	Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
		Address: 2e047d69dfc7ac80  Data: d6f4
	Kernel driver in use: tg3
00: e4 14 48 16 06 00 b0 02 00 00 00 02 10 40 80 00
10: 04 00 40 00 00 00 00 00 04 00 12 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 8e 10 48 16
30: 00 00 00 00 40 00 00 00 00 00 00 00 22 02 40 00
40: 07 48 02 00 f9 ff 43 04 01 50 02 40 00 20 00 00
50: 03 58 00 00 d8 30 08 01 05 00 86 00 80 ac c7 df
60: 69 7d 04 2e f4 d6 00 00 9a 02 03 20 00 00 3f 76
70: 0e 02 00 00 c4 00 00 00 00 00 00 00 00 00 00 00
80: e4 14 48 16 f8 80 3b 05 36 00 00 00 fe 90 60 02
90: 01 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0001:00:06.0 Non-VGA unclassified device: ULi Electronics Inc. M7101 Power Management Controller [PMU]
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: [virtual] I/O ports at <unassigned> [size=16]
	Region 1: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	Region 2: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	[virtual] Expansion ROM at fffff80100000000 [disabled]
00: b9 10 01 71 00 00 00 02 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 20 00 08 18 08 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 01
70: 0f 11 00 00 00 00 00 08 00 00 00 00 00 00 00 00
80: 00 00 10 10 00 00 00 00 01 02 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 08 00 00 01 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 40 40 01 00 00 02 00 60 00 00 03 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 06 00 00 00 00 00 00 00 00 00 00 0b 00 00 00
e0: 00 08 00 06 01 00 01 00 00 00 00 00 00 00 00 00
f0: 45 00 88 6e 00 00 00 00 00 00 00 00 00 00 00 00

0001:00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Region 0: [virtual] I/O ports at 0000 [size=64K]
	Region 1: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M]
	Region 2: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M]
	Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	[virtual] Expansion ROM at fffff80100000000 [disabled]
	Capabilities: [a0] Power Management version 1
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
00: b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
40: 03 13 4b 80 83 09 00 47 00 00 06 00 00 00 eb 31
50: 00 00 00 20 90 02 20 03 66 03 00 00 00 00 00 08
60: 40 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00
70: 00 00 0a 00 47 00 00 db 04 02 00 04 00 80 01 90
80: a5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0001:00:0a.0 USB controller: ULi Electronics Inc. USB 1.1 Controller (rev 03) (prog-if 10 [OHCI])
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 17
	Region 0: Memory at 01000000 (32-bit, non-prefetchable) [disabled] [size=16M]
	Region 1: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	Region 2: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	[virtual] Expansion ROM at fffff80100000000 [disabled]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
00: b9 10 37 52 00 00 90 02 03 10 03 0c 00 40 00 00
10: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 60 00 00 00 00 00 00 00 00 01 00 50
40: 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 01 00 02 80 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0001:00:0d.0 IDE interface: ULi Electronics Inc. M5229 IDE (rev c4) (prog-if ff)
	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (500ns min, 1000ns max)
	Interrupt: pin A routed to IRQ 18
	Region 0: I/O ports at 0900 [disabled] [size=8]
	Region 1: I/O ports at 0918 [disabled] [size=8]
	Region 2: I/O ports at 0910 [disabled] [size=8]
	Region 3: I/O ports at 0908 [disabled] [size=8]
	Region 4: I/O ports at 0920 [disabled] [size=16]
	Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
	[virtual] Expansion ROM at fffff80100000000 [disabled]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
00: b9 10 29 52 04 00 90 02 c4 ff 01 01 00 40 00 00
10: 01 09 00 00 19 09 00 00 11 09 00 00 09 09 00 00
20: 21 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 60 00 00 00 00 00 00 00 00 01 02 04
40: 00 00 00 7f 00 00 00 00 30 00 02 c0 00 80 ba 1a
50: 03 00 00 81 55 55 44 44 03 00 00 00 03 00 00 00
60: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0002:00:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 66MHz  Ultra3 SCSI Adapter (rev 01)
	Subsystem: LSI Logic / Symbios Logic LSI53C1000/1000R/1010R/1010-66 PCI to Ultra160 SCSI Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (4250ns min, 4500ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 24
	Region 0: I/O ports at 0900 [size=256]
	Region 1: Memory at 00100000 (64-bit, non-prefetchable) [size=8K]
	Region 3: Memory at 00102000 (64-bit, non-prefetchable) [size=8K]
	Region 5: [virtual] Memory at fffff83100000000 (32-bit, non-prefetchable)
	[virtual] Expansion ROM at fffff83100000000 [disabled]
	Capabilities: [40] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: sym53c8xx
00: 00 10 21 00 57 01 30 02 01 00 00 01 10 40 80 00
10: 01 09 00 00 04 00 10 00 00 00 00 00 04 20 10 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 10
30: 00 00 00 00 40 00 00 00 00 00 00 00 00 01 11 12
40: 01 00 02 06 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0002:00:02.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 66MHz  Ultra3 SCSI Adapter (rev 01)
	Subsystem: LSI Logic / Symbios Logic LSI53C1000/1000R/1010R/1010-66 PCI to Ultra160 SCSI Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (4250ns min, 4500ns max), Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 25
	Region 0: I/O ports at 0a00 [size=256]
	Region 1: Memory at 00104000 (64-bit, non-prefetchable) [size=8K]
	Region 3: Memory at 00106000 (64-bit, non-prefetchable) [size=8K]
	Region 5: [virtual] Memory at fffff83100000000 (32-bit, non-prefetchable)
	[virtual] Expansion ROM at fffff83100000000 [disabled]
	Capabilities: [40] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: sym53c8xx
00: 00 10 21 00 57 01 30 02 01 00 00 01 10 40 80 00
10: 01 0a 00 00 04 40 10 00 00 00 00 00 04 60 10 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 10
30: 00 00 00 00 40 00 00 00 00 00 00 00 00 02 11 12
40: 01 00 02 06 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0003:00:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
	Subsystem: Oracle/SUN Device 1648
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (16000ns min), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 31
	Region 0: Memory at 00200000 (64-bit, non-prefetchable) [size=2M]
	Region 2: Memory at 00110000 (64-bit, non-prefetchable) [size=64K]
	Region 4: [virtual] Memory at fffff83900000000 (32-bit, non-prefetchable)
	Region 5: [virtual] Memory at fffff83900000000 (32-bit, non-prefetchable)
	[virtual] Expansion ROM at fffff83900000000 [disabled]
	Capabilities: [40] PCI-X non-bridge device
		Command: DPERE- ERO+ RBC=512 OST=1
		Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz-
	Capabilities: [48] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [50] Vital Product Data
		Not readable
	Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
		Address: 3080414020d22000  Data: 3000
	Kernel driver in use: tg3
00: e4 14 48 16 06 00 b0 02 00 00 00 02 10 40 80 00
10: 04 00 20 00 00 00 00 00 04 00 11 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 8e 10 48 16
30: 00 00 00 00 40 00 00 00 00 00 00 00 2d 01 40 00
40: 07 48 02 00 f8 ff 43 04 01 50 02 40 00 20 00 00
50: 03 58 00 00 08 04 10 40 05 00 86 00 00 20 d2 20
60: 40 41 80 30 00 30 00 00 9a 02 03 20 00 00 3f 76
70: 8e 02 00 00 c4 00 00 00 00 00 00 00 00 00 00 00
80: e4 14 48 16 ea ec 23 13 36 00 00 00 fe 90 20 02
90: 01 07 00 01 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0003:00:02.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
	Subsystem: Oracle/SUN Device 1648
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (16000ns min), Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 32
	Region 0: Memory at 00400000 (64-bit, non-prefetchable) [size=2M]
	Region 2: Memory at 00120000 (64-bit, non-prefetchable) [size=64K]
	Region 4: [virtual] Memory at fffff83900000000 (32-bit, non-prefetchable)
	Region 5: [virtual] Memory at fffff83900000000 (32-bit, non-prefetchable)
	[virtual] Expansion ROM at fffff83900000000 [disabled]
	Capabilities: [40] PCI-X non-bridge device
		Command: DPERE- ERO+ RBC=512 OST=1
		Status: Dev=ff:1f.1 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz-
	Capabilities: [48] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [50] Vital Product Data
		Not readable
	Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
		Address: 30001484410f4000  Data: 0500
	Kernel driver in use: tg3
00: e4 14 48 16 06 00 b0 02 00 00 00 02 10 40 80 00
10: 04 00 40 00 00 00 00 00 04 00 12 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 8e 10 48 16
30: 00 00 00 00 40 00 00 00 00 00 00 00 02 02 40 00
40: 07 48 02 00 f9 ff 43 04 01 50 02 40 00 20 00 00
50: 03 58 00 00 0c 01 12 02 05 00 86 00 00 40 0f 41
60: 84 14 00 30 00 05 00 00 9a 02 03 20 00 00 3f 76
70: 8e 02 00 00 c4 00 00 00 00 00 00 00 00 00 00 00
80: e4 14 48 16 60 8b 36 00 36 00 00 00 fe 90 60 02
90: 01 07 00 01 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


-+-[0003:00]-+-02.0  Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
 |           \-02.1  Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
 +-[0002:00]-+-02.0  LSI Logic / Symbios Logic 53c1010 66MHz  Ultra3 SCSI Adapter
 |           \-02.1  LSI Logic / Symbios Logic 53c1010 66MHz  Ultra3 SCSI Adapter
 +-[0001:00]-+-06.0  ULi Electronics Inc. M7101 Power Management Controller [PMU]
 |           +-07.0  ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
 |           +-0a.0  ULi Electronics Inc. USB 1.1 Controller
 |           \-0d.0  ULi Electronics Inc. M5229 IDE
 \-[0000:00]-+-02.0  Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
             \-02.1  Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet

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

[toc] | [prev] | [next] | [standalone]

#1246226

FromYinghai Lu <yinghai@kernel.org>
Date2015-10-14 02:50 +0200
Message-ID<qjiqu-6wV-1@gated-at.bofh.it>
In reply to#1246122

[Multipart message — attachments visible in raw view] — view raw

On Tue, Oct 13, 2015 at 1:39 PM, Meelis Roos <mroos@linux.ee> wrote:
>
> 0001:00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
>         Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 0
>         Region 0: [virtual] I/O ports at 0000 [size=64K]
>         Region 1: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M]
>         Region 2: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M]
>         Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
>         Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
>         Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
>         [virtual] Expansion ROM at fffff80100000000 [disabled]
>         Capabilities: [a0] Power Management version 1
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> 00: b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
> 40: 03 13 4b 80 83 09 00 47 00 00 06 00 00 00 eb 31
> 50: 00 00 00 20 90 02 20 03 66 03 00 00 00 00 00 08
> 60: 40 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00
> 70: 00 00 0a 00 47 00 00 db 04 02 00 04 00 80 01 90
> 80: a5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Please check attached patch.

Thanks

Yinghai

[toc] | [prev] | [next] | [standalone]

#1246369

FromMeelis Roos <mroos@linux.ee>
Date2015-10-14 09:40 +0200
Message-ID<qjoPg-8w0-25@gated-at.bofh.it>
In reply to#1246226
> > 0001:00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
> >         Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> >         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> >         Latency: 0
> >         Region 0: [virtual] I/O ports at 0000 [size=64K]
> >         Region 1: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M]
> >         Region 2: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M]
> >         Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
> >         Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
> >         Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
> >         [virtual] Expansion ROM at fffff80100000000 [disabled]
> >         Capabilities: [a0] Power Management version 1
> >                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> >                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> > 00: b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00
> > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
> > 40: 03 13 4b 80 83 09 00 47 00 00 06 00 00 00 eb 31
> > 50: 00 00 00 20 90 02 20 03 66 03 00 00 00 00 00 08
> > 60: 40 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00
> > 70: 00 00 0a 00 47 00 00 db 04 02 00 04 00 80 01 90
> > 80: a5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > a0: 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
> > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 
> Please check attached patch.

Thank you, it seems to work. First, the following lines are gone:
PCI: Claiming 0001:00:07.0: Resource 0: 000007fe01000000..000007fe0100ffff [101]
PCI: Claiming 0001:00:07.0: Resource 1: 000007ff00000000..000007ff000fffff [200]
PCI: Claiming 0001:00:07.0: Resource 2: 000007ff00000000..000007ff000fffff [200]

And then all following PCI: Claiming... lines succeed, with no address 
conflicts.

Now, how can I be sure that removing the ULi ISA bridge allocations does 
not break anything? It seems I did not have I2C enabled in kernel conf - 
I emabled it now, recompiled, got this but it seems to be for another 
PCI device so not related?
ali15x3_smbus 0001:00:06.0: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr
ali15x3_smbus 0001:00:06.0: ALI15X3 not detected, module not inserted.

Additionally, another driver (i2c-ali1535) claimed 0001:00:06.0 and was 
happy but did not find anything (but I do not know what it sahould find 
so I can see no problem at the moment).

I also applied the patch on Sun Blade 100 where i2c was working for me. 
It was still working with this ali quirk patch applied, and no BAR 
errors.

What about other arches - does this patch affect other arches where the 
firmware has configured some addresses for this ULi bridge?

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

[toc] | [prev] | [next] | [standalone]

#1247211

FromYinghai Lu <yinghai@kernel.org>
Date2015-10-14 23:50 +0200
Message-ID<qjC5P-2Mx-1@gated-at.bofh.it>
In reply to#1246369
On Wed, Oct 14, 2015 at 12:34 AM, Meelis Roos <mroos@linux.ee> wrote:
>> > 0001:00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
>> >         Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
>> >         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>> >         Latency: 0
>> >         Region 0: [virtual] I/O ports at 0000 [size=64K]
>> >         Region 1: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M]
>> >         Region 2: Memory at <unassigned> (32-bit, non-prefetchable) [size=1M]
>> >         Region 3: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
>> >         Region 4: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
>> >         Region 5: [virtual] Memory at fffff80100000000 (32-bit, non-prefetchable)
>> >         [virtual] Expansion ROM at fffff80100000000 [disabled]
>> >         Capabilities: [a0] Power Management version 1
>> >                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
>> >                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>> > 00: b9 10 33 15 0f 00 10 02 00 00 01 06 00 00 00 00
>> > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> > 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> > 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
>> > 40: 03 13 4b 80 83 09 00 47 00 00 06 00 00 00 eb 31
>> > 50: 00 00 00 20 90 02 20 03 66 03 00 00 00 00 00 08
>> > 60: 40 00 00 00 00 00 00 00 00 00 00 00 80 20 00 00
>> > 70: 00 00 0a 00 47 00 00 db 04 02 00 04 00 80 01 90
>> > 80: a5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> > a0: 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
>> > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>
>> Please check attached patch.
>
> Thank you, it seems to work. First, the following lines are gone:
> PCI: Claiming 0001:00:07.0: Resource 0: 000007fe01000000..000007fe0100ffff [101]
> PCI: Claiming 0001:00:07.0: Resource 1: 000007ff00000000..000007ff000fffff [200]
> PCI: Claiming 0001:00:07.0: Resource 2: 000007ff00000000..000007ff000fffff [200]
>
> And then all following PCI: Claiming... lines succeed, with no address
> conflicts.
>
> Now, how can I be sure that removing the ULi ISA bridge allocations does
> not break anything? It seems I did not have I2C enabled in kernel conf -
> I emabled it now, recompiled, got this but it seems to be for another
> PCI device so not related?
> ali15x3_smbus 0001:00:06.0: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr
> ali15x3_smbus 0001:00:06.0: ALI15X3 not detected, module not inserted.

code segment:
        /* Determine the address of the SMBus area */
        pci_read_config_word(ALI15X3_dev, SMBBA, &ali15x3_smba);
        ali15x3_smba &= (0xffff & ~(ALI15X3_SMB_IOSIZE - 1));
        if (ali15x3_smba == 0 && force_addr == 0) {
                dev_err(&ALI15X3_dev->dev, "ALI15X3_smb region uninitialized "
                        "- upgrade BIOS or use force_addr=0xaddr\n");
                return -ENODEV;
        }

SMBBA is 0x14

from lspci:

0001:00:06.0 Non-VGA unclassified device: ULi Electronics Inc. M7101
Power Management Controller [PMU]
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Region 0: [virtual] I/O ports at <unassigned> [size=16]
        [virtual] Expansion ROM at fffff80100000000 [disabled]
00: b9 10 01 71 00 00 00 02 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0x14 BAR has 0 really.

>
> Additionally, another driver (i2c-ali1535) claimed 0001:00:06.0 and was
> happy but did not find anything (but I do not know what it sahould find
> so I can see no problem at the moment).

it should complain too:

        /* Determine the address of the SMBus area */
        pci_read_config_word(dev, SMBBA, &ali1535_offset);
        dev_dbg(&dev->dev, "ALI1535_smb is at offset 0x%04x\n", ali1535_offset);
        ali1535_offset &= (0xffff & ~(ALI1535_SMB_IOSIZE - 1));
        if (ali1535_offset == 0) {
                dev_warn(&dev->dev,
                        "ALI1535_smb region uninitialized - upgrade BIOS?\n");
                retval = -ENODEV;
                goto exit;
        }


>
> I also applied the patch on Sun Blade 100 where i2c was working for me.
> It was still working with this ali quirk patch applied, and no BAR
> errors.

Good.

assume v210 does use those for i2c.

>
> What about other arches - does this patch affect other arches where the
> firmware has configured some addresses for this ULi bridge?

According to data sheet, those BAR on 00:07.0 are all 0, and read only.
Not sure how are those to to use them.

Thanks

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

[toc] | [prev] | [next] | [standalone]

#1245365

FromYinghai Lu <yinghai@kernel.org>
Date2015-10-13 08:20 +0200
Message-ID<qj16h-6rl-3@gated-at.bofh.it>
In reply to#1245339
On Mon, Oct 12, 2015 at 10:06 PM, Meelis Roos <mroos@linux.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1241851

FromYinghai Lu <yinghai@kernel.org>
Date2015-10-08 01:20 +0200
Message-ID<qh6a5-2y3-3@gated-at.bofh.it>
In reply to#1241282
On Wed, Oct 7, 2015 at 2:25 AM, Meelis Roos <mroos@linux.ee> wrote:
> amd64 machine:
>
> http://kodu.ut.ee/~mroos/dm/dm.x2100

[    0.156360] bus: [bus 00-05] on node 0 link 0
[    0.156362] bus: 00 [io  0x0000-0xffff]
[    0.156364] bus: 00 [mem 0x000a0000-0x000bffff]
[    0.156365] bus: 00 [mem 0xfe030000-0xffffffff]
[    0.156366] bus: 00 [mem 0xc0000000-0xefffffff]
[    0.156368] bus: 00 [mem 0xf0000000-0xfe02ffff]
[    0.156369] bus: 00 [mem 0x140000000-0xfcffffffff]

[    0.174069] PCI: Using host bridge windows from ACPI; if necessary,
use "pci=nocrs" and report a bug
[    0.180821] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-05])
[    0.180943] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM
ClockPM Segments MSI]
[    0.181139] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[    0.181917] PCI host bridge to bus 0000:00
[    0.182030] pci_bus 0000:00: root bus resource [bus 00-05]
[    0.182144] pci_bus 0000:00: root bus resource [io  0x0000-0x03af window]
[    0.182262] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7 window]
[    0.182379] pci_bus 0000:00: root bus resource [io  0x6000-0xffff window]
[    0.182494] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df window]
[    0.182609] pci_bus 0000:00: root bus resource [mem
0x000a0000-0x000bffff window]
[    0.182799] pci_bus 0000:00: root bus resource [mem
0xc0000000-0xdfffffff window]
[    0.182989] pci_bus 0000:00: root bus resource [mem
0xf0000000-0xfe02ffff window]
[    0.183179] pci_bus 0000:00: root bus resource [mem
0xfeb00000-0xfebfffff window]

BIOS report different resource from _CRS setting and setting with cpu registers.

[    0.183379] pci 0000:00:00.0: [10de:005e] type 00 class 0x058000
[    0.183542] pci 0000:00:01.0: [10de:0050] type 00 class 0x060100

root bus io range from _CRS does not include that.

boot with pci=nocrs should avoid that and it is safe as we get ranges
from register.

Thanks

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

[toc] | [prev] | [next] | [standalone]

#1242450

FromBjorn Helgaas <helgaas@kernel.org>
Date2015-10-08 16:50 +0200
Message-ID<qhkG6-6u9-33@gated-at.bofh.it>
In reply to#1241851
On Wed, Oct 07, 2015 at 04:16:37PM -0700, Yinghai Lu wrote:
> On Wed, Oct 7, 2015 at 2:25 AM, Meelis Roos <mroos@linux.ee> wrote:
> > amd64 machine:
> >
> > http://kodu.ut.ee/~mroos/dm/dm.x2100
> 
> [    0.156360] bus: [bus 00-05] on node 0 link 0
> [    0.156362] bus: 00 [io  0x0000-0xffff]
> [    0.156364] bus: 00 [mem 0x000a0000-0x000bffff]
> [    0.156365] bus: 00 [mem 0xfe030000-0xffffffff]
> [    0.156366] bus: 00 [mem 0xc0000000-0xefffffff]
> [    0.156368] bus: 00 [mem 0xf0000000-0xfe02ffff]
> [    0.156369] bus: 00 [mem 0x140000000-0xfcffffffff]
> 
> [    0.174069] PCI: Using host bridge windows from ACPI; if necessary,
> use "pci=nocrs" and report a bug
> [    0.180821] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-05])
> [    0.180943] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM
> ClockPM Segments MSI]
> [    0.181139] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
> [    0.181917] PCI host bridge to bus 0000:00
> [    0.182030] pci_bus 0000:00: root bus resource [bus 00-05]
> [    0.182144] pci_bus 0000:00: root bus resource [io  0x0000-0x03af window]
> [    0.182262] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7 window]
> [    0.182379] pci_bus 0000:00: root bus resource [io  0x6000-0xffff window]
> [    0.182494] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df window]
> [    0.182609] pci_bus 0000:00: root bus resource [mem
> 0x000a0000-0x000bffff window]
> [    0.182799] pci_bus 0000:00: root bus resource [mem
> 0xc0000000-0xdfffffff window]
> [    0.182989] pci_bus 0000:00: root bus resource [mem
> 0xf0000000-0xfe02ffff window]
> [    0.183179] pci_bus 0000:00: root bus resource [mem
> 0xfeb00000-0xfebfffff window]
> 
> BIOS report different resource from _CRS setting and setting with cpu registers.
> 
> [    0.183379] pci 0000:00:00.0: [10de:005e] type 00 class 0x058000
> [    0.183542] pci 0000:00:01.0: [10de:0050] type 00 class 0x060100

I don't know how the above two devices are related, since they don't
have any BARs at all.

But 00:01.1 does have two I/O BARs that are invalid per _CRS:

  pci 0000:00:01.1: can't claim BAR 4 [io  0x1c00-0x1c3f]: no compatible bridge window
  pci 0000:00:01.1: can't claim BAR 5 [io  0x1c40-0x1c7f]: no compatible bridge window

> root bus io range from _CRS does not include that.
> 
> boot with pci=nocrs should avoid that and it is safe as we get ranges
> from register.

As far as I'm concerned, it is not safe to use "pci=nocrs" in this
situation.  The BIOS programmed the hardware aperture
("bus: 00 [io 0x0000-0xffff]") *and* it explicitly excluded pieces of
that range when it told the OS what it could use.  The OS has to
assume the BIOS knows what it is doing and is using those excluded
ranges for something else, so it is *not* safe for the OS to put
devices there.

It's certainly possible and even likely that this is a BIOS defect.
But we cannot assume "pci=nocrs" is safe in general.

If you want to tell users to boot with "pci=nocrs", that's up to you.
Personally, I don't think that's an acceptable user experience.

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web