Have it catched again on kernel 3.2.0 final, this time right after the stacktraces my system crashed. I have had to shut it down the hardway. Some indodes became corrupteted, but were cleaned uped the next start as far as I could see.
I attach the stacktraces again from begiining until system crashed(not much). There are points on it: With kernel 3.2.0 final the error become rarer than with 3.2.0rc7. Instead of the error you could see in mass what I have posted in #5. The stacktraces looks verry similiar, but they are not really the same. At timepoint of crashing the log shows nothing, only the stacktrace of the ath9k error. Than follows the newstart sequence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/910519 Title: network breaks - ath9k for TP-Link 5008 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/910519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
