| 1 |
> So, this issue in some way related to PaX changes between 2.6.27-r8 and |
| 2 |
> 2.6.28-r7. |
| 3 |
|
| 4 |
Maybe; there are also a lot of core kernel changes between those |
| 5 |
versions, any of which could interact with the hardened patchset in a |
| 6 |
negative manner. |
| 7 |
|
| 8 |
Given that identical systems with identical configurations work, I |
| 9 |
find the specific, physical machine more suspect than something with |
| 10 |
PaX. The memory management changes it provides in combination with |
| 11 |
the memory management changes introduced in 2.6.28 could well |
| 12 |
exacerbate existing issues in a RAM module that weren't being |
| 13 |
triggered previously. |
Archives