scan not working or limited

scan not working or limited

[James]

I get the errors:
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA!
on all the kernels that my scans don't work right.

I did:
$ 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 bisect start
$ git bisect good v2.6.36
$ git bisect bad v2.6.37.6
It said 3044100e58c84e133791c8b60a2f5bef69d732e4 is the first bad commit.

I typed that number. :-(
How do I make git print it again?
How do I find the details of that commit?
How do I reverse what that commit did?

Re: scan not working or limited

[Mohammed Shafi]

On Fri, May 6, 2011 at 10:57 AM, James <bjlockie@lockie.ca> wrote:
>
> I get the errors:
> ath: Failed to stop TX DMA in 100 msec after killing last frame
> ath: Failed to stop TX DMA!
> on all the kernels that my scans don't work right.
>
> I did:
> $ 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 bisect start
> $ git bisect good v2.6.36
> $ git bisect bad v2.6.37.6
> It said 3044100e58c84e133791c8b60a2f5bef69d732e4 is the first bad commit.
>
> I typed that number. :-(
> How do I make git print it again?
> How do I find the details of that commit?

git show 3044100e58c84e133791c8b60a2f5bef69d732e4

> How do I reverse what that commit did?

git revert 3044100e58c84e133791c8b60a2f5bef69d732e4

but that commit is not related to the problem you have

>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: scan not working or limited

[James]

On 05/06/11 01:49, Mohammed Shafi wrote:
> On Fri, May 6, 2011 at 10:57 AM, James <bjlockie@lockie.ca> wrote:
>> I get the errors:
>> ath: Failed to stop TX DMA in 100 msec after killing last frame
>> ath: Failed to stop TX DMA!
>> on all the kernels that my scans don't work right.
>>
>> I did:
>> $ 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 bisect start
>> $ git bisect good v2.6.36
>> $ git bisect bad v2.6.37.6
>> It said 3044100e58c84e133791c8b60a2f5bef69d732e4 is the first bad commit.
>>
>> I typed that number. :-(
>> How do I make git print it again?
>> How do I find the details of that commit?
> git show 3044100e58c84e133791c8b60a2f5bef69d732e4
>
>> How do I reverse what that commit did?
> git revert 3044100e58c84e133791c8b60a2f5bef69d732e4
>
> but that commit is not related to the problem you have
$ git checkout v2.6.37.6

$ git revert 3044100e58c84e133791c8b60a2f5bef69d732e4
fatal: Commit 3044100e58c84e133791c8b60a2f5bef69d732e4 is a merge but no
-m option was given.