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

[Takashi Iwai]

On Mon, 05 Aug 2019 14:03:55 +0200,
Luca Coelho wrote:
> 
> On Mon, 2019-08-05 at 13:10 +0300, Luca Coelho wrote:
> > On Mon, 2019-08-05 at 12:05 +0200, Takashi Iwai wrote:
> > > On Mon, 05 Aug 2019 11:53:33 +0200,
> > > Luca Coelho wrote:
> > > > On Mon, 2019-08-05 at 12:48 +0300, Luca Coelho wrote:
> > > > > On Sun, 2019-07-21 at 18:43 +0200, Takashi Iwai wrote:
> > > > > > On Sat, 20 Jul 2019 22:49:33 +0200,
> > > > > > Luca Coelho wrote:
> > > > > > > On Sat, 2019-07-20 at 22:42 +0200, Takashi Iwai wrote:
> > > > > > > > On Fri, 19 Jul 2019 20:07:46 +0200,
> > > > > > > > Takashi Iwai wrote:
> > > > > > > > > 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.
> > > > > > > > 
> > > > > > > > FYI, the dmesg's have been uploaded to the same bugzilla entry:
> > > > > > > >   https://bugzilla.opensuse.org/show_bug.cgi?id=1142128
> > > > > > > > 
> > > > > > > 
> > > > > > > Thanks!
> > > > > > > 
> > > > > > > BTW, I pushed new firmwares to our firmware tree in git.kernel.org
> > > > > > > today.  This is the patch:
> > > > > > > 
> > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=b5f09bb4f816abace0227d0f4e749859364cef6b
> > > > > > > 
> > > > > > > It would be great if you can try it out and let us know whether the problem is gone or not.
> > > > > > 
> > > > > > I created a test package and asked for testing.
> > > > > > The test result seems negative, showing the same error,
> > > > > > unfortunately.
> > > > > > 
> > > > > > The dmesg was uploaded on the bugzilla entry.
> > > > > 
> > > > > Thanks Takashi! We will look into them as soon as possible (sorry for
> > > > > the late reply, I just came back from vacations).
> > > > 
> > > > Actually, I just noticed that your bugzilla is closed as "RESOLVED
> > > > FIXED".  Is this still an issue?
> > > 
> > > It's "closed" because our package contains the revert.
> > > 
> > > > This seems like a mismatch between the WiFi and BT firmwares... And
> > > > most likely the same issue as this:
> > > > 
> > > > https://bugzilla.kernel.org/show_bug.cgi?id=202163
> > > 
> > > OK, so we need the update of the whole linux-firmware.
> > > I'll refresh the package and ask for testing.
> > 
> > I'm not sure the new BT firmware is in linux-firmware yet, since I
> > don't handle BT stuff.  I hope it is.
> 
> I just double-checked this and got confirmation that the latest BT
> firmware in linux-firmware.git is compatible with the latest WiFi
> firmware there as well.
> 
> The only caveat is that the machine needs to be cold-booted for it to
> work....
> 
> But we are taking steps to make sure this will not happen next time
> (i.e. for future hardware), by syncing our BT and WiFi firmware
> releases.

Now we got a feedback from the latest linux-firmware (20190726) and
surprising the result was negative.  The dmesg after the cold boot is
found at:
  https://bugzilla.suse.com/show_bug.cgi?id=1142128#c26

The kernel is 5.2.3, so it should be new enough.

If anything else needed (or something missing), let us know.


thanks,

Takashi