From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: reinette chatre <reinette.chatre@intel.com>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlagn: default to MAX_UCODE_BEACON_INTERVAL in iwl_adjust_beacon_interval
Date: Mon, 23 Feb 2009 18:38:13 -0800 [thread overview]
Message-ID: <1235443093.4455.77.camel@johannes.local> (raw)
In-Reply-To: <20090221003133.GB3890@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Ok, starting to look into this ...
Since it seems you get this all the time, could you please put a printk
into net/wireless/scan.c in cfg80211_inform_bss_frame where it sets
res->pub.beacon_interval, and print out
"%p %d", &res->pub, res->pub.beacon_interval
and another one in cfg80211_get_bss where you print out the return value
(just to make sure it's returning the right thing). Maybe also put one
into cfg80211_bss_update where it updates things.
I suspect that some memory is getting overwritten or something. The
embedded struct thing was a bit of a hack.
Also please put a printk into the iwlwifi code and into
net/mac80211/mlme.c where it assigns
sdata->vif.bss_conf.beacon_int = bss->cbss.beacon_interval;
so that I can see the order this happening.
Thanks,
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-02-24 2:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <154E55ADF9629D4E8D13F08BF92ABEB629C9D28B8D@PDSMSX501.ccr.corp.intel.com>
[not found] ` <20090220145223.GA15006@tuxdriver.com>
[not found] ` <1235155966.5860.44.camel@rc-desk>
[not found] ` <20090220194306.GA4051@tuxdriver.com>
[not found] ` <20090221003013.GA3890@tuxdriver.com>
2009-02-21 0:31 ` [PATCH] iwlagn: default to MAX_UCODE_BEACON_INTERVAL in iwl_adjust_beacon_interval John W. Linville
2009-02-21 17:31 ` reinette chatre
2009-02-21 22:59 ` John W. Linville
2009-02-24 2:38 ` Johannes Berg [this message]
2009-02-25 1:44 ` John W. Linville
2009-03-14 15:59 ` Johannes Berg
2009-03-14 16:01 ` Johannes Berg
2009-03-14 17:08 ` Kalle Valo
2009-03-14 17:14 ` Johannes Berg
2009-03-14 17:33 ` Kalle Valo
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=1235443093.4455.77.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.com \
/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).