Return-path: Received: from mail-wm0-f52.google.com ([74.125.82.52]:56119 "EHLO mail-wm0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752283AbeDISVO (ORCPT ); Mon, 9 Apr 2018 14:21:14 -0400 Received: by mail-wm0-f52.google.com with SMTP id b127so21142321wmf.5 for ; Mon, 09 Apr 2018 11:21:13 -0700 (PDT) Subject: Re: iwlwifi-7265-ucode-25.30.14.0.tgz. in Centos 7 To: Larry Finger , Dusan Bruncko , linux-wireless@vger.kernel.org, centos-devel@centos.org References: <238bda30-c983-f4aa-fdaf-a4f06cb83c1d@lwfinger.net> <23bb800e-544c-607e-43ae-6833949167af@lwfinger.net> From: Arend van Spriel Message-ID: <5ACBAF17.5050808@broadcom.com> (sfid-20180409_202118_487887_8AE0CC99) Date: Mon, 9 Apr 2018 20:21:11 +0200 MIME-Version: 1.0 In-Reply-To: <23bb800e-544c-607e-43ae-6833949167af@lwfinger.net> Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 4/9/2018 6:18 PM, Larry Finger wrote: > On 04/08/2018 11:56 PM, Dusan Bruncko wrote: >> Dear Larry, >> >> Thank you for your mail. But concerning to "capa flags index 3", I am >> not sure. Please look >> following message receiving for command "ps aux", >> >> /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: >> CPU: INFO: possible recursive locking detected ernel BUG at list_del >> corruption list_add corruption do_IRQ: stack over >> flow: ear stack overflow (cur: eneral protection fault nable to handle >> kernel ouble fault: RTNL: assertion failed eek! >> page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl >> table check failed : nobody cared IRQ handler type >> mismatch Machine Check Exception: Machine check events logged divide >> error: bounds: coprocessor segment overrun: inva >> lid TSS: segment not present: invalid opcode: alignment check: stack >> segment: fpu exception: simd exception: iret exce >> ption: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD >> >> I am not software expert, but also looking on message from abrt: >> >> Subject: [abrt] : divide error: 0000 [#1] SMP => look attachment. >> >> Maybe it is direct consequence connected with my wi-fi problem... >> >> Regards, >> Dusan >> >> Larry Finger wrote: >>> On 04/08/2018 01:58 AM, Dusan Bruncko wrote: >>>> Hello, >>>> >>>> Allow me to ask you the following question: >>>> >>>> I have laptop with: "02:00.0 Network controller: Intel Corporation >>>> Wireless 7265 (rev 59)". >>>> For this device I found firmware iwlwifi-7265-ucode-25.30.14.0.tgz. >>>> >>>> My problem is following: This firmware was created for kernel 4.2+, >>>> but I am using >>>> Centos 7 with kernels a la 3.10. Therefore I see during booting and >>>> after switch off some >>>> problematic messages a la: >>>> capa flags index 3 larger than supported by driver or >>>> failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware ... >>>> >>>> Wi-fi works properly, not to look on the previous messages. >>>> >>>> My question to you: do you have in schedule to include proper >>>> firmware also for >>>> centos 7/redhat 7? >>> >>> If your kernel were newer, I would recommend running the backports >>> drivers, but I think 3.10 is too old. That said, this code change >>> would not fix the "failed to remove key" message as I get that on my >>> 7260 device with kernel 4.16.0. I think you may safely ignore this >>> one if for no other reason than it only happens when the device is >>> being shut down. backports works for 3.10 and higher kernels so you are just on the good side of it. >>> If the "capa flags index 3" message is not causing any problems, I >>> would ignore it as well. > > On this and most mailing lists, one should not top post. It is most > inconvenient to have to continually scroll up and down to get to your > comments while writing mine. > > In your first posting, you said "Wi-fi works properly". That certainly > does not imply any problems other than the strange messages in the log. > If you are getting BUG and/or WARNING dumps, then the output of the > dmesg command will list the traceback. I do not see any of those. They > may be a consequence of using such an old kernel. I am only an Intel > wifi user, not a developer, and it is unlikely that I will be able to > fix any of your problems. In any case, you need to post the full > tracebacks of those BUGS/WARNINGS here. Remember, do not post at the top. The log shows that the "divide error" occurs in your (proprietary) nvidia driver. There is no relation to the wifi "issues" discussed in this thread. Regards, Arend