<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16674" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=451413322-21072008><FONT face=Arial
color=#0000ff size=2>Joachim,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=451413322-21072008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=451413322-21072008><FONT face=Arial
color=#0000ff size=2>No, we are stable now once we fixed the bus numbering
issue.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=451413322-21072008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=451413322-21072008><FONT face=Arial
color=#0000ff size=2>Vince</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> joachim.bader@diehl-aerospace.de
[mailto:joachim.bader@diehl-aerospace.de] <BR><B>Sent:</B> Monday, July 21,
2008 3:15 AM<BR><B>To:</B> vasbridge@sanblaze.com<BR><B>Cc:</B> 'Dave
Maruska'; linuxppc-embedded@ozlabs.org; 'Mitul Patel'; 'Geary Sean-R60898';
'Stephen Shirron'; 'Hynes, Stephen'<BR><B>Subject:</B> Antwort: RE: Migrating
from 2.6.11 to 2.6.23 breaks pci-e <BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>Hello Vince,</FONT> <BR><BR><FONT
face=sans-serif size=2>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 face=sans-serif size=2>The kernel did not scan all buses and did not
recognize the connected pci-e bridges and devices.</FONT> <BR><BR><FONT
face=sans-serif size=2>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 face=sans-serif size=2>Do you
have some more information? regarding behavior of newer kernels?</FONT>
<BR><BR><FONT face=sans-serif size=2>Thank you</FONT> <BR><FONT
face=sans-serif size=2>Joachim Bader</FONT> <BR><FONT face=sans-serif
size=2>-- <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%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>"Vince Asbridge"
<vasbridge@sanblaze.com></B> </FONT><BR><FONT face=sans-serif
size=1>Gesendet von:
linuxppc-embedded-bounces+joachim.bader=diehl-aerospace.de@ozlabs.org</FONT>
<P><FONT face=sans-serif size=1>02.07.2008 23:40</FONT> </P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>An</FONT></DIV>
<TD><FONT face=sans-serif
size=1><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 face=sans-serif size=1>Kopie</FONT></DIV>
<TD>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Thema</FONT></DIV>
<TD><FONT face=sans-serif size=1>RE: Migrating from 2.6.11 to
2.6.23 breaks pci-e with LSI 1068 SAS
chip (solved!)</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></TR></TBODY></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-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: sans-serif,helvetica">_______________________________________________________________________________________________________________________</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: sans-serif,helvetica">Der
Inhalt dieser E-Mail ist fC<R span < verbindlich. nicht rechtlich Absender
den><BR><SPAN
style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: sans-serif,helvetica">Informieren
Sie uns bitte, wenn Sie diese E-Mail fC$lschlicherweise erhalten haben (Fax:
+49-69-5805-1399). Bitte lC6schen Sie in diesem Fall die Nachricht. Jede Form
der weiteren Benutzung ist untersagt.</SPAN><BR><BR><SPAN
style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: sans-serif,helvetica">The
content of this e-mail is not legally binding upon the sender.</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: sans-serif,helvetica">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></BLOCKQUOTE></SPAN></BODY></HTML>