svn commit: r252646 - head/sys/amd64/amd64

[Jean-Sébastien Pédron]

Le 20/07/2013 20:26, Neel Natu a écrit :
> I would start looking by looking at the value of the page table entry
> in question (this would be 'tpte' in pmap_remove_pages()).
>
> In particular, it would be useful to identify whether this is pointing
> to a superpage mapping and if so what page within the superpage is
> triggering the "vm_page_dirty: page is invalid" panic.

Here's what was logged by your patch:

va = 0x8007da000
tpte = 0x80000000d2f834f7
m->phys_addr = 0xd2eaf000
m->valid = 0
m->dirty= 0
m->flags = 4, aflags = 0, oflags = 0
panic: vm_page_dirty: page is invalid!

So it corresponds to page m[175] in the superpage. I don't know if it 
helps but I checked the remaining pages: they all have '->valid = 0', 
except a few ones (265 to 267, 345, 361 to 363, 379 to 387 and 425 to 
431 have '->valid = VM_PAGE_BITS_ALL').

-- 
Jean-Sébastien Pédron