Alas, I spoke too soon, but did get good data out of it.
For my report above (#26 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/548992/comments/26) I had done the grub modification, reboot and testing remotely from a machine other than the troubled "flatguy". I was ssh'ed into flatguy in multiple sessions, running netperf and such, but the laptop itself was physically untouched. Since reboot, the console was running gdm waiting for a login.
After posting, I logged in on flatguy's console and logged six WiFi deauthentications in 17 minutes. However, this information does place the triggering event firmly in some user-space application.
Now I can stop groveling through the kernel WiFi stack and hunt through the Kubuntu XFCE start-up processes for the trigger. Sigh.
Alas, I spoke too soon, but did get good data out of it.
For my report above (#26 https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/548992/ comments/ 26) I had done the grub modification, reboot and testing remotely from a machine other than the troubled "flatguy". I was ssh'ed into flatguy in multiple sessions, running netperf and such, but the laptop itself was physically untouched. Since reboot, the console was running gdm waiting for a login.
After posting, I logged in on flatguy's console and logged six WiFi deauthentications in 17 minutes. However, this information does place the triggering event firmly in some user-space application.
Now I can stop groveling through the kernel WiFi stack and hunt through the Kubuntu XFCE start-up processes for the trigger. Sigh.