Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Dec 2016 17:37:54 -0800
From:      Peter Grehan <grehan@freebsd.org>
To:        Rajil Saraswat <rajil.s@gmail.com>
Cc:        freebsd-virtualization@FreeBSD.org
Subject:   Re: Debian 8 CPU stall
Message-ID:  <002b80bb-d56b-95b8-6249-cf46d0896441@freebsd.org>
In-Reply-To: <a0f6d675-1387-e8c9-3421-4b377c02bc0e@gmail.com>
References:  <b011b080-5637-2da5-8a8a-819b7b1fabd3@gmail.com> <9c9e83a5-16c6-0ab5-0ac4-af0a54430706@freebsd.org> <6cff5bf2-9654-8627-83c4-6ab48ee763b5@gmail.com> <56863fec-d8f8-2601-811f-511cd199e82f@freebsd.org> <abc9aca0-ce64-a9d9-213a-957e0a599284@gmail.com> <131518ab-c3fc-6509-ba24-08b5c32cddd5@freebsd.org> <a0f6d675-1387-e8c9-3421-4b377c02bc0e@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Rajil,

> This seems to have worked. Even after 5 days of uptime, i dont see the
> CPU stall messages. It looks like an issue with debian only as my other
> vm's based off ubuntu and centos did not have those errors.

  Thanks very much for testing that out. The problem is certainly 
narrowed down a lot: Debian 8, single vCPU, APIC virtualization, with 
multiple PCI passthru ports. That will help a lot with debugging the issue.

later,

Peter.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002b80bb-d56b-95b8-6249-cf46d0896441>