On Fri, Nov 17, 2017 at 3:53 PM, Luca Coelho <luca@xxxxxxxxx> wrote: > On Fri, 2017-11-17 at 15:38 +0800, Chris Chiu wrote: >> On Fri, Nov 17, 2017 at 2:46 PM, Luca Coelho <luca@xxxxxxxxx> wrote: >> > On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote: >> > > On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@xxxxxxxxx> >> > > wrote: >> > > > Hi Chris, >> > > > >> > > > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: >> > > > > Hi Luca, >> > > > > Any suggestion for the "Failed to start INIT ucode: -110" >> > > > > issue >> > > > > for the firmware? >> > > > >> > > > There were a few problems which should now be fixed. We >> > > > published >> > > > new >> > > > firmwares in our linux-firmware.git tree[1] and also made some >> > > > fixes in >> > > > the driver[2]. Please update your system accordingly and let >> > > > me >> > > > know >> > > > if it works for you. >> > > > >> > > > Thanks! >> > > > >> > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/lin >> > > > ux-f >> > > > irmware.git/ >> > > > [2] https://patchwork.kernel.org/patch/10059871/ >> > > > https://patchwork.kernel.org/patch/10059875/ >> > > > https://patchwork.kernel.org/patch/10059873/ >> > > > >> > > > -- >> > > > Cheers, >> > > > Luca. >> > > >> > > Hi Luca, >> > >> > Hi Chris, >> > >> > >> > > Thanks for your patch and updated firmware. The driver can >> > > initialize w/o error now. However, it always fails on ip-config >> > > after >> > > 4-way handshake complete. I have to mention that I removed the >> > > field >> > > ".soc_latency" in all new iwl_cfg you added in >> > > https://patchwork.kernel.org/patch/10059875/ to remove compile >> > > error >> > > based on the linux mainline 4.14. >> > > I don't know whether if this causes the problem. Do you need >> > > me >> > > to >> > > do anything for more information? >> > >> > That was my fault, I forgot to include one file in my commit. I >> > have >> > sent v2 of the two last patches to solve the problem. Can you try >> > them? >> > >> > The problem you're seeing could be related to that, because we use >> > a >> > bit longer wait period for HW stabilization with integrated >> > devices. >> > And if you remove it, you may encounter random problems... >> > >> > -- >> > Cheers, >> > Luca. >> >> Hi Luca, >> Thanks for your quick response. I tried your v2 patch but things >> remain the same. The signal strength and scan results seems nothing >> wrong but still fail to get ip from DHCP server. Please let me know >> what I can help here. > > Can you provide the dmesg output and trace-cmd logs as explained here? > > https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging > > > -- > Cheers, > Luca. Hi Luca, Here's the dmesg log of the fail case on DHCP. https://gist.github.com/mschiu77/ec1a4579e6b863da68b703205cf8a0e4 Chris
