From: JDeas <jdeas@jadsystems.com>
To: linux-kernel@vger.kernel.org
Subject: Tracking remap_page_range error
Date: 25 Sep 2003 14:31:44 -0700 [thread overview]
Message-ID: <1064525484.2372.14.camel@HD1> (raw)
What tools can I use to track a error with remap_page_range?
I am working on a driver that remaps a 64M chunk from a
PCI card. I have confirmed that the driver executes
remap_page_range(42133000,f0000000,400000,27)
vma->Flags = 840fb
in the driver mmap. This is driven from my apps mmap
command where I pass NULL for the address.
While the application has the driver open
/proc/[ps]/maps shows the following
42133000-46133000 rw-s 000000
I have also checked /proc/iomem and found
f0000000-f3ffffff
listed on the PCI card I am working on
MY problem is a single write to 42133000 in the application
locks the system and is appearing to try and write to the
vga cards memory (or the crash is affecting the vga screen mem).
What other tools can I use to check/trace this remapping?
Redhat9.0 (2.4.20-6smp) (mem=768 passed to stay under 1G)
PCI card uses Xilinx PCI core
Thanks
JDeas
reply other threads:[~2003-09-25 21:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1064525484.2372.14.camel@HD1 \
--to=jdeas@jadsystems.com \
--cc=linux-kernel@vger.kernel.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