* PCI conflicts with latest kernels
@ 2010-03-14 10:31 Giampaolo Bellini
2010-03-14 20:12 ` Rafael J. Wysocki
0 siblings, 1 reply; 8+ messages in thread
From: Giampaolo Bellini @ 2010-03-14 10:31 UTC (permalink / raw)
To: linux-kernel
Hi all...
I'm experimenting PCI address space collisions on an ICOP PC104
VDX-6357 motherboard (with no cards/expansion at all) and kernels
2.6.33/34
collisions where not there with kernel 2.6.29 (I start with this
.config and I've done a make oldconfig for 2.6.33/34).
I have no ACPI support and I'm using the sisfb framebuffer on a XGI
Technology Inc. (eXtreme Graphics Innovation) Volari Z7 chipset.
thanks for any ideas
Paolo
here are some info:
-------------------------------------------------------------------
cat /proc/cmdline
-------------------------------------------------------------------
root=/dev/sda2 quiet video=sisfb:640x480-32 ar8.debug=1
ar8.outputs=0x80 BOOT_IMAGE=vmlinuz-2.6.33-r3-vdx
-------------------------------------------------------------------
dmesg kernel 2.6.33:
-------------------------------------------------------------------
Linux version 2.6.33-ibty3-vdx (root@nibble) (gcc version 4.2.4
(Ubuntu 4.2.4-1ubuntu3)) #22 Sun Mar 14 00:35:18 CET 2010
CPU: vendor_id 'Vortex86 SoC' unknown, using generic init.
CPU: Your system may be unstable.
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
Notice: NX (Execute Disable) protection missing in CPU or disabled in BIOS!
DMI not present or invalid.
last_pfn = 0x20000 max_arch_pfn = 0x100000
initial memory mapped : 0 - 01800000
init_memory_mapping: 0000000000000000-0000000020000000
0000000000 - 0020000000 page 4k
kernel direct mapping tables up to 20000000 @ 7000-8a000
512MB LOWMEM available.
mapped low ram: 0 - 20000000
low ram: 0 - 20000000
node 0 low ram: 00000000 - 20000000
node 0 bootmap 00001000 - 00005000
(6 early reservations) ==> bootmem [0000000000 - 0020000000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0001000000 - 00012f6154] TEXT DATA BSS ==> [0001000000 - 00012f6154]
#2 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
#3 [00012f7000 - 00012fd000] BRK ==> [00012f7000 - 00012fd000]
#4 [0000007000 - 0000081000] PGTABLE ==> [0000007000 - 0000081000]
#5 [0000001000 - 0000005000] BOOTMAP ==> [0000001000 - 0000005000]
Zone PFN ranges:
DMA 0x00000000 -> 0x00001000
Normal 0x00001000 -> 0x00020000
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000000 -> 0x0000009f
0: 0x00000100 -> 0x00020000
On node 0 totalpages: 130975
free_area_init_node: node 0, pgdat c12a2004, node_mem_map c12fd000
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3967 pages, LIFO batch:0
Normal zone: 992 pages used for memmap
Normal zone: 125984 pages, LIFO batch:31
Allocating PCI resources starting at 20000000 (gap: 20000000:df000000)
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129951
Kernel command line: root=/dev/sda2 quiet video=sisfb:640x480-32
ar8.debug=1 ar8.outputs=0x80 BOOT_IMAGE=vmlinuz-2.6.33-r3-vdx
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Initializing CPU#0
Memory: 515600k/524288k available (1844k kernel code, 8044k reserved,
863k data, 212k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xfffe5000 - 0xfffff000 ( 104 kB)
vmalloc : 0xe0800000 - 0xfffe3000 ( 503 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
.init : 0xc12a5000 - 0xc12da000 ( 212 kB)
.data : 0xc11cd056 - 0xc12a4ed8 ( 863 kB)
.text : 0xc1000000 - 0xc11cd056 (1844 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
Hierarchical RCU implementation.
NR_IRQS:16
Console: colour VGA+ 80x25
console [tty0] enabled
Fast TSC calibration using PIT
Detected 800.001 MHz processor.
Calibrating delay loop (skipped), value calculated using timer
frequency.. 1600.00 BogoMIPS (lpj=3200004)
Mount-cache hash table entries: 512
Performance Events:
CPU: Vortex86 SoC 05/02 stepping 02
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=0
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
pci 0000:00:01.0: reg 10: [io 0xdc00-0xdcff]
pci 0000:00:01.0: reg 14: [mem 0xfefbb000-0xfefbb0ff]
pci 0000:00:01.0: supports D1 D2
pci 0000:00:01.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:00:01.0: PME# disabled
pci 0000:00:02.0: reg 10: [io 0xdd00-0xddff]
pci 0000:00:02.0: reg 14: [mem 0xfefbb400-0xfefbb4ff]
pci 0000:00:02.0: supports D1 D2
pci 0000:00:02.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:00:02.0: PME# disabled
pci 0000:00:03.0: reg 10: [mem 0xf8000000-0xfbffffff pref]
pci 0000:00:03.0: reg 14: [mem 0xfefc0000-0xfeffffff]
pci 0000:00:03.0: reg 18: [io 0xdf80-0xdfff]
pci 0000:00:03.0: supports D1 D2
pci 0000:00:08.0: reg 10: [io 0xde00-0xdeff]
pci 0000:00:08.0: reg 14: [mem 0xfefbb800-0xfefbb8ff]
pci 0000:00:08.0: reg 30: [mem 0xfefa0000-0xfefaffff pref]
pci 0000:00:0b.0: reg 10: [mem 0x000e0000-0x000e0fff]
pci 0000:00:0b.1: reg 10: [mem 0x000e1000-0x000e10ff]
pci 0000:00:0c.0: reg 10: [io 0x01f0-0x01f7]
pci 0000:00:0c.0: reg 14: [io 0x03f4-0x03f7]
pci 0000:00:0c.0: reg 18: [io 0x0170-0x0177]
pci 0000:00:0c.0: reg 1c: [io 0x0374-0x0377]
pci 0000:00:0c.0: reg 20: [io 0xfff0-0xffff]
pci 0000:00:0c.0: reg 30: [mem 0x00000000-0x0001ffff pref]
vgaarb: device added: PCI:0000:00:03.0,decodes=io+mem,owns=io+mem,locks=none
pci 0000:00:07.0: default IRQ router [17f3:6031]
PCI: pci_cache_line_size set to 32 bytes
pci 0000:00:0b.0: address space collision: [mem 0x000e0000-0x000e0fff]
already in use
pci 0000:00:0b.0: can't reserve [mem 0x000e0000-0x000e0fff]
pci 0000:00:0b.1: address space collision: [mem 0x000e1000-0x000e10ff]
already in use
pci 0000:00:0b.1: can't reserve [mem 0x000e1000-0x000e10ff]
Switching to clocksource tsc
pci 0000:00:0c.0: BAR 6: assigned [mem 0x20000000-0x2001ffff pref]
pci 0000:00:0b.0: BAR 0: assigned [mem 0x20020000-0x20020fff]
pci 0000:00:0b.0: BAR 0: set to [mem 0x20020000-0x20020fff] (PCI
address [0x20020000-0x20020fff]
pci 0000:00:0b.1: BAR 0: assigned [mem 0x20021000-0x200210ff]
pci 0000:00:0b.1: BAR 0: set to [mem 0x20021000-0x200210ff] (PCI
address [0x20021000-0x200210ff]
pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
...
-------------------------------------------------------------------
-------------------------------------------------------------------
lspci
-------------------------------------------------------------------
00:00.0 Host bridge: RDC Semiconductor, Inc. Unknown device 6021 (rev 01)
Control: I/O- Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
00:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at dc00 [size=256]
Region 1: Memory at fefbb000 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0-,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 6
Region 0: I/O ports at dd00 [size=256]
Region 1: Memory at fefbb400 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0-,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:03.0 VGA compatible controller: XGI Technology Inc. (eXtreme
Graphics Innovation) Volari Z7 (prog-if 00 [VGA controller])
Subsystem: XGI Technology Inc. (eXtreme Graphics Innovation) Volari Z7
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
BIST result: 00
Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
Region 1: Memory at fefc0000 (32-bit, non-prefetchable) [size=256K]
Region 2: I/O ports at df80 [size=128]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.0 ISA bridge: RDC Semiconductor, Inc. Unknown device 6031 (rev 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=?? >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
00:08.0 Ethernet controller: RDC Semiconductor, Inc. R6040 MAC Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128 (750ns min, 2000ns max)
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at de00 [size=256]
Region 1: Memory at fefbb800 (32-bit, non-prefetchable) [size=256]
Expansion ROM at fefa0000 [disabled] [size=64K]
00:0b.0 USB Controller: RDC Semiconductor, Inc. R6060 USB 1.1
Controller (rev 11) (prog-if 10 [OHCI])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128, Cache Line Size: 16 bytes
Interrupt: pin A routed to IRQ 15
Region 0: Memory at 20020000 (32-bit, non-prefetchable) [size=4K]
00:0b.1 USB Controller: RDC Semiconductor, Inc. R6061 USB 2.0
Controller (rev 02) (prog-if 20 [EHCI])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128, Cache Line Size: 16 bytes
Interrupt: pin B routed to IRQ 9
Region 0: Memory at 20021000 (32-bit, non-prefetchable) [size=256]
00:0c.0 Mass storage controller: RDC Semiconductor, Inc. Unknown
device 1010 (rev 13)
Subsystem: RDC Semiconductor, Inc. Unknown device 1010
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (2000ns min, 2000ns max)
Interrupt: pin A routed to IRQ 14
Region 0: I/O ports at 01f0 [size=8]
Region 1: I/O ports at 03f4 [size=4]
Region 2: I/O ports at 0170 [size=8]
Region 3: I/O ports at 0374 [size=4]
Region 4: I/O ports at fff0 [size=16]
[virtual] Expansion ROM at 20000000 [disabled] [size=128K]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
-------------------------------------------------------------------
-------------------------------------------------------------------
/proc/cpuinfo
-------------------------------------------------------------------
processor : 0
vendor_id : Vortex86 SoC
cpu family : 5
model : 2
model name : 05/02
stepping : 2
cpu MHz : 800.001
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu tsc cx8
bogomips : 1600.00
clflush size : 32
cache_alignment : 32
address sizes : 32 bits physical, 32 bits virtual
power management:
-------------------------------------------------------------------
dmesg kernel 2.6.29:
-------------------------------------------------------------------
...
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
pci 0000:00:01.0: reg 10 io port: [0xdc00-0xdcff]
pci 0000:00:01.0: reg 14 32bit mmio: [0xfefbb000-0xfefbb0ff]
pci 0000:00:01.0: supports D1 D2
pci 0000:00:01.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:00:01.0: PME# disabled
pci 0000:00:02.0: reg 10 io port: [0xdd00-0xddff]
pci 0000:00:02.0: reg 14 32bit mmio: [0xfefbb400-0xfefbb4ff]
pci 0000:00:02.0: supports D1 D2
pci 0000:00:02.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:00:02.0: PME# disabled
pci 0000:00:03.0: reg 10 32bit mmio: [0xf8000000-0xfbffffff]
pci 0000:00:03.0: reg 14 32bit mmio: [0xfefc0000-0xfeffffff]
pci 0000:00:03.0: reg 18 io port: [0xdf80-0xdfff]
pci 0000:00:03.0: supports D1 D2
pci 0000:00:08.0: reg 10 io port: [0xde00-0xdeff]
pci 0000:00:08.0: reg 14 32bit mmio: [0xfefbb800-0xfefbb8ff]
pci 0000:00:08.0: reg 30 32bit mmio: [0xfefa0000-0xfefaffff]
pci 0000:00:0b.0: reg 10 32bit mmio: [0x0e0000-0x0e0fff]
pci 0000:00:0b.1: reg 10 32bit mmio: [0x0e1000-0x0e10ff]
pci 0000:00:0c.0: reg 10 io port: [0x1f0-0x1f7]
pci 0000:00:0c.0: reg 14 io port: [0x3f4-0x3f7]
pci 0000:00:0c.0: reg 18 io port: [0x170-0x177]
pci 0000:00:0c.0: reg 1c io port: [0x374-0x377]
pci 0000:00:0c.0: reg 20 io port: [0xfff0-0xffff]
pci 0000:00:0c.0: reg 30 32bit mmio: [0x000000-0x01ffff]
pci 0000:00:07.0: default IRQ router [17f3:6031]
pci 0000:00:0b.0: BAR 0: can't allocate resource
pci 0000:00:0b.1: BAR 0: can't allocate resource
...
-------------------------------------------------------------------
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PCI conflicts with latest kernels
2010-03-14 10:31 PCI conflicts with latest kernels Giampaolo Bellini
@ 2010-03-14 20:12 ` Rafael J. Wysocki
2010-03-14 21:12 ` Bjorn Helgaas
0 siblings, 1 reply; 8+ messages in thread
From: Rafael J. Wysocki @ 2010-03-14 20:12 UTC (permalink / raw)
To: Giampaolo Bellini; +Cc: linux-kernel, Linux PCI
[CCing linux-pci]
On Sunday 14 March 2010, Giampaolo Bellini wrote:
> Hi all...
>
> I'm experimenting PCI address space collisions on an ICOP PC104
> VDX-6357 motherboard (with no cards/expansion at all) and kernels
> 2.6.33/34
>
> collisions where not there with kernel 2.6.29 (I start with this
> .config and I've done a make oldconfig for 2.6.33/34).
>
> I have no ACPI support and I'm using the sisfb framebuffer on a XGI
> Technology Inc. (eXtreme Graphics Innovation) Volari Z7 chipset.
>
> thanks for any ideas
>
> Paolo
>
>
> here are some info:
>
>
> -------------------------------------------------------------------
> cat /proc/cmdline
> -------------------------------------------------------------------
> root=/dev/sda2 quiet video=sisfb:640x480-32 ar8.debug=1
> ar8.outputs=0x80 BOOT_IMAGE=vmlinuz-2.6.33-r3-vdx
>
>
> -------------------------------------------------------------------
> dmesg kernel 2.6.33:
> -------------------------------------------------------------------
> Linux version 2.6.33-ibty3-vdx (root@nibble) (gcc version 4.2.4
> (Ubuntu 4.2.4-1ubuntu3)) #22 Sun Mar 14 00:35:18 CET 2010
> CPU: vendor_id 'Vortex86 SoC' unknown, using generic init.
> CPU: Your system may be unstable.
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
> BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
> Notice: NX (Execute Disable) protection missing in CPU or disabled in BIOS!
> DMI not present or invalid.
> last_pfn = 0x20000 max_arch_pfn = 0x100000
> initial memory mapped : 0 - 01800000
> init_memory_mapping: 0000000000000000-0000000020000000
> 0000000000 - 0020000000 page 4k
> kernel direct mapping tables up to 20000000 @ 7000-8a000
> 512MB LOWMEM available.
> mapped low ram: 0 - 20000000
> low ram: 0 - 20000000
> node 0 low ram: 00000000 - 20000000
> node 0 bootmap 00001000 - 00005000
> (6 early reservations) ==> bootmem [0000000000 - 0020000000]
> #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
> #1 [0001000000 - 00012f6154] TEXT DATA BSS ==> [0001000000 - 00012f6154]
> #2 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
> #3 [00012f7000 - 00012fd000] BRK ==> [00012f7000 - 00012fd000]
> #4 [0000007000 - 0000081000] PGTABLE ==> [0000007000 - 0000081000]
> #5 [0000001000 - 0000005000] BOOTMAP ==> [0000001000 - 0000005000]
> Zone PFN ranges:
> DMA 0x00000000 -> 0x00001000
> Normal 0x00001000 -> 0x00020000
> Movable zone start PFN for each node
> early_node_map[2] active PFN ranges
> 0: 0x00000000 -> 0x0000009f
> 0: 0x00000100 -> 0x00020000
> On node 0 totalpages: 130975
> free_area_init_node: node 0, pgdat c12a2004, node_mem_map c12fd000
> DMA zone: 32 pages used for memmap
> DMA zone: 0 pages reserved
> DMA zone: 3967 pages, LIFO batch:0
> Normal zone: 992 pages used for memmap
> Normal zone: 125984 pages, LIFO batch:31
> Allocating PCI resources starting at 20000000 (gap: 20000000:df000000)
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129951
> Kernel command line: root=/dev/sda2 quiet video=sisfb:640x480-32
> ar8.debug=1 ar8.outputs=0x80 BOOT_IMAGE=vmlinuz-2.6.33-r3-vdx
> PID hash table entries: 2048 (order: 1, 8192 bytes)
> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> Initializing CPU#0
> Memory: 515600k/524288k available (1844k kernel code, 8044k reserved,
> 863k data, 212k init, 0k highmem)
> virtual kernel memory layout:
> fixmap : 0xfffe5000 - 0xfffff000 ( 104 kB)
> vmalloc : 0xe0800000 - 0xfffe3000 ( 503 MB)
> lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
> .init : 0xc12a5000 - 0xc12da000 ( 212 kB)
> .data : 0xc11cd056 - 0xc12a4ed8 ( 863 kB)
> .text : 0xc1000000 - 0xc11cd056 (1844 kB)
> Checking if this processor honours the WP bit even in supervisor mode...Ok.
> Hierarchical RCU implementation.
> NR_IRQS:16
> Console: colour VGA+ 80x25
> console [tty0] enabled
> Fast TSC calibration using PIT
> Detected 800.001 MHz processor.
> Calibrating delay loop (skipped), value calculated using timer
> frequency.. 1600.00 BogoMIPS (lpj=3200004)
> Mount-cache hash table entries: 512
> Performance Events:
> CPU: Vortex86 SoC 05/02 stepping 02
> Checking 'hlt' instruction... OK.
> NET: Registered protocol family 16
> PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=0
> PCI: Using configuration type 1 for base access
> bio: create slab <bio-0> at 0
> vgaarb: loaded
> SCSI subsystem initialized
> libata version 3.00 loaded.
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> PCI: Probing PCI hardware
> PCI: Probing PCI hardware (bus 00)
> pci 0000:00:01.0: reg 10: [io 0xdc00-0xdcff]
> pci 0000:00:01.0: reg 14: [mem 0xfefbb000-0xfefbb0ff]
> pci 0000:00:01.0: supports D1 D2
> pci 0000:00:01.0: PME# supported from D1 D2 D3hot D3cold
> pci 0000:00:01.0: PME# disabled
> pci 0000:00:02.0: reg 10: [io 0xdd00-0xddff]
> pci 0000:00:02.0: reg 14: [mem 0xfefbb400-0xfefbb4ff]
> pci 0000:00:02.0: supports D1 D2
> pci 0000:00:02.0: PME# supported from D1 D2 D3hot D3cold
> pci 0000:00:02.0: PME# disabled
> pci 0000:00:03.0: reg 10: [mem 0xf8000000-0xfbffffff pref]
> pci 0000:00:03.0: reg 14: [mem 0xfefc0000-0xfeffffff]
> pci 0000:00:03.0: reg 18: [io 0xdf80-0xdfff]
> pci 0000:00:03.0: supports D1 D2
> pci 0000:00:08.0: reg 10: [io 0xde00-0xdeff]
> pci 0000:00:08.0: reg 14: [mem 0xfefbb800-0xfefbb8ff]
> pci 0000:00:08.0: reg 30: [mem 0xfefa0000-0xfefaffff pref]
> pci 0000:00:0b.0: reg 10: [mem 0x000e0000-0x000e0fff]
> pci 0000:00:0b.1: reg 10: [mem 0x000e1000-0x000e10ff]
> pci 0000:00:0c.0: reg 10: [io 0x01f0-0x01f7]
> pci 0000:00:0c.0: reg 14: [io 0x03f4-0x03f7]
> pci 0000:00:0c.0: reg 18: [io 0x0170-0x0177]
> pci 0000:00:0c.0: reg 1c: [io 0x0374-0x0377]
> pci 0000:00:0c.0: reg 20: [io 0xfff0-0xffff]
> pci 0000:00:0c.0: reg 30: [mem 0x00000000-0x0001ffff pref]
> vgaarb: device added: PCI:0000:00:03.0,decodes=io+mem,owns=io+mem,locks=none
> pci 0000:00:07.0: default IRQ router [17f3:6031]
> PCI: pci_cache_line_size set to 32 bytes
>
>
> pci 0000:00:0b.0: address space collision: [mem 0x000e0000-0x000e0fff]
> already in use
> pci 0000:00:0b.0: can't reserve [mem 0x000e0000-0x000e0fff]
> pci 0000:00:0b.1: address space collision: [mem 0x000e1000-0x000e10ff]
> already in use
> pci 0000:00:0b.1: can't reserve [mem 0x000e1000-0x000e10ff]
>
>
> Switching to clocksource tsc
> pci 0000:00:0c.0: BAR 6: assigned [mem 0x20000000-0x2001ffff pref]
> pci 0000:00:0b.0: BAR 0: assigned [mem 0x20020000-0x20020fff]
> pci 0000:00:0b.0: BAR 0: set to [mem 0x20020000-0x20020fff] (PCI
> address [0x20020000-0x20020fff]
> pci 0000:00:0b.1: BAR 0: assigned [mem 0x20021000-0x200210ff]
> pci 0000:00:0b.1: BAR 0: set to [mem 0x20021000-0x200210ff] (PCI
> address [0x20021000-0x200210ff]
> pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
> pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
> ...
> -------------------------------------------------------------------
>
>
> -------------------------------------------------------------------
> lspci
> -------------------------------------------------------------------
> 00:00.0 Host bridge: RDC Semiconductor, Inc. Unknown device 6021 (rev 01)
> Control: I/O- Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
> Latency: 0
>
> 00:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
> Subsystem: Realtek Semiconductor Co., Ltd. RT8139
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 128 (8000ns min, 16000ns max)
> Interrupt: pin A routed to IRQ 9
> Region 0: I/O ports at dc00 [size=256]
> Region 1: Memory at fefbb000 (32-bit, non-prefetchable) [size=256]
> Capabilities: [50] Power Management version 2
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0-,D1+,D2+,D3hot+,D3cold+)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
> Subsystem: Realtek Semiconductor Co., Ltd. RT8139
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 128 (8000ns min, 16000ns max)
> Interrupt: pin A routed to IRQ 6
> Region 0: I/O ports at dd00 [size=256]
> Region 1: Memory at fefbb400 (32-bit, non-prefetchable) [size=256]
> Capabilities: [50] Power Management version 2
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0-,D1+,D2+,D3hot+,D3cold+)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:03.0 VGA compatible controller: XGI Technology Inc. (eXtreme
> Graphics Innovation) Volari Z7 (prog-if 00 [VGA controller])
> Subsystem: XGI Technology Inc. (eXtreme Graphics Innovation) Volari Z7
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> BIST result: 00
> Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
> Region 1: Memory at fefc0000 (32-bit, non-prefetchable) [size=256K]
> Region 2: I/O ports at df80 [size=128]
> Capabilities: [40] Power Management version 2
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:07.0 ISA bridge: RDC Semiconductor, Inc. Unknown device 6031 (rev 01)
> Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=?? >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
>
> 00:08.0 Ethernet controller: RDC Semiconductor, Inc. R6040 MAC Controller
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 128 (750ns min, 2000ns max)
> Interrupt: pin A routed to IRQ 5
> Region 0: I/O ports at de00 [size=256]
> Region 1: Memory at fefbb800 (32-bit, non-prefetchable) [size=256]
> Expansion ROM at fefa0000 [disabled] [size=64K]
>
> 00:0b.0 USB Controller: RDC Semiconductor, Inc. R6060 USB 1.1
> Controller (rev 11) (prog-if 10 [OHCI])
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 128, Cache Line Size: 16 bytes
> Interrupt: pin A routed to IRQ 15
> Region 0: Memory at 20020000 (32-bit, non-prefetchable) [size=4K]
>
> 00:0b.1 USB Controller: RDC Semiconductor, Inc. R6061 USB 2.0
> Controller (rev 02) (prog-if 20 [EHCI])
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 128, Cache Line Size: 16 bytes
> Interrupt: pin B routed to IRQ 9
> Region 0: Memory at 20021000 (32-bit, non-prefetchable) [size=256]
>
> 00:0c.0 Mass storage controller: RDC Semiconductor, Inc. Unknown
> device 1010 (rev 13)
> Subsystem: RDC Semiconductor, Inc. Unknown device 1010
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64 (2000ns min, 2000ns max)
> Interrupt: pin A routed to IRQ 14
> Region 0: I/O ports at 01f0 [size=8]
> Region 1: I/O ports at 03f4 [size=4]
> Region 2: I/O ports at 0170 [size=8]
> Region 3: I/O ports at 0374 [size=4]
> Region 4: I/O ports at fff0 [size=16]
> [virtual] Expansion ROM at 20000000 [disabled] [size=128K]
> Capabilities: [80] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> -------------------------------------------------------------------
>
> -------------------------------------------------------------------
> /proc/cpuinfo
> -------------------------------------------------------------------
> processor : 0
> vendor_id : Vortex86 SoC
> cpu family : 5
> model : 2
> model name : 05/02
> stepping : 2
> cpu MHz : 800.001
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu tsc cx8
> bogomips : 1600.00
> clflush size : 32
> cache_alignment : 32
> address sizes : 32 bits physical, 32 bits virtual
> power management:
>
>
> -------------------------------------------------------------------
> dmesg kernel 2.6.29:
> -------------------------------------------------------------------
> ...
> PCI: Probing PCI hardware
> PCI: Probing PCI hardware (bus 00)
> pci 0000:00:01.0: reg 10 io port: [0xdc00-0xdcff]
> pci 0000:00:01.0: reg 14 32bit mmio: [0xfefbb000-0xfefbb0ff]
> pci 0000:00:01.0: supports D1 D2
> pci 0000:00:01.0: PME# supported from D1 D2 D3hot D3cold
> pci 0000:00:01.0: PME# disabled
> pci 0000:00:02.0: reg 10 io port: [0xdd00-0xddff]
> pci 0000:00:02.0: reg 14 32bit mmio: [0xfefbb400-0xfefbb4ff]
> pci 0000:00:02.0: supports D1 D2
> pci 0000:00:02.0: PME# supported from D1 D2 D3hot D3cold
> pci 0000:00:02.0: PME# disabled
> pci 0000:00:03.0: reg 10 32bit mmio: [0xf8000000-0xfbffffff]
> pci 0000:00:03.0: reg 14 32bit mmio: [0xfefc0000-0xfeffffff]
> pci 0000:00:03.0: reg 18 io port: [0xdf80-0xdfff]
> pci 0000:00:03.0: supports D1 D2
> pci 0000:00:08.0: reg 10 io port: [0xde00-0xdeff]
> pci 0000:00:08.0: reg 14 32bit mmio: [0xfefbb800-0xfefbb8ff]
> pci 0000:00:08.0: reg 30 32bit mmio: [0xfefa0000-0xfefaffff]
> pci 0000:00:0b.0: reg 10 32bit mmio: [0x0e0000-0x0e0fff]
> pci 0000:00:0b.1: reg 10 32bit mmio: [0x0e1000-0x0e10ff]
> pci 0000:00:0c.0: reg 10 io port: [0x1f0-0x1f7]
> pci 0000:00:0c.0: reg 14 io port: [0x3f4-0x3f7]
> pci 0000:00:0c.0: reg 18 io port: [0x170-0x177]
> pci 0000:00:0c.0: reg 1c io port: [0x374-0x377]
> pci 0000:00:0c.0: reg 20 io port: [0xfff0-0xffff]
> pci 0000:00:0c.0: reg 30 32bit mmio: [0x000000-0x01ffff]
> pci 0000:00:07.0: default IRQ router [17f3:6031]
> pci 0000:00:0b.0: BAR 0: can't allocate resource
> pci 0000:00:0b.1: BAR 0: can't allocate resource
> ...
> -------------------------------------------------------------------
> --
> 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/
>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PCI conflicts with latest kernels
2010-03-14 20:12 ` Rafael J. Wysocki
@ 2010-03-14 21:12 ` Bjorn Helgaas
[not found] ` <463bccef1003141611q26229896y5d75b035552ff6fc@mail.gmail.com>
0 siblings, 1 reply; 8+ messages in thread
From: Bjorn Helgaas @ 2010-03-14 21:12 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: Giampaolo Bellini, linux-kernel, Linux PCI
On Sun, 2010-03-14 at 21:12 +0100, Rafael J. Wysocki wrote:
> [CCing linux-pci]
>
> On Sunday 14 March 2010, Giampaolo Bellini wrote:
> > Hi all...
> >
> > I'm experimenting PCI address space collisions on an ICOP PC104
> > VDX-6357 motherboard (with no cards/expansion at all) and kernels
> > 2.6.33/34
> >
> > collisions where not there with kernel 2.6.29 (I start with this
> > .config and I've done a make oldconfig for 2.6.33/34).
> >
> > I have no ACPI support and I'm using the sisfb framebuffer on a XGI
> > Technology Inc. (eXtreme Graphics Innovation) Volari Z7 chipset.
If you apply the patches here: http://lkml.org/lkml/2010/3/11/512
on 2.6.34-rc1, you'll get a little more information about the
collisions. /proc/iomem may also be helpful.
The messages have changed somewhat between 2.6.29 and the current
kernel, but from the snippets you posted, I don't see any functional
differences.
Bjorn
> > -------------------------------------------------------------------
> > cat /proc/cmdline
> > -------------------------------------------------------------------
> > root=/dev/sda2 quiet video=sisfb:640x480-32 ar8.debug=1
> > ar8.outputs=0x80 BOOT_IMAGE=vmlinuz-2.6.33-r3-vdx
> >
> >
> > -------------------------------------------------------------------
> > dmesg kernel 2.6.33:
> > -------------------------------------------------------------------
> > Linux version 2.6.33-ibty3-vdx (root@nibble) (gcc version 4.2.4
> > (Ubuntu 4.2.4-1ubuntu3)) #22 Sun Mar 14 00:35:18 CET 2010
> > CPU: vendor_id 'Vortex86 SoC' unknown, using generic init.
> > CPU: Your system may be unstable.
> > BIOS-provided physical RAM map:
> > BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> > BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> > BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> > BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
> > BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
> > Notice: NX (Execute Disable) protection missing in CPU or disabled in BIOS!
> > DMI not present or invalid.
> > last_pfn = 0x20000 max_arch_pfn = 0x100000
> > initial memory mapped : 0 - 01800000
> > init_memory_mapping: 0000000000000000-0000000020000000
> > 0000000000 - 0020000000 page 4k
> > kernel direct mapping tables up to 20000000 @ 7000-8a000
> > 512MB LOWMEM available.
> > mapped low ram: 0 - 20000000
> > low ram: 0 - 20000000
> > node 0 low ram: 00000000 - 20000000
> > node 0 bootmap 00001000 - 00005000
> > (6 early reservations) ==> bootmem [0000000000 - 0020000000]
> > #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
> > #1 [0001000000 - 00012f6154] TEXT DATA BSS ==> [0001000000 - 00012f6154]
> > #2 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
> > #3 [00012f7000 - 00012fd000] BRK ==> [00012f7000 - 00012fd000]
> > #4 [0000007000 - 0000081000] PGTABLE ==> [0000007000 - 0000081000]
> > #5 [0000001000 - 0000005000] BOOTMAP ==> [0000001000 - 0000005000]
> > Zone PFN ranges:
> > DMA 0x00000000 -> 0x00001000
> > Normal 0x00001000 -> 0x00020000
> > Movable zone start PFN for each node
> > early_node_map[2] active PFN ranges
> > 0: 0x00000000 -> 0x0000009f
> > 0: 0x00000100 -> 0x00020000
> > On node 0 totalpages: 130975
> > free_area_init_node: node 0, pgdat c12a2004, node_mem_map c12fd000
> > DMA zone: 32 pages used for memmap
> > DMA zone: 0 pages reserved
> > DMA zone: 3967 pages, LIFO batch:0
> > Normal zone: 992 pages used for memmap
> > Normal zone: 125984 pages, LIFO batch:31
> > Allocating PCI resources starting at 20000000 (gap: 20000000:df000000)
> > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129951
> > Kernel command line: root=/dev/sda2 quiet video=sisfb:640x480-32
> > ar8.debug=1 ar8.outputs=0x80 BOOT_IMAGE=vmlinuz-2.6.33-r3-vdx
> > PID hash table entries: 2048 (order: 1, 8192 bytes)
> > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> > Initializing CPU#0
> > Memory: 515600k/524288k available (1844k kernel code, 8044k reserved,
> > 863k data, 212k init, 0k highmem)
> > virtual kernel memory layout:
> > fixmap : 0xfffe5000 - 0xfffff000 ( 104 kB)
> > vmalloc : 0xe0800000 - 0xfffe3000 ( 503 MB)
> > lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
> > .init : 0xc12a5000 - 0xc12da000 ( 212 kB)
> > .data : 0xc11cd056 - 0xc12a4ed8 ( 863 kB)
> > .text : 0xc1000000 - 0xc11cd056 (1844 kB)
> > Checking if this processor honours the WP bit even in supervisor mode...Ok.
> > Hierarchical RCU implementation.
> > NR_IRQS:16
> > Console: colour VGA+ 80x25
> > console [tty0] enabled
> > Fast TSC calibration using PIT
> > Detected 800.001 MHz processor.
> > Calibrating delay loop (skipped), value calculated using timer
> > frequency.. 1600.00 BogoMIPS (lpj=3200004)
> > Mount-cache hash table entries: 512
> > Performance Events:
> > CPU: Vortex86 SoC 05/02 stepping 02
> > Checking 'hlt' instruction... OK.
> > NET: Registered protocol family 16
> > PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=0
> > PCI: Using configuration type 1 for base access
> > bio: create slab <bio-0> at 0
> > vgaarb: loaded
> > SCSI subsystem initialized
> > libata version 3.00 loaded.
> > usbcore: registered new interface driver usbfs
> > usbcore: registered new interface driver hub
> > usbcore: registered new device driver usb
> > PCI: Probing PCI hardware
> > PCI: Probing PCI hardware (bus 00)
> > pci 0000:00:01.0: reg 10: [io 0xdc00-0xdcff]
> > pci 0000:00:01.0: reg 14: [mem 0xfefbb000-0xfefbb0ff]
> > pci 0000:00:01.0: supports D1 D2
> > pci 0000:00:01.0: PME# supported from D1 D2 D3hot D3cold
> > pci 0000:00:01.0: PME# disabled
> > pci 0000:00:02.0: reg 10: [io 0xdd00-0xddff]
> > pci 0000:00:02.0: reg 14: [mem 0xfefbb400-0xfefbb4ff]
> > pci 0000:00:02.0: supports D1 D2
> > pci 0000:00:02.0: PME# supported from D1 D2 D3hot D3cold
> > pci 0000:00:02.0: PME# disabled
> > pci 0000:00:03.0: reg 10: [mem 0xf8000000-0xfbffffff pref]
> > pci 0000:00:03.0: reg 14: [mem 0xfefc0000-0xfeffffff]
> > pci 0000:00:03.0: reg 18: [io 0xdf80-0xdfff]
> > pci 0000:00:03.0: supports D1 D2
> > pci 0000:00:08.0: reg 10: [io 0xde00-0xdeff]
> > pci 0000:00:08.0: reg 14: [mem 0xfefbb800-0xfefbb8ff]
> > pci 0000:00:08.0: reg 30: [mem 0xfefa0000-0xfefaffff pref]
> > pci 0000:00:0b.0: reg 10: [mem 0x000e0000-0x000e0fff]
> > pci 0000:00:0b.1: reg 10: [mem 0x000e1000-0x000e10ff]
> > pci 0000:00:0c.0: reg 10: [io 0x01f0-0x01f7]
> > pci 0000:00:0c.0: reg 14: [io 0x03f4-0x03f7]
> > pci 0000:00:0c.0: reg 18: [io 0x0170-0x0177]
> > pci 0000:00:0c.0: reg 1c: [io 0x0374-0x0377]
> > pci 0000:00:0c.0: reg 20: [io 0xfff0-0xffff]
> > pci 0000:00:0c.0: reg 30: [mem 0x00000000-0x0001ffff pref]
> > vgaarb: device added: PCI:0000:00:03.0,decodes=io+mem,owns=io+mem,locks=none
> > pci 0000:00:07.0: default IRQ router [17f3:6031]
> > PCI: pci_cache_line_size set to 32 bytes
> >
> >
> > pci 0000:00:0b.0: address space collision: [mem 0x000e0000-0x000e0fff]
> > already in use
> > pci 0000:00:0b.0: can't reserve [mem 0x000e0000-0x000e0fff]
> > pci 0000:00:0b.1: address space collision: [mem 0x000e1000-0x000e10ff]
> > already in use
> > pci 0000:00:0b.1: can't reserve [mem 0x000e1000-0x000e10ff]
> >
> >
> > Switching to clocksource tsc
> > pci 0000:00:0c.0: BAR 6: assigned [mem 0x20000000-0x2001ffff pref]
> > pci 0000:00:0b.0: BAR 0: assigned [mem 0x20020000-0x20020fff]
> > pci 0000:00:0b.0: BAR 0: set to [mem 0x20020000-0x20020fff] (PCI
> > address [0x20020000-0x20020fff]
> > pci 0000:00:0b.1: BAR 0: assigned [mem 0x20021000-0x200210ff]
> > pci 0000:00:0b.1: BAR 0: set to [mem 0x20021000-0x200210ff] (PCI
> > address [0x20021000-0x200210ff]
> > pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
> > pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
> > ...
> > -------------------------------------------------------------------
> >
> >
> > -------------------------------------------------------------------
> > lspci
> > -------------------------------------------------------------------
> > 00:00.0 Host bridge: RDC Semiconductor, Inc. Unknown device 6021 (rev 01)
> > Control: I/O- Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
> > ParErr- Stepping- SERR- FastB2B-
> > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> > >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
> > Latency: 0
> >
> > 00:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> > RTL-8139/8139C/8139C+ (rev 10)
> > Subsystem: Realtek Semiconductor Co., Ltd. RT8139
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR+ FastB2B-
> > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > Latency: 128 (8000ns min, 16000ns max)
> > Interrupt: pin A routed to IRQ 9
> > Region 0: I/O ports at dc00 [size=256]
> > Region 1: Memory at fefbb000 (32-bit, non-prefetchable) [size=256]
> > Capabilities: [50] Power Management version 2
> > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> > PME(D0-,D1+,D2+,D3hot+,D3cold+)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> > RTL-8139/8139C/8139C+ (rev 10)
> > Subsystem: Realtek Semiconductor Co., Ltd. RT8139
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR+ FastB2B-
> > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > Latency: 128 (8000ns min, 16000ns max)
> > Interrupt: pin A routed to IRQ 6
> > Region 0: I/O ports at dd00 [size=256]
> > Region 1: Memory at fefbb400 (32-bit, non-prefetchable) [size=256]
> > Capabilities: [50] Power Management version 2
> > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> > PME(D0-,D1+,D2+,D3hot+,D3cold+)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:03.0 VGA compatible controller: XGI Technology Inc. (eXtreme
> > Graphics Innovation) Volari Z7 (prog-if 00 [VGA controller])
> > Subsystem: XGI Technology Inc. (eXtreme Graphics Innovation) Volari Z7
> > Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR- FastB2B-
> > Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > BIST result: 00
> > Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
> > Region 1: Memory at fefc0000 (32-bit, non-prefetchable) [size=256K]
> > Region 2: I/O ports at df80 [size=128]
> > Capabilities: [40] Power Management version 2
> > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
> > PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:07.0 ISA bridge: RDC Semiconductor, Inc. Unknown device 6031 (rev 01)
> > Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
> > ParErr- Stepping- SERR- FastB2B-
> > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=?? >TAbort-
> > <TAbort- <MAbort- >SERR- <PERR-
> > Latency: 0
> >
> > 00:08.0 Ethernet controller: RDC Semiconductor, Inc. R6040 MAC Controller
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR- FastB2B-
> > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > Latency: 128 (750ns min, 2000ns max)
> > Interrupt: pin A routed to IRQ 5
> > Region 0: I/O ports at de00 [size=256]
> > Region 1: Memory at fefbb800 (32-bit, non-prefetchable) [size=256]
> > Expansion ROM at fefa0000 [disabled] [size=64K]
> >
> > 00:0b.0 USB Controller: RDC Semiconductor, Inc. R6060 USB 1.1
> > Controller (rev 11) (prog-if 10 [OHCI])
> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR+ FastB2B-
> > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > Latency: 128, Cache Line Size: 16 bytes
> > Interrupt: pin A routed to IRQ 15
> > Region 0: Memory at 20020000 (32-bit, non-prefetchable) [size=4K]
> >
> > 00:0b.1 USB Controller: RDC Semiconductor, Inc. R6061 USB 2.0
> > Controller (rev 02) (prog-if 20 [EHCI])
> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR+ FastB2B-
> > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > Latency: 128, Cache Line Size: 16 bytes
> > Interrupt: pin B routed to IRQ 9
> > Region 0: Memory at 20021000 (32-bit, non-prefetchable) [size=256]
> >
> > 00:0c.0 Mass storage controller: RDC Semiconductor, Inc. Unknown
> > device 1010 (rev 13)
> > Subsystem: RDC Semiconductor, Inc. Unknown device 1010
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR- FastB2B-
> > Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > Latency: 64 (2000ns min, 2000ns max)
> > Interrupt: pin A routed to IRQ 14
> > Region 0: I/O ports at 01f0 [size=8]
> > Region 1: I/O ports at 03f4 [size=4]
> > Region 2: I/O ports at 0170 [size=8]
> > Region 3: I/O ports at 0374 [size=4]
> > Region 4: I/O ports at fff0 [size=16]
> > [virtual] Expansion ROM at 20000000 [disabled] [size=128K]
> > Capabilities: [80] Power Management version 2
> > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> > PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> > -------------------------------------------------------------------
> >
> > -------------------------------------------------------------------
> > /proc/cpuinfo
> > -------------------------------------------------------------------
> > processor : 0
> > vendor_id : Vortex86 SoC
> > cpu family : 5
> > model : 2
> > model name : 05/02
> > stepping : 2
> > cpu MHz : 800.001
> > fdiv_bug : no
> > hlt_bug : no
> > f00f_bug : no
> > coma_bug : no
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 1
> > wp : yes
> > flags : fpu tsc cx8
> > bogomips : 1600.00
> > clflush size : 32
> > cache_alignment : 32
> > address sizes : 32 bits physical, 32 bits virtual
> > power management:
> >
> >
> > -------------------------------------------------------------------
> > dmesg kernel 2.6.29:
> > -------------------------------------------------------------------
> > ...
> > PCI: Probing PCI hardware
> > PCI: Probing PCI hardware (bus 00)
> > pci 0000:00:01.0: reg 10 io port: [0xdc00-0xdcff]
> > pci 0000:00:01.0: reg 14 32bit mmio: [0xfefbb000-0xfefbb0ff]
> > pci 0000:00:01.0: supports D1 D2
> > pci 0000:00:01.0: PME# supported from D1 D2 D3hot D3cold
> > pci 0000:00:01.0: PME# disabled
> > pci 0000:00:02.0: reg 10 io port: [0xdd00-0xddff]
> > pci 0000:00:02.0: reg 14 32bit mmio: [0xfefbb400-0xfefbb4ff]
> > pci 0000:00:02.0: supports D1 D2
> > pci 0000:00:02.0: PME# supported from D1 D2 D3hot D3cold
> > pci 0000:00:02.0: PME# disabled
> > pci 0000:00:03.0: reg 10 32bit mmio: [0xf8000000-0xfbffffff]
> > pci 0000:00:03.0: reg 14 32bit mmio: [0xfefc0000-0xfeffffff]
> > pci 0000:00:03.0: reg 18 io port: [0xdf80-0xdfff]
> > pci 0000:00:03.0: supports D1 D2
> > pci 0000:00:08.0: reg 10 io port: [0xde00-0xdeff]
> > pci 0000:00:08.0: reg 14 32bit mmio: [0xfefbb800-0xfefbb8ff]
> > pci 0000:00:08.0: reg 30 32bit mmio: [0xfefa0000-0xfefaffff]
> > pci 0000:00:0b.0: reg 10 32bit mmio: [0x0e0000-0x0e0fff]
> > pci 0000:00:0b.1: reg 10 32bit mmio: [0x0e1000-0x0e10ff]
> > pci 0000:00:0c.0: reg 10 io port: [0x1f0-0x1f7]
> > pci 0000:00:0c.0: reg 14 io port: [0x3f4-0x3f7]
> > pci 0000:00:0c.0: reg 18 io port: [0x170-0x177]
> > pci 0000:00:0c.0: reg 1c io port: [0x374-0x377]
> > pci 0000:00:0c.0: reg 20 io port: [0xfff0-0xffff]
> > pci 0000:00:0c.0: reg 30 32bit mmio: [0x000000-0x01ffff]
> > pci 0000:00:07.0: default IRQ router [17f3:6031]
> > pci 0000:00:0b.0: BAR 0: can't allocate resource
> > pci 0000:00:0b.1: BAR 0: can't allocate resource
> > ...
> > -------------------------------------------------------------------
> > --
> > 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/
> >
> >
>
> --
> 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/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PCI conflicts with latest kernels
[not found] ` <463bccef1003141611q26229896y5d75b035552ff6fc@mail.gmail.com>
@ 2010-03-15 15:42 ` Bjorn Helgaas
2010-03-22 14:41 ` Otavio Salvador
0 siblings, 1 reply; 8+ messages in thread
From: Bjorn Helgaas @ 2010-03-15 15:42 UTC (permalink / raw)
To: Giampaolo Bellini; +Cc: Linux PCI, linux-kernel, Rafael J. Wysocki
[I re-added the CC: list, so the archives will have the whole
conversation, in case anybody else has similar problems or
can help answer this.]
On Sunday 14 March 2010 05:11:55 pm Giampaolo Bellini wrote:
> I apply the patch but seems that it does not solve conflicts
Yes, I didn't expect it to fix anything, only to tell us more about
what's happening.
But from your dmesg, I think the problem is that the e820 map reserves
0xe0000-0x100000, and then PCI device 0b.0 has a BAR programmed to part
of that same region:
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
pci 0000:00:0b.0: reg 10: [mem 0x000e0000-0x000e0fff]
pci 0000:00:0b.0: address space collision: [mem 0x000e0000-0x000e0fff] already in use
I don't know enough about the e820 map to know whether this is a bug in
the e820 map or a problem in the PCI BAR programming, or what.
> as far I understand, the problem was there also with 2.6.29 but was not
> logged the same way and/or with the same debug-level due to changes made in
> *drivers/pci/setup-res.c* (expecially in pci_claim_resource()))
Yes. In 2.6.29, pcibios_allocate_resources() used request_resource()
directly and logged errors with dev_info(). In 2.6.34-rc1, we use
pci_claim_resource(), which calls request_resource() and logs errors
with dev_err(), so we now have a higher priority message than we used
to have.
> machine, however, seems stable... for me the problem is that I'm trying to
> avoid text-messages during boot stage and printk(KERN_ERR "message") cause
> the system to switch in text mode & show such errors...
If you only want to hide the message, you can use "loglevel=2".
> as you can see, I've try also with pci=use_crs
Since you don't have ACPI, pci=use_crs and pci=nocrs are not relevant
for your system.
Bjorn
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PCI conflicts with latest kernels
2010-03-15 15:42 ` Bjorn Helgaas
@ 2010-03-22 14:41 ` Otavio Salvador
2010-03-22 14:50 ` Bjorn Helgaas
0 siblings, 1 reply; 8+ messages in thread
From: Otavio Salvador @ 2010-03-22 14:41 UTC (permalink / raw)
To: Bjorn Helgaas
Cc: Giampaolo Bellini, Linux PCI, linux-kernel, Rafael J. Wysocki
Hello,
On Mon, Mar 15, 2010 at 12:42 PM, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> [I re-added the CC: list, so the archives will have the whole
> conversation, in case anybody else has similar problems or
> can help answer this.]
>
> On Sunday 14 March 2010 05:11:55 pm Giampaolo Bellini wrote:
>> I apply the patch but seems that it does not solve conflicts
>
> Yes, I didn't expect it to fix anything, only to tell us more about
> what's happening.
Has any progress been done in this issue?
I have this same problem in VortexSX machine.
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PCI conflicts with latest kernels
2010-03-22 14:41 ` Otavio Salvador
@ 2010-03-22 14:50 ` Bjorn Helgaas
2010-03-22 21:27 ` Otavio Salvador
0 siblings, 1 reply; 8+ messages in thread
From: Bjorn Helgaas @ 2010-03-22 14:50 UTC (permalink / raw)
To: Otavio Salvador
Cc: Giampaolo Bellini, Linux PCI, linux-kernel, Rafael J. Wysocki
On Monday 22 March 2010 08:41:03 am Otavio Salvador wrote:
> Hello,
>
> On Mon, Mar 15, 2010 at 12:42 PM, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> > [I re-added the CC: list, so the archives will have the whole
> > conversation, in case anybody else has similar problems or
> > can help answer this.]
> >
> > On Sunday 14 March 2010 05:11:55 pm Giampaolo Bellini wrote:
> >> I apply the patch but seems that it does not solve conflicts
> >
> > Yes, I didn't expect it to fix anything, only to tell us more about
> > what's happening.
>
> Has any progress been done in this issue?
>
> I have this same problem in VortexSX machine.
Hi Otavio,
Can you post your entire dmesg log and a description of what
problem you're seeing (e.g., device X doesn't work or whatever)?
If this is a regression, i.e., your system used to work and
now doesn't work, please tell us which version used to work
and when it broke.
Thanks,
Bjorn
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PCI conflicts with latest kernels
2010-03-22 14:50 ` Bjorn Helgaas
@ 2010-03-22 21:27 ` Otavio Salvador
2010-03-22 22:18 ` Bjorn Helgaas
0 siblings, 1 reply; 8+ messages in thread
From: Otavio Salvador @ 2010-03-22 21:27 UTC (permalink / raw)
To: Bjorn Helgaas
Cc: Giampaolo Bellini, Linux PCI, linux-kernel, Rafael J. Wysocki
Hello Bjorn,
On Mon, Mar 22, 2010 at 11:50 AM, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Monday 22 March 2010 08:41:03 am Otavio Salvador wrote:
>> I have this same problem in VortexSX machine.
> Can you post your entire dmesg log and a description of what
> problem you're seeing (e.g., device X doesn't work or whatever)?
> If this is a regression, i.e., your system used to work and
> now doesn't work, please tell us which version used to work
> and when it broke.
This has already been done at http://article.gmane.org/gmane.linux.kernel/916237
Cheers,
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PCI conflicts with latest kernels
2010-03-22 21:27 ` Otavio Salvador
@ 2010-03-22 22:18 ` Bjorn Helgaas
0 siblings, 0 replies; 8+ messages in thread
From: Bjorn Helgaas @ 2010-03-22 22:18 UTC (permalink / raw)
To: Otavio Salvador
Cc: Giampaolo Bellini, Linux PCI, linux-kernel, Rafael J. Wysocki
On Monday 22 March 2010 03:27:18 pm Otavio Salvador wrote:
> Hello Bjorn,
>
> On Mon, Mar 22, 2010 at 11:50 AM, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> > On Monday 22 March 2010 08:41:03 am Otavio Salvador wrote:
> >> I have this same problem in VortexSX machine.
> > Can you post your entire dmesg log and a description of what
> > problem you're seeing (e.g., device X doesn't work or whatever)?
> > If this is a regression, i.e., your system used to work and
> > now doesn't work, please tell us which version used to work
> > and when it broke.
Since you don't mention any working version, I assume that Linux
has never worked correctly on this system.
> This has already been done at http://article.gmane.org/gmane.linux.kernel/916237
That post is about the fact that your disk doesn't work unless you
use "irqpoll". That just means the interrupts don't appear where
we expect them, which has nothing to do with the PCI address space
collisions.
I'm sorry I don't know enough about interrupts to help more. If
I were debugging it, I would start by adding printks to the
pirq_enable_irq() path and see if I could figure out why it works
for some devices, but for IDE.
Bjorn
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2010-03-22 22:18 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-03-14 10:31 PCI conflicts with latest kernels Giampaolo Bellini
2010-03-14 20:12 ` Rafael J. Wysocki
2010-03-14 21:12 ` Bjorn Helgaas
[not found] ` <463bccef1003141611q26229896y5d75b035552ff6fc@mail.gmail.com>
2010-03-15 15:42 ` Bjorn Helgaas
2010-03-22 14:41 ` Otavio Salvador
2010-03-22 14:50 ` Bjorn Helgaas
2010-03-22 21:27 ` Otavio Salvador
2010-03-22 22:18 ` Bjorn Helgaas
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).