>>> On 09.11.12 at 10:05, <philippe.simo...@swisscom.com> wrote: > oops, excuse me, here is a description : I have the problem on 4 systems, > all with same hardware. > the problem occured on each system, 1 time each 2 month in average. since > January 2012, I decided to reboot them all monthly, > and the clock jump occurred only once in February ... > > SYSTEM : HP ProLiant DL385 G7, with 2 * AMD Processor 6174 (12 > cores) = 24 > cores, 16 GB MEMORY > XEN (XEN) Xen version 4.0.1 (Debian 4.0.1-5.4) > (ultrot...@debian.org) > (gcc version 4.4.5 (Debian 4.4.5-8) ) Sat Sep 8 19:15:46 UTC 2012 > DOM0 Linux 2.6.32-5-xen-amd64 #1 SMP Sun Sep 23 13:49:30 UTC > 2012 x86_64 > GNU/Linux > CPU > processor : 0 > vendor_id : AuthenticAMD > cpu family : 16 > model : 9 > model name : AMD Opteron(tm) Processor 6174
Huh - so we have the problem on even different vendor CPUs (as Mauro's are Intel ones). But I take it that you haven't see an event yet with the debugging patch? Plus, what's puzzling me a little too - before the occurrence of the event on Mauro's system, I was under the impression that this requires quite a bit of uptime. Yet the event he observed occurred early on the second day after boot afaict. Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
