All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: ATI Radeon 9600SE and intel-agp, again
Date: Mon, 07 Feb 2005 13:42:49 -0800	[thread overview]
Message-ID: <4207E0D9.8010401@diku.dk> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D123738@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:
>>>    if (direct_remap_area_pages(&init_mm, (unsigned long) 
>>
>>addr, phys_addr,
>>
>>>                    size, __pgprot(_PAGE_PRESENT | _PAGE_RW |
>>>                           _PAGE_DIRTY | _PAGE_ACCESSED
>>>                           | flags), DOMID_IO)) {
> 
> 
> The previous patch was trivially broken - it calculated the domid to use
> then always passed in a constant (as above).

Thanks, I should have spotted that. This is equal to my own hacked 
version (using DOMID_LOCAL or remming out the owner check in Xen), so I 
can now load intel-agp without that bad taste in my mouth :-)

Anyway, I now encounter the following crash in the r300-supplied drm-module:

Oops: 0000 [#1]
DEBUG_PAGEALLOC
Modules linked in: radeon drm intel_agp agpgart
CPU:    0
EIP:    0061:[<c0143546>]    Not tainted VLI
EFLAGS: 00013206   (2.6.10-xen0)
EIP is at remap_pfn_range+0x176/0x220
eax: c0527000   ebx: 000e0000   ecx: 00000027   edx: 000e0000
esi: 003ee000   edi: c9b48fb8   ebp: 00400000   esp: c9917eac
ds: 007b   es: 007b   ss: 0069
Process X (pid: 6673, threadinfo=c9916000 task=c9977b20)
Stack: 00400000 af400000 000dfc12 003ee000 c994eaf4 c994fddc af8ef000 
c994eaf4
        00000000 c7a10804 c9c6a5b0 ce4c67f8 d087c2b6 c9c6a5b0 af7ee000 
00030812
        00101000 00000027 c9c6a5ac c9b4af6c c9c6a5b0 af7ee000 ffffffea 
c9b4af6c
Call Trace:
  [<d087c2b6>] drm_mmap+0x1c6/0x2b9 [drm]
  [<c014624f>] 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 08 4f c0 89 ca c1 ea 0
c 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

I have seen some mention of a drm-patch earlier, but it is no longer in 
the tree. What happened to that / is it likely that I need to apply 
something similar to the r300 drm module?

thanks,
Jacob


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-07 21:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06  9:34 ATI Radeon 9600SE and intel-agp, again Ian Pratt
2005-02-07 21:42 ` Jacob Gorm Hansen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-07 22:08 Ian Pratt
2005-02-07 22:45 ` Jacob Gorm Hansen
2005-02-05  7:52 Ian Pratt
2005-02-06  7:31 ` Jacob Gorm Hansen
2005-02-06  7:59   ` Jacob Gorm Hansen
2005-02-05  2:47 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=4207E0D9.8010401@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.