From: James <bjlockie@lockie.ca>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: kernel bug relating to networking
Date: Mon, 16 May 2011 11:35:00 -0400 [thread overview]
Message-ID: <4DD14424.8000003@lockie.ca> (raw)
I originally posted to linux-net@vger.kernel.org but all that list
received in the last day was 3 Russian (spam?) messages.
I'm hoping here will be less spam.
I'm having a wireless problem that I think is kernel issue.
kernel-2.6.36.4 is good but recent kernels are bad.
CompatWireless (recent wireless code) works on kernel-2.6.36.4 so I
don't think it is the wireless subsystem..
I have a Network controller: Atheros Communications Inc. AR5008 Wireless
Network Adapter (rev 01).
"iwlist wlan0 scan | grep SSID" under kernel-2.6.36.4 returns ~15 APs
and associates to my AP.
Recent kernels are bad and return ~0-3 APs and do not associate to my AP.
I need help to debug this.
I think the scans fail whenever dmesg shows this:
> ath: Failed to stop TX DMA in 100 msec after killing last frame
> ath: Failed to stop TX DMA!
It seems to be 100% if I boot a kernel and that message is there, it'll
be a bad kernel.
I tried:
$ git clone
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.37.y.git
$ cd linux-2.6.37.y
# git tag
What tag is 2.6.36.4?
v2.6.36
v2.6.36-rc1
v2.6.36-rc2
v2.6.36-rc3
v2.6.36-rc4
v2.6.36-rc5
v2.6.36-rc6
v2.6.36-rc7
v2.6.36-rc8
v2.6.37
v2.6.37-rc1
v2.6.37-rc2
v2.6.37-rc3
v2.6.37-rc4
v2.6.37-rc5
v2.6.37-rc6
v2.6.37-rc7
v2.6.37-rc8
v2.6.37.1
v2.6.37.2
v2.6.37.3
v2.6.37.4
v2.6.37.5
v2.6.37.6
Is the next step to do:
$ git bisect start
$ git bisect good v2.6.36.4
$ git bisect bad v2.6.37.6
next reply other threads:[~2011-05-16 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 15:35 James [this message]
2011-05-16 15:47 ` kernel bug relating to networking Daniel Baluta
2011-05-16 20:47 ` James
2011-05-16 21:20 ` Ben Hutchings
2011-05-16 21:27 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DD14424.8000003@lockie.ca \
--to=bjlockie@lockie.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.