On Tue, Oct 12, 2010 at 9:46 PM, Bob Copeland <m...@bobcopeland.com> wrote: > On Tue, Oct 12, 2010 at 03:39:01PM +1000, Jonathan Guerin wrote: >> >> Try turning off CONFIG_NETWORK_PHY_TIMESTAMPING. >> >> >> 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? > > No, I think it's more likely that no one uses that config option; > I think it's fairly new and I'm pretty sure ath5k at least doesn't > support it. But the timestamping code seems weird to me, I'll > have to read it more closely. > > You may also try keeping the option on and reverting the following > patch to see if it makes a difference. > > commit b61279809860690fe5c9fcb40441008d31fabab6 > Author: Nick Kossifidis <mickfl...@gmail.com> > Date: Sun Aug 15 13:03:11 2010 -0400 > > ath5k: remove own (wrong) IEEE80211_MAX_LEN > > Use the version already supplied in include/linux/ieee80211.h.
I'll try that tomorrow! Thanks, Jonathan > > > -- > Bob Copeland %% www.bobcopeland.com > > _______________________________________________ > ath5k-devel mailing list > ath5k-devel@lists.ath5k.org > https://lists.ath5k.org/mailman/listinfo/ath5k-devel > _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
