On Wed October 13 2010 02:14:19 Qasim Javed wrote:
> How about using trace-cmd and kernelshark with function graph tracer
> to see what is getting called so often?
>
> -Qasim
>
> On Tue, Oct 12, 2010 at 5:33 AM, Bruno Randolf wrote:
> > Hello!
> >
> > I am trying to debug a strange effect, I am
2010/10/12 Bruno Randolf :
> Hello!
>
> I am trying to debug a strange effect, I am seeing on soekris net48xx boards
> with two ath5k interfaces:
>
> * wlan0 [phy0] configured in ad-hoc mode, A band, and it is getting a lot of
> traffic routed thru it
> * wlan1 [phy1] also configured in ad-hoc mo
How about using trace-cmd and kernelshark with function graph tracer
to see what is getting called so often?
-Qasim
On Tue, Oct 12, 2010 at 5:33 AM, Bruno Randolf wrote:
> Hello!
>
> I am trying to debug a strange effect, I am seeing on soekris net48xx boards
> with two ath5k interfaces:
>
> *
On Tue, Oct 12, 2010 at 6:33 AM, Bruno Randolf wrote:
> So my question is: How can I find out, what [phy1] is so busy doing? Any ideas
> how to profile this?
/proc/interrupts shows lots of interrupts on phy1 line? Is it shared irq?
What options did you try with oprofile?
You can try perf -- as
Hello!
I am trying to debug a strange effect, I am seeing on soekris net48xx boards
with two ath5k interfaces:
* wlan0 [phy0] configured in ad-hoc mode, A band, and it is getting a lot of
traffic routed thru it
* wlan1 [phy1] also configured in ad-hoc mode, G band, but not actively
sending (
