Skip to contentSkip to conversation

kernel bug relating to networking

DISCUSSION James 4 participants 5 messages May 16, 2011

Subsystems (2)
lore
Share & tools
lore

James

author
#0 lore raw

I originally posted to [email protected] 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:

Quoted 2 lines

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
#1 lore raw
Quoted 1 line · James

I originally posted to [email protected] but all that list

This should be [email protected].

Quoted 66 lines

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:

Quoted 2 lines

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

#3 lore raw
Quoted 9 lines · James
Quoted 3 lines · Daniel Baluta
Quoted 1 line · James

I originally posted to [email protected] but all that list

This should be [email protected].

That is confusing since the welcome message said: "welcome message for [email protected]".

Both lists are listed at http://vger.kernel.org/vger-lists.html but it doesn't say the difference.

linux-net: spam and unanswered questions
netdev: actual discussions

David, is it not time to stop the confusion by shutting down linux-net?

Ben.

Signature · 3 lines
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
maintainer
#4 lore raw

From: Ben Hutchings <[email protected]>
Date: Mon, 16 May 2011 22:20:25 +0100

Quoted 8 lines · James
Quoted 7 lines · Daniel Baluta
Quoted 3 lines · James
Quoted 1 line

I originally posted to [email protected] but all that list

This should be [email protected].

That is confusing since the welcome message said: "welcome message for [email protected]".

Quoted 7 lines
Quoted 2 lines

Both lists are listed at http://vger.kernel.org/vger-lists.html but it doesn't say the difference.

linux-net: spam and unanswered questions
netdev: actual discussions

David, is it not time to stop the confusion by shutting down linux-net?

Agreed, linux-net has been deleted.