--
View this message in context:
http://linuxppc.10917.n7.nabble.com/Re-PCIE-device-errors-after-linux-kernel-upgrade-tp74563p79160.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
___
Linuxppc-dev mailing list
Linuxppc-dev
On Wed, 2014-01-08 at 00:24 -0800, ravich wrote:
Finally I found the problem causing the sudden system reset :
our setup :
P2020PCI Bridge = FPGA
The reset occurs when we allocating skb and giving the Fpga dma addr of
skb-data of this skb and when the FPGA tries to reach this
for my problem ?
Thanks a lot.
Leonid
--
View this message in context:
http://linuxppc.10917.n7.nabble.com/Re-PCIE-device-errors-after-linux-kernel-upgrade-tp74563p78251.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
___
Linuxppc
Nope , same situation, can't find whats wrong :(
--
View this message in context:
http://linuxppc.10917.n7.nabble.com/Re-PCIE-device-errors-after-linux-kernel-upgrade-tp74563p77605.html
Sent from the linuxppc-dev mailing list archive at Nabble.com
On Fri, Aug 16, 2013 at 4:05 PM, Bjorn Helgaas bhelg...@google.com wrote:
On Tue, Aug 6, 2013 at 11:41 PM, Leon Ravich lrav...@gmail.com wrote:
From comparison of pci printout from the two kernel ,
beside the EDAC errors I noticed other strange differences:
In 3.8.13 I got BAR 7 and BAR 8:
[
or similar?
cant I post here??
Thanks for your time
--
View this message in context:
http://linuxppc.10917.n7.nabble.com/Re-PCIE-device-errors-after-linux-kernel-upgrade-tp74563p75193.html
Sent from the linuxppc-dev mailing list archive at Nabble.com
On Tue, Aug 6, 2013 at 11:41 PM, Leon Ravich lrav...@gmail.com wrote:
From comparison of pci printout from the two kernel ,
beside the EDAC errors I noticed other strange differences:
In 3.8.13 I got BAR 7 and BAR 8:
[ 39.017749] pci :00:00.0: BAR 8: assigned [mem 0xc000-0xdfff]
On Mon, Aug 05, 2013 at 09:38:45AM -0600, Bjorn Helgaas wrote:
[+cc linuxppc-dev]
On Mon, Aug 5, 2013 at 5:17 AM, Leon Ravich lrav...@gmail.com wrote:
Hi all ,
I am trying to upgrade ours embedded device (freescale powerPC P2020 cpu)
linux kernel , till now we used 2.6.32 I am trying to
On Tue, Aug 06, 2013 at 10:26:18AM +0300, Leon Ravich wrote:
Hi Johannes
no panic just reboot.
it is not the first read, it takes few minutes of work with pcie to reboot.
Ah, OK. Unfortunately I can't really help you then.
Have you looked up the error values from the EDAC driver?
If it's
Thanks Bjorn.
1) If I understand it right this patch only removes the pci
:00:00.0: ignoring class 0x0b2000 (doesn't
match header type 01) message , don't care about it , had it before .
2) regarding the comparing of printouts:
kernel 3.8.13:
[ 37.908846] pci_bus :00: scanning bus
[
Hi Johannes
no panic just reboot.
it is not the first read, it takes few minutes of work with pcie to reboot.
On 6 August 2013 10:07, Johannes Thumshirn johannes.thumsh...@men.de wrote:
On Mon, Aug 05, 2013 at 09:38:45AM -0600, Bjorn Helgaas wrote:
[+cc linuxppc-dev]
On Mon, Aug 5, 2013 at
Have you looked up the error values from the EDAC driver?
[ 37.961580] PCIE error(s) detected
[ 37.964971] PCIE ERR_DR register: 0x0002
= Invalid CONFIG_ADDR/PEX_CONFIG_DATA access detected
[ 37.969229] PCIE ERR_CAP_STAT register: 0x0041 =
Transaction originated
device errors after linux kernel upgrade
Hi Johannes
no panic just reboot.
it is not the first read, it takes few minutes of work with pcie to
reboot.
You may need to check the error code in EDAC driver as Johannes suggested.
Roy
___
Linuxppc-dev
From comparison of pci printout from the two kernel ,
beside the EDAC errors I noticed other strange differences:
In 3.8.13 I got BAR 7 and BAR 8:
[ 39.017749] pci :00:00.0: BAR 8: assigned [mem 0xc000-0xdfff]
[ 39.024530] pci :00:00.0: BAR 7: can't assign io (size 0x1)
[+cc linuxppc-dev]
On Mon, Aug 5, 2013 at 5:17 AM, Leon Ravich lrav...@gmail.com wrote:
Hi all ,
I am trying to upgrade ours embedded device (freescale powerPC P2020 cpu)
linux kernel , till now we used 2.6.32 I am trying to upgrade to 3.8.13 .
I took the source from freescale git:
15 matches
Mail list logo
