headers
Chatre, Reinette | 1 Apr 01:09
Picon
Favicon

RE: iwlwifi page allocation failure oops

On , maximilian attems  wrote:

> have that oops since 2.6.24 after some cycles of suspend to ram.
> just happened again with 2.6.25-rc7 on a x61s box
> ap is plain unencrypted network.
> 

...

Coud you please submit a new bug at
http://www.intellinuxwireless.org/bugzilla that includes the details of
your environment (which kernel/driver) and the log of the oops?

Thanks

Reinette

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
maximilian attems | 1 Apr 01:12
Picon

Re: iwlwifi page allocation failure oops

On Mon, Mar 31, 2008 at 04:09:54PM -0700, Chatre, Reinette wrote:
> On , maximilian attems  wrote:
> 
> > have that oops since 2.6.24 after some cycles of suspend to ram.
> > just happened again with 2.6.25-rc7 on a x61s box
> > ap is plain unencrypted network.
> > 
> 
> ...
> 
> Coud you please submit a new bug at
> http://www.intellinuxwireless.org/bugzilla that includes the details of
> your environment (which kernel/driver) and the log of the oops?

thanks for quick response
is bugzilla.k.o fine, why another bugzilla?
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Chatre, Reinette | 1 Apr 01:20
Picon
Favicon

RE: problem with iwl4965 and kernel 2.6.24.4

On Monday, March 31, 2008 3:02 PM, John Goulah  wrote:

> I have to use both.  I have to use iwconfig to pick my essid and
> access point, and I use wpa_supplicant to setup the encryption tunnel.
> Then I dhclient the IP address.    In previous wireless experience,
> once I've set the essid , it automatically associates to the access
> point (at least I can see that the MAC address is defined when I run
> iwconfig).  That does not happen with this driver- only "Not
> Associated" or "Invalid". Unfortunately debug for these cases isn't
> spitting any info.  I've been setting my access point mac address
> specifically with "iwconfig wlan0 ap <MAC>"   -before- running
> wpa_supplicant since I thought I had to be associated before running
> wpa_supplicant but it sounds like you are saying otherwise, so I'll
> try that tonight and then submit my findings in a bug.   If something
> I've said sounds completely wrong let me know.

It should not be necessary to use both iwconfig and wpa_supplicant.
wpa_supplicant will take care of the association for you. 

You will need to bring the interface up (ifconfig wlan0 up) before you
run wpa_supplicant.

If you run into issues, please also send wpa_supplicant's configuration
and debug log.

Thanks

Reinette
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
(Continue reading)

Permalink | Reply | 0 comments |
headers
Chatre, Reinette | 1 Apr 01:27
Picon
Favicon

RE: iwlwifi page allocation failure oops

On Monday, March 31, 2008 4:13 PM, maximilian attems  wrote:

> On Mon, Mar 31, 2008 at 04:09:54PM -0700, Chatre, Reinette wrote:
>> On , maximilian attems  wrote:
>> 
>>> have that oops since 2.6.24 after some cycles of suspend to ram.
>>> just happened again with 2.6.25-rc7 on a x61s box
>>> ap is plain unencrypted network.
>>> 
>> 
>> ...
>> 
>> Coud you please submit a new bug at
>> http://www.intellinuxwireless.org/bugzilla that includes the details
>> of your environment (which kernel/driver) and the log of the oops?
> 
> thanks for quick response
> is bugzilla.k.o fine, why another bugzilla?

We actively track the bugs in
http://www.intellinuxwireless.org/bugzilla. 

Reinette
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Denys Vlasenko | 1 Apr 02:56

[PATCH] wavelan_cs: stop inlining largish static functions

Hi John,

Can you please take a look at this patch?

drivers/net/wireless/wavelan_cs.c has unusually large number
of static inline functions - 27.

I looked through them and 20 of them do not seem to warrant inlining.
Some are really big; others call mdelay(1) or busy-wait for a bit
to be set in a hardware register - it's pointless
to optimize such functions for speed.

This patch removes "inline" from these static function
(regardless of number of callsites - gcc nowadays auto-inlines
statics with one callsite).

Size difference for 32bit x86:

   text    data     bss     dec     hex filename
  17020     372       8   17400    43f8 linux-2.6-ALLYES/drivers/net/wireless/wavelan_cs.o
  14032     356       8   14396    383c linux-2.6.inline-ALLYES/drivers/net/wireless/wavelan_cs.o

Signed-off-by: Denys Vlasenko <vda.linux@...>
--
vda
Attachment (deinline_wavelan_cs.diff): text/x-diff, 19 KiB
Permalink | Reply | 0 comments |
headers
Luis Carlos Cobo | 1 Apr 01:00

[PATCH 1/2] mac80211: check for mesh_config length on incoming management frames


Signed-off-by: Luis Carlos Cobo <luisca@...>
---
 net/mac80211/ieee80211_sta.c |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/net/mac80211/ieee80211_sta.c b/net/mac80211/ieee80211_sta.c
index cfe6fcc..feec201 100644
--- a/net/mac80211/ieee80211_sta.c
+++ b/net/mac80211/ieee80211_sta.c
@@ -2153,11 +2153,14 @@ ieee80211_rx_mesh_bss_get(struct net_device *dev, u8 *mesh_id, int mesh_id_len,

 static struct ieee80211_sta_bss *
 ieee80211_rx_mesh_bss_add(struct net_device *dev, u8 *mesh_id, int mesh_id_len,
-			  u8 *mesh_cfg, int freq)
+			  u8 *mesh_cfg, int mesh_config_len, int freq)
 {
 	struct ieee80211_local *local = wdev_priv(dev->ieee80211_ptr);
 	struct ieee80211_sta_bss *bss;

+	if (mesh_config_len != MESH_CFG_LEN)
+		return NULL;
+
 	bss = kzalloc(sizeof(*bss), GFP_ATOMIC);
 	if (!bss)
 		return NULL;
@@ -2530,7 +2533,8 @@ static void ieee80211_rx_bss_info(struct net_device *dev,
 #ifdef CONFIG_MAC80211_MESH
 		if (elems.mesh_config)
 			bss = ieee80211_rx_mesh_bss_add(dev, elems.mesh_id,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Luis Carlos Cobo | 1 Apr 02:39

[PATCH 2/2] mac80211: use a struct for bss->mesh_config

This allows cleaner code when accesing bss->mesh_config components.

Signed-off-by: Luis Carlos Cobo <luisca@...>
---
 net/mac80211/ieee80211_i.h   |   13 +++++++++++--
 net/mac80211/ieee80211_sta.c |   32 ++++++++++++++++++++------------
 net/mac80211/mesh.c          |    4 ----
 net/mac80211/mesh.h          |   10 ++++++++++
 4 files changed, 41 insertions(+), 18 deletions(-)

diff --git a/net/mac80211/ieee80211_i.h b/net/mac80211/ieee80211_i.h
index 7ab8066..69e2bc5 100644
--- a/net/mac80211/ieee80211_i.h
+++ b/net/mac80211/ieee80211_i.h
@@ -69,6 +69,14 @@ struct ieee80211_fragment_entry {
 	u8 last_pn[6]; /* PN of the last fragment if CCMP was used */
 };

+struct bss_mesh_config {
+	u32 path_proto_id;
+	u32 path_metric_id;
+	u32 cong_control_id;
+	u32 channel_precedence;
+	u8 mesh_version;
+};
+

 struct ieee80211_sta_bss {
 	struct list_head list;
@@ -94,7 +102,7 @@ struct ieee80211_sta_bss {
(Continue reading)

Permalink | Reply | 1 comment |
headers
bruno randolf | 1 Apr 03:53

Re: mac80211 bug? no data is being transmitted after interface is brought down and then up again

On Tuesday 01 April 2008 04:02:25 John W. Linville wrote:
> On Sat, Mar 29, 2008 at 07:32:51PM +0100, Thomas Bächler wrote:
> > My question is, should this be considered a bug in mac80211?
> > IMO, when an interface is brought down and then up again, one of the
> > following things should happen:
> > 1) Everything works as before
> > 2) Nothing works, but the card disassociates from the network.
>
> #2 would be my vote.

why is that? would it be so difficult to provide #1?

from a usability point of view #1 would be clearly better. whatever the state 
was before, when i bring the interface up it want it to work (associate, join 
IBSS) and be able to transmit data.

bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 2 comments |
headers
Marcelo Tosatti | 1 Apr 05:15

Re: [PATCH, take 3] libertas: convert RSSI to a direct command

On Thu, Mar 27, 2008 at 05:24:02PM -0400, Dan Williams wrote:
> On Wed, 2008-03-26 at 10:21 +0100, Holger Schurig wrote:
> > Besided the direct conversion of the CMD_802_11_RSSI command, this
> > patch also changes the following things:
> > 
> > * calls CMD_802_11_RSSI either asynchronosly (in the background)
> >   when main.c thinks the firmware is hosed and just want's to
> >   get a command through
> > * calls CMD_802_11_RSSI synchronously when called to get wireless
> >   statistics.
> > * don't do in-driver averaging anymore, this and the previous point
> >   eliminates the need for any "struct lbs_private" values
> > * use a 100% quality in a  special ADHOC case
> > 
> > Signed-off-by: Holger Schurig <hs4233@...>
> 
> Acked-by: Dan Williams <dcbw@...>
> 
> > Index: wireless-testing/drivers/net/wireless/libertas/cmd.c
> > ===================================================================
> > --- wireless-testing.orig/drivers/net/wireless/libertas/cmd.c	2008-03-26
09:18:24.000000000 +0100
> > +++ wireless-testing/drivers/net/wireless/libertas/cmd.c	2008-03-26 09:18:31.000000000 +0100
> > @@ -692,6 +692,44 @@ static int lbs_cmd_802_11_rate_adapt_rat
> >  	return 0;
> >  }
> >  
> > +int lbs_get_rssi(struct lbs_private *priv, u16 *snr, u16 *nf)
> > +{
> > +	struct cmd_ds_802_11_rssi cmd;
(Continue reading)

Permalink | Reply | 5 comments |
headers
Tomas Winkler | 1 Apr 07:49
Picon

Re: [PATCH 2/2] mac80211: use short_preamble mode from capability if ERP IE not present

On Mon, Mar 31, 2008 at 6:05 PM, Vladimir Koutny <vlado@...> wrote:
> When associating to a b-only AP where there is no ERP IE, short preamble
>  mode is left at previous state (probably also protection mode). In this
>  case, disable protection and use short preamble mode as specified in
>  capability field. The same is done if capability field is changed on-the-fly.
>

Not sure that capability information elements can change on the fly.
I've posted patch that passes the whole capability upon association to
driver and driver can choose whether short preabmle MIGHT by used or
not.
AP my force stations to move to long preamble by issuing ERP IE.

So I think this patch is redunant.

>  Signed-off-by: Vladimir Koutny <vlado@...>
>
>  ---
>  diff --git a/net/mac80211/ieee80211_sta.c b/net/mac80211/ieee80211_sta.c
>  index 6fb179a..2b49852 100644
>  --- a/net/mac80211/ieee80211_sta.c
>  +++ b/net/mac80211/ieee80211_sta.c
>  @@ -353,14 +353,12 @@ static void ieee80211_sta_wmm_params(struct net_device *dev,
>         }
>   }
>
>  -
>  -static u32 ieee80211_handle_erp_ie(struct ieee80211_sub_if_data *sdata,
>  -                                  u8 erp_value)
>  +static u32 ieee80211_handle_protect_preamb(struct ieee80211_sub_if_data *sdata,
(Continue reading)

Permalink | Reply | 1 comment |

Gmane