From: Daniel Nilsson <gnuffel@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] ixp425 pci accesses crash in redboot
Date: Wed, 30 Sep 2009 16:11:00 -0000 [thread overview]
Message-ID: <ba87a860909300911x1282f30ft256e9f6c662268e0@mail.gmail.com> (raw)
I am using a IXP425 and a custom PCI target device,
The device enumeration and configuration all go well in redboot, but
sometimes (one in 200 reboots or so) I get a data abort exception that
ends up in the GDB stubs when I try to read from the PCI device using
PCI Memory Window transactions (reading/writing to/from
(0x49000000+offset)). I I get past this stage, the unit will stay up
forever happily serving PCI access. Only the reboots are dangerous.
When this happens, I have used gdb to read the pci configuration
parameters from the PCI target controller (0xC0000000 ->), and all is
as it should be (except that the PCI fatal error flag is raised) .
What I wonder is what can cause this behaviour, and how I should
handle it. Can this be caused by my PCI device doing an abort, by some
MMU/cache setting in the IXP425 or similar?
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2009-09-30 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 16:11 Daniel Nilsson [this message]
2009-09-30 23:54 ` Kurt Siedenburg
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=ba87a860909300911x1282f30ft256e9f6c662268e0@mail.gmail.com \
--to=gnuffel@gmail.com \
--cc=ecos-discuss@ecos.sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).