Bug#377959: problem exists also in 18.104.22.168
On Mon, 17 Jul 2006, Toni Mueller wrote:
> I just created a 22.214.171.124 kernel (patch as of yesterday), and tried
> again, with much the same results. So, I suspect it's somewhere in the
> guts of the 2.6.17 kernel - switching back to 2.6.16 also brings
> performance back to acceptable levels (already included in the report).
> Should I report this bug upstream?
how is linux image 2.6.18 performing?
thanks for an update.