On Wed, 2014-12-31 at 06:08 -0200, Rogério Brito wrote:
> unarchive 764162
> found 764162 3.16.7-ckt2-1
> notfound 764162 3.16.7-2
> thanks
>
> Hi.
>
> I have a Kurobox Pro that I use as a NAS and I was affected by the network
> corruption when the TSO was enabled in versions 3.16 before the version with
> the "workaround" on the mv643xx_eth (not having seen the code, from a user's
> perspective, this workaround was more like a fix than a dirty hack).
The workaround was just turning off the feature.
Please can you clarify which of these kernels did/didn't work (or for
which you have no data):
* 3.16.7-1 (has the bug)
* 3.16.7-2 (with the hack/workaround of disabling TSO by default)
* 3.16.7-ckt2-1 (with the supposed proper fix, 2c2a9cb from
upstream, backported via the -ckt tree)
FWIW I am running 3.16.7-ckt2-1 on my kirkwood based ts-419 right now
and it seems fine. It's possible that your system has a separate issue
or is somehow more susceptible to the original (Which IIRC was cache
based, so could affect different platforms differently).
Please can you also confirm that flash-kernel has been run and is
picking up the correct kernel image, i.e. it hasn't installed an old
kernel for you or something like that. "uname -v" includes the actual
running version.
> Can we get a fix for this in time for jessie?
If one can be found of course we will try and apply it.
Since I can't reproduce it would be useful if you could take this issue
to the upstream developers who were involved in the original bug report
and work with them directly to find a cure.
If we can't find one then I suppose we will fall back to just disabling
TSO by default on these systems.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
