Christoph Hellwig writes: > does this still happen with 2.6.8? I've only seen it happen once with 2.6.7 and with 2.6.8 I'm somewhat blocked because I've got an atheros wireless chip and the driver doesn't work there yet. The problem did show up without the atheros madwifi driver, though.
Is there any kind of debugging that can be turned on so that if it does happen again, I'll have more data for you? Jerry
