On Sun, Mar 22, 2009 at 8:56 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Sun, 2009-03-22 at 17:45 +0500, Alexander E. Patrakov wrote: > >> There are several different panic messages, >> the common thing is "Fatal exception in interrupt". Without uvesafb, >> they also include "zd_op_tx+0x98/0x1cc [zd1211rw]" as the last line, > > http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commitdiff;h=3b23889bb2366c1b10f69bcca16cf53426b5e309 > >> but with uvesafb, this sometimes changes to >> "rate_control_get_rate+0xb7/0xc3 [mac80211]". Hmm, I've seen the rate_control one before, and there's a guy with ath5k who can reproduce it easily. Looks like minstrel somehow gets confused about the rate table and eventually tries to use -1 as a valid rate index. Neither I nor Felix could come up with a logical explanation, though (I am completely lost in the RC code, so that's not saying much for me). He is using ad-hoc too - but I use adhoc on a daily basis and haven't seen it myself. Bugzilla is here: http://bugzilla.kernel.org/show_bug.cgi?id=12490 By the way Alexander, W taint means the kernel already warned about something, probably that get_tx_rate is returning null. -- Bob Copeland %% www.bobcopeland.com -- 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