On Sat, Jan 23, 2010 at 10:32 AM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote: > On Sat, Jan 23, 2010 at 8:40 AM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: >> So it looks like we receive some strange packets that haven’t been >> explained yet. It might be worth looking at a few --- sounds kind of >> interesting. >> >> Am I understanding correctly? This is a hardware bug or undocumented >> hardware feature then, right? >> >> It might be nice to add some user-oriented explanation too, but for >> now, how about this comment? >> > > That's ok with me. I'd also be fine with removing the log spam. I think > ultimately it represents some kind of driver issue, I'm just not sure what, > exactly, yet. I recently added more debugging to a kernel on a system of > mine that produces it more often -- I'll see what it turns up. Jumbo frames are frames which the hardware receives for which it does not have enough DMA leg room for, and so needs to split it out into multiple descriptors. It should be OK to just drop them if ath5k is setting the max RX dma size to the max 802.11 frame, as they could be bogus frames or 11n AMSDU frames which ath5k obviously would not support. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
