Bug#674907: reassign 674907 to src:linux-2.6, forcibly merging 599161 674907
can't really know if it's in the hypervisor or the linux kernel's way to
handle the clocksource from the hypervisor.
after some google search, the bug seems to appear in kernel 2.6.20
(don't take this for granted)
If it's really like this, then the bug is probably in the linux kernel.
Anyway the unstable tsc does not seems to be xen specific but more
generally linked with virtualization.
I just found a vmware documentation file that points this as a common
Le 01/10/2012 19:28, anarcat a écrit :
> On Mon, Oct 01, 2012 at 04:06:27PM +0200, Bastian Blank wrote:
>> reassign 674907 src:linux-2.6
> Why was this reassigned to the linux kernel?
> I explicitely stated (twice) that machines not running Xen are *not*
> affected, so this is specifically a Xen issue.
> I do not want to get into an edit war here, if there is proper
> justification I don't mind having it assigned to anything...
> But I don't think the bug is in the linux kernel as much as the Xen
> extensions somehow.
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com