1 |
Hi, |
2 |
It's a couple of times I see my system horribly die while I'm |
3 |
re-emerging xmame (because of having added the +joystick USE flag). |
4 |
|
5 |
The system becomes rapidly (but not all of a sudden) extremly |
6 |
unresponsive: first XMMS begins to skip, then mouse begins to seriously |
7 |
lag... until all grinds to a halt. The rxvt terminal gave no sign of |
8 |
errors during compilation, it just stopped. |
9 |
|
10 |
I hard rebooted one time, then I left my system on for a couple of days |
11 |
without any problem. |
12 |
Then I re-tried emerging xmame and I found the system freezed again. It |
13 |
went later in compiling, but it didn't finish. This time I found this |
14 |
error in messages, just before of my hard reboot: |
15 |
|
16 |
----- |
17 |
Dec 5 18:39:38 voynich oom-killer: gfp_mask=0x1d2 |
18 |
Dec 5 18:39:38 voynich DMA per-cpu: |
19 |
Dec 5 18:39:38 voynich cpu 0 hot: low 2, high 6, batch 1 |
20 |
Dec 5 18:39:38 voynich cpu 0 cold: low 0, high 2, batch 1 |
21 |
Dec 5 18:39:38 voynich Normal per-cpu: |
22 |
Dec 5 18:39:38 voynich cpu 0 hot: low 62, high 186, batch 31 |
23 |
Dec 5 18:39:38 voynich cpu 0 cold: low 0, high 62, batch 31 |
24 |
Dec 5 18:39:38 voynich HighMem per-cpu: empty |
25 |
Dec 5 18:39:38 voynich |
26 |
Dec 5 18:39:38 voynich Free pages: 5096kB (0kB HighMem) |
27 |
Dec 5 18:39:38 voynich Active:59302 inactive:59085 dirty:0 writeback:0 |
28 |
unstable:0 free:1274 slab:4307 mapped:116741 pagetables:556 |
29 |
Dec 5 18:39:38 voynich DMA free:2068kB min:88kB low:108kB high:132kB |
30 |
active:5096kB inactive:3852kB present:16384kB pages_scanned:9646 |
31 |
all_unreclaimable? yes |
32 |
Dec 5 18:39:38 voynich lowmem_reserve[]: 0 495 495 |
33 |
Dec 5 18:39:38 voynich Normal free:3028kB min:2804kB low:3504kB |
34 |
high:4204kB active:232112kB inactive:232488kB present:507840kB |
35 |
pages_scanned:530600 all_unreclaimable? yes |
36 |
Dec 5 18:39:38 voynich lowmem_reserve[]: 0 0 0 |
37 |
Dec 5 18:39:38 voynich HighMem free:0kB min:128kB low:160kB high:192kB |
38 |
active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no |
39 |
Dec 5 18:39:38 voynich lowmem_reserve[]: 0 0 0 |
40 |
Dec 5 18:39:38 voynich DMA: 1*4kB 0*8kB 1*16kB 0*32kB 0*64kB 0*128kB |
41 |
0*256kB 0*512kB 0*1024kB 1*2048kB 0*4096kB = 2068kB |
42 |
Dec 5 18:39:38 voynich Normal: 51*4kB 7*8kB 7*16kB 1*32kB 1*64kB |
43 |
2*128kB 1*256kB 0*512kB 0*1024kB 1*2048kB 0*4096kB = 3028kB |
44 |
Dec 5 18:39:38 voynich HighMem: empty |
45 |
Dec 5 18:39:38 voynich Swap cache: add 409212, delete 409212, find |
46 |
86175/120838, race 0+1 |
47 |
Dec 5 18:39:38 voynich Free swap = 0kB |
48 |
Dec 5 18:39:38 voynich Total swap = 506008kB |
49 |
Dec 5 18:39:38 voynich Out of Memory: Killed process 22118 (firefox-bin). |
50 |
Dec 5 18:39:38 voynich Out of Memory: Killed process 22126 (firefox-bin). |
51 |
Dec 5 18:39:38 voynich Out of Memory: Killed process 22127 (firefox-bin). |
52 |
Dec 5 18:39:38 voynich Out of Memory: Killed process 22133 (firefox-bin). |
53 |
Dec 5 18:39:38 voynich Out of Memory: Killed process 22154 (firefox-bin). |
54 |
|
55 |
...then the silence, and my reboot. |
56 |
|
57 |
Looking in the logs for a cause of this thing (that I have never seen |
58 |
happening in my year-old Gentoo box) I found these lines in the log, 4 |
59 |
hours before the OOM crash: |
60 |
|
61 |
------ |
62 |
Dec 3 14:45:30 voynich TCP: Treason uncloaked! Peer |
63 |
82.113.24.190:4662/59982 shrinks window 3213745620:3213748388. Repaired. |
64 |
Dec 3 14:45:33 voynich TCP: Treason uncloaked! Peer |
65 |
82.113.24.190:4662/59982 shrinks window 3213745620:3213748388. Repaired. |
66 |
Dec 3 14:45:38 voynich TCP: Treason uncloaked! Peer |
67 |
82.113.24.190:4662/59982 shrinks window 3213745620:3213748388. Repaired. |
68 |
Dec 3 14:46:45 voynich TCP: Treason uncloaked! Peer |
69 |
82.113.24.190:4662/59982 shrinks window 3213798180:3213799068. Repaired. |
70 |
Dec 3 14:46:48 voynich TCP: Treason uncloaked! Peer |
71 |
82.113.24.190:4662/59982 shrinks window 3213798180:3213799068. Repaired. |
72 |
Dec 3 14:46:56 voynich TCP: Treason uncloaked! Peer |
73 |
82.113.24.190:4662/59982 shrinks window 3213798180:3213799068. Repaired. |
74 |
Dec 3 14:50:01 voynich cron[24853]: (root) CMD (test -x |
75 |
/usr/sbin/run-crons && /usr/sbin/run-crons ) |
76 |
Dec 3 14:53:40 voynich TCP: Treason uncloaked! Peer |
77 |
82.113.24.190:4662/59982 shrinks window 3214065924:3214068396. Repaired. |
78 |
------- |
79 |
|
80 |
Just because of curiosity, I googled for this and I found a thread on |
81 |
the Debian mailing list: |
82 |
http://lists.debian.org/debian-isp/2002/04/msg00192.html |
83 |
|
84 |
"So it appears that someone is running some sort of "tar-pit" system |
85 |
that is |
86 |
designed to keep sockets in a bad state and run you out of kernel memory." |
87 |
|
88 |
The thread also says that probably such a DoS attack shouldn't be able |
89 |
to crash a Linux box... but I feel the coincidence quite suspect. I |
90 |
can't guess what else it can be, apart from the xmame compile horribly |
91 |
memory leaking, but why should it? |
92 |
|
93 |
Grepping, I found here are other sporadic sequences of "Treason |
94 |
uncloaked" in my syslogs in the past, but no other one of an OOM. |
95 |
|
96 |
In the meantime I'll try to compile something else to see if I can |
97 |
repeat the problem with other emerges... |
98 |
|
99 |
Thanks, |
100 |
|
101 |
m. |
102 |
-- |
103 |
gentoo-user@g.o mailing list |