From: Scott Wood <scottwood@freescale.com>
To: Gokul C G <gokul.g@kalkitech.in>
Cc: <linux-pci@vger.kernel.org>, <meta-freescale@yoctoproject.org>,
<linuxppc-dev@lists.ozlabs.org>, <djiang@mvista.com>
Subject: Re: PCIe driver not working properly after upgrading to linux 3.8.13
Date: Tue, 19 Aug 2014 18:46:24 -0500 [thread overview]
Message-ID: <1408491984.4058.48.camel@snotra.buserror.net> (raw)
In-Reply-To: <53F3629A.6060208@kalkitech.in>
On Tue, 2014-08-19 at 20:13 +0530, Gokul C G wrote:
> HI,
>
>
>
> I am facing problem with PCIE driver in new Linux kernel compiled for
> powerpc architecture (Big endian) ,freescales P2040 processor.I was
> using old kernel Linux version 3.0.48 previously and now updated to
> Linux version 3.8.13-rt9.After updating to the new kernel,
3.8.13-rt9 is also an old kernel. :-)
It is also presumably a Freescale SDK kernel (not even the most recent
one), so it would be best to stick with community.freescale.com (you
didn't follow up to my response there) or, in the case of problems with
third party code you've added on to the SDK kernel, the support channels
of whoever provided you with the software.
> PCIe device drivers not working properly and i am getting some error
> messages in the boot-up .My intention is to use EXAR PCIe Multiport
> serial driver and add 8 serial ports in addition to 4 built in serial
> ports provided by P2040 processor. The PCIe driver form EXAR is
> compiled and loaded as kernel module . The same was working with
> linux kernel 3.0.48 and following prints observed while loading kernel
> module.
>
>
> linux 3.0.48 ,working insmod log
>
>
> ========================
>
>
>
>
> Exar PCIe (XR17V35x) serial driver Revision: 1.2
I don't see this driver in the kernel tree. We can't help you with code
we can't see. Are you sure that the driver is expected to work with
3.8? Have you tried debugging it and/or contacting Exar for support
with their driver?
> PCI: Probing PCI hardware
>
> fsl-pci ffe201000.pcie: PCI host bridge to bus 0000:00
>
> pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
>
> pci_bus 0000:00: root bus resource [mem 0xc20000000-0xc3fffffff] (bus
> address [0xe0000000-0xffffffff])
>
> pci_bus 0000:00: root bus resource [bus 00-ff]
>
> PCIE error(s) detected
>
> PCIE ERR_DR register: 0x80020000
>
> PCIE ERR_CAP_STAT register: 0x80000001
>
> PCIE ERR_CAP_R0 register: 0x00000800
>
> pci 0000:00:00.0: PCI bridge to [bus 01-ff]
>
> PCIE ERR_CAP_R1 register: 0x00000000
>
> PCIE ERR_CAP_R2 register: 0x00000000
>
> PCIE ERR_CAP_R3 register: 0x00000000
>
> PCI: Cannot allocate resource region 0 of device 0000:00:00.0, will
> remap
>
> pci 0000:00:00.0: BAR 0: can't assign mem (size 0x1000000)
>
> pci 0000:00:00.0: BAR 9: can't assign mem pref (size 0x200000)
>
> pci 0000:00:00.0: PCI bridge to [bus 01]
>
> pci 0000:00:00.0: bridge window [io 0x0000-0xffff]
>
> pci 0000:00:00.0: bridge window [mem 0xc20000000-0xc3fffffff]
>
>
>
I get very similar errors on Freescale's SDK 1.5 kernel (based on
v3.8.13-rt9), and it doesn't stop a PCIe network card from working. So
I wouldn't focus too much on these errors.
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Gokul C G <gokul.g@kalkitech.in>
Cc: meta-freescale@yoctoproject.org, linux-pci@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, djiang@mvista.com
Subject: Re: PCIe driver not working properly after upgrading to linux 3.8.13
Date: Tue, 19 Aug 2014 18:46:24 -0500 [thread overview]
Message-ID: <1408491984.4058.48.camel@snotra.buserror.net> (raw)
In-Reply-To: <53F3629A.6060208@kalkitech.in>
On Tue, 2014-08-19 at 20:13 +0530, Gokul C G wrote:
> HI,
>
>
>
> I am facing problem with PCIE driver in new Linux kernel compiled for
> powerpc architecture (Big endian) ,freescales P2040 processor.I was
> using old kernel Linux version 3.0.48 previously and now updated to
> Linux version 3.8.13-rt9.After updating to the new kernel,
3.8.13-rt9 is also an old kernel. :-)
It is also presumably a Freescale SDK kernel (not even the most recent
one), so it would be best to stick with community.freescale.com (you
didn't follow up to my response there) or, in the case of problems with
third party code you've added on to the SDK kernel, the support channels
of whoever provided you with the software.
> PCIe device drivers not working properly and i am getting some error
> messages in the boot-up .My intention is to use EXAR PCIe Multiport
> serial driver and add 8 serial ports in addition to 4 built in serial
> ports provided by P2040 processor. The PCIe driver form EXAR is
> compiled and loaded as kernel module . The same was working with
> linux kernel 3.0.48 and following prints observed while loading kernel
> module.
>
>
> linux 3.0.48 ,working insmod log
>
>
> ========================
>
>
>
>
> Exar PCIe (XR17V35x) serial driver Revision: 1.2
I don't see this driver in the kernel tree. We can't help you with code
we can't see. Are you sure that the driver is expected to work with
3.8? Have you tried debugging it and/or contacting Exar for support
with their driver?
> PCI: Probing PCI hardware
>
> fsl-pci ffe201000.pcie: PCI host bridge to bus 0000:00
>
> pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
>
> pci_bus 0000:00: root bus resource [mem 0xc20000000-0xc3fffffff] (bus
> address [0xe0000000-0xffffffff])
>
> pci_bus 0000:00: root bus resource [bus 00-ff]
>
> PCIE error(s) detected
>
> PCIE ERR_DR register: 0x80020000
>
> PCIE ERR_CAP_STAT register: 0x80000001
>
> PCIE ERR_CAP_R0 register: 0x00000800
>
> pci 0000:00:00.0: PCI bridge to [bus 01-ff]
>
> PCIE ERR_CAP_R1 register: 0x00000000
>
> PCIE ERR_CAP_R2 register: 0x00000000
>
> PCIE ERR_CAP_R3 register: 0x00000000
>
> PCI: Cannot allocate resource region 0 of device 0000:00:00.0, will
> remap
>
> pci 0000:00:00.0: BAR 0: can't assign mem (size 0x1000000)
>
> pci 0000:00:00.0: BAR 9: can't assign mem pref (size 0x200000)
>
> pci 0000:00:00.0: PCI bridge to [bus 01]
>
> pci 0000:00:00.0: bridge window [io 0x0000-0xffff]
>
> pci 0000:00:00.0: bridge window [mem 0xc20000000-0xc3fffffff]
>
>
>
I get very similar errors on Freescale's SDK 1.5 kernel (based on
v3.8.13-rt9), and it doesn't stop a PCIe network card from working. So
I wouldn't focus too much on these errors.
-Scott
next prev parent reply other threads:[~2014-08-19 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 14:43 PCIe driver not working properly after upgrading to linux 3.8.13 Gokul C G
2014-08-19 14:43 ` Gokul C G
2014-08-19 23:46 ` Scott Wood [this message]
2014-08-19 23:46 ` Scott Wood
[not found] ` <53F9E486.9050801@kalkitech.in>
2014-08-25 18:47 ` Scott Wood
2014-08-20 16:21 ` Aaron Sierra
2014-08-20 16:21 ` Aaron Sierra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1408491984.4058.48.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=djiang@mvista.com \
--cc=gokul.g@kalkitech.in \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=meta-freescale@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.