I should also note that if I load powernow_k8 *after* my wireless is already working, the bug does not return. It only seems to happen if powernow_k8 loads first.
On Sun, Aug 12, 2012 at 9:03 AM, Jesse Rhodes <dr...@drubo.net> wrote: > Yes, it does! Confirmed on both bcf3655... and 3.2.0-3 from sid. Why would > a cpufreq module break a PCI wireless card like that? > > On Sat, Aug 11, 2012 at 9:43 PM, Ben Hutchings <b...@decadent.org.uk>wrote: > >> On Sat, 2012-08-11 at 21:17 -0600, Jesse Rhodes wrote: >> > sney@bivouac:~/data/debian/linux$ git bisect good >> > bcf3655971d24d7f08f373ed5830e8e11010088a is the first bad commit >> > commit bcf3655971d24d7f08f373ed5830e8e11010088a >> > Author: Andi Kleen <a...@linux.intel.com> >> > Date: Thu Jan 26 00:09:12 2012 +0100 >> > >> > cpufreq: Add support for x86 cpuinfo auto loading v4 >> [...] >> >> So does the problem go away if you unload the cpufreq driver >> (powernow_k8)? >> >> Ben. >> >> -- >> Ben Hutchings >> Sturgeon's Law: Ninety percent of everything is crap. >> > >
