linux-kernel - CE: xen increasing min_delta_ns to 7651397591976463850 nsec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 22 Feb 2010 09:26:59 +0100
From:	Jens Seidel <jensseidel@...rs.sf.net>
To:	linux-kernel@...r.kernel.org
Subject: CE: xen increasing min_delta_ns to 7651397591976463850 nsec

Hi,

I'm using vanilla 2.6.32.7 domU kernel with Xen 3.2 and get very often a
unresponsible system after approximately one or two days with messages such as

[43616.674502] CE: xen increasing min_delta_ns to 16086592372704132408 nsec
[43616.674502] CE: xen increasing min_delta_ns to 5683144485346646996 nsec
[43616.674502] CE: xen increasing min_delta_ns to 17748088764874746302 nsec
[43616.674502] CE: xen increasing min_delta_ns to 17398761110457343644 nsec
[43616.674502] CE: xen increasing min_delta_ns to 7651397591976463850 nsec
[43616.674502] CE: xen increasing min_delta_ns to 2253724351109919966 nsec
[43616.674502] CE: xen increasing min_delta_ns to 3380586526664879948 nsec
[43616.674502] CE: xen increasing min_delta_ns to 5070879789997319922 nsec
[43616.674502] CE: xen increasing min_delta_ns to 7606319684995979882 nsec
[43616.674502] CE: xen increasing min_delta_ns to 11409479527493969822 nsec
[43616.674502] CE: xen increasing min_delta_ns to 17114219291240954732 nsec

on the console. I fail to login via ssh and even to cleanly shutdown this
system via xm <id> shutdown. sysrq requests still work.

I searched the net but found only messages with 15000 nsec. My values are a
little bit larger :-)) Found references to the kernel parameter notsc and
tried it but the problem remains.

The problem started once I upgraded the kernel from 2.6.26 to 2.6.32.7.
I changed from 32bit to 64bit but apart from this I did only a make oldconfig.
That's why I think it's not my config which causes trouble.

Any ideas? Is it a known problem?

PS: Please CC: me.

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