On Thu, Jun 20, 2013 at 09:20:01AM -0700, Dustin Lundquist wrote:
>
> Since the system is still half way responsive after this occurs, is
> there any other information I can gather after if occurs to aid in
> diagnosing this?
Hmm.... the only thing I can think of is to sprinkle in some
WARN_ON(irqs_disabled());
calls in various top-half routines in ext4 code, especially in
ext4_lookup() and ext4_find_entry(), and perhaps in the vfs layer to
see if we can figure out where the interrupts are getting disabled.
The fact that blkcipher_walk_done() was showing up in the stack trace
is certainly suspicious.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
