From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Jacob Gorm Hansen <jacobg@diku.dk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: Failure to get memory for GATT table, again
Date: Tue, 01 Feb 2005 00:59:23 -0800 [thread overview]
Message-ID: <41FF44EB.5020707@diku.dk> (raw)
In-Reply-To: <41FF41DE.2070000@diku.dk>
Jacob Gorm Hansen wrote:
> Jacob Gorm Hansen wrote:
> I instrumented some more, apparently the page has the wrong owner,
> causing the mmu update to fail. The page is almost at the top of memory,
> probably outside of dom0s reservation.
Remming out the ownership test in xen's get_page() made the intel-agp
module load without errors. Unless someone beats me to it, I will try to
figure out what makes the AGPGART code wish to exceed dom0s memory area
tomorrow Seattle time.
The fglrx module also loads fine, but attempting to start X ends up like
this;
Oops: 0000 [#1]
DEBUG_PAGEALLOC
Modules linked in: fglrx intel_agp agpgart
CPU: 0
EIP: 0061:[<c0143596>] Tainted: P VLI
EFLAGS: 00213206 (2.6.10-xen0)
EIP is at remap_pfn_range+0x176/0x220
eax: c0523000 ebx: 000e0001 ecx: 00000027 edx: 000e0001
esi: 00062000 edi: f23e7188 ebp: 00162000 esp: f22efe8c
ds: 007b es: 007b ss: 0069
Process X (pid: 6571, threadinfo=f22ee000 task=f6b63b20)
Stack: 00162000 b7c00000 000dff9f 00062000 f23f6b7c f23f5ddc b7d62000
f23f6b7c
b7c62000 f125ac70 f125ac70 f8921260 f88f5781 f125ac70 b7c62000
0002839f
00100000 00000027 f18e5f6c f89213fc f88f66ec f18e5f6c f125ac70
00000004
Call Trace:
[<f88f5781>] __ke_vm_map+0x191/0x250 [fglrx]
[<f88f66ec>] firegl_mmap+0x1bc/0x460 [fglrx]
[<c014629f>] do_mmap_pgoff+0x35f/0x730
[<c0110e76>] old_mmap+0xd6/0x110
[<c0109530>] syscall_call+0x7/0xb
Code: e0 05 01 d0 8b 00 f6 c4 08 74 2a 8b 44 24 44 89 d9 c1 e1 0c 09 c1
f6 c1 01 74 18 a1 80 c8 4e c0 89 ca c1 ea 0c 81 e1 ff 0f 00 00 <8b> 04
90 c1 e0 0c 09 c1 89 0f 43 83 c7 04 81 c6 00 10 00 00 74
-- however, I just blindly replaced all virt_to_phys calls with
virt_to_machine in the wrapper code, and that is probably wrong. Problem
is if there are similar address conversions inside the binary-only part
of the module.
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-02-01 8:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 7:27 Failure to get memory for GATT table, again Ian Pratt
2005-02-01 8:23 ` Jacob Gorm Hansen
2005-02-01 8:46 ` Jacob Gorm Hansen
2005-02-01 8:59 ` Jacob Gorm Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-02 22:38 Ian Pratt
2005-02-02 23:55 ` Jacob Gorm Hansen
2005-02-02 0:01 Ian Pratt
2005-02-02 0:55 ` Jacob Gorm Hansen
2005-02-02 21:28 ` Jacob Gorm Hansen
2005-02-01 21:25 Ian Pratt
2005-02-01 22:15 ` Jacob Gorm Hansen
2005-02-01 22:45 ` Ian Pratt
2005-02-01 22:52 ` Jacob Gorm Hansen
2005-02-01 23:18 ` Ian Pratt
2005-02-01 23:29 ` Jacob Gorm Hansen
2005-02-01 16:39 Ian Pratt
2005-02-01 20:08 ` Jacob Gorm Hansen
2005-02-01 4:29 Jacob Gorm Hansen
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=41FF44EB.5020707@diku.dk \
--to=jacobg@diku.dk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.