linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "Grzegorz Duszyński" <gfduszynski@gmail.com>,
	linux-wireless@vger.kernel.org,
	"Johannes Berg" <johannes@sipsolutions.net>,
	"Haim Dreyfuss" <haim.dreyfuss@intel.com>
Subject: Re: Cpu stall caused by hostapd running two interfaces
Date: Tue, 14 Aug 2018 08:26:09 +0200	[thread overview]
Message-ID: <20180814062608.GA5561@redhat.com> (raw)
In-Reply-To: <87tvnycw2b.fsf@purkki.adurom.net>

On Mon, Aug 13, 2018 at 03:03:56PM +0300, Kalle Valo wrote:
> Stanislaw Gruszka <sgruszka@redhat.com> writes:
> 
> > (cc Haim and Johannes)
> >
> > On Sun, Aug 12, 2018 at 09:54:00PM +0200, Grzegorz Duszyński wrote:
> >> Hello,
> >> 
> >> I'm running into problems while trying to start AP's on 2 interfaces.
> >> Devices are:
> >> - Compex WLE900VX (QCA9880)
> >> - Killer 1535 (QCA6174)
> >> 
> >> The 1535 is a new addition to the system.
> >> Compex by itself runs fine, Killer also can run alone.
> >> 
> >> But when running them together all hell breaks lose.
> >> System is unusable, cannot even reboot.
> >> 
> >> I'm running Arch Linux.
> >> My system was updated before testing & posting.
> >> 
> >> Attachments:
> >> dmesg - https://pastebin.com/wf3Fq8gh
> >> 
> >> Please let me know if additional info is required.
> >
> > This is oops in ieee80211_regulatory_limit_wmm_params().
> > Looks like new regulatory code do not like ath10k.
> > I have another bug report with reg.c WARNING also on ath10k:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1612537
> 
> I think bug #1612537 is with ath9k, not ath10k. But anyway, both use
> ath.ko which has some custom regulatory code.

Actually warning from #1612537 is not driver depended. It can be
reproduced just by loading cfg80211 with ieee80211_regdom parameter,
for example:

sudo modprobe cfg80211 ieee80211_regdom=AQ

Regards
Stanislaw

  parent reply	other threads:[~2018-08-14  9:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-12 19:54 Cpu stall caused by hostapd running two interfaces Grzegorz Duszyński
2018-08-13  8:41 ` Stanislaw Gruszka
2018-08-13 12:03   ` Kalle Valo
2018-08-13 18:48     ` Grzegorz Duszyński
2018-08-14  5:14       ` Stanislaw Gruszka
2018-08-19 16:09         ` Grzegorz Duszyński
2018-08-19 17:28           ` Grzegorz Duszyński
2018-08-14  6:26     ` Stanislaw Gruszka [this message]
2018-08-20  7:37   ` Johannes Berg

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=20180814062608.GA5561@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=gfduszynski@gmail.com \
    --cc=haim.dreyfuss@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    /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).