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$
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
On Sun, 2012-08-12 at 09:03 -0600, Jesse Rhodes 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?
According to a comment in the code that logs the error message:
* If we are in a noisy environment,
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
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
Ok:
3.2.0-3 (3.2.23-1) also produces the timeouts. So, just use the kernel
from sid isn't even a workaround. I will continue bisecting.
On Thu, Aug 9, 2012 at 10:41 AM, Ben Hutchings b...@decadent.org.uk wrote:
On Thu, Aug 09, 2012 at 09:57:17AM -0600, Jesse Rhodes wrote:
Bisecting away.
tags 681232 - patch
quit
Jesse Rhodes wrote:
(iii) broke,
(iv) worked.
Weird. I can't find any obvious candidate for a patch that would have
broken the driver.
Can you bisect? Even a few iterations would help a lot in narrowing
down the search. It works like so:
cd linux
Bisecting away.
Is 3.2.0-3 (3.2.23-1) from sid exempt from the freeze? I'm going to try
that one as well. If it works, at least it'll likely work for the release,
though we should probably keep hunting for the cause of this bug lest it
surface again.
On Thu, Aug 09, 2012 at 09:57:17AM -0600, Jesse Rhodes wrote:
Bisecting away.
Is 3.2.0-3 (3.2.23-1) from sid exempt from the freeze? I'm going to try
that one as well. If it works, at least it'll likely work for the release,
though we should probably keep hunting for the cause of this bug
Jesse Rhodes wrote:
Well, it's not going to happen when I'm using 3.2.0-2, and it always
happens on 3.2.0-3 rendering it basically useless for a working system
Thanks for clarifying. I missed that you had tried 3.2.21-3 again.
Could you list the versions you've tested, in order, and what
(i) 3.2.21-1 from snapshot produces the gain calibration timeouts.
(ii) so does a rebuild of debian patched 3.2.21-3.
Other kernels tried so far in order (we'll use worked for functional
wifi, and broke for calibration timeouts):
debian 3.2.0-2 (3.2.20-1) worked
debian 3.2.0-3 (3.2.21-3) broke
Hi again,
Jesse Rhodes wrote:
(i) 3.2.21-1 from snapshot produces the gain calibration timeouts.
(ii) so does a rebuild of debian patched 3.2.21-3.
Ok, perfect.
Two more tests:
(iii) patched 3.2.21-3 with .config used for vanilla 3.2.21?
(iv) vanilla 3.2.21 with Debian .config
Thanks
(iii) broke,
(iv) worked.
On Tue, Aug 7, 2012 at 1:17 PM, Jonathan Nieder jrnie...@gmail.com wrote:
Hi again,
Jesse Rhodes wrote:
(i) 3.2.21-1 from snapshot produces the gain calibration timeouts.
(ii) so does a rebuild of debian patched 3.2.21-3.
Ok, perfect.
Two more tests:
Well, it's not going to happen when I'm using 3.2.0-2, and it always
happens on 3.2.0-3 rendering it basically useless for a working system -
not only is my network controller unusable, it also constantly spams the
console with those gain calibration timeout messages.
Since 3.2.0-3 reports itself
tags 681232 + patch moreinfo
quit
Hi,
Russ Lind wrote:
For what it's worth, the 3.5-1 kernel from experimental works for me
[...]
I'd also built the 3.4.7 kernel from the sources at kernel.org.
[...]
I've read about a number of people having this issue thru the 3.3
kernels with various
whoa, I'll see what I can do.
Building the 3.4.7 kernel was my first try at building the kernel, I
downloaded the bz2 file from kernel.org and followed the steps in
Telemachus' post (post #5) in the following thread:
http://forums.debian.net/viewtopic.php?f=16t=36525
I haven't used git
copying my message to everyone else manually because gmail ate my CC.
Hi there,
Steps a. and c.: Neither 3.3.0-rc6 (from snapshots), nor 3.2.21, nor 3.2.20
reproduced the bug. I'm typing this email from 3.2.21 right now with a
fully functional wireless connection.
I skipped step b. due to not
17 matches
Mail list logo
