scan not working or limited

DISCUSSION James 2 participants 3 messages May 6, 2011

Share & tools

James

author

2011-05-06 05:36 UTC #0 lore raw

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?

Mohammed Shafi

2011-05-06 05:49 UTC #1 lore raw

Quoted 15 lines · 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.

Quoted 3 lines

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

git show 3044100e58c84e133791c8b60a2f5bef69d732e4

Quoted 1 line

How do I reverse what that commit did?

git revert 3044100e58c84e133791c8b60a2f5bef69d732e4

but that commit is not related to the problem you have

Quoted 6 lines

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

James

author

2011-05-06 13:29 UTC #2 lore raw

Quoted 18 lines · Mohammed Shafi

Quoted 14 lines · 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.
Quoted 3 lines
I typed that number. :-(
How do I make git print it again?
How do I find the details of that commit?

Quoted 6 lines

git show 3044100e58c84e133791c8b60a2f5bef69d732e4
Quoted 1 line
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.