All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.01.org
Subject: Re: >=iwd-1.8: crash in dmesg at boot
Date: Tue, 20 Oct 2020 09:28:49 -0700	[thread overview]
Message-ID: <d163a616006b4fc97fc7af2048b19d19068ff74e.camel@gmail.com> (raw)
In-Reply-To: <20201020161422.GD1676@host>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

Hi,

On Tue, 2020-10-20 at 18:14 +0200, m1027(a)posteo.net wrote:
> Hi,
> 
> I am forwarding the following issue from Gentoo linux to you here.
> Please see: https://bugs.gentoo.org/746539
> 
> I hope this is the right place to continue with this issue.
> 
> This is the summary:
> 
> iwd-1.7 was not hit, but 1.8 and 1.9 have been hit by the issue.
> 
> The kernel has been bisected down to this commit:
> https://git.kernel.org/pub/scm/network/wireless/iwd.git/commit/?id=b43e915b989dcbb0fa763fb7f256e30fe7426f14
> However, it may not be the real cause, maybe only revealing the
> issue. Still happening with linux 5.9.1.

Yes since adding the call to GET_REG it appears that IWD is just
exposing the kernel warning. I think this needs to be forwarded to
linux-wireless.

Side note: wpa_supplicant likely doesn't have this problem since it
does not include ATTR_WIPHY with its GET_REG call AFAIK. Anyone know if
GET_REG is intended to be per-phy? Or why we are including ATTR_WIPHY?

Thanks,
James

  reply	other threads:[~2020-10-20 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20 16:14 >=iwd-1.8: crash in dmesg at boot m1027
2020-10-20 16:28 ` James Prestwood [this message]
2020-10-20 16:42   ` Denis Kenzior
2020-10-21 10:36   ` m1027

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=d163a616006b4fc97fc7af2048b19d19068ff74e.camel@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.01.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 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.