Re: PROBLEM: Linux-2.6.6 with dm-crypt hangs on SMP boxes

[Andrew Morton]

"Dr. Ernst Molitor" <molitor@xxxxxxx> wrote:
>
> [1.] Linux-2.6.6 caused full halts on two SMP boxes.
> [2.] I've been using Linux-2.4.20 with   cryptoloop/cryptoapi for 156
> days uptime; on two boxes, I have installed 2.6.6-rc3-bk5 (one box) and
> 2.6.6-bk5 (the other one), with dm-crypt on the partitions created with
> cryptoloop/cryptoapi. Both boxes ran like a charm, but both of them
> repeatedly came to a halt (no screen, no network connectivity, no
> reaction to keyboard or mouse activity: Need for hard reset) repeatedly.
> [3.] dm-crypt, loop device (maybe other things).
> In kern.log on the box with 2.6.6-bk5, I found the line
>   Incorrect TSC synchronization on an SMP system (see dmesg).
> with the 2.6.6 kernels, with 2.4.20, the message was
>  checking TSC synchronization across CPUs: passed.
> [4.] 2.6.6, 2.6.6-bk5

Are the machines using highmem? (What is in /proc/meminfo?)

Please add `nmi_watchdog=1' to the kernel boot command line and reboot.

After booting, do:

	echo 1 > /proc/sys/kernel/sysrq

After a machine hangs up, see if there is an NMI watchdog message on the
console.  If not, try typing ALT-sysrq-P.  If this generates a trace, type
it again until you capture the trace from the other CPU as well.  We'd need
to see both those traces.  A digital camera helps...

Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/