On Tue, Oct 12, 2010 at 10:58 AM, Jonathan Guerin <jonat...@guerin.id.au> wrote: > On Mon, Oct 11, 2010 at 10:56 PM, Bob Copeland <m...@bobcopeland.com> wrote: >> By the way, I just got a chance to look at the stack trace. >> >> Try turning off CONFIG_NETWORK_PHY_TIMESTAMPING. >> >> It seems the skb doesn't have enough headroom for the >> skb_pull(skb, ETH_HLEN) in skb_defer_rx_timestamp. > > By the way, does turning this off mean that timestamps will be > generated using the CPU's clock instead?
I can confirm that this fix does indeed stop the panics. Could the reason this can't be replicated by the amount of RAM on the machine, compared to your dev machines? Thanks, Jonathan > > Thanks, > > Jonathan > _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
