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=16&t=36525
I haven't used git before but I will give your steps a try.
I definitely did not have this problem with the 3.2.20 Debian kernel
build. I diff'd the 3.2.20 and 3.2.21 kernel code (from kernel.org) in
net/wireless/ath and I didn't see any differences so I was surprised the
issue started happening with 3.2.21.
On 08/05/2012 01:37 AM, Jonathan Nieder wrote:
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 distros, and read the issue was supposedly
fixed in the 3.4 branch. I get the impression it's an upstream
issue.
Maybe one of the following patches helped.
v3.3-rc1~182^2~44^2~292 ath5k: Calibration re-work
v3.4-rc1~177^2~108^2~108 ath5k: do not stop queues for full
calibration
v3.4-rc1~177^2~108^2~107 ath5k: do not re-run AGC calibration
periodically
What seems oddest to me is that I'm not aware of any patches from
the range 3.2.20->3.2.21 that might have had this effect. Are you
sure that 3.2.20 did not reproduce the bug? If you have time to try
one of the following, I'd be interested:
a. Please test v3.2.20 and v3.2.21 from kernel.org, following
instructions from [1] or the following steps:
# get the kernel history, if you don't already have it
git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
# fetch point releases:
cd linux
git remote add stable \
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
git fetch stable
# configure, build, test:
git checkout v3.2.21
cp /boot/config-$(uname -r) .config; # current configuration
scripts/config --disable DEBUG_INFO
make localmodconfig; # optional: minimize configuration
make deb-pkg; # optionally with -j<num> for parallel build
dpkg -i ../<name of package>; # as root
reboot
... test test test ...
# hopefully it reproduces the bug, so try the older kernel:
cd linux
git checkout v3.2.20
make deb-pkg; # maybe with -j4
dpkg -i ../<name of package>; # as root
reboot
... test test test ...
# hopefully it does not reproduce the bug
b. If (a) goes well, please bisect to find which patch introduced
the bug, as described at [2]:
cd linux
git bisect start
git bisect good<some known-good kernel>
git bisect bad v3.2.21
# a version halfway between is automatically checked out
make deb-pkg; # maybe with -j4
dpkg -i ../<name of package>; # as root
reboot
... test test test ...
cd linux
git bisect good; # if it works well
git bisect bad; # if it reproduces the calibration timeouts
git bisect skip; # if some other bug makes it hard to test
... rinse and repeat until it prints the "first bad commit"
or until bored ...
# at any step, to see the regression range narrowing
apt-get install gitk
git bisect visualize
# to get a log of revs tested so far, which will let someone
# else pick up where you left off
git bisect log
c. How does a pre-compiled 3.3 kernel from http://snapshot.debian.org
do?
d. Please test the three attached patches together against a 3.2.y
kernel, following the directions at [3] or the following
instructions:
cd linux
git checkout stable/linux-3.2.y
git am -3sc $(ls -1 /path/to/patches/0[123]-*)
make deb-pkg; # maybe with -j4
dpkg -i ../<name of package>; # as root
reboot
... test test test ...
Hope that helps,
Jonathan
[1]
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package
[2] http://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.2.1
[3]
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/501e8d6b.6060...@comcast.net
