[Prism54-devel] Re: islpci_mgt_transaction and stability

Denis Vlasenko vda at port.imtp.ilyichevsk.odessa.ua
Mon Aug 9 21:35:05 UTC 2004


> > > But I noticed one interesting thing. Whenever link is restored,
> > > I see lone "islpci_mgt_transaction(op 0, oid 10000001, sendlen 6)"
> > > in syslog. What that can be?
> > >
> > > 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:

Aug 10 00:33:24 shadow kernel: islpci_mgt_transaction(op 0, oid 10000001, sendlen 6)
Aug 10 00:33:24 shadow kernel:  [<c0105cf2>] dump_stack+0x17/0x1b
Aug 10 00:33:24 shadow kernel:  [<d0ab632c>] islpci_mgt_transaction+0x349/0x35a [prism54]
Aug 10 00:33:24 shadow kernel:  [<d0abb0ba>] mgt_get_request+0x252/0x2c3 [prism54]
Aug 10 00:33:24 shadow kernel:  [<d0ab6ec2>] prism54_get_wap+0x22/0x50 [prism54]
Aug 10 00:33:24 shadow kernel:  [<d0ab85bf>] link_changed+0x40/0x5a [prism54]
Aug 10 00:33:24 shadow kernel:  [<d0ab8af9>] prism54_process_trap_helper+0x60/0x114 [prism54]
Aug 10 00:33:24 shadow kernel:  [<d0ab8bdf>] prism54_process_trap+0x32/0x43 [prism54]
Aug 10 00:33:24 shadow kernel:  [<c011f9ba>] worker_thread+0x158/0x1e7
Aug 10 00:33:24 shadow kernel:  [<c012275d>] kthread+0x97/0x9d
Aug 10 00:33:24 shadow kernel:  [<c0103dd1>] kernel_thread_helper+0x5/0xb

It's link state change notification code kicking in...
--
vda



More information about the Prism54-devel mailing list