On Thu, Sep 21, 2006 at 09:22:16AM +0200, Ingo Molnar wrote:
> * Bill Huey <[email protected]> wrote:
>
> > Also, triggering a panic() at the beginning of the rt mutex acquire
> > was very useful since it made "in_atomic()" violations an explicit
> > error stopping the machine. Stack traces started to get really crazy
> > in this preemptive kernel with all sorts of things running unlike the
> > non-preemptive kernel and it was time consuming to figure out the real
> > stuff from the noise in the stack trace.
>
> well you should absolutely have serial console if you effectively want
> to hack the Linux kernel. And in the serial console log you should
> search for stacktraces top-down, and concentrate on the first one - any
> subsequent one might be collateral damage of the first one.
Of course I did that. I'm not that stupid. :) The stack traces, even with
your above suggestions were too many and I had to break it down a bug at
a time, stack trace at a time, since I realize problems earlier could
clash and trigger other unrelated problems.
It was even problematic with the serial console on which is why I did
that. Maybe it was an artifact of having both the serial console and video
consoles on ?
bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
