Comment 144 for bug 286285

I began exhibiting these problems upgrading from gutsy to hardy to ibex the other day, and it got annoying fast. I updated a bit ago to the -10 kernel, and it's much better now. Thanks!

The only side-effect I'm seeing thus far is my thinkfinger/fingerprint hardware is broken and my wireless won't auto-connect any longer after a reboot or suspend/awake. It's a 4965, so i'm assuming it is affected somehow in all of this as you mention iwl specifically. The kernel and firmware blobs are included in the kernel releases, no? Are there separate iwl updates that need applied? Am I the only one seeing this?

Flicking off and on the wireless seems to get it going again. When Network Manager tries, I never see the driver actually attempt to connect to my ssid via iwconfig, though NM clearly says it's trying. After reloading the hardware via hotpug and the switch, NM connects to the ssid, and auths fine. I'll check it a bit more with another suspend or boot to see if the hardware probes properly. Dmesg shows some oddities, included as attachment - my ap is xx:xx...

Something is amiss as NM was perfect before this scheduler bug became an issue. Thoughts on if you believe this was a direct relation to the kernel changes?

I'm not at all sure what's up with the fingerprint reader either, it seems to probe just fine, but I get no response when I attempt "tf-tool --acquire", which normally I would. I was using a dev build of the driver, not the stock ubuntu package, so I'll try reapplying. This pretty much breaks anyone with a thinkpad or dell at moment using that driver.

Let me know if you'd like any specific info, I'd be happy to dig into it a bit more as the hardware switch will get annoying fast.