linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Takashi Iwai <tiwai@suse.de>
Cc: dor.shaish@intel.com, Josh Boyer <jwboyer@kernel.org>,
	Johannes Berg <johannes.berg@intel.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Regression with the latest iwlwifi-9260-*-46.ucode
Date: Mon, 05 Aug 2019 12:48:43 +0300	[thread overview]
Message-ID: <38635c1b10018859457787ecff4f92a3ceec34a4.camel@coelho.fi> (raw)
In-Reply-To: <s5hmuh7xrqy.wl-tiwai@suse.de>

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).

--
Cheers,
Luca.


  parent reply	other threads:[~2019-08-05  9:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 15:35 Regression with the latest iwlwifi-9260-*-46.ucode Takashi Iwai
2019-07-19 16:36 ` Luciano Coelho
2019-07-19 18:07   ` Takashi Iwai
2019-07-20 20:42     ` Takashi Iwai
2019-07-20 20:49       ` Luca Coelho
2019-07-21 16:43         ` Takashi Iwai
2019-07-22 23:24           ` Brandon Darbro
2019-07-25 21:20             ` Brandon Darbro
2019-08-05  9:48           ` Luca Coelho [this message]
2019-08-05  9:53             ` Luca Coelho
2019-08-05 10:05               ` Takashi Iwai
2019-08-05 10:10                 ` Luca Coelho
2019-08-05 12:03                   ` Luca Coelho
2019-08-06 13:04                     ` Takashi Iwai
2019-08-09 19:00                       ` Thomas Backlund
2019-08-20 13:11                         ` Luca Coelho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38635c1b10018859457787ecff4f92a3ceec34a4.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=dor.shaish@intel.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=jwboyer@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).