On Tue, Aug 6, 2013 at 6:51 PM, Sedat Dilek [off-list ref] wrote:
On Tue, Aug 6, 2013 at 6:07 PM, Sedat Dilek [off-list ref] wrote:
quoted
On Tue, Aug 6, 2013 at 6:03 PM, Johannes Berg [off-list ref] wrote:
quoted
[reducing mailing lists - Stephen if you want off let us know]
On Tue, 2013-08-06 at 17:58 +0200, Sedat Dilek wrote:
quoted
$ cat /proc/version
Linux version 3.11.0-rc4-1-wl-20130805 (sedat.dilek@gmail.com@fambox)
(gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #1 SMP Tue Aug 6
17:52:45 CEST 2013
This kernel boots fine and has no WiFi problems.
quoted
You assume a breakage in a different area than wireless or network in general?
Any wild guess?
Not really, but maybe you can pull the other trees on top again and see
if those broke it? I don't really think/hope so but it's possible that
one of my pending pull requests broke it, I guess?
Hmm, I pulled in latest for-john of mac80211(-next) and
iwlwifi-(fixes|next) which did not help.
I am testing next-20130805 and next-20130802 to identify which
Linux-next release is BROKEN.
GOOD: next-20130801 and next-20130802
BROKEN: next-20130805 and next-20130806
Comparing diffs between next-20130802 and next-20130805.
[ To Dave and CC netdev ]
[ Full thread see [1] ]
The diff was not very helpful.
$ cd linux-next-20130805
$ git log --oneline v3.11-rc4.. | grep "Merge remote-tracking" | egrep
'net-next|slave-dma|wireless'
7f84622 Merge remote-tracking branch 'net-next/master' <--- BAD
(before slave-dma/next)
3580d24 Merge remote-tracking branch 'slave-dma/next' <--- GOOD (after
net-next/master)
88825c7 Merge remote-tracking branch 'wireless/master' <--- GOOD
So, the culprit commit seems to be in the merge of 'net-next/master'.
( BTW, disabling IPv6 in NM/wifi-setup did not change behaviour -
still disconnected to AP. )
- Sedat -
[1] http://marc.info/?t=137579712800008&r=1&w=2