You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
It could be bad luck?
Console scrollback OOMs machine. Something something blocking in the network path ends up breaking the wifi. Firmware restarts, meanwhile all this triggers too much time blocked in irq context and PS/2 buffer doesn't get read in time, fills up, loses sync. That's my guess anyway
I can believe all that but I don't understand how the wifi fail is manifesting as a firmware crash. You would think that would most likely be hardware initiated.
Actually it just says it was a timeout, maybe it didn't crash and it was just the driver misinterpreting a CPU stall due to OOM as a hardware stall? And then the response to that is resetting the hardware and reloading firmware and dumping registers unconditionally.
You lost me rip
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
