I've been chasing a bug for some time. (Not my project, I was dropped onto
it.) Anyway, they were using kdb, and I thought it was a AWESOME tool.
But, the backtraces were never enough to find the problem. It looked like I
had some memory corruption somewhere on the stack (since backtraces were never
useful).
So, I decided to try to debug somemore at home. I installed kdb into a 2.2.19
kernel (required a little massaging, but no major changes from the patch).
The first thing I noticed was that my ethernet module was crashing on startup.
It still functioned ok, but the init part was hung (in lsmod, it was stuck
in initializing after the crash).
After several more clean tests (with 2.2.18 as well), it was determined that
kdb was *causing* the panics it was meant to observe.
Has anyone else had any experiences like that?
You can reproduce my crash with a vanilla 2.2.19 or 2.2.18 kernel, and a 3com
Vortex card with the driver loaded as a module (3c59x).
Later,
-Dave
