Messages in this thread |  | | | From | Nick Piggin <> | | Subject | Re: 2.6.27-rc5-mm1: 3 WARN_ON dumps during boot (acpi + vmap_pte_range) | | Date | Tue, 9 Sep 2008 17:55:23 +1000 |
| |
On Tuesday 09 September 2008 15:05, Krzysztof Helt wrote: > On Tue, 9 Sep 2008 13:04:47 +1000 > > Nick Piggin <nickpiggin@yahoo.com.au> wrote: > > On Tuesday 09 September 2008 03:52, Krzysztof Helt wrote: > > > alloc_vmap_area within(e07f0000-fffb7000) size=801000 > > > returns=(e0880000-e1081000) > > > alloc_vmap_area within(e07f0000-fffb7000) size=2000 > > > returns=(e07f0000-e07f2000) > > > alloc_vmap_area within(e07f0000-fffb7000) size=2000 > > > returns=(e0822000-e0824000) > > > vunmap_page_range (e07f0000-e07f2000 size=2000) > > > free_vmap_area (e07f0000-e07f2000 size=2000) > > > > > > alloc_vmap_area within(e07f0000-fffb7000) size=5000 > > > returns=(e07f0000-e07f5000) > > > ------------[ cut here ]------------ > > > WARNING: at mm/vmalloc.c:40 check_pte_range+0x83/0x90() > > > > Thanks for that, it clearly shows the virtual address allocator > > is allowing an overlapping allocation after a vm_unmap_aliases() > > call. Unfortunately, my "random" test case happened not to > > trigger that... I should have paid more attention to edge cases > > rather than just random testing. > > > > Anyway, I hope this fix should solve the problem for you? (it > > fixes it here) > > Your patch fixes two WARN_ON dumps from my original dmesg (agp > related and module loading related). > The remaining one is the acpi kobject duplication. > > Tested-by: Krzysztof Helt <krzysztof.h1@wp.pl> > > Thanks a lot Nick, > Krzysztof
Great, thanks very much for reporting and testing.
|  |