1 |
Booted into 2.6.7rc2 |
2 |
|
3 |
cd /usr/src/linux-2.6.7-rc1 |
4 |
make clean |
5 |
uptime: 09:39:30 up 8m, 2 users, load avg: 0.29, 0.29, 0.19 |
6 |
|
7 |
make -j all |
8 |
|
9 |
uptime: 09:41:41 up 10m, 2 users, load avg: 200.90, 65.79, 23.42 |
10 |
|
11 |
Dec 3 09:43:54 Out of Memory: killed ... |
12 |
|
13 |
Dec 3 09:47:21 apache: page allocation failure. order:0, mode:0x1d2 |
14 |
Call trace: |
15 |
filemap_nopage |
16 |
do_no_page |
17 |
handle_mm_fault |
18 |
do_sparc64_fault |
19 |
sparc64_realfault_common |
20 |
|
21 |
repeated 5 times before: |
22 |
|
23 |
Dec 3 09:48:05 VM: killing process apache2 |
24 |
|
25 |
I note that this is a slightly different killer than the OOM |
26 |
|
27 |
I manually killed the build at 09:57:58, as it had not yet crashed the |
28 |
machine |
29 |
in the past 15 minutes, yet gds-267-r12 will crash and burn within 2 minutes |
30 |
|
31 |
|
32 |
OOMkiller 'feels' more aggressive in -rc2, but still doesn't have the |
33 |
instability |
34 |
that gds-267-r16 has |
35 |
|
36 |
-leif |