Juan owns Lenovo affected by well-known LP-PHY DMA errors. His testing procedure is following: modprobe wl; connect; download sth small; rmmod wl; modprobe b43; download 2GB When working on DMA errors we discovered that wireless-testing is not working well for him. Even after performing above procedure his machine disconnects quickly and he is not able to reconnect. We tested 2.6.39-rc6 from tarball and it was working fine. I'd like to highlight here, that we were switching between mainline and wireless-testing few times. It is not a random issue. I suspected this regression could be caused by my recent ssb patches. So I reverted all of them but this didn't help. In this situation we decided to bisect. I was a little afraid of last merges so we took older 2.6.38 as GOOD (we tested this twice) and wireless-testing commit before my ssb changes as BAD. Today Juan finished bisecting kernel: http://pastebin.com/HSKbRzpB According to his bisection the first bad commit is e06383db9ec591696a06654257474b85bac1f8cb [0]: hrtimers: extend hrtimer base code to handle more then 2 clockids Does it make any sense to you? Could this be some timing issue? It was too late to test this today, we (Juan) will work on this tomorrow. It's impossible to revert this commit from HEAD of wireless-testing, so my idea is to checkout commit, test, revert, test. Did anyone else experience any similar problems with latest wireless-testing? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e06383db9ec591696a06654257474b85bac1f8cb -- RafaÅ -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
