"Boerner, Brian" <Brian_Boerner@ntc.adaptec.com> writes:
> I'm working on preparing a raid driver for eventual submission to open
> source. I'm currently running into a problem that results in a kernel panic.
> Since these drivers have not yet been released and business issues are still
> being worked out, I can not comment a great deal about the inner workings.
> However, that doesn't prevent me from asking for assistance from you folks.
> Our QA folks have recently uncovered that performing several operations to
> the containers in rapid succession results in a kernel panic. The panic
> string is:
> Kernel panic: CPU 0 trying to acquire lock again: lock count = -1
Neither the 2.2 nor the 2.4 tree contain this message, so it is probably
generated by your own code.
> Then the system rebooted. No other messages were reported. I have read and
> followed the instructions in oops-tracing.txt and have read a number of
> other documents in the Documentation directory.
> Does anyone have any suggestions for debugging with as little information as
> the above message.
Unlikely because of the reasons above.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:15 EST