https://bugzilla.novell.com/show_bug.cgi?id=344877#c2 Franz Fleischmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |franz.fleischmann@landshut.org --- Comment #2 from Franz Fleischmann 2007-12-03 09:00:42 MST --- I have a similar problem, see Bug # 335121. The problem exists after adding all patches until yesterday. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c4 --- Comment #4 from Jeff Mahoney 2007-12-04 08:32:23 MST --- Out of band comment from the original reporter:

This bug seems to be related to the "time went backwards" bug, it's like the dom0 timer stop and block the system forever (even the magic sys req keys are not fonctionnal). Hard reboot required. Do you have an idea of how much time it could takes to solve this bug ? I can run test with prepatch on my system if you want.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User maxime.pierron@lippi.fr added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c6 --- Comment #6 from Maxime Pierron 2007-12-05 04:26:58 MST --- I just find this bugs report for centos, and it seems very interesting and directly related to the present bug. My idea to set the kernel timer to 100Hz seems to be not so bad... http://bugs.centos.org/view.php?id=2189 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c8 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |maxime.pierron@lippi.fr --- Comment #8 from Jan Beulich 2007-12-07 02:01:05 MST --- Please re-test with next kernel maintenance update (2.6.22.14-* or later), fix which might also address this just committed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c10 Glen Barney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gb2@c5i.net --- Comment #10 from Glen Barney 2007-12-09 18:23:50 MST --- I'm having a similar problem, and am not sure if I should open a new bug or not. I'm using OpenSuse 10.3 + XEN-PAE, all updates applied. I have two separate machines - one is a Dell 2950 4-core 2.0 GHZ with 4GB of RAM manufactured about three months ago, the other is a Dell 2950 8-core 3.0 GHZ with 8GB of RAM manufactured about three weeks ago. In both cases, I'm in the XEN-PAE kernel, runlevel 5, logged in to the KDE desktop, using the graphic installer. (Someone on the OpenSuse list suggested trying the command line installer, which I will.) Since I cannot use either installer to install from CD-ROM, of course, because of the problems in the python script, I have copied the CD-ROM to a directory, and "published" that directory via Apache. I then use http://my.ip.address/ as the installation source. Everything goes well until the system starts copying the installation packages from the web server. Within minutes, the entire server freezes - not just the guest, but the actual physical host. It is so frozen, in fact, that it powers off immediately when I hit the power button, and dumps no output anywhere. Since this happens on two seperate servers, every time, I thought I might open a new bug... but this one may fit? Any guidance or comments would be welcome! Glen -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c12 --- Comment #12 from Jan Beulich 2007-12-10 09:06:20 MST --- Re #9: This is going to be with the *next* update, not an already available one. Re #10: Please submit a new one *if* this same next kernel update doesn't fix your problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c14 --- Comment #14 from Glen Barney 2007-12-10 15:28:39 MST --- Re #5/#7: I tried recompiling the existing xenpae kernel (2.6.22.13-xenpae) changing the timer value from 250 to 100. The kernel did recompile and install, and the system did boot. However, this did not solve my problem. I have an image of the SuSE 10.3 DVD published on localhost through Apache2, and I am "downloading" the installation sources into my domU client from this image. So dom0 runs the modified xenpae kernel, but, during installation at least, domU is running the original off-the-media kernel. It got farther this time, but it did once again crash my entire physical server. Is the 2.6.22.14 kernel expected to solve this? Am I experiencing the same problem? Or do I have a new bug that needs reporting? Thanks, Glen -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User rodc@ravenet.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c16 Rodney Crossman changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rodc@ravenet.ca --- Comment #16 from Rodney Crossman 2008-01-06 14:40:24 MST --- it has been a month since Jan mentioned kernel 2.6.22.14 should have these fixes yet this kernel still is not one of the suse updates. Is this fix coming soon? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c18 Tamás Németh changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nice@titanic.nyme.hu --- Comment #18 from Tamás Németh 2008-01-08 09:24:13 MST --- I also have this problem (or similar) on an x86_64 system which runs a paravirtualized Linux domU (x86_64 of course, but 32 bit userland) and a fully virtualized Windows Server 2003. After 2-3 days of continuous running the clock of dom0 suddenly jums into the year 2203 and freezes, but the logs keep complainig about the time going backwards. However, setting the clocksource to jiffies solved the problem for me. It was even possible to log in via SSH into the virtually unresponsive dom0 and change the clock source on the fly. Let's see some parts of /var/log/messages: Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164325959175799191 shadow=182530936064246 offset=51157 Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164325959175786337 shadow=182530936064246 offset=63939 Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164325959175776875 shadow=182530936064246 offset=73371 Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164325959175758012 shadow=182530936064246 offset=92210 Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164325959175745946 shadow=182530936064246 offset=104288 Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164325959175731660 shadow=182530936064246 offset=118562 Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164325959175723354 shadow=182530936064246 offset=126875 Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164325959175705242 shadow=182530936064246 offset=144986 Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164325959175693748 shadow=182530936064246 offset=156475 May 1 13:38:47 carrier1 syslog-ng[3110]: STATS: dropped 165 May 1 13:38:47 carrier1 kernel: 284321 shadow=194035956173844 offset=142457115 May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed. May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164314454013278739 shadow=194035956173844 offset=142462709 May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed. May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164314454013273157 shadow=194035956173844 offset=142468291 May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed. May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164314454013267575 shadow=194035956173844 offset=142473867 May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed. May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164314454013261987 shadow=194035956173844 offset=142479455 May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed. May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164314454013256399 shadow=194035956173844 offset=142485043 May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed. May 1 13:38:47 carrier1 nmbd[4024]: [2203/05/01 13:38:47, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351) May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164314454013250793 shadow=194035956173844 offset=142490649 May 1 13:38:47 carrier1 nmbd[4024]: find_domain_master_name_query_fail: May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed. As you can see, there is a point when the time suddenly changes, but before that point complaining begins. After the time journey, the time is virtually frozen, but not entirely: Let's see, what happened somewhat(?) later: May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164305755947820318 shadow=202733992062057 offset=172040497 May 1 13:38:47 carrier1 kernel: printk: 8738 messages suppressed. May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164305750947799778 shadow=202738992057513 offset=172069418 May 1 13:38:47 carrier1 kernel: printk: 8609 messages suppressed. May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164305745947835361 shadow=202743992057509 offset=172029508 May 1 13:38:47 carrier1 kernel: printk: 8704 messages suppressed. May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164305740947825450 shadow=202748992058412 offset=172038763 May 1 20:18:41 carrier1 kernel: printk: 12490 messages suppressed. May 1 20:18:41 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164328465117250601 shadow=202753992057501 offset=172023354 May 1 20:18:41 carrier1 syslog-ng[3110]: STATS: dropped 7238 May 1 20:18:41 carrier1 nmbd[4024]: [2203/05/01 20:18:41, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351) May 1 20:18:41 carrier1 nmbd[4024]: find_domain_master_name_query_fail: May 1 20:18:41 carrier1 nmbd[4024]: Unable to find the Domain Master Browser name AD<1b> for the workgroup AD. May 1 20:18:41 carrier1 nmbd[4024]: Unable to sync browse lists in this workgroup. May 1 20:18:41 carrier1 kernel: printk: 9544 messages suppressed. May 1 20:18:41 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164328460117239584 shadow=202758992058125 offset=172033212 May 1 20:18:41 carrier1 kernel: printk: 9039 messages suppressed. May 1 20:18:41 carrier1 kernel: clocksource/0: Time went backwards: delta=-6164328455117234725 shadow=202763992057246 offset=172038426 May 1 20:18:41 carrier1 kernel: printk: 9328 messages suppressed. I've also found the description of the same (or very similar) bug at: https://bugs.launchpad.net/xen/+bug/146924 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User rodc@ravenet.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c20 --- Comment #20 from Rodney Crossman 2008-01-17 17:48:28 MST --- I installed the Jan 3 2008 2.6.22.15 kotd and after a week it happend again so still not fixed apparently. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User rodc@ravenet.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c22 --- Comment #22 from Rodney Crossman 2008-01-18 07:35:21 MST --- (In reply to comment #21 from Maxime Pierron)

Where did you download this kernel 2.6.22.15 ? Because 2.6.22.14 nor 2.6.22.15 are available from suse update repository. Can you give me the url ? Thx.

KOTD = Kernel of the Day. they are normally automated build kernels and not pretested so your taking a risk installing them. from the novell KOTD which I think a person at novell actually builds to test latest patches etc. http://ftp.suse.com/pub/projects/kernel/kotd/SL103_BRANCH/ there is also the novell/suse automated build system (zero human interaction or testing) http://download.opensuse.org/repositories/Kernel:/SL103_BRANCH/openSUSE_10.3... these are at-your-own-risk kernels and may totally break things. I installed the Jan 13 KOTD x64 xen kernel from ftp.suse.com and it is running so that one seems RELATIVELY safe. guess I'll find out over the next week if its better than previous. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |maxime.pierron@lippi.fr -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344877 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=344877#c25 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|maxime.pierron@lippi.fr | Resolution| |FIXED --- Comment #25 from Jan Beulich 2008-03-12 10:00:25 MST --- Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.