[Prism54-devel] Re: islpci_mgt_transaction and stability

Denis Vlasenko vda at port.imtp.ilyichevsk.odessa.ua
Wed Aug 11 06:17:03 UTC 2004


> > > > > oid_mgt.c:
> > > > >         OID_STRUCT_C(DOT11_OID_BSSID, 0x10000001, u8[6],
> > > > > OID_TYPE_RAW),
> > > > >
> > > > > I wonder, is this the result of (re)assoc happened?
> > > > > Or maybe it is other way around and this transaction kicked hw so
> > > > > that hw noticed the problem and reassociated?
> > > >
> > > > Hmm, strange indeed. My only guess would be a bogus call to
> > > > mgt_get_request where the "extra" parameter was set to some value it
> > > > shouldn't have. When extra is set, the oid used for the get can be
> > > > affected by:
> > > >
> > > > oid = isl_oid[n].oid + extra;
> > > >
> > > > Perhaps try printk'ing extra here for all gets see if that triggered
> > > > it
> > >
> > > I'll give dump_stack() a try instead ;)
> >
> > -ENOTABUG:
> >
...
> >
> > It's link state change notification code kicking in...
>
> Hmm, but we still don't know now if it was because of bogus extra value
> in:
>
> oid = isl_oid[n].oid + extra;
>
> :)

It was requested directly:

prism54_get_wap(struct net_device *ndev, struct iw_request_info *info..) {
...
        rvalue = mgt_get_request(priv, DOT11_OID_BSSID, 0, NULL, &r);

Looks like we have no bug here.
--
vda



More information about the Prism54-devel mailing list