From: Fabio Coatti <fabio.coatti@gmail.com>
To: Luca Coelho <luca@coelho.fi>
Cc: Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
linuxwifi <linuxwifi@intel.com>
Subject: Re: kernel 4.9 iwlwifi startup error
Date: Tue, 10 Jan 2017 09:21:10 +0100 [thread overview]
Message-ID: <2231220.vMvt4J1trM@calvin> (raw)
In-Reply-To: <1484000511.5227.33.camel@coelho.fi>
In data marted=EC 10 gennaio 2017 00:21:51 CET, Luca Coelho ha scritto:
> On Tue, 2017-01-03 at 13:42 +1100, Andrew Donnellan wrote:
> > On 02/01/17 21:12, Fabio Coatti wrote:
> > > Hi all,
> > > I'm using kernel 4.9 and maybe half of the times I boot my laptop I g=
et
> > > the
> > > error reported below, and the wifi does not work. I have to remove
> > > iwlwifi (like modprobe -r iwldvm iwlwifi) and insert it again to get
> > > things workig again. This seems a bit random, it does not happens all
> > > the times so it could be a timing issue or even a flaky hardware
> > > (unlikely, as I see only this issue with wifi, once it starts it works
> > > just fine)
> > > I'm pretty sure to have seen the same behaviour at some point in 4.8.X
> > > release, but right now I lost the related notes.
> > > Environment:
> > > Distro: gentoo
> > > gcc 5.4.0
> > > HW: Hewlett-Packard HP EliteBook Folio 9470m/18DF, BIOS 68IBD Ver. F.=
63
> > > 04/26/2016
> > > Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz
> > > Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 2=
4)
> > >=20
> > > Of course if more info is needed, just drop me a note.
> > >=20
> > > I'm not subscribed to mailing lists, so please keep me in CC: for any
> > > information request.
> > >=20
> > > Many thanks.
> >=20
> > I've so far seen this once on my laptop, a Samsung NP540U3C (don't have
> > it with me right now, so I'm not sure what the wifi chipset is), running
> > with a Debian 4.9 kernel.
>=20
> This bug has already been reported in bugzilla:
>=20
> https://bugzilla.kernel.org/show_bug.cgi?id=3D190281
>=20
> Did you have any problems with older kernel versions? If so, would it be
> possible for you to bisect?
Well, it happens on a laptop that I use quite intensively, so it will take=
=20
some time to bisect. However, in the meantime I checked the old logs and th=
e=20
first recorded occurrence happened with 4.8.10 release and firmware version=
=20
18.168.6.1
=2D-=20
=46abio
WARNING: multiple messages have this Message-ID (diff)
From: Fabio Coatti <fabio.coatti@gmail.com>
To: Luca Coelho <luca@coelho.fi>
Cc: Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
linuxwifi <linuxwifi@intel.com>
Subject: Re: kernel 4.9 iwlwifi startup error
Date: Tue, 10 Jan 2017 09:21:10 +0100 [thread overview]
Message-ID: <2231220.vMvt4J1trM@calvin> (raw)
In-Reply-To: <1484000511.5227.33.camel@coelho.fi>
In data martedì 10 gennaio 2017 00:21:51 CET, Luca Coelho ha scritto:
> On Tue, 2017-01-03 at 13:42 +1100, Andrew Donnellan wrote:
> > On 02/01/17 21:12, Fabio Coatti wrote:
> > > Hi all,
> > > I'm using kernel 4.9 and maybe half of the times I boot my laptop I get
> > > the
> > > error reported below, and the wifi does not work. I have to remove
> > > iwlwifi (like modprobe -r iwldvm iwlwifi) and insert it again to get
> > > things workig again. This seems a bit random, it does not happens all
> > > the times so it could be a timing issue or even a flaky hardware
> > > (unlikely, as I see only this issue with wifi, once it starts it works
> > > just fine)
> > > I'm pretty sure to have seen the same behaviour at some point in 4.8.X
> > > release, but right now I lost the related notes.
> > > Environment:
> > > Distro: gentoo
> > > gcc 5.4.0
> > > HW: Hewlett-Packard HP EliteBook Folio 9470m/18DF, BIOS 68IBD Ver. F.63
> > > 04/26/2016
> > > Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz
> > > Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
> > >
> > > Of course if more info is needed, just drop me a note.
> > >
> > > I'm not subscribed to mailing lists, so please keep me in CC: for any
> > > information request.
> > >
> > > Many thanks.
> >
> > I've so far seen this once on my laptop, a Samsung NP540U3C (don't have
> > it with me right now, so I'm not sure what the wifi chipset is), running
> > with a Debian 4.9 kernel.
>
> This bug has already been reported in bugzilla:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=190281
>
> Did you have any problems with older kernel versions? If so, would it be
> possible for you to bisect?
Well, it happens on a laptop that I use quite intensively, so it will take
some time to bisect. However, in the meantime I checked the old logs and the
first recorded occurrence happened with 4.8.10 release and firmware version
18.168.6.1
--
Fabio
next prev parent reply other threads:[~2017-01-10 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 10:12 kernel 4.9 iwlwifi startup error Fabio Coatti
2017-01-03 2:42 ` Andrew Donnellan
2017-01-03 15:41 ` Alexander Morozov
2017-01-09 22:26 ` Luca Coelho
2017-01-09 22:21 ` Luca Coelho
2017-01-10 8:21 ` Fabio Coatti [this message]
2017-01-10 8:21 ` Fabio Coatti
2017-01-10 8:26 ` 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=2231220.vMvt4J1trM@calvin \
--to=fabio.coatti@gmail.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luca@coelho.fi \
/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.