linux-kernel - Re: kernel bug relating to networking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTikF3ntwWjV3iuwwCnJhZKJMVHHygQ@mail.gmail.com>
Date:	Mon, 16 May 2011 18:47:40 +0300
From:	Daniel Baluta <daniel.baluta@...il.com>
To:	James <bjlockie@...kie.ca>
Cc:	Kernel Mailing List <linux-kernel@...r.kernel.org>,
	netdev@...r.kernel.org
Subject: Re: kernel bug relating to networking

On Mon, May 16, 2011 at 6:35 PM, James <bjlockie@...kie.ca> wrote:
> I originally posted to linux-net@...r.kernel.org but all that list

This should be netdev@...r.kernel.org.

> 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/