From: Emmanuel Grumbach <egrumbach@gmail.com>
To: "Mika Penttilä" <mika.penttila@nextfour.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-rockchip@lists.infradead.org
Subject: Re: iwlwifi firmware loading problems, rk3399
Date: Wed, 20 May 2020 16:01:43 +0300 [thread overview]
Message-ID: <CANUX_P3kqY9wMBmAZoKsdzQv0TdW1pY7d=yqp5925Ryhkyq=Xg@mail.gmail.com> (raw)
In-Reply-To: <f27e0e85-6e45-15bd-1460-4140671ee4cd@nextfour.com>
> > I guess you need to debug your board :)
> > The interrupt is not coming, then.. there isn't much the driver can do.
>
> Well it does get interrupts, but stops getting them during fw loading at
> some point which causes it to fail. I have seen similar posts while
> googling and they are happening on x86/ubuntu and popular platforms. So
> I'm afraid it is something with iwlwifi or its usage of MSIX or such.
> The kernel version is 5.4.
You can try to disable msix.
In iwl_pcie_set_interrupt_capa, just goto enable_msi.
WARNING: multiple messages have this Message-ID (diff)
From: Emmanuel Grumbach <egrumbach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Mika Penttilä" <mika.penttila-MRsr7dthA9VWk0Htik3J/w@public.gmane.org>
Cc: Johannes Berg
<johannes.berg-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Emmanuel Grumbach
<emmanuel.grumbach-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: iwlwifi firmware loading problems, rk3399
Date: Wed, 20 May 2020 16:01:43 +0300 [thread overview]
Message-ID: <CANUX_P3kqY9wMBmAZoKsdzQv0TdW1pY7d=yqp5925Ryhkyq=Xg@mail.gmail.com> (raw)
In-Reply-To: <f27e0e85-6e45-15bd-1460-4140671ee4cd-MRsr7dthA9VWk0Htik3J/w@public.gmane.org>
> > I guess you need to debug your board :)
> > The interrupt is not coming, then.. there isn't much the driver can do.
>
> Well it does get interrupts, but stops getting them during fw loading at
> some point which causes it to fail. I have seen similar posts while
> googling and they are happening on x86/ubuntu and popular platforms. So
> I'm afraid it is something with iwlwifi or its usage of MSIX or such.
> The kernel version is 5.4.
You can try to disable msix.
In iwl_pcie_set_interrupt_capa, just goto enable_msi.
next prev parent reply other threads:[~2020-05-20 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 9:44 iwlwifi firmware loading problems, rk3399 Mika Penttilä
2020-05-20 9:44 ` Mika Penttilä
2020-05-20 12:27 ` Emmanuel Grumbach
2020-05-20 12:27 ` Emmanuel Grumbach
2020-05-20 12:34 ` Mika Penttilä
2020-05-20 12:34 ` Mika Penttilä
2020-05-20 13:01 ` Emmanuel Grumbach [this message]
2020-05-20 13:01 ` Emmanuel Grumbach
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='CANUX_P3kqY9wMBmAZoKsdzQv0TdW1pY7d=yqp5925Ryhkyq=Xg@mail.gmail.com' \
--to=egrumbach@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mika.penttila@nextfour.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.