LKML Archive on
help / color / mirror / Atom feed
From: Andrew Morton <>
To: "Dr. Ernst Molitor" <>
Cc:, Christophe Saout <>
Subject: Re: PROBLEM: Linux-2.6.6 with dm-crypt hangs on SMP boxes
Date: Fri, 21 May 2004 18:56:40 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1085043539.18199.20.camel@felicia>

"Dr. Ernst Molitor" <> 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...


  reply	other threads:[~2004-05-22  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20  8:59 Dr. Ernst Molitor
2004-05-22  1:56 ` Andrew Morton [this message]
2004-05-24 20:33   ` Dr. Ernst Molitor
2004-05-26 11:41     ` Dr. Ernst Molitor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: PROBLEM: Linux-2.6.6 with dm-crypt hangs on SMP boxes' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).