linux-kernel - Re: Regression with the latest iwlwifi-9260-*-46.ucode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 19 Jul 2019 20:07:46 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     Luciano Coelho <luciano.coelho@...el.com>
Cc:     dor.shaish@...el.com, Josh Boyer <jwboyer@...nel.org>,
        Johannes Berg <johannes.berg@...el.com>,
        Emmanuel Grumbach <emmanuel.grumbach@...el.com>,
        linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Regression with the latest iwlwifi-9260-*-46.ucode

On Fri, 19 Jul 2019 18:36:53 +0200,
Luciano Coelho wrote:
> 
> Adding Dor.
> 
> Hi Takashi,
> 
> Do you have full logs of the crash? We can't see much from the log
> snippet pasted in the bug report.

OK, I'll ask reporters.  If you have a SUSE/openSUSE bugzilla account,
feel free to join there.

> In any case, today or tomorrow, I'll release a new FW version for 9260,
> hopefully it will solve the problem.  I'll send you a link so you can
> test it when I push it to our tree (which feeds linux-firmware.git).

Good to hear.  I'll create a test package once when I have the new
firmware.


Thanks!

Takashi


> 
> Thanks for reporting!
> 
> --
> Cheers,
> Luca.
> 
> 
> On Fri, 2019-07-19 at 17:35 +0200, Takashi Iwai wrote:
> > Hi,
> > 
> > we've got a report about the regression with the latest iwlwifi 9260
> > *-46.ucode that landed recently in linux-firmware tree.  WiFi doesn't
> > work any longer on some Dell machines with that firmware.  See details
> > in:
> >   https://bugzilla.opensuse.org/show_bug.cgi?id=1142128
> > 
> > Currently we're reverting to the previously released firmware files.
> > 
> > Is it a known problem that has been already addressed?
> > If not, shall we revert the changes as a tentative workaround?
> > 
> > 
> > Thanks!
> > 
> > Takashi
>