Dear Pavel Roskin,
I have changed my point to point link configuration from AP<==>STN to WDS<==>WDS.
This seems to be working. No panic even after 24 hours.
I have NOT made any changes in my code.
The downside of this is that WDS will not scan and pick a quite channel at startup.
Also I have to specify the MAC address of the remote.
I will live with WDS link for now and return to figuring out the panic later.
From: Pavel Roskin [mailto:proski@...]
Sent: Saturday, July 30, 2011 7:00 PM
To: rm_mohan@...; R.Mohan
Subject: Re: [Madwifi-users] Madwifi-0.9.4-r4126-20100324: Kernel Panic
instation evereytime after approx 30 minutes
Quoting "R.Mohan" <mohan_r01@...>:
> Attached is the dump from the kernel. The stack trace in the kernel dump is
> always at the very same
It's hard to help you if you are using a modified snapshot that is
more than a year old. Maybe you could at least use the current
There is a lot of documentation how to debug kernel code. If your
kernel is compiled with debug information, you can do this:
That should show you the line where the oops is happening.
The next step is to add printk() statements around that place to see
where exactly the crash happens. Print all the data that is used by
the code, and then you should be able to see what is going wrong.