Re: wireless-testing on 4.7

[Luca Coelho]

On Sun, 2016-06-05 at 19:09 -0600, Reinoud Koornstra wrote:
> On Thu, Jun 2, 2016 at 11:59 PM, Luca Coelho  wrote:
> > On Thu, 2016-06-02 at 23:09 -0600, Reinoud Koornstra wrote:
> > > On Thu, Jun 2, 2016 at 2:16 AM, Luca Coelho  wrote:
> > > > This shows that you have iwlwifi-7260-16.ucode in your file system.
> > > >  But here we are reading it much later.  So it's possible that the
> > > > kernel cannot access the firmware at a very early stage (because
> > > > the
> > > > filesystem that contains it is not mounted yet) when you use in-
> > > > kernel.
> > > > 
> > > > So, first of all, please make sure they're built as modules.  We
> > > > can
> > > > continue from there then.
> > > 
> > > Your suggestion worked. When it's compiled as module, the
> > > iwlwifi-7260-16.ucode loads fine.
> > > No problems detected so far.
> > 
> > Great! :)
> 
> It is. :)
> I git pulled again and build it again.
> This time with gcc 6.1.0
> I couldn't find warning specific to iwlwifi with gcc 6, so that's great.
> Didn't find anything worrysome yet, in addition I am running the cake
> qdisc as well from Dave Taht.
> objdump --full-contents --section=.comment vmlinux
> 
> vmlinux: file format elf64-x86-64
> 
> Contents of section .comment:
>  4743433a 2028474e 55292036 2e312e30  GCC: (GNU) 6.1.0
> 0010 00
> 
> reinoud@router-dev:~/Downloads/wireless-testing$ objdump
> --full-contents --section=.comment
> /lib/modules/4.7.0-rc1-wt+/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
> 
> /lib/modules/4.7.0-rc1-wt+/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko:
> file format elf64-x86-64
> 
> Contents of section .comment:
>  00474343 3a202847 4e552920 362e312e  .GCC: (GNU) 6.1.
> 0010 3047 43433a20 28474e55 2920362e  0..GCC: (GNU) 6.
> [SNIP]
> 0180 28474e55 2920362e 312e3000   (GNU) 6.1.0.
> 
> 
> > 
> > 
> > > It does make me think whether this is desired behavior though that
> > > due
> > > to the later reading we cannot have iwlwifi build in the kernel.
> > 
> > It should work, but then you have to make sure the firmware is
> > available at very early stages of boot.  If you add it to the proper
> > place in your initrd, the kernel should find it when the driver
> > requests it.
> > 
> > I didn't want to go into the details of this, because in most cases the
> > best option is to have the driver as a module.  If you really need it
> > in-kernel, then you need to make sure all the needed pieces are
> > available very early as well.
> 
> Ah, thanks, I'll study this as how to have it inside initrd at the right 
> place.
> Any pointers would be great.

It should be really straightforward.  It just depends on how your
distro creates and uses initrd images.  You only need to add the
appropriate .ucode file to /lib/firmware in the initrd image, nothing
else.  Google for it, I'm sure there is a lot of info on how to do it
readily available.



> Btw, I did build gcc 6.1.0 like this, if you have hints or ways I
> should build it differently I would like to know.
> 
> reinoud@router-dev:~/Downloads/wireless-testing$ gcc -v
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/home/reinoud/GCC/libexec/gcc/x86_64-linux-gnu/6.1.0/lto-wrapper
> Target: x86_64-linux-gnu
> Configured with: ../gcc-6.1.0/configure -v
> --enable-languages=c,c++,go,fortran,objc,obj-c++
> --prefix=/home/reinoud/GCC --enable-shared --enable-linker-build-id
> --without-included-gettext --enable-threads=posix --enable-nls
> --with-sysroot=/ --enab
> le-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
> --with-default-libstdcxx-abi=new --enable-gnu-unique-object
> --disable-vtable-verify --enable-libmpx --enable-plugin
> --with-system-zlib --disable-browser-plugin --with-arch-direct
> ory=amd64 --enable-objc-gc --enable-multiarch --disable-werror
> --with-abi=m64 --enable-checking=release --build=x86_64-linux-gnu
> --host=x86_64-linux-gnu --target=x86_64-linux-gnu
> Thread model: posix
> gcc version 6.1.0 (GCC)
> 
> The --with-tune=skylake didn't work as it didn't know it. unfortunately.

I'm sorry, but I have no clue.  This is probably a question to some gcc
development mailing list. ;)

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

Re: wireless-testing on 4.7

[Reinoud Koornstra]

On Thu, Jun 2, 2016 at 11:59 PM, Luca Coelho  wrote:
> On Thu, 2016-06-02 at 23:09 -0600, Reinoud Koornstra wrote:
>> On Thu, Jun 2, 2016 at 2:16 AM, Luca Coelho  wrote:
>> > This shows that you have iwlwifi-7260-16.ucode in your file system.
>> >  But here we are reading it much later.  So it's possible that the
>> > kernel cannot access the firmware at a very early stage (because
>> > the
>> > filesystem that contains it is not mounted yet) when you use in-
>> > kernel.
>> >
>> > So, first of all, please make sure they're built as modules.  We
>> > can
>> > continue from there then.
>>
>> Your suggestion worked. When it's compiled as module, the
>> iwlwifi-7260-16.ucode loads fine.
>> No problems detected so far.
>
> Great! :)

It is. :)
I git pulled again and build it again.
This time with gcc 6.1.0
I couldn't find warning specific to iwlwifi with gcc 6, so that's great.
Didn't find anything worrysome yet, in addition I am running the cake
qdisc as well from Dave Taht.
objdump --full-contents --section=.comment vmlinux

vmlinux: file format elf64-x86-64

Contents of section .comment:
 4743433a 2028474e 55292036 2e312e30  GCC: (GNU) 6.1.0
0010 00

reinoud@router-dev:~/Downloads/wireless-testing$ objdump
--full-contents --section=.comment
/lib/modules/4.7.0-rc1-wt+/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko

/lib/modules/4.7.0-rc1-wt+/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko:
file format elf64-x86-64

Contents of section .comment:
 00474343 3a202847 4e552920 362e312e  .GCC: (GNU) 6.1.
0010 3047 43433a20 28474e55 2920362e  0..GCC: (GNU) 6.
[SNIP]
0180 28474e55 2920362e 312e3000   (GNU) 6.1.0.


>
>
>> It does make me think whether this is desired behavior though that
>> due
>> to the later reading we cannot have iwlwifi build in the kernel.
>
> It should work, but then you have to make sure the firmware is
> available at very early stages of boot.  If you add it to the proper
> place in your initrd, the kernel should find it when the driver
> requests it.
>
> I didn't want to go into the details of this, because in most cases the
> best option is to have the driver as a module.  If you really need it
> in-kernel, then you need to make sure all the needed pieces are
> available very early as well.

Ah, thanks, I'll study this as how to have it inside initrd at the right place.
Any pointers would be great.

Btw, I did build gcc 6.1.0 like this, if you have hints or ways I
should build it differently I would like to know.

reinoud@router-dev:~/Downloads/wireless-testing$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/home/reinoud/GCC/libexec/gcc/x86_64-linux-gnu/6.1.0/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../gcc-6.1.0/configure -v
--enable-languages=c,c++,go,fortran,objc,obj-c++
--prefix=/home/reinoud/GCC --enable-shared --enable-linker-build-id
--without-included-gettext --enable-threads=posix --enable-nls
--with-sysroot=/ --enab
le-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin
--with-system-zlib --disable-browser-plugin --with-arch-direct
ory=amd64 --enable-objc-gc --enable-multiarch --disable-werror
--with-abi=m64 --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.1.0 (GCC)

The --with-tune=skylake didn't work as it didn't know it. unfortunately.

>
> --
> Cheers,
> Luca.

Thanks,

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

Re: wireless-testing on 4.7

[Luca Coelho]

On Thu, 2016-06-02 at 23:09 -0600, Reinoud Koornstra wrote:
> On Thu, Jun 2, 2016 at 2:16 AM, Luca Coelho  wrote:
> > This shows that you have iwlwifi-7260-16.ucode in your file system.
> >  But here we are reading it much later.  So it's possible that the
> > kernel cannot access the firmware at a very early stage (because
> > the
> > filesystem that contains it is not mounted yet) when you use in-
> > kernel.
> > 
> > So, first of all, please make sure they're built as modules.  We
> > can
> > continue from there then.
> 
> Your suggestion worked. When it's compiled as module, the
> iwlwifi-7260-16.ucode loads fine.
> No problems detected so far.

Great! :)


> It does make me think whether this is desired behavior though that
> due
> to the later reading we cannot have iwlwifi build in the kernel.

It should work, but then you have to make sure the firmware is
available at very early stages of boot.  If you add it to the proper
place in your initrd, the kernel should find it when the driver
requests it.

I didn't want to go into the details of this, because in most cases the
best option is to have the driver as a module.  If you really need it
in-kernel, then you need to make sure all the needed pieces are
available very early as well.

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

Re: wireless-testing on 4.7

[Reinoud Koornstra]

On Thu, Jun 2, 2016 at 2:16 AM, Luca Coelho <l...@coelho.fi> wrote:
> On Thu, 2016-06-02 at 02:02 -0600, Reinoud Koornstra wrote:
>> On Wed, Jun 1, 2016 at 10:27 PM, Coelho, Luciano
>> <luciano.coe...@intel.com> wrote:
>> > On Wed, 2016-06-01 at 16:08 -0600, Reinoud Koornstra wrote:
>> > > On Wed, Jun 1, 2016 at 7:19 AM, Coelho, Luciano
>> > > <luciano.coe...@intel.com> wrote:
>> > > > On Wed, 2016-06-01 at 08:54 -0400, Bob Copeland wrote:
>> > > > > + Luca, Emmanuel
>> > > >
>> > > > Thanks, Bob!
>> > > >
>> > > >
>> > > > > On Tue, May 31, 2016 at 10:06:57PM -0600, Reinoud Koornstra
>> > > > > wrote:
>> > > > > > Today I compiled 4.6+ and pulled sources today
>> > > > > > iwlwifi isn't super smooth.
>> > > > >
>> > > > > I assume you mean wireless-testing, based on 4.7-rc1 (as this
>> > > > > email
>> > > > > is
>> > > > > in reply to my announcement of same).
>> > > >
>> > > > Yes, we need to know exactly what kernel you're using so we know
>> > > > what
>> > > > we're debugging.
>> > > >
>> > >
>> > > Yesterday this is what I did to obtain the latest source:
>> > >
>> > > git clone
>> > > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> > > kernel_current
>> > >
>> > > This is the latest commit in that tree:
>> > >
>> > > commit 367d3fd50566a313946fa9c5b2116a81bf3807e4
>> > > Merge: 5eca831 cf0d44d
>> > > Author: Linus Torvalds <torva...@linux-foundation.org>
>> > > Date:   Tue May 31 09:43:24 2016 -0700
>> > >
>> > >Merge branch 'for-linus' of
>> > > git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
>> > >
>> > >Pull s390 fixes from Martin Schwidefsky:
>> > > "Three bugs fixes and an update for the default configuration"
>> > >
>> > >* 'for-linus' of
>> > > git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
>> > >  s390: fix info leak in do_sigsegv
>> > >  s390/config: update default configuration
>> > >  s390/bpf: fix recache skb->data/hlen for skb_vlan_push/pop
>> > >  s390/bpf: reduce maximum program size to 64 KB
>> >
>> > Ah, okay.  This has nothing to do with the wireless-testing tree.  This
>> > is random commit in Linus' tree.  I suggest that you use a release tag
>> > or such.  For instance you could do this in Linus' tree to get the
>> > current release candidate for 4.7:
>> >
>> > git checkout v4.7-rc1
>> >
>> > Or you could use the wireless-testing tree that Bob is maintaining,
>> > which is always based on an official release candidate (currently the
>> > above mentioned v4.7-rc1 release) plus the latest and greatest (and
>> > probably "brokenest" :P) wireless changes:
>> >
>> > git clone 
>> > git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-testing.git
>> >
>>
>> Ok, i got this tree.
>> From the start it didn't work.
>>
>> [0.00] Linux version 4.7.0-rc1-wt+
>> [SNIP]
>> [2.156875] iwlwifi :04:00.0: Direct firmware load for
>> iwlwifi-7260-17.ucode failed with error -2
>> [2.157681] iwlwifi :04:00.0: Direct firmware load for
>> iwlwifi-7260-16.ucode failed with error -2
>> [2.158438] iwlwifi :04:00.0: no suitable firmware found!
>
> This is happening pretty early, did you compile the iwlwifi driver into
> the kernel (instead of compiling them as modules)? There have been
> problems when it's in-kernel, so we recommend that you compile them as
> modules (unless strictly necessary).
>
>
>> I've attached the dmesg in it's entirety.
>> Booting back to 4.6:
>>
>> [   17.987698] iwlwifi :04:00.0: loaded firmware version
>> 16.242414.0 op_mode iwlmvm
>> [   18.269667] iwlwifi :04:00.0: Detected Intel(R) Dual Band
>> Wireless AC 7260, REV=0x144
>
> This shows that you have iwlwifi-7260-16.ucode in your file system.
>  But here we are reading it much later.  So it's possible that the
> kernel cannot access the firmware at a very early stage (because the
> filesystem that contains it is not mounted yet) when you use in-kernel.
>
> So, first of all, please make sure they're built as modules.  We can
> continue from there then.

Your suggestion worked. When it's compiled as module, the
iwlwifi-7260-16.ucode loads fine.
No problems detected so far.
It does make me think whether this is desired behavior though that due
to the later reading we cannot have iwlwifi build in the kernel.
Thanks,

Reinoud.

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

Re: wireless-testing on 4.7

[Luca Coelho]

On Thu, 2016-06-02 at 02:02 -0600, Reinoud Koornstra wrote:
> On Wed, Jun 1, 2016 at 10:27 PM, Coelho, Luciano
> <luciano.coe...@intel.com> wrote:
> > On Wed, 2016-06-01 at 16:08 -0600, Reinoud Koornstra wrote:
> > > On Wed, Jun 1, 2016 at 7:19 AM, Coelho, Luciano
> > > <luciano.coe...@intel.com> wrote:
> > > > On Wed, 2016-06-01 at 08:54 -0400, Bob Copeland wrote:
> > > > > + Luca, Emmanuel
> > > > 
> > > > Thanks, Bob!
> > > > 
> > > > 
> > > > > On Tue, May 31, 2016 at 10:06:57PM -0600, Reinoud Koornstra
> > > > > wrote:
> > > > > > Today I compiled 4.6+ and pulled sources today
> > > > > > iwlwifi isn't super smooth.
> > > > > 
> > > > > I assume you mean wireless-testing, based on 4.7-rc1 (as this
> > > > > email
> > > > > is
> > > > > in reply to my announcement of same).
> > > > 
> > > > Yes, we need to know exactly what kernel you're using so we know
> > > > what
> > > > we're debugging.
> > > > 
> > > 
> > > Yesterday this is what I did to obtain the latest source:
> > > 
> > > git clone
> > > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > > kernel_current
> > > 
> > > This is the latest commit in that tree:
> > > 
> > > commit 367d3fd50566a313946fa9c5b2116a81bf3807e4
> > > Merge: 5eca831 cf0d44d
> > > Author: Linus Torvalds <torva...@linux-foundation.org>
> > > Date:   Tue May 31 09:43:24 2016 -0700
> > > 
> > >    Merge branch 'for-linus' of
> > > git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
> > > 
> > >    Pull s390 fixes from Martin Schwidefsky:
> > > "Three bugs fixes and an update for the default configuration"
> > > 
> > >    * 'for-linus' of
> > > git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
> > >  s390: fix info leak in do_sigsegv
> > >  s390/config: update default configuration
> > >  s390/bpf: fix recache skb->data/hlen for skb_vlan_push/pop
> > >  s390/bpf: reduce maximum program size to 64 KB
> > 
> > Ah, okay.  This has nothing to do with the wireless-testing tree.  This
> > is random commit in Linus' tree.  I suggest that you use a release tag
> > or such.  For instance you could do this in Linus' tree to get the
> > current release candidate for 4.7:
> > 
> > git checkout v4.7-rc1
> > 
> > Or you could use the wireless-testing tree that Bob is maintaining,
> > which is always based on an official release candidate (currently the
> > above mentioned v4.7-rc1 release) plus the latest and greatest (and
> > probably "brokenest" :P) wireless changes:
> > 
> > git clone 
> > git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-testing.git
> > 
> 
> Ok, i got this tree.
> From the start it didn't work.
> 
> [0.00] Linux version 4.7.0-rc1-wt+
> [SNIP]
> [2.156875] iwlwifi :04:00.0: Direct firmware load for
> iwlwifi-7260-17.ucode failed with error -2
> [2.157681] iwlwifi :04:00.0: Direct firmware load for
> iwlwifi-7260-16.ucode failed with error -2
> [2.158438] iwlwifi :04:00.0: no suitable firmware found!

This is happening pretty early, did you compile the iwlwifi driver into
the kernel (instead of compiling them as modules)? There have been
problems when it's in-kernel, so we recommend that you compile them as
modules (unless strictly necessary).


> I've attached the dmesg in it's entirety.
> Booting back to 4.6:
> 
> [   17.987698] iwlwifi :04:00.0: loaded firmware version
> 16.242414.0 op_mode iwlmvm
> [   18.269667] iwlwifi :04:00.0: Detected Intel(R) Dual Band
> Wireless AC 7260, REV=0x144

This shows that you have iwlwifi-7260-16.ucode in your file system.
 But here we are reading it much later.  So it's possible that the
kernel cannot access the firmware at a very early stage (because the
filesystem that contains it is not mounted yet) when you use in-kernel.

So, first of all, please make sure they're built as modules.  We can
continue from there then.

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

Re: wireless-testing on 4.7

[Coelho, Luciano]

On Wed, 2016-06-01 at 16:08 -0600, Reinoud Koornstra wrote:
> On Wed, Jun 1, 2016 at 7:19 AM, Coelho, Luciano
> <luciano.coe...@intel.com> wrote:
> > On Wed, 2016-06-01 at 08:54 -0400, Bob Copeland wrote:
> > > + Luca, Emmanuel
> > 
> > Thanks, Bob!
> > 
> > 
> > > On Tue, May 31, 2016 at 10:06:57PM -0600, Reinoud Koornstra
> > > wrote:
> > > > Today I compiled 4.6+ and pulled sources today
> > > > iwlwifi isn't super smooth.
> > > 
> > > I assume you mean wireless-testing, based on 4.7-rc1 (as this
> > > email
> > > is
> > > in reply to my announcement of same).
> > 
> > Yes, we need to know exactly what kernel you're using so we know
> > what
> > we're debugging.
> > 
> 
> Yesterday this is what I did to obtain the latest source:
> 
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> kernel_current
> 
> This is the latest commit in that tree:
> 
> commit 367d3fd50566a313946fa9c5b2116a81bf3807e4
> Merge: 5eca831 cf0d44d
> Author: Linus Torvalds <torva...@linux-foundation.org>
> Date:   Tue May 31 09:43:24 2016 -0700
> 
>    Merge branch 'for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
> 
>    Pull s390 fixes from Martin Schwidefsky:
> "Three bugs fixes and an update for the default configuration"
> 
>    * 'for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
>  s390: fix info leak in do_sigsegv
>  s390/config: update default configuration
>  s390/bpf: fix recache skb->data/hlen for skb_vlan_push/pop
>  s390/bpf: reduce maximum program size to 64 KB

Ah, okay.  This has nothing to do with the wireless-testing tree.  This
is random commit in Linus' tree.  I suggest that you use a release tag
or such.  For instance you could do this in Linus' tree to get the
current release candidate for 4.7:

git checkout v4.7-rc1

Or you could use the wireless-testing tree that Bob is maintaining,
which is always based on an official release candidate (currently the
above mentioned v4.7-rc1 release) plus the latest and greatest (and
probably "brokenest" :P) wireless changes:

git clone 
git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-testing.git


> > > > 
> > > > [  112.345457] wlp4s0: authenticate with 00:30:44:1d:cf:2b
> > > > [  112.349002] wlp4s0: send auth to 00:30:44:1d:cf:2b (try 1/3)
> > > > [  112.349647] wlp4s0: authenticated
> > > > [  112.352456] wlp4s0: associate with 00:30:44:1d:cf:2b (try
> > > > 1/3)
> > > > [  112.353764] wlp4s0: RX AssocResp from 00:30:44:1d:cf:2b
> > > > (capab=0x11
> > > > status=0 aid=3)
> > > > [  112.355035] wlp4s0: associated
> > > > [  112.355393] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link
> > > > becomes
> > > > ready
> > > > [  118.616327] wlp4s0: deauthenticated from 00:30:44:1d:cf:2b
> > > > (Reason:
> > > > 15=4WAY_HANDSHAKE_TIMEOUT)
> > > > [  128.673812] wlp4s0: authenticate with 00:30:44:1d:cf:2b
> > > > [  128.676997] wlp4s0: send auth to 00:30:44:1d:cf:2b (try 1/3)
> > > > [  128.677648] wlp4s0: authenticated
> > > > [  128.678691] wlp4s0: associate with 00:30:44:1d:cf:2b (try
> > > > 1/3)
> > > > [  128.679807] wlp4s0: RX AssocResp from 00:30:44:1d:cf:2b
> > > > (capab=0x11
> > > > status=0 aid=3)
> > > > [  128.681198] wlp4s0: associated
> > > > 
> > > > I never experienced the 4 way handshake 802.11i timeout in my
> > > > home
> > > > setup.
> > > > With other setups plenty of times, especially with mediatek
> > > > drivers. :)
> > > > If you wish I can sniff and see which side is at fault.
> > > 
> > > I have not noticed any problems on my laptop with iwldvm on a
> > > 6205,
> > > with
> > > latest wireless-testing.  But maybe intel devs can weigh in.
> > 
> > I'm not going to put all my weight in lest I break things even
> > more. :P
> > 
> > I can't really see much from the log extract you posted.  Can you
> > get
> > some logs (especially trace-cmd and a sniffer capture) and report a
> > bug
> > in bugzilla? We have some instructions on how to do it here:
> > 
> > https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging
> > 
> 
> Ok, will do so, thanks,

Great, thanks! Please use one of the more-well-known trees/tags I
mentioned above and report if you still have trouble.

--
Cheers,
Luca.N�r��yb�X��ǧv�^�)޺{.n�+{��*ޕ�,�{ay�ʇڙ�,j��f���h���z��w���
���j:+v���w�j�mzZ+�ݢj"��!�i

Re: wireless-testing on 4.7

[Reinoud Koornstra]

On Wed, Jun 1, 2016 at 7:19 AM, Coelho, Luciano
<luciano.coe...@intel.com> wrote:
> On Wed, 2016-06-01 at 08:54 -0400, Bob Copeland wrote:
>> + Luca, Emmanuel
>
> Thanks, Bob!
>
>
>> On Tue, May 31, 2016 at 10:06:57PM -0600, Reinoud Koornstra wrote:
>> > Today I compiled 4.6+ and pulled sources today
>> > iwlwifi isn't super smooth.
>>
>> I assume you mean wireless-testing, based on 4.7-rc1 (as this email
>> is
>> in reply to my announcement of same).
>
> Yes, we need to know exactly what kernel you're using so we know what
> we're debugging.
>

Yesterday this is what I did to obtain the latest source:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel_current

This is the latest commit in that tree:

commit 367d3fd50566a313946fa9c5b2116a81bf3807e4
Merge: 5eca831 cf0d44d
Author: Linus Torvalds <torva...@linux-foundation.org>
Date:   Tue May 31 09:43:24 2016 -0700

   Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux

   Pull s390 fixes from Martin Schwidefsky:
"Three bugs fixes and an update for the default configuration"

   * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
 s390: fix info leak in do_sigsegv
 s390/config: update default configuration
 s390/bpf: fix recache skb->data/hlen for skb_vlan_push/pop
 s390/bpf: reduce maximum program size to 64 KB

>> >
>> > [  112.345457] wlp4s0: authenticate with 00:30:44:1d:cf:2b
>> > [  112.349002] wlp4s0: send auth to 00:30:44:1d:cf:2b (try 1/3)
>> > [  112.349647] wlp4s0: authenticated
>> > [  112.352456] wlp4s0: associate with 00:30:44:1d:cf:2b (try 1/3)
>> > [  112.353764] wlp4s0: RX AssocResp from 00:30:44:1d:cf:2b
>> > (capab=0x11
>> > status=0 aid=3)
>> > [  112.355035] wlp4s0: associated
>> > [  112.355393] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes
>> > ready
>> > [  118.616327] wlp4s0: deauthenticated from 00:30:44:1d:cf:2b
>> > (Reason:
>> > 15=4WAY_HANDSHAKE_TIMEOUT)
>> > [  128.673812] wlp4s0: authenticate with 00:30:44:1d:cf:2b
>> > [  128.676997] wlp4s0: send auth to 00:30:44:1d:cf:2b (try 1/3)
>> > [  128.677648] wlp4s0: authenticated
>> > [  128.678691] wlp4s0: associate with 00:30:44:1d:cf:2b (try 1/3)
>> > [  128.679807] wlp4s0: RX AssocResp from 00:30:44:1d:cf:2b
>> > (capab=0x11
>> > status=0 aid=3)
>> > [  128.681198] wlp4s0: associated
>> >
>> > I never experienced the 4 way handshake 802.11i timeout in my home
>> > setup.
>> > With other setups plenty of times, especially with mediatek
>> > drivers. :)
>> > If you wish I can sniff and see which side is at fault.
>>
>> I have not noticed any problems on my laptop with iwldvm on a 6205,
>> with
>> latest wireless-testing.  But maybe intel devs can weigh in.
>
> I'm not going to put all my weight in lest I break things even more. :P
>
> I can't really see much from the log extract you posted.  Can you get
> some logs (especially trace-cmd and a sniffer capture) and report a bug
> in bugzilla? We have some instructions on how to do it here:
>
> https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging
>

Ok, will do so, thanks,

Reinoud.

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

Re: wireless-testing on 4.7

[Coelho, Luciano]

On Wed, 2016-06-01 at 08:54 -0400, Bob Copeland wrote:
> + Luca, Emmanuel

Thanks, Bob!


> On Tue, May 31, 2016 at 10:06:57PM -0600, Reinoud Koornstra wrote:
> > Today I compiled 4.6+ and pulled sources today
> > iwlwifi isn't super smooth.
> 
> I assume you mean wireless-testing, based on 4.7-rc1 (as this email
> is
> in reply to my announcement of same).

Yes, we need to know exactly what kernel you're using so we know what
we're debugging.

> > 
> > [  112.345457] wlp4s0: authenticate with 00:30:44:1d:cf:2b
> > [  112.349002] wlp4s0: send auth to 00:30:44:1d:cf:2b (try 1/3)
> > [  112.349647] wlp4s0: authenticated
> > [  112.352456] wlp4s0: associate with 00:30:44:1d:cf:2b (try 1/3)
> > [  112.353764] wlp4s0: RX AssocResp from 00:30:44:1d:cf:2b
> > (capab=0x11
> > status=0 aid=3)
> > [  112.355035] wlp4s0: associated
> > [  112.355393] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes
> > ready
> > [  118.616327] wlp4s0: deauthenticated from 00:30:44:1d:cf:2b
> > (Reason:
> > 15=4WAY_HANDSHAKE_TIMEOUT)
> > [  128.673812] wlp4s0: authenticate with 00:30:44:1d:cf:2b
> > [  128.676997] wlp4s0: send auth to 00:30:44:1d:cf:2b (try 1/3)
> > [  128.677648] wlp4s0: authenticated
> > [  128.678691] wlp4s0: associate with 00:30:44:1d:cf:2b (try 1/3)
> > [  128.679807] wlp4s0: RX AssocResp from 00:30:44:1d:cf:2b
> > (capab=0x11
> > status=0 aid=3)
> > [  128.681198] wlp4s0: associated
> > 
> > I never experienced the 4 way handshake 802.11i timeout in my home
> > setup.
> > With other setups plenty of times, especially with mediatek
> > drivers. :)
> > If you wish I can sniff and see which side is at fault.
> 
> I have not noticed any problems on my laptop with iwldvm on a 6205,
> with
> latest wireless-testing.  But maybe intel devs can weigh in.

I'm not going to put all my weight in lest I break things even more. :P

I can't really see much from the log extract you posted.  Can you get
some logs (especially trace-cmd and a sniffer capture) and report a bug
in bugzilla? We have some instructions on how to do it here:

https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging

Thanks for reporting!

--
Cheers,
Luca.

Re: wireless-testing on 4.7

[Bob Copeland]

+ Luca, Emmanuel

On Tue, May 31, 2016 at 10:06:57PM -0600, Reinoud Koornstra wrote:
> Today I compiled 4.6+ and pulled sources today
> iwlwifi isn't super smooth.

I assume you mean wireless-testing, based on 4.7-rc1 (as this email is
in reply to my announcement of same).

> 
> [  112.345457] wlp4s0: authenticate with 00:30:44:1d:cf:2b
> [  112.349002] wlp4s0: send auth to 00:30:44:1d:cf:2b (try 1/3)
> [  112.349647] wlp4s0: authenticated
> [  112.352456] wlp4s0: associate with 00:30:44:1d:cf:2b (try 1/3)
> [  112.353764] wlp4s0: RX AssocResp from 00:30:44:1d:cf:2b (capab=0x11
> status=0 aid=3)
> [  112.355035] wlp4s0: associated
> [  112.355393] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [  118.616327] wlp4s0: deauthenticated from 00:30:44:1d:cf:2b (Reason:
> 15=4WAY_HANDSHAKE_TIMEOUT)
> [  128.673812] wlp4s0: authenticate with 00:30:44:1d:cf:2b
> [  128.676997] wlp4s0: send auth to 00:30:44:1d:cf:2b (try 1/3)
> [  128.677648] wlp4s0: authenticated
> [  128.678691] wlp4s0: associate with 00:30:44:1d:cf:2b (try 1/3)
> [  128.679807] wlp4s0: RX AssocResp from 00:30:44:1d:cf:2b (capab=0x11
> status=0 aid=3)
> [  128.681198] wlp4s0: associated
> 
> I never experienced the 4 way handshake 802.11i timeout in my home setup.
> With other setups plenty of times, especially with mediatek drivers. :)
> If you wish I can sniff and see which side is at fault.

I have not noticed any problems on my laptop with iwldvm on a 6205, with
latest wireless-testing.  But maybe intel devs can weigh in.

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

wireless-testing on 4.7

[Bob Copeland]

Since Linus released 4.7-rc1 today, I've resumed wireless-testing
updates since its merge window hiatus, with tag wt-2016-05-29.

Please test and let me know of any issues.

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