Comments interleaved below .... On Thu, May 27, 2010 at 5:41 AM, Bruno Randolf <b...@einfach.org> wrote: > On Thursday 27 May 2010 17:02:12 Roman Yepishev wrote: >> Usually this happens when a continuous block of data is transmitted, >> i.e. during deb packages updates via http. >> When corruption happens this is accompanied by >> [ 469.663234] ath5k phy0: unsupported jumbo >> [ 469.935929] ath5k phy0: unsupported jumbo > > that might be a good clue! robert do you see the same? in newer kernels we > have removed the warning, however...
Yes, I have also seen the unsupported jumbo messages when data was corrupted. I have also seen the messages without noticing corrupt data, so there may not be a one-to-one mapping between the messages and data corruption. Could be coincidence, but definitely worth checking out. I don't remember seeing an instance of corruption without also seeing the jumbo message (except for newer driver releases that don't print it). > how easy is it for you to reproduce the problem? do you know any kernel > version where this problem didn't happen? I first noticed the problem 6 or 8 months ago with Ubuntu Karmic, but I had been using that OS for some time and the kernel had been updated several times. Anyway, I think it's likely that some older kernel/driver combinations work fine. Perhaps I should try 6 month or 1 year old compat-wireless releases to see if they work well with my current kernel and Ubuntu Lucid. bob _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
