Message ID | 20140908191630.GB29412@tuxdriver.com |
---|---|
State | Accepted, archived |
Delegated to: | David Miller |
Headers | show |
From: "John W. Linville" <linville@tuxdriver.com> Date: Mon, 8 Sep 2014 15:16:31 -0400 > Please pull this batch of updates intended for the 3.18 stream... Pulled into net-next, thanks a lot John. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello John, all, on my i7 Laptop with iwlwifi the latest net-next does not connect to my access point: [ 10.305284] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S [ 10.312179] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1 [ 10.524936] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S [ 10.531762] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1 [ 10.614189] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 17.097238] wlan0: authenticate with 84:c9:b2:d5:87:80 [ 17.130120] wlan0: send auth to 84:c9:b2:d5:87:80 (try 1/3) [ 17.922281] wlan0: send auth to 84:c9:b2:d5:87:80 (try 2/3) [ 18.935272] wlan0: send auth to 84:c9:b2:d5:87:80 (try 3/3) [ 19.936236] wlan0: authentication with 84:c9:b2:d5:87:80 timed out [ 21.962337] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 0 [ 21.962348] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 3 [ 21.962413] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [ 21.962455] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000 [ 21.962491] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x00000000 [ 21.962528] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000 [ 21.962564] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x00000000 [ 21.962600] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000 [ 21.962636] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000 [ 21.962673] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000 [ 21.962709] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x0070402f [ 21.962790] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [0,3] [ 21.962869] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [0,0] [ 21.962949] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [0,0] [ 21.963030] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963109] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 7 ra_tid 0x0000 [48,48] [ 21.963189] iwlwifi 0000:02:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963270] iwlwifi 0000:02:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963350] iwlwifi 0000:02:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963428] iwlwifi 0000:02:00.0: Q 8 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963508] iwlwifi 0000:02:00.0: Q 9 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963588] iwlwifi 0000:02:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963669] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963750] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963829] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963909] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.963988] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.964069] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.964149] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.964228] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 21.964308] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] [ 22.116816] wlan0: authenticate with xx:xx:xx:xx:xx:xx [ 22.155887] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3) (..) and again and again ... Mainly this is the changing stuff in the following dmesg output: [ 21.962348] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 3 [ 26.951325] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 6 [ 34.979316] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 9 [ 39.964287] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 12 [ 47.984243] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 15 [ 55.984240] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 18 [ 60.981221] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 21 [ 73.878064] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 24 [ 86.342476] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 27 [ 98.770854] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 30 [ 111.287320] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 33 [ 121.045034] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 36 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) Any idea? Regards, Oliver -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Sep 09, 2014 at 09:46:47PM +0200, Oliver Hartkopp wrote: > Hello John, all, > > on my i7 Laptop with iwlwifi the latest net-next does not connect to my access point: > > [ 10.305284] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S > [ 10.312179] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1 > [ 10.524936] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S > [ 10.531762] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1 > [ 10.614189] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > [ 17.097238] wlan0: authenticate with 84:c9:b2:d5:87:80 > [ 17.130120] wlan0: send auth to 84:c9:b2:d5:87:80 (try 1/3) > [ 17.922281] wlan0: send auth to 84:c9:b2:d5:87:80 (try 2/3) > [ 18.935272] wlan0: send auth to 84:c9:b2:d5:87:80 (try 3/3) > [ 19.936236] wlan0: authentication with 84:c9:b2:d5:87:80 timed out > [ 21.962337] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 0 > [ 21.962348] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 3 > [ 21.962413] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > [ 21.962455] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000 > [ 21.962491] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x00000000 > [ 21.962528] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000 > [ 21.962564] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x00000000 > [ 21.962600] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000 > [ 21.962636] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000 > [ 21.962673] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000 > [ 21.962709] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x0070402f > [ 21.962790] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [0,3] > [ 21.962869] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [0,0] > [ 21.962949] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [0,0] > [ 21.963030] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963109] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 7 ra_tid 0x0000 [48,48] > [ 21.963189] iwlwifi 0000:02:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963270] iwlwifi 0000:02:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963350] iwlwifi 0000:02:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963428] iwlwifi 0000:02:00.0: Q 8 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963508] iwlwifi 0000:02:00.0: Q 9 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963588] iwlwifi 0000:02:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963669] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963750] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963829] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963909] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963988] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.964069] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.964149] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.964228] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.964308] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 22.116816] wlan0: authenticate with xx:xx:xx:xx:xx:xx > [ 22.155887] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3) > > (..) > > and again and again ... > > Mainly this is the changing stuff in the following dmesg output: > > [ 21.962348] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 3 > [ 26.951325] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 6 > [ 34.979316] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 9 > [ 39.964287] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 12 > [ 47.984243] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 15 > [ 55.984240] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 18 > [ 60.981221] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 21 > [ 73.878064] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 24 > [ 86.342476] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 27 > [ 98.770854] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 30 > [ 111.287320] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 33 > [ 121.045034] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 36 > > 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) > > Any idea? > > Regards, > Oliver Hopefully the Intel guys are listening. As a hunch, what sort of encryption are you using? John
On Tue, Sep 9, 2014 at 10:46 PM, Oliver Hartkopp <socketcan@hartkopp.net> wrote: > Hello John, all, > > on my i7 Laptop with iwlwifi the latest net-next does not connect to my access point: Are you sure this wasn't the case before? Can you bisect? > > [ 10.305284] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S > [ 10.312179] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1 > [ 10.524936] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S > [ 10.531762] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1 > [ 10.614189] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > [ 17.097238] wlan0: authenticate with 84:c9:b2:d5:87:80 > [ 17.130120] wlan0: send auth to 84:c9:b2:d5:87:80 (try 1/3) > [ 17.922281] wlan0: send auth to 84:c9:b2:d5:87:80 (try 2/3) > [ 18.935272] wlan0: send auth to 84:c9:b2:d5:87:80 (try 3/3) > [ 19.936236] wlan0: authentication with 84:c9:b2:d5:87:80 timed out > [ 21.962337] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 0 > [ 21.962348] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 3 > [ 21.962413] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > [ 21.962455] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000 > [ 21.962491] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x00000000 > [ 21.962528] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000 > [ 21.962564] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x00000000 > [ 21.962600] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000 > [ 21.962636] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000 > [ 21.962673] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000 > [ 21.962709] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x0070402f > [ 21.962790] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [0,3] > [ 21.962869] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [0,0] > [ 21.962949] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [0,0] > [ 21.963030] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963109] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 7 ra_tid 0x0000 [48,48] > [ 21.963189] iwlwifi 0000:02:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963270] iwlwifi 0000:02:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963350] iwlwifi 0000:02:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963428] iwlwifi 0000:02:00.0: Q 8 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963508] iwlwifi 0000:02:00.0: Q 9 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963588] iwlwifi 0000:02:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963669] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963750] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963829] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963909] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.963988] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.964069] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.964149] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.964228] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 21.964308] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0] > [ 22.116816] wlan0: authenticate with xx:xx:xx:xx:xx:xx > [ 22.155887] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3) > > (..) > > and again and again ... > > Mainly this is the changing stuff in the following dmesg output: > > [ 21.962348] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 3 > [ 26.951325] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 6 > [ 34.979316] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 9 > [ 39.964287] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 12 > [ 47.984243] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 15 > [ 55.984240] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 18 > [ 60.981221] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 21 > [ 73.878064] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 24 > [ 86.342476] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 27 > [ 98.770854] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 30 > [ 111.287320] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 33 > [ 121.045034] iwlwifi 0000:02:00.0: Current SW read_ptr 0 write_ptr 36 > > 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) > > Any idea? > > Regards, > Oliver > > -- > 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 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 09.09.2014 21:52, John W. Linville wrote: > > Hopefully the Intel guys are listening. As a hunch, what sort of > encryption are you using? They are :-) I'm using WPA2. Regards, Oliver -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 09.09.2014 22:02, Emmanuel Grumbach wrote: > On Tue, Sep 9, 2014 at 10:46 PM, Oliver Hartkopp <socketcan@hartkopp.net> wrote: >> Hello John, all, >> >> on my i7 Laptop with iwlwifi the latest net-next does not connect to my access point: > > Are you sure this wasn't the case before? Indeed I moved to net-next right today - as I also had the LED lockdep splat on 3.17-rcX with X < 4. So it can be that this issue was already introduced at the beginning of this net-next cycle. Don't know, sorry. The latest 3.17-rc4 from Linus' tree works fine. I'm running a Debian unstable here (in both cases). > Can you bisect? Not really. I'm running the kernel on my bare machine - and I just wanted to go to bed right now ... So I will be able to test patches tomorrow morning again. Tnx for your fast feedback, Oliver -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
I have the same issue with iwlwifi. On Tue, Sep 9, 2014 at 11:23 PM, Oliver Hartkopp <socketcan@hartkopp.net> wrote: > On 09.09.2014 22:02, Emmanuel Grumbach wrote: >> On Tue, Sep 9, 2014 at 10:46 PM, Oliver Hartkopp <socketcan@hartkopp.net> wrote: >>> Hello John, all, >>> >>> on my i7 Laptop with iwlwifi the latest net-next does not connect to my access point: >> >> Are you sure this wasn't the case before? > > Indeed I moved to net-next right today - as I also had the LED lockdep splat > on 3.17-rcX with X < 4. > > So it can be that this issue was already introduced at the beginning of this > net-next cycle. Don't know, sorry. The latest 3.17-rc4 from Linus' tree works > fine. I'm running a Debian unstable here (in both cases). > >> Can you bisect? > > Not really. I'm running the kernel on my bare machine - and I just wanted to > go to bed right now ... > > So I will be able to test patches tomorrow morning again. > > Tnx for your fast feedback, > Oliver > > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 10.09.2014 00:07, Vadim Kochan wrote: > I have the same issue with iwlwifi. I tried an old zd1211 wireless USB stick to check if this problem is 80211 related. But the USB stick works fine (I'm using it right now). So its definitely looks like an iwlwifi issue. > iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 0 Wasn't there any change in the iwlwifi tx path recently?? Regards, Oliver > > On Tue, Sep 9, 2014 at 11:23 PM, Oliver Hartkopp <socketcan@hartkopp.net> wrote: >> On 09.09.2014 22:02, Emmanuel Grumbach wrote: >>> On Tue, Sep 9, 2014 at 10:46 PM, Oliver Hartkopp <socketcan@hartkopp.net> wrote: >>>> Hello John, all, >>>> >>>> on my i7 Laptop with iwlwifi the latest net-next does not connect to my access point: >>> >>> Are you sure this wasn't the case before? >> >> Indeed I moved to net-next right today - as I also had the LED lockdep splat >> on 3.17-rcX with X < 4. >> >> So it can be that this issue was already introduced at the beginning of this >> net-next cycle. Don't know, sorry. The latest 3.17-rc4 from Linus' tree works >> fine. I'm running a Debian unstable here (in both cases). >> >>> Can you bisect? >> >> Not really. I'm running the kernel on my bare machine - and I just wanted to >> go to bed right now ... >> >> So I will be able to test patches tomorrow morning again. >> >> Tnx for your fast feedback, >> Oliver >> >> -- >> To unsubscribe from this list: send the line "unsubscribe netdev" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html