1 |
Hi! |
2 |
|
3 |
On Fri, Apr 03, 2009 at 02:04:31AM +0300, Alex Efros wrote: |
4 |
> To resume, what we've now: |
5 |
> |
6 |
> Fact 1: previous kernel (2.6.27-hardened-r8) doesn't hangs |
7 |
> Fact 2: kernel hang after "Freeing unused kernel memory:" |
8 |
> * so I suppose it failed to start process N1 |
9 |
> Fact 3: kernel compiled without MPROTECT doesn't hangs |
10 |
> * so I suppose it's something related to PaX ... |
11 |
> * or some very unique hardware issue |
12 |
> Fact 4: kernel loaded with init=/bin/bash hangs in same way |
13 |
> * so it's unlikely issue with runit-init |
14 |
> Fact 5: paxctl -m for init command (/sbin/runit-init or /bin/bash) fix issue |
15 |
> * so there workaround exists which doesn't lower overall server security |
16 |
> Fact 6: /bin/bash works just fine without paxctl -m after boot |
17 |
> * so it has nothing with usual PaX work |
18 |
> Fact 7: this issue happens on one of several similar (if no equal) servers |
19 |
> * buggy hardware or some conflict (there IRQ differences between servers)? |
20 |
|
21 |
This just happens again: after upgrade from 2.6.32-hardened-r9 to |
22 |
2.6.32-hardened-r22 kernel hangs after "Freeing unused kernel memory:". |
23 |
With init=/bin/bash it boots ok (bash flags: -------x-e--). |
24 |
With init=/sbin/runit-init it hangs (with flags: -------x-e--). |
25 |
paxctl -m /sbin/runit-init fixed this issue. |
26 |
|
27 |
Strange thing is: I've 4 HP servers with same hardware and same software, |
28 |
but this issue happens only on one of servers - three other boot new |
29 |
kernel without issues while their /sbin/runit-init has flags -------x-e--. |
30 |
|
31 |
-- |
32 |
WBR, Alex. |