<br><font size=2 face="sans-serif">Hello Vince,</font>
<br>
<br><font size=2 face="sans-serif">we ran into the similar problem using
U-boot version 1.1.4 and Linux kernel 2.6.23 on a Freescale MPC8641D platform.</font>
<br><font size=2 face="sans-serif">The kernel did not scan all buses and
did not recognize the connected pci-e bridges and devices.</font>
<br>
<br><font size=2 face="sans-serif">Your mail was very helpfull and due
to the information you sent we disabled CONFIG_PCI in U-boot and now the
kernel was able to detect all connected bridges and devices. But during
allocation of the pci-e resources the kernel runs in an address access
violation. We will continue to investigate this behavior.</font>
<br>
<br><font size=2 face="sans-serif">Do you have some more information? regarding
behavior of newer kernels?</font>
<br>
<br><font size=2 face="sans-serif">Thank you</font>
<br><font size=2 face="sans-serif">Joachim Bader</font>
<br><font size=2 face="sans-serif">-- <br>
Dipl.-Ing. Joachim Bader<br>
Research & Technology<br>
Cockpit and Display Systems<br>
<br>
Diehl Aerospace GmbH<br>
An der Sandelmuehle 13<br>
D-60439 Frankfurt<br>
Phone +49-69-5805-1270<br>
Fax +49-69-5805-1400<br>
e-mail: joachim.bader@diehl-aerospace.de<br>
http://www.diehl-aerospace.de</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Vince Asbridge"
<vasbridge@sanblaze.com></b> </font>
<br><font size=1 face="sans-serif">Gesendet von: linuxppc-embedded-bounces+joachim.bader=diehl-aerospace.de@ozlabs.org</font>
<p><font size=1 face="sans-serif">02.07.2008 23:40</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">An</font></div>
<td><font size=1 face="sans-serif"><linuxppc-embedded@ozlabs.org>,
"'Stephen Shirron'" <sshirron@sanblaze.com>, "'Mitul
Patel'" <mpatel@sanblaze.com>, "'Dave Maruska'" <dmaruska@sanblaze.com>,
"'Geary Sean-R60898'" <sean.geary@freescale.com>, "'Hynes,
Stephen'" <Stephen.Hynes@lsi.com></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Kopie</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Thema</font></div>
<td><font size=1 face="sans-serif">RE: Migrating from 2.6.11 to 2.6.23
breaks pci-e with LSI 1068 SAS chip
(solved!)</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Solved!<br>
<br>
Problem summary.<br>
<br>
LSI logic devices (1068e, 1064e, fc949e) do not work with uBoot version<br>
1.3.0 and Linux kernel 2.6.23, where they work perfectly fine in kernel<br>
2.6.11.<br>
<br>
Symptom is that they do not show up at all to Linux once booted (lspci
shows<br>
nothing).<br>
<br>
We obtained a pci-e analyzer and found the following:<br>
<br>
uBoot V1.3.0 now scans the pci configuration, and when it does it assigns<br>
bus numbers to the pci-e devices it finds. These numbers that are
assigned<br>
are different from those that are assigned by Linux when the system boots.<br>
<br>
It is legal to change pci-e bus numbers "on the fly" but doing
so requires a<br>
config write cycle to the pci-e device, because the pci-e spec states that<br>
the device must register a new bus number if a config write cycle is issues<br>
with the new bus number.<br>
<br>
When we boot the Freescale machine with uBoot 1.3.0 and kernel 2.6.23,
the<br>
bus number under uBoot gets assigned to 1, and the bus number under Linux<br>
gets assigned to 4. Between the change of bus numbers we do not see
a<br>
config write go to the LSI device with the new bus number, and therefore
it<br>
continues to respond on bus 1 and ignore config reads to bus 4.<br>
<br>
We temporarily fixed the issue by defining the CONFIG_PCI_NOSCAN flag under<br>
uBoot, which causes the LSI device not to get assigned a bus number at<br>
uBoot, and therefore when Linux begins doing config reads at bus 4 to the<br>
LSI device registers the bus number and responds correctly.<br>
<br>
We will do a bit more investigation to see if this has already been fixed
in<br>
a newer kernel, but for now not scanning at uBoot fixes the issue.<br>
<br>
It's a bit of a mystery why the LSI devices behave differently from any<br>
other pci-e device we put in the system, but they seem to be adhering to
the<br>
letter of the specification.<br>
<br>
Vince Asbridge<br>
<br>
------- original post -------<br>
<br>
All,<br>
<br>
I'm new to this mailing list, but have not had any luck finding information<br>
on this issue.<br>
<br>
Please be kind if I break the forum rules on my first post.<br>
<br>
We recently tried to upgrade our Freescale CDS 8548 look-alike module (code<br>
name ATCA1000) from the 2.6.11 based BSP to the 2.6.23 based BSP.<br>
<br>
The upgrade went fairly smoothly, until we tried using SOME pci-e devices<br>
(some work fine, some don't show up to lspci).<br>
<br>
LSI pci-e controllers no longer show up at all!<br>
<br>
We see the ixgbe (intel 10G), SiliconImage SATA controller but do not see<br>
LSI devices (Specifically 1068 SAS, FC949-E fibrechannel).<br>
<br>
We're guessing it's a resource issue behind the bridge, because the LSI<br>
devices try to allocate 1 - 3M behind the bridge, but we can't find the
bug,<br>
or where we would debug such an issue.<br>
<br>
The devices seem to "train" correctly, because we have an LED
on the pci-e<br>
switch (PLX 8 port pci-e switch), and it's ON indicating pci-e link between<br>
the bridge and the 1068 device).<br>
<br>
We're totally at a loss as to why this always worked on the 2.6.11 kernel<br>
but doesn't work on 2.6.23.<br>
<br>
Using lspci, the LSI adapters do not show up in the list at all, as though<br>
they are not plugged into the system.<br>
<br>
Is there something that needs to be done with respect to PCI-E devices
that<br>
is new in the 2.6.23 based BSP that did not need to be done in the 2.6.11<br>
based kit? For example, are pci resources allocated by a different
piece of<br>
code, that may have some issue allocating resources for the LSI adapters?<br>
<br>
I currently do not have access to a pci-e analyzer.<br>
<br>
Thanks for any help,<br>
Vince Asbridge<br>
<br>
<br>
<br>
_______________________________________________<br>
Linuxppc-embedded mailing list<br>
Linuxppc-embedded@ozlabs.org<br>
https://ozlabs.org/mailman/listinfo/linuxppc-embedded</tt></font>
<br>
<br>
<br>
<br>
<span style="font-family:sans-serif,helvetica; font-size:10pt; color:#000000">_______________________________________________________________________________________________________________________</span><br>
<span style="font-family:sans-serif,helvetica; font-size:10pt; color:#000000">Der Inhalt dieser E-Mail ist für den Absender rechtlich nicht verbindlich. </span><br>
<span style="font-family:sans-serif,helvetica; font-size:10pt; color:#000000">Informieren Sie uns bitte, wenn Sie diese E-Mail fälschlicherweise erhalten haben (Fax: +49-69-5805-1399). Bitte löschen Sie in diesem Fall die Nachricht. Jede Form der weiteren Benutzung ist untersagt.</span><br>
<br>
<span style="font-family:sans-serif,helvetica; font-size:10pt; color:#000000">The content of this e-mail is not legally binding upon the sender.</span><br>
<span style="font-family:sans-serif,helvetica; font-size:10pt; color:#000000">If this e-mail was transmitted to you by error, then please inform us accordingly (Fax: +49-69-5805-1399). In such case you are requested to erase the message. Any use of such e-mail message is strictly prohibited.</span><br>
<br>