On Sun, Sep 21, 2008 at 11:54 PM, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote: > On Sat, Sep 20, 2008 at 06:48:05PM -0700, Steven Noonan wrote: >> >> OK, here's the time index at which it b0rked: >> >> 18:28:42 sum 1155.00 >> 18:28:43 sum 1339.00 >> 18:28:44 sum 18355.00 >> 18:28:45 sum 17845.45 >> >> And the entire log of the minute 18:28 is here: >> http://www.uplinklabs.net/~tycho/linux/18.28.00-59.log.gz >> >> It looks pretty crazy. > > Thanks, I'll take a look when I get a chance (remember aggretion > is in the queue too) unless someone beats me to it. > You may want to take a quick look at it now. I certainly don't mean you should push aggregation aside, but the log looks kind of screwy at 18:28:43 (look at line 4972 to see what I mean). It looks as though it did printk()s from multiple threads with no locking mechanism. It's possible I will need to re-capture the error, and I'd like to know if this log will help or not. - Steven -- 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
