> All code interacting with FreeBSD data structures resides in the open
> part of the kernel module; a pointer to the newly allocated object is
> passed to rm_alloc_agp_pages as an opaque pointer, it is required later
> when the NVIDIA AGP GART driver needs to obtain the physical addresses
> of the
> It'd be interesting to learn if the code path you suspect really is the
> one taken in the case of this failure. Is this problem easily
> reproducible on your machine? If so, how and with what hard/software
> combination?
I think the stack is getting (somewhat) smashed so there's no real way to
On Thu, Nov 14, 2002 at 10:55:17AM -0500, Kenneth Culver wrote:
>
> I'm not positive, but looking at the code this is what happens.
>
> first an object is allocated, then it goes and finds some nvidia
> specific data structure contained in that object (from what I can
> tell), then it calls rm_all
> Are you sure that nv_free_vm_object() is free'ing a valid object?
>
I'm not positive, but looking at the code this is what happens.
first an object is allocated, then it goes and finds some nvidia specific
data structure contained in that object (from what I can tell), then it
calls rm_alloc_agp
On 14-Nov-2002 Kenneth Culver wrote:
>> several functions that call vm_object functions in FreeBSD's kernel that
>> eventually call atomic_clear_short(). For some reason those functions in
>> between aren't in the backtrace though, and without that I can (and
>> have) look through the code in the
> several functions that call vm_object functions in FreeBSD's kernel that
> eventually call atomic_clear_short(). For some reason those functions in
> between aren't in the backtrace though, and without that I can (and
> have) look through the code in the kernel to see how nv_alloc_pages can
> get
> Looks like it is indeed nvidia's fault. It called atomic_clear_short()
> with an invalid pointer in nv_alloc_pages(). You might be able to look
> at nv_alloc_pages() to try and figure out the bug.
nv_alloc_pages never actually calls atomic_clear_short(), but it does call
several functions that
On 14-Nov-2002 Kenneth Culver wrote:
> I'm posting this here because of a panic I'm getting using the FreeBSD
> nvidia driver; however, I'm not convinced that this panic is the fault of
> the driver, and I wanted to post the backtrace here (from a serial
> console, can't see anything on the pc con
8 matches
Mail list logo
