| 1 |
On Sun, Aug 22, 2010 at 8:35 PM, Alan Warren <bluemoonshine@×××××.com> wrote: |
| 2 |
> I think you are correct though. It does seem to only happen while the system |
| 3 |
> is under heavy I/O. |
| 4 |
> |
| 5 |
> I've never experienced anything like this in previous versions of the linux |
| 6 |
> kernel, |
| 7 |
> and resorting back to gentoo-sources-2.6.34 fixes the issue completely. |
| 8 |
> |
| 9 |
> If there are I/O fixes upstream, then I am assuming you are referring to a |
| 10 |
> cut |
| 11 |
> that is more recent then gentoo-sources-2.6.35-r2 that the Gentoo devs have |
| 12 |
> yet to provide their patches to? ( I see vanilla sources has 2.6.35 .3) |
| 13 |
|
| 14 |
Well, the fix is in the line for 2.6.36 IIRC, so wouldn't be in an |
| 15 |
2.6.35 kernel. |
| 16 |
|
| 17 |
That said, the problem supposedly being fixed goes back well before |
| 18 |
2.6.34, so if that kernel works, it suggests that it is a different |
| 19 |
issue you are hitting. However... If there was a FF update, that could |
| 20 |
be triggering the bug, as FF3.5+ are pretty stinky for I/O levels. |
Archives