On Wed, 2005-08-03 at 11:15 -0400, Steven Rostedt wrote:
> I tested this patch by switching the kjournald to FIFO prio 30 and doing
> a make of the kernel and "find / -name vmlinux", but this took 40
> minutes to cause the deadlock.  Attached is a dumb module that creates a
> thread and spins. If you want to test my softlockup detect, this will
> trigger it.  The thread that is created is not RT so you can still do
> work. My detector doesn't care if something spins in the kernel as an RT
> task or not, it will flag it regardless.

Here's an updated version of the tarball. I've included another module
called nodeadlock that does a msleep(1) instead of a schedule.  This
should _not_ be detected as a lockup.

-- Steve

Attachment: deadlock_module.tar
Description: Unix tar archive

Reply via email to