This is a rather strange bug:
- It happens if I enable exactly two out of the three modules deflate, reqtimeout, dump_io. But not with only one or all three of them.
- I have also tried replacing mod_ssl.so, mod_deflate.so, and the openssl-libs with the versions from karmic and mod_ssl.so with the version from jaunty: no change
But the bug disappears if I do
mv /lib/i686 /lib/disabled_i686
There was a bug recently in Debian related to some gcc versions creating wrong code for SSE4. Maybe that is the problem here, too.
What CPUs do you people have? Mine is a Core i7.
Does moving /lib/i686 away (or deinstalling libc6-i686) help for you too?
Does the "flags" line in /proc/cpuinfo on your machines contain sse4_1 or sse4_2?
This is a rather strange bug:
- It happens if I enable exactly two out of the three modules deflate, reqtimeout, dump_io. But not with only one or all three of them.
- I have also tried replacing mod_ssl.so, mod_deflate.so, and the openssl-libs with the versions from karmic and mod_ssl.so with the version from jaunty: no change
But the bug disappears if I do
mv /lib/i686 /lib/disabled_i686
There was a bug recently in Debian related to some gcc versions creating wrong code for SSE4. Maybe that is the problem here, too.
What CPUs do you people have? Mine is a Core i7.
Does moving /lib/i686 away (or deinstalling libc6-i686) help for you too?
Does the "flags" line in /proc/cpuinfo on your machines contain sse4_1 or sse4_2?
For reference, the Debian bug was http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 583858