From: Luca Coelho <luca@coelho.fi>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Marc MERLIN <marc@merlins.org>,
linux-wireless@vger.kernel.org, linuxwifi@intel.com
Subject: Re: After upgrading to 4.11.1, wifi driver refuses to load after being unloaded once.
Date: Wed, 18 Oct 2017 13:22:56 +0300 [thread overview]
Message-ID: <1508322176.5497.152.camel@coelho.fi> (raw)
In-Reply-To: <87bml4iy40.fsf@kamboji.qca.qualcomm.com>
On Wed, 2017-10-18 at 12:50 +0300, Kalle Valo wrote:
> Luca Coelho <luca@coelho.fi> writes:
>
> > On Wed, 2017-10-18 at 07:59 +0300, Kalle Valo wrote:
> > > Luca Coelho <luca@coelho.fi> writes:
> > >
> > > > On Tue, 2017-10-17 at 14:23 -0700, Marc MERLIN wrote:
> > > >
> > > > > I don't know how or why, but I seem to:
> > > > > saruman:~# grep IWLWIFI /boot/config-4.12.10-amd64-preempt-
> > > > > sysrq-
> > > > > 20170406
> > > > > CONFIG_IWLWIFI=m
> > > > > CONFIG_IWLWIFI_LEDS=y
> > > > > CONFIG_IWLWIFI_OPMODE_MODULAR=y
> > > > > # CONFIG_IWLWIFI_BCAST_FILTERING is not set
> > > > > CONFIG_IWLWIFI_PCIE_RTPM=y
> > > > > CONFIG_IWLWIFI_DEBUG=y
> > > > > CONFIG_IWLWIFI_DEVICE_TRACING=y
> > > > >
> > > > > I'll remove that, thanks.
> > > >
> > > > Cool, I think that might help. If it doesn't, please report a
> > > > bug
> > > > in
> > > > buzilla. ;)
> > >
> > > But a Kconfig option should never break functionality, so IMHO
> > > this
> > > still sounds like a bug in iwlwifi.
> >
> > The problem is that to get this to work, some changes need to be
> > made
> > in the platform side. In this case, the rootport is not configured
> > properly so it won't work.
>
> Yeah, but users or distros might accidentally enable this Kconfig
> option and break the driver unintentionally. And subtle bugs like
> this
> are even worse as the user will not realise that it's because of a
> new
> Kconfig option.
>
> So I guess you can't automatically detect it the platform supports
> RTPM,
> right? Maybe there should be a module parameter which has to be set
> to
> enable this? And at least a big fat warning to the user that RTPM is
> enabled, bugs are likely and the user has to know what she's doing.
I thought this was what EXPERT was used for:
menuconfig EXPERT
bool "Configure standard kernel features (expert users)"
# Unhide debug options, to make the on-by-default options visible
select DEBUG_KERNEL
help
This option allows certain base kernel options and settings
to be disabled or tweaked. This is for specialized
environments which can tolerate a "non-standard" kernel.
Only use this if you really know what you are doing.
But it seems that it's widely used even by people/distros who don't
know what they are doing. :(
Would it be okay if we just add a printk(KERN_ERR, ...)?
> > We discussed this before and that's why this option now depends on
> > EXPERT.
>
> Heh, we did? I have no recollection of whatsoever about that :)
I'm not sure you were involved in the discussion, but that discussion
was the reason we introduced EXPERT as a dependency.
--
Luca.
next prev parent reply other threads:[~2017-10-18 10:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 2:48 After upgrading to 4.11.1, wifi driver refuses to load after being unloaded once Marc MERLIN
2017-06-02 9:42 ` Luca Coelho
2017-06-03 16:59 ` Marc MERLIN
2017-08-16 23:38 ` Marc MERLIN
2017-08-27 0:56 ` Marc MERLIN
2017-10-17 9:44 ` Marc MERLIN
2017-10-17 14:05 ` Luca Coelho
2017-10-17 21:23 ` Marc MERLIN
2017-10-17 21:34 ` Luca Coelho
2017-10-18 4:59 ` Kalle Valo
2017-10-18 6:16 ` Luca Coelho
2017-10-18 9:50 ` Kalle Valo
2017-10-18 10:22 ` Luca Coelho [this message]
2017-10-20 6:35 ` Kalle Valo
2017-10-21 0:50 ` Marc MERLIN
2017-10-21 10:22 ` Marc MERLIN
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=1508322176.5497.152.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=marc@merlins.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).