| 1 |
Hello, |
| 2 |
|
| 3 |
Those using amd64 systems should be aware of the following bug: |
| 4 |
|
| 5 |
http://bugs.gentoo.org/show_bug.cgi?id=337645 |
| 6 |
|
| 7 |
For a quick fix in production, please note that individual patches are |
| 8 |
available here, numbered 1700 and 1705: |
| 9 |
|
| 10 |
http://sources.gentoo.org/cgi-bin/viewvc.cgi/linux-patches/genpatches-2.6/tags/2.6.35-8/ |
| 11 |
|
| 12 |
These are intended to be applied to 2.6.35 but will very likely apply |
| 13 |
to previous releases without issue. If in doubt, make use of the |
| 14 |
--dry-run feature before actually applying any patches: |
| 15 |
|
| 16 |
# cd /usr/src/linux |
| 17 |
# patch -p1 --dry-run -s < ~/1700_retruncate-rax-after-ia32-syscall.patch |
| 18 |
# patch -p1 -s < ~/1700_retruncate-rax-after-ia32-syscall.patch |
| 19 |
# patch -p1 --dry-run -s < ~/1705_syscall-number-test-fix.patch |
| 20 |
# patch -p1 -s < ~/1705_syscall-number-test-fix.patch |
| 21 |
# make |
| 22 |
|
| 23 |
Note also that the problem has been resolved in the upstream 2.6.35.5 |
| 24 |
and the 2.6.32.22 releases (2.6.32 is currently the long term stable |
| 25 |
branch). |
| 26 |
|
| 27 |
Cheers, |
| 28 |
|
| 29 |
--Kerin |
Archives