On Thu, Oct 04, 2007 at 07:32:52AM +0200, Torsten Kaiser wrote:
quoted text
> On 10/3/07, Matt Mackall <mpm@selenic.com> wrote:
> > Well I can see no reason why the vma we just got to by the mm->mmap
> > would have a vm_mm != mm, but I've certainly been wrong before.
> >
> > Try changing it to:
> >
> >         for (vma = mm->mmap; vma; vma = vma->vm_next)
> >                 if (!is_vm_hugetlb_page(vma)) {
> >                         if (vma->vm_mm != mm)
> >                                 printk("WTF: vma->vm_mm %p mm %p\n",
> >                                         vma->vm_mm, mm);
> >                         walk_page_range(vma->vm_mm, vma->vm_start, vma->vm_end,
> >                                         &clear_refs_walk, vma);
> >         }
> 
> You were right.
> I was able to trigger the error with above printk added, but nothing
> was written to the syslog.
> 
> So now I'm rather out of ideas what to test... :(

I'd give your previous bisect step another try.

Looking back at the thread a bit, anything that requires the machine
to be off for more than a couple seconds to manifest stops looking
like software and firmware and starts looking like a heat-related
electrical or mechanical issue. Make sure your backups are current.

-- 
Mathematics is the supreme nostalgia of our time.
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/