From: ravich <lravich@gmail•com>
To: linuxppc-dev@ozlabs•org
Subject: Re: PCIE device errors after linux kernel upgrade
Date: Wed, 8 Jan 2014 00:24:59 -0800 (PST) [thread overview]
Message-ID: <1389169499473-79160.post@n7.nabble.com> (raw)
In-Reply-To: <1383059241779-77605.post@n7.nabble.com>
Finally I found the problem causing the sudden system reset :
our setup :
P2020<====>PCI 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 address we are
having a hardware reset.
To fixed it we used GFP_DMA flag on skb allocations.
If you can explain me few thinks I will be more then happy :
1) how come we managed to work in 2.6.32 kernel without this flag.
2) Ok gave you a bad dma address why reset the system without any warning.
Thanks for your time and support
Leonid Ravich
--
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.
next prev parent reply other threads:[~2014-01-08 8:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPWoNkJ3NKM-_g93LdRpjvdNFtLt-Pjpg4d4oEKC9CvkpzZ-Wg@mail.gmail.com>
[not found] ` <CAPWoNkLQUbFG2vZ7wqoqqVNj4uxKz3Fa_vsSH=1_TDD=XC1f2A@mail.gmail.com>
2013-08-05 15:38 ` PCIE device errors after linux kernel upgrade Bjorn Helgaas
2013-08-06 6:32 ` Leon Ravich
2013-08-07 5:41 ` Leon Ravich
2013-08-16 22:05 ` Bjorn Helgaas
2013-08-18 11:30 ` ravich
2013-10-11 22:01 ` Bjorn Helgaas
2013-10-29 15:07 ` ravich
2014-01-08 8:24 ` ravich [this message]
2014-01-08 21:07 ` Scott Wood
2013-11-20 7:53 ` ravich
2013-08-06 7:07 ` Johannes Thumshirn
2013-08-06 7:26 ` Leon Ravich
2013-08-06 7:36 ` Johannes Thumshirn
2013-08-06 8:34 ` Leon Ravich
2013-08-07 3:35 ` Zang Roy-R61911
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=1389169499473-79160.post@n7.nabble.com \
--to=lravich@gmail$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox