The 8/17 run of the nightly bk testing I'm doing turned up a lot of page
allocation failures in the dmesg and eventually an oops in swap.c:85
(uncaptured, will try to reproduce on current). Unfortunatly this meant
the test did not run after that. This morning I rebooted the machine
and ran it against the current bk tree and with a single test was able
to produce a LOT of these messages:
page allocation failure. order:0, mode:0x50
The test was: 'mtest01 -p80 -w' which will essentially allocate up to
80% of the memory and write to it. I'll keep pounding on it with LTP to
see if I can reproduce the swap.c:80 oops.
Thanks,
Paul Larson
Linux Test Project
-
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/
This archive was generated by hypermail 2b29 : Fri Aug 23 2002 - 22:00:17 EST