MPC8641D PCI-Express error

MPC8641D PCI-Express error

[Marco Stornelli]

Hi,

I'm working with the Freescale evaluation board MPC8641DHPCN and the
VIRTEX5 evaluation board ML555 connected with the PCI-Express. When I
try to read some register I have this problem:

Machine check in kernel mode.
Caused by (from SRR1=149030): Transfer error ack signal
Oops: Machine check, sig: 7 [#1]
PREEMPT SMP NR_CPUS=2
Modules linked in: virtex5
LTT NESTING LEVEL : 0
NIP: F108019C LR: F1080198 CTR: 00000001
REGS: c044dd60 TRAP: 0200   Tainted: GF      (2.6.18-mpc8641d_hpcn)
MSR: 00149030 <EE,ME,IR,DR>  CR: 22000222  XER: 00000000
TASK = c20e9990[568] 'insmod' THREAD: c044c000 CPU: 0
GPR00: F1080198 C044DE10 C20E9990 0000002E 80000000 FFFFFFFF 00008000
00002EA3
GPR08: C20E9990 00000000 C04C0220 C044C000 22000222 1001956C 00000000
00000000
GPR16: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
GPR24: 3000EAA0 7FD6FDC0 00000000 C045FCC0 F107E594 F10A0000 00000000
C2036000
NIP [F108019C] virtex5_probe+0x130/0x1c4 [virtex5]
LR [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5]
Call Trace:
[C044DE10] [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5] (unreliable)
[C044DE30] [C01D2A58] pci_device_probe+0x84/0xbc
[C044DE50] [C0213754] driver_probe_device+0x60/0x118
[C044DE70] [C0213890] __driver_attach+0x84/0x88
[C044DE90] [C02130F4] bus_for_each_dev+0x58/0x94
[C044DEC0] [C02135D4] driver_attach+0x24/0x34
[C044DED0] [C0212AC8] bus_add_driver+0x88/0x164
[C044DEF0] [C021397C] driver_register+0x70/0xb8
[C044DF00] [C01D284C] __pci_register_driver+0x64/0x98
[C044DF10] [F1080030] init_module+0x30/0x6c [virtex5]
[C044DF20] [C004CBFC] sys_init_module+0xc8/0x25c
[C044DF40] [C0011358] ret_from_syscall+0x0/0x38
--- Exception: c00 at 0xff6de0c
    LR = 0x10000de4
Instruction dump:
40820060 3c60f108 3863cea0 48000311 807f0238 3c800001 48000395 7c7d1b78
3c60f108 3863ced4 480002f5 809d0000 <3c60f108> 3863cf04 480002e5 3c60f108

Have you got any suggestions?

Thanks.

Marco

Re: MPC8641D PCI-Express error

[Jon Loeliger]

Marco Stornelli wrote:
> Hi,
> 
> I'm working with the Freescale evaluation board MPC8641DHPCN and the
> VIRTEX5 evaluation board ML555 connected with the PCI-Express. When I
> try to read some register I have this problem:
> 
> Machine check in kernel mode.


Any chance you can tell us what rev anything is?
SoC, Board, Kernel?

Significant improvement went into the 2.6.24 kernel
development effort for many FSL PCI/PCI-E parts.

Thanks,
jdl

Re: MPC8641D PCI-Express error

[Marco Stornelli]

Jon Loeliger ha scritto:
> Marco Stornelli wrote:
>> Hi,
>>
>> I'm working with the Freescale evaluation board MPC8641DHPCN and the
>> VIRTEX5 evaluation board ML555 connected with the PCI-Express. When I
>> try to read some register I have this problem:
>>
>> Machine check in kernel mode.
> 
> 
> Any chance you can tell us what rev anything is?
> SoC, Board, Kernel?
> 
> Significant improvement went into the 2.6.24 kernel
> development effort for many FSL PCI/PCI-E parts.
> 
> Thanks,
> jdl
> 

Board: MPC8641D HPCN
SoC: MPC8641D rev. 2
Kernel: 2.6.18

Thanks.

Marco

Re: MPC8641D PCI-Express error

[Jon Loeliger]

Marco Stornelli wrote:
> 
> Board: MPC8641D HPCN
> SoC: MPC8641D rev. 2

OK, this is good.

> Kernel: 2.6.18

And this is really old.  Any chance of up-rev'ing
that to something modern like 2.6.24?  You may find
that your PCI-E issues are Just Fixed there.  Dunno.

HTH,
jdl

Re: MPC8641D PCI-Express error

[Marco Stornelli]

Jon Loeliger ha scritto:
> Marco Stornelli wrote:
>>
>> Board: MPC8641D HPCN
>> SoC: MPC8641D rev. 2
> 
> OK, this is good.
> 
>> Kernel: 2.6.18
> 
> And this is really old.  Any chance of up-rev'ing
> that to something modern like 2.6.24?  You may find
> that your PCI-E issues are Just Fixed there.  Dunno.
> 
> HTH,
> jdl
> 

No, but I can try to backport the PCI-E code from 2.6.24 to 2.6.18 if it
could help. What do you think about it? Do you think this problem could
be not present in 2.6.24?

Re: MPC8641D PCI-Express error

[Jon Loeliger]

Marco Stornelli wrote:

> No, but I can try to backport the PCI-E code from 2.6.24 to 2.6.18 if it
> could help. What do you think about it? Do you think this problem could
> be not present in 2.6.24?

I have no idea there, honestly.  Sorry.

jdl

Re: MPC8641D PCI-Express error

[Kumar Gala]

On Feb 19, 2008, at 10:59 AM, Jon Loeliger wrote:

> Marco Stornelli wrote:
>
>> No, but I can try to backport the PCI-E code from 2.6.24 to 2.6.18  
>> if it
>> could help. What do you think about it? Do you think this problem  
>> could
>> be not present in 2.6.24?
>
> I have no idea there, honestly.  Sorry.

As Jon said, try 2.6.24 and see if it has an issue, if so we can look  
at helping.  if not, you know you need to back port the fixes.

- k

Re: MPC8641D PCI-Express error

[Marco Stornelli]

Kumar Gala wrote:
>> Marco Stornelli wrote:
>>
>>> No, but I can try to backport the PCI-E code from 2.6.24 to 2.6.18
>>> if it could help. What do you think about it? Do you think this
>>> problem could be not present in 2.6.24?
>>> I have no idea there, honestly.  Sorry.

>As Jon said, try 2.6.24 and see if it has an issue, if so we can look
>at helping.  if not, you know you need to back port the fixes.

>- k

I've "backported" the PCI-Express code from 2.6.24 to 2.6.18, but it
still doesn't work, I have the same problem (sigh), could you give me
any suggestions?

Thanks.

Marco

Re: MPC8641D PCI-Express error

[Kumar Gala]

On Feb 20, 2008, at 10:13 AM, Marco Stornelli wrote:

> Kumar Gala wrote:
>>> Marco Stornelli wrote:
>>>
>>>> No, but I can try to backport the PCI-E code from 2.6.24 to 2.6.18
>>>> if it could help. What do you think about it? Do you think this
>>>> problem could be not present in 2.6.24?
>>>> I have no idea there, honestly.  Sorry.
>
>> As Jon said, try 2.6.24 and see if it has an issue, if so we can look
>> at helping.  if not, you know you need to back port the fixes.
>
>> - k
>
> I've "backported" the PCI-Express code from 2.6.24 to 2.6.18, but it
> still doesn't work, I have the same problem (sigh), could you give me
> any suggestions?

did 2.6.24 work for you or not?

- k

Re: MPC8641D PCI-Express error

[Marco Stornelli]

Kumar Gala ha scritto:
> 
> On Feb 20, 2008, at 10:13 AM, Marco Stornelli wrote:
> 
>> Kumar Gala wrote:
>>>> Marco Stornelli wrote:
>>>>
>>>>> No, but I can try to backport the PCI-E code from 2.6.24 to 2.6.18
>>>>> if it could help. What do you think about it? Do you think this
>>>>> problem could be not present in 2.6.24?
>>>>> I have no idea there, honestly.  Sorry.
>>
>>> As Jon said, try 2.6.24 and see if it has an issue, if so we can look
>>> at helping.  if not, you know you need to back port the fixes.
>>
>>> - k
>>
>> I've "backported" the PCI-Express code from 2.6.24 to 2.6.18, but it
>> still doesn't work, I have the same problem (sigh), could you give me
>> any suggestions?
> 
> did 2.6.24 work for you or not?
> 
> - k
> 
No, it didn't. I have the same problem even with the 2.6.18 plus the
2.6.24 PCI-Express code. I performed this action because I can't change
kernel version but I can modify it.

Marco

Re: MPC8641D PCI-Express error

[Timur Tabi]

Marco Stornelli wrote:

> No, it didn't. I have the same problem even with the 2.6.18 plus the
> 2.6.24 PCI-Express code. I performed this action because I can't change
> kernel version but I can modify it.

Please try 2.6.24 (or even better, 2.6.25-rc2).  You may have done something 
wrong in back-porting the code to 2.6.18.  There's no reason why you can't at 
least try the latest version of the code for testing purposes, even if you can't 
use it in production.

-- 
Timur Tabi
Linux kernel developer at Freescale

Re: MPC8641D PCI-Express error

[Jon Loeliger]

Timur Tabi wrote:
> Marco Stornelli wrote:
> 
>> No, it didn't. I have the same problem even with the 2.6.18 plus the
>> 2.6.24 PCI-Express code. I performed this action because I can't change
>> kernel version but I can modify it.
> 
> Please try 2.6.24 (or even better, 2.6.25-rc2).  You may have done something 
> wrong in back-porting the code to 2.6.18.  There's no reason why you can't at 
> least try the latest version of the code for testing purposes, even if you can't 
> use it in production.
> 

Also, once you back-ported it and all the DTS changes, and all
the fsl_soc.c changes needed and , and, and otherwise made it
look _like_, 2.6.24 but still called it 2.6.18, after all that,
can you remind us what was the error or failure mode that you saw?

jdl

Re: MPC8641D PCI-Express error

[Marco Stornelli]

Jon Loeliger ha scritto:
> Timur Tabi wrote:
>> Marco Stornelli wrote:
>>
>>> No, it didn't. I have the same problem even with the 2.6.18 plus the
>>> 2.6.24 PCI-Express code. I performed this action because I can't change
>>> kernel version but I can modify it.
>>
>> Please try 2.6.24 (or even better, 2.6.25-rc2).  You may have done
>> something wrong in back-porting the code to 2.6.18.  There's no reason
>> why you can't at least try the latest version of the code for testing
>> purposes, even if you can't use it in production.
>>
> 
> Also, once you back-ported it and all the DTS changes, and all
> the fsl_soc.c changes needed and , and, and otherwise made it
> look _like_, 2.6.24 but still called it 2.6.18, after all that,
> can you remind us what was the error or failure mode that you saw?
> 
> jdl
> 
> 

When I try to read some register from my FPGA (virtex5) I have this bus
error:

Machine check in kernel mode.
Caused by (from SRR1=149030): Transfer error ack signal
Oops: Machine check, sig: 7 [#1]
PREEMPT SMP NR_CPUS=2
Modules linked in: virtex5
LTT NESTING LEVEL : 0
NIP: F108019C LR: F1080198 CTR: 00000001
REGS: c044dd60 TRAP: 0200   Not tainted      (2.6.18-mpc8641d_hpcn)
MSR: 00149030 <EE,ME,IR,DR>  CR: 22000222  XER: 00000000
TASK = c20e9990[568] 'insmod' THREAD: c044c000 CPU: 0
GPR00: F1080198 C044DE10 C20E9990 0000002E 80000000 FFFFFFFF 00008000
00002EA3
GPR08: C20E9990 00000000 C04C0220 C044C000 22000222 1001956C 00000000
00000000
GPR16: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
GPR24: 3000EAA0 7FD6FDC0 00000000 C045FCC0 F107E594 F10A0000 00000000
C2036000
NIP [F108019C] virtex5_probe+0x130/0x1c4 [virtex5]
LR [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5]
Call Trace:
[C044DE10] [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5] (unreliable)
[C044DE30] [C01D2A58] pci_device_probe+0x84/0xbc
[C044DE50] [C0213754] driver_probe_device+0x60/0x118
[C044DE70] [C0213890] __driver_attach+0x84/0x88
[C044DE90] [C02130F4] bus_for_each_dev+0x58/0x94
[C044DEC0] [C02135D4] driver_attach+0x24/0x34
[C044DED0] [C0212AC8] bus_add_driver+0x88/0x164
[C044DEF0] [C021397C] driver_register+0x70/0xb8
[C044DF00] [C01D284C] __pci_register_driver+0x64/0x98
[C044DF10] [F1080030] init_module+0x30/0x6c [virtex5]
[C044DF20] [C004CBFC] sys_init_module+0xc8/0x25c
[C044DF40] [C0011358] ret_from_syscall+0x0/0x38
--- Exception: c00 at 0xff6de0c
    LR = 0x10000de4
Instruction dump:
40820060 3c60f108 3863cea0 48000311 807f0238 3c800001 48000395 7c7d1b78
3c60f108 3863ced4 480002f5 809d0000 <3c60f108> 3863cf04 480002e5 3c60f108

Re: MPC8641D PCI-Express error

[Jon Loeliger]

Marco Stornelli wrote:
> 
> When I try to read some register from my FPGA (virtex5) I have this bus
> error:


Hmmm....  OK, so if we've eliminated PCI-E as a source
for this issue, it really must be in the Virtex support
somewhere then.  Unfortunately, I know nothing about those,
and am not going to be much direct help there.

Sorry.

jdl


> Machine check in kernel mode.
> Caused by (from SRR1=149030): Transfer error ack signal
> Oops: Machine check, sig: 7 [#1]
> PREEMPT SMP NR_CPUS=2
> Modules linked in: virtex5
> LTT NESTING LEVEL : 0
> NIP: F108019C LR: F1080198 CTR: 00000001
> REGS: c044dd60 TRAP: 0200   Not tainted      (2.6.18-mpc8641d_hpcn)
> MSR: 00149030 <EE,ME,IR,DR>  CR: 22000222  XER: 00000000
> TASK = c20e9990[568] 'insmod' THREAD: c044c000 CPU: 0
> GPR00: F1080198 C044DE10 C20E9990 0000002E 80000000 FFFFFFFF 00008000
> 00002EA3
> GPR08: C20E9990 00000000 C04C0220 C044C000 22000222 1001956C 00000000
> 00000000
> GPR16: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> GPR24: 3000EAA0 7FD6FDC0 00000000 C045FCC0 F107E594 F10A0000 00000000
> C2036000
> NIP [F108019C] virtex5_probe+0x130/0x1c4 [virtex5]
> LR [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5]
> Call Trace:
> [C044DE10] [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5] (unreliable)
> [C044DE30] [C01D2A58] pci_device_probe+0x84/0xbc
> [C044DE50] [C0213754] driver_probe_device+0x60/0x118
> [C044DE70] [C0213890] __driver_attach+0x84/0x88
> [C044DE90] [C02130F4] bus_for_each_dev+0x58/0x94
> [C044DEC0] [C02135D4] driver_attach+0x24/0x34
> [C044DED0] [C0212AC8] bus_add_driver+0x88/0x164
> [C044DEF0] [C021397C] driver_register+0x70/0xb8
> [C044DF00] [C01D284C] __pci_register_driver+0x64/0x98
> [C044DF10] [F1080030] init_module+0x30/0x6c [virtex5]
> [C044DF20] [C004CBFC] sys_init_module+0xc8/0x25c
> [C044DF40] [C0011358] ret_from_syscall+0x0/0x38
> --- Exception: c00 at 0xff6de0c
>     LR = 0x10000de4
> Instruction dump:
> 40820060 3c60f108 3863cea0 48000311 807f0238 3c800001 48000395 7c7d1b78
> 3c60f108 3863ced4 480002f5 809d0000 <3c60f108> 3863cf04 480002e5 3c60f108

Re: MPC8641D PCI-Express error

[Marco Stornelli]

Jon Loeliger ha scritto:
> Marco Stornelli wrote:
>> When I try to read some register from my FPGA (virtex5) I have this bus
>> error:
> 
> 
> Hmmm....  OK, so if we've eliminated PCI-E as a source
> for this issue, it really must be in the Virtex support
> somewhere then.  Unfortunately, I know nothing about those,
> and am not going to be much direct help there.
> 
> Sorry.
> 
> jdl
> 
> 
>> Machine check in kernel mode.
>> Caused by (from SRR1=149030): Transfer error ack signal
>> Oops: Machine check, sig: 7 [#1]
>> PREEMPT SMP NR_CPUS=2
>> Modules linked in: virtex5
>> LTT NESTING LEVEL : 0
>> NIP: F108019C LR: F1080198 CTR: 00000001
>> REGS: c044dd60 TRAP: 0200   Not tainted      (2.6.18-mpc8641d_hpcn)
>> MSR: 00149030 <EE,ME,IR,DR>  CR: 22000222  XER: 00000000
>> TASK = c20e9990[568] 'insmod' THREAD: c044c000 CPU: 0
>> GPR00: F1080198 C044DE10 C20E9990 0000002E 80000000 FFFFFFFF 00008000
>> 00002EA3
>> GPR08: C20E9990 00000000 C04C0220 C044C000 22000222 1001956C 00000000
>> 00000000
>> GPR16: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>> 00000000
>> GPR24: 3000EAA0 7FD6FDC0 00000000 C045FCC0 F107E594 F10A0000 00000000
>> C2036000
>> NIP [F108019C] virtex5_probe+0x130/0x1c4 [virtex5]
>> LR [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5]
>> Call Trace:
>> [C044DE10] [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5] (unreliable)
>> [C044DE30] [C01D2A58] pci_device_probe+0x84/0xbc
>> [C044DE50] [C0213754] driver_probe_device+0x60/0x118
>> [C044DE70] [C0213890] __driver_attach+0x84/0x88
>> [C044DE90] [C02130F4] bus_for_each_dev+0x58/0x94
>> [C044DEC0] [C02135D4] driver_attach+0x24/0x34
>> [C044DED0] [C0212AC8] bus_add_driver+0x88/0x164
>> [C044DEF0] [C021397C] driver_register+0x70/0xb8
>> [C044DF00] [C01D284C] __pci_register_driver+0x64/0x98
>> [C044DF10] [F1080030] init_module+0x30/0x6c [virtex5]
>> [C044DF20] [C004CBFC] sys_init_module+0xc8/0x25c
>> [C044DF40] [C0011358] ret_from_syscall+0x0/0x38
>> --- Exception: c00 at 0xff6de0c
>>     LR = 0x10000de4
>> Instruction dump:
>> 40820060 3c60f108 3863cea0 48000311 807f0238 3c800001 48000395 7c7d1b78
>> 3c60f108 3863ced4 480002f5 809d0000 <3c60f108> 3863cf04 480002e5 3c60f108
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

I tried to use 2.6.24 but I have the same error. It looks like this
problem happens when I try to read something in my ML555 board (Virtex5
evaluation board), but if try to write everything works fine. I tried to
change the settings about inbound/outbound PCI-E windows but I have the
same problem. Have you got any suggestions?

Thanks.

Marco

MPC8641D PCI-Express error

[Marco Stornelli]

Hi,

I have some news about my problem. When the system makes the boot
(kernel 2.6.24) I see these messages:

...........
PCI: Probing PCI hardware
PCI: 0000:00:00.0: class b20 doesn't match header type 01. Ignoring class.
PCI: Transparent bridge - 0000:00:00.0
PCI: Transparent bridge - 0000:01:00.0
PCI: 0001:03:00.0: class b20 doesn't match header type 01. Ignoring class.
PCI: Transparent bridge - 0001:03:00.0
PCI: Cannot allocate resource region 0 of device 0000:02:1f.0
PCI: Cannot allocate resource region 1 of device 0000:02:1f.0
PCI: Cannot allocate resource region 2 of device 0000:02:1f.0
PCI: Cannot allocate resource region 3 of device 0000:02:1f.0
PCI: Cannot allocate resource region 4 of device 0000:02:1f.0
PCI: Cannot allocate resource region 0 of device 0000:02:1f.1
PCI: Cannot allocate resource region 1 of device 0000:02:1f.1
PCI: Cannot allocate resource region 2 of device 0000:02:1f.1
PCI: Cannot allocate resource region 3 of device 0000:02:1f.1
PCI: Cannot allocate resource region 4 of device 0000:02:1f.1
PCI: Cannot allocate resource region 0 of device 0001:04:00.0
PCI: Cannot allocate resource region 1 of device 0001:04:00.0
PCI: Error while updating region 0000:02:1f.1/0 (00001419 != 00001411)
PCI: Error while updating region 0000:02:1f.1/2 (00001439 != 00001431)
PCI: Error while updating region 0000:02:1f.1/3 (00001435 != 00001431)

..............

where the device 0001:04:00.0 is my ML555 Virtex5 evaluation board. The
lspci output is:

0000:02:1f.0 Class 0101: Unknown device 10b9:5229 (rev c8) (prog-if 8f
[Master SecP SecO PriP PriO])
        Subsystem: Unknown device 10b9:5229
        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: 32 bytes
        Interrupt: pin A routed to IRQ 14
        Region 0: I/O ports at 1400 [size=8]
        Region 1: I/O ports at 1408 [size=4]
        Region 2: I/O ports at 1410 [size=8]
        Region 3: I/O ports at 140c [size=4]
        Region 4: I/O ports at 1420 [size=16]
        Capabilities: [60] 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-
        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
                Address: 00000000  Data: 0000




0000:02:1f.1 Class 0101: Unknown device 10b9:5288 (rev 10) (prog-if 01
[PriO])
        Subsystem: Unknown device 10b9:5288
        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: 32 bytes
        Interrupt: pin A routed to IRQ 5
        Region 0: I/O ports at 1418 [size=8]
        Region 1: I/O ports at 1430 [size=4]
        Region 2: I/O ports at 1438 [size=8]
        Region 3: I/O ports at 1434 [size=4]
        Region 4: I/O ports at 1440 [size=16]
        Region 5: Memory at 80006000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [60] 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-
        Capabilities: [70] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000






0001:04:00.0 Class 0500: Unknown device 10ee:0007
        Subsystem: Unknown device 14d0:6601
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 19
        Region 0: Memory at a0000000 (32-bit, non-prefetchable)
[disabled] [size=1M]
        Region 1: Memory at a0100000 (32-bit, non-prefetchable)
[disabled] [size=1M]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [48] Message Signalled Interrupts: Mask+ 64bit+
Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000
                Masking: 00000000  Pending: 00000000
        Capabilities: [60] Express Endpoint IRQ 0
                Device: Supported: MaxPayload 256 bytes, PhantFunc 1,
ExtTag+
                Device: Latency L0s unlimited, L1 unlimited
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
                Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s L1, Port 0
                Link: Latency L0s unlimited, L1 unlimited
                Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x4
        Capabilities: [100] Device Serial Number 35-0a-00-01-01-00-00-00

(The last device appears disabled because the driver isn't still
loaded). Are  these prints a normal behaviour? Because I read in the
function which prints this messages (alloc_resource in
arch/powerpc/kernel/pci_32.c) this comment:

/* We'll assign a new address later */

Is there some bug in the kernel? Any suggestions? Please help me.

Thanks.

Marco