> Encountered this first with Linux-2.5.25+rmap and it looks like the
> problem also slipped into 2.5.27. The same machine boots fine with a
> vanilla 2.5.25 or 2.5.26, but gets this on boot with rmap. The machine
> is an 8-way PIII-700.
Bill Irwin has told me about a rare bug with exec() mapping
garbage into the address space of a process, which might
trigger this bug check the next time that process exec()s.
I've gotten two reports of this bug now, but have no idea
what particular combination of hardware / compiler / config
triggers the bug. The rmap code seems to have survived akpm's
stress tests so it's probably not a simple bug to track down ;/
regards,
Rik
-- Bravely reimplemented by the knights who say "NIH".http://www.surriel.com/ http://distro.conectiva.com/
- 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/