As far as the errors from the driver goes, the first one I see is "could not activate Heartbeat timer" (not sure yet what the heartbeat timer does, perhaps expiring peer STAs in the IBSS network when beacons aren't seen for some period). This is printed using some internal logging functions and has the log level LOGP, and any message of this log level will trigger the stack trace.
There's a few ways for enabling the heartbeat timer to fail. The first is that some ACTIVEMODE_OFFLOAD feature is enabled, the second is that the timer hasn't been initialized, and the third is that the actual timer activation fails for any of a variety of reasons. There's no clues in the log about why it failed. However it's also not apparent whether or not failing to activate the heartbeat timer is fatal. The driver just logs the error and continues on. Without digging deeper into the driver I can't tell whether it's the cause for IBSS not working; it could just be a symptom of a larger hardware misconfiguration or even unrelated to the other observed issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337753 Title: [mako] can not create an ad-hoc network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1337753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
