[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#511412: marked as done (clocksource/0: Time went backwards)

Your message dated Tue, 4 Jun 2013 00:29:27 +0200
with message-id <20130603222926.GC5604@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #511412,
regarding clocksource/0: Time went backwards
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
511412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511412
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.26-1-xen-686
Version: 2.6.26-12
Severity: normal

After upgrading a domU from etch to lenny kernel, I've faced a hard domU
lockup that very looks like
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1098
after severak hours f running.

I've applied the workaround descried there at comment 13, and since
then domU worked several days under high load without issues.

Maybe make debian kernels not to use xen clocksource until the issue is
fixed? 


-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: