From: Johannes Berg <johannes@sipsolutions.net>
To: Norbert Preining <preining@logic.at>
Cc: "Venkataraman, Meenakshi" <meenakshi.venkataraman@intel.com>,
"Lin, Hsien KuoX" <hsien.kuox.lin@intel.com>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Emmanuel Grumbach <egrumbach@gmail.com>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable
Date: Thu, 28 Jun 2012 09:51:08 +0200 [thread overview]
Message-ID: <1340869868.4491.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120628072512.GF31944@gamma.logic.tuwien.ac.at>
Hi Norbert,
> I am coming back to this old thread, not because it has been solved,
Somehow your mail didn't make it to the lists, not sure why.
> but because today I got a funny new message while checking why
> everything got stuck again:
> [69588.972126] iwlwifi 0000:06:00.0: fail to flush all tx fifo queues
> and after doing
> rfkill block wifi
> sleep 20
> rfkill unblock wifi
> I got a kernel warning:
> [76477.289251] WARNING: at net/mac80211/driver-ops.h:12 ieee80211_bss_info_change_notify+0x14e/0x1ca [mac80211]()
> [76477.289256] Hardware name: VGN-Z11VN_B
> [76477.289260] wlan0: Failed check-sdata-in-driver check, flags: 0x0
> [76477.289350] Modules linked in: ...
> [76477.289361] Pid: 4278, comm: NetworkManager Tainted: P W O 3.5.0-rc4+ #78
> [76477.289365] Call Trace:
> [76477.289380] [<ffffffff8102ba46>] warn_slowpath_common+0x83/0x9c
> [76477.289389] [<ffffffff8102bb02>] warn_slowpath_fmt+0x46/0x48
> [76477.289402] [<ffffffff813f21da>] ? neigh_ifdown+0xc5/0xd6
> [76477.289424] [<ffffffffa00b252e>] ieee80211_bss_info_change_notify+0x14e/0x1ca [mac80211]
> [76477.289448] [<ffffffffa00b267d>] ieee80211_ifa_changed+0xd3/0xe6 [mac80211]
> [76477.289458] [<ffffffff8104b7e3>] notifier_call_chain+0x37/0x61
> [76477.289467] [<ffffffff8104b919>] __blocking_notifier_call_chain+0x46/0x5f
> [76477.289475] [<ffffffff8104b946>] blocking_notifier_call_chain+0x14/0x16
> [76477.289485] [<ffffffff81432cc0>] __inet_del_ifa+0x176/0x22c
> [76477.289494] [<ffffffff81432f96>] inet_rtm_deladdr+0xe7/0x128
> [76477.289504] [<ffffffff813f61e0>] rtnetlink_rcv_msg+0x226/0x235
Fun. I don't actually see how this can possibly happen though?!
> Maybe this tells you something.
>
> > > > [ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
> > > >station id 0 addr 00:24:c4:ab:bd:e0
>
> These messages now appear only now and then.
I fixed those recently.
You seem to be on 3.5.0-rc now, is that really no different from 3.4?
johannes
next prev parent reply other threads:[~2012-06-28 7:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 1:17 iwlagn (3.3-wl), the saga continuous Norbert Preining
2012-04-11 2:37 ` 3.4-rc2, ilwagn still most of the time completely unusable Norbert Preining
2012-04-11 2:54 ` David Miller
2012-04-11 18:40 ` Ted Ts'o
2012-04-11 20:01 ` Dave Jones
2012-04-11 23:01 ` Norbert Preining
2012-04-11 23:24 ` Venkataraman, Meenakshi
2012-04-12 0:02 ` Norbert Preining
2012-04-13 1:32 ` Venkataraman, Meenakshi
2012-04-13 1:40 ` Norbert Preining
[not found] ` <59083F8344AE164EB150C0518405C0680E0F285C@FMSMSX107.amr.corp.intel.com>
2012-06-28 7:25 ` Norbert Preining
2012-06-28 7:51 ` Johannes Berg [this message]
2012-06-28 8:16 ` [Ilw] " Norbert Preining
2012-07-03 19:35 ` Alessandro Suardi
2012-07-12 8:14 ` Norbert Preining
2012-07-12 16:16 ` Johannes Berg
2012-07-25 3:07 ` Norbert Preining
2012-04-13 5:38 ` Norbert Preining
2012-04-25 1:06 ` Venkataraman, Meenakshi
2012-04-26 0:51 ` Norbert Preining
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=1340869868.4491.4.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=egrumbach@gmail.com \
--cc=hsien.kuox.lin@intel.com \
--cc=ilw@linux.intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meenakshi.venkataraman@intel.com \
--cc=preining@logic.at \
/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).