On 14/02/2018 03:04, Josh Poimboeuf wrote:
> On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote:
>> Hi,
>>
>> after in total nine weeks of bisecting, broken filesystems, service
>> outages (thankfully on unportant systems), 4.15 seems to have fixed the
>> issue. After going to 4.15, the
On 14/02/2018 03:04, Josh Poimboeuf wrote:
> On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote:
>> Hi,
>>
>> after in total nine weeks of bisecting, broken filesystems, service
>> outages (thankfully on unportant systems), 4.15 seems to have fixed the
>> issue. After going to 4.15, the
On Wed, Feb 14, 2018 at 10:56:35AM +0800, Haozhong Zhang wrote:
> On 02/13/18 20:04 -0600, Josh Poimboeuf wrote:
> > On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote:
> > > Hi,
> > >
> > > after in total nine weeks of bisecting, broken filesystems, service
> > > outages (thankfully on
On Wed, Feb 14, 2018 at 10:56:35AM +0800, Haozhong Zhang wrote:
> On 02/13/18 20:04 -0600, Josh Poimboeuf wrote:
> > On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote:
> > > Hi,
> > >
> > > after in total nine weeks of bisecting, broken filesystems, service
> > > outages (thankfully on
On 02/13/18 20:04 -0600, Josh Poimboeuf wrote:
> On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote:
> > Hi,
> >
> > after in total nine weeks of bisecting, broken filesystems, service
> > outages (thankfully on unportant systems), 4.15 seems to have fixed the
> > issue. After going to
On 02/13/18 20:04 -0600, Josh Poimboeuf wrote:
> On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote:
> > Hi,
> >
> > after in total nine weeks of bisecting, broken filesystems, service
> > outages (thankfully on unportant systems), 4.15 seems to have fixed the
> > issue. After going to
On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote:
> Hi,
>
> after in total nine weeks of bisecting, broken filesystems, service
> outages (thankfully on unportant systems), 4.15 seems to have fixed the
> issue. After going to 4.15, the crashes never happened again.
>
> They have,
On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote:
> Hi,
>
> after in total nine weeks of bisecting, broken filesystems, service
> outages (thankfully on unportant systems), 4.15 seems to have fixed the
> issue. After going to 4.15, the crashes never happened again.
>
> They have,
Hi,
after in total nine weeks of bisecting, broken filesystems, service
outages (thankfully on unportant systems), 4.15 seems to have fixed the
issue. After going to 4.15, the crashes never happened again.
They have, however, happened with each and every 4.14 release I tried,
which I stopped
Hi,
after in total nine weeks of bisecting, broken filesystems, service
outages (thankfully on unportant systems), 4.15 seems to have fixed the
issue. After going to 4.15, the crashes never happened again.
They have, however, happened with each and every 4.14 release I tried,
which I stopped
Hi,
it's been five weeks since I gave you the last information about this
issue. Alas, I don't have a solution yet, only reports:
- The bisect between 4.13 and 4.14 ended up on a one-character fix in a
comment, so that was a total waste.
- The issue is present in all recent kernels up to
Hi,
it's been five weeks since I gave you the last information about this
issue. Alas, I don't have a solution yet, only reports:
- The bisect between 4.13 and 4.14 ended up on a one-character fix in a
comment, so that was a total waste.
- The issue is present in all recent kernels up to
4.14.3 is still affected.
I am still bisecting between 4.13 and 4.14, 5 steps to go. Defining a
kernel as "good" if it survived 24 hours on the hosts.
Greetings
Marc
On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> From: 王金浦 <jinpuw...@gmail.com>
> Subject: Re:
4.14.3 is still affected.
I am still bisecting between 4.13 and 4.14, 5 steps to go. Defining a
kernel as "good" if it survived 24 hours on the hosts.
Greetings
Marc
On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> From: 王金浦
> Subject: Re: VMs freezing when host
On Thu, Nov 23, 2017 at 06:26:36PM +0200, Liran Alon wrote:
> If there is no nested guest so no. My fix here probably won't help.
I can confirm that I am not running nested virt, the host is running
directly on the APU. I also have three other machines that are running
flawlessly with 4.14, and
On Thu, Nov 23, 2017 at 06:26:36PM +0200, Liran Alon wrote:
> If there is no nested guest so no. My fix here probably won't help.
I can confirm that I am not running nested virt, the host is running
directly on the APU. I also have three other machines that are running
flawlessly with 4.14, and
On 23/11/17 18:24, Radim Krčmář wrote:
2017-11-23 18:18+0200, Liran Alon:
On 23/11/17 17:59, Radim Krčmář wrote:
Btw. there have been already many fixes from Liran Alon for that patch
and your case could be the one adressed in
On 23/11/17 18:24, Radim Krčmář wrote:
2017-11-23 18:18+0200, Liran Alon:
On 23/11/17 17:59, Radim Krčmář wrote:
Btw. there have been already many fixes from Liran Alon for that patch
and your case could be the one adressed in
2017-11-23 18:18+0200, Liran Alon:
> On 23/11/17 17:59, Radim Krčmář wrote:
> > Btw. there have been already many fixes from Liran Alon for that patch
> > and your case could be the one adressed in
> >
2017-11-23 18:18+0200, Liran Alon:
> On 23/11/17 17:59, Radim Krčmář wrote:
> > Btw. there have been already many fixes from Liran Alon for that patch
> > and your case could be the one adressed in
> >
On 23/11/17 17:59, Radim Krčmář wrote:
2017-11-23 16:20+0100, Marc Haber:
On Wed, Nov 22, 2017 at 05:43:13PM +0100, Radim Krčmář wrote:
2017-11-22 16:52+0100, Marc Haber:
On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
So all guest kernels are 4.14, or also other older kernel?
Guest
On 23/11/17 17:59, Radim Krčmář wrote:
2017-11-23 16:20+0100, Marc Haber:
On Wed, Nov 22, 2017 at 05:43:13PM +0100, Radim Krčmář wrote:
2017-11-22 16:52+0100, Marc Haber:
On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
So all guest kernels are 4.14, or also other older kernel?
Guest
2017-11-23 16:20+0100, Marc Haber:
> On Wed, Nov 22, 2017 at 05:43:13PM +0100, Radim Krčmář wrote:
> > 2017-11-22 16:52+0100, Marc Haber:
> > > On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> > > > So all guest kernels are 4.14, or also other older kernel?
> > >
> > > Guest kernels are
2017-11-23 16:20+0100, Marc Haber:
> On Wed, Nov 22, 2017 at 05:43:13PM +0100, Radim Krčmář wrote:
> > 2017-11-22 16:52+0100, Marc Haber:
> > > On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> > > > So all guest kernels are 4.14, or also other older kernel?
> > >
> > > Guest kernels are
On Wed, Nov 22, 2017 at 05:43:13PM +0100, Radim Krčmář wrote:
> 2017-11-22 16:52+0100, Marc Haber:
> > On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> > > So all guest kernels are 4.14, or also other older kernel?
> >
> > Guest kernels are also 4.14, but the issue disappears when the host
On Wed, Nov 22, 2017 at 05:43:13PM +0100, Radim Krčmář wrote:
> 2017-11-22 16:52+0100, Marc Haber:
> > On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> > > So all guest kernels are 4.14, or also other older kernel?
> >
> > Guest kernels are also 4.14, but the issue disappears when the host
2017-11-22 16:52+0100, Marc Haber:
> On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> > So all guest kernels are 4.14, or also other older kernel?
>
> Guest kernels are also 4.14, but the issue disappears when the host is
> downgraded to an older kernel. I therefore reckoned that the guest
2017-11-22 16:52+0100, Marc Haber:
> On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> > So all guest kernels are 4.14, or also other older kernel?
>
> Guest kernels are also 4.14, but the issue disappears when the host is
> downgraded to an older kernel. I therefore reckoned that the guest
On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> So all guest kernels are 4.14, or also other older kernel?
Guest kernels are also 4.14, but the issue disappears when the host is
downgraded to an older kernel. I therefore reckoned that the guest
kernel doesn't matter, but that was before I
On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> So all guest kernels are 4.14, or also other older kernel?
Guest kernels are also 4.14, but the issue disappears when the host is
downgraded to an older kernel. I therefore reckoned that the guest
kernel doesn't matter, but that was before I
+cc kvm
2017-11-22 10:39 GMT+01:00 Marc Haber :
> On Tue, Nov 21, 2017 at 05:18:21PM +0100, Marc Haber wrote:
>> On the affected host, VMs freeze at a rate about two or three per day.
>> They just stop dead in their tracks, console and serial console become
>>
+cc kvm
2017-11-22 10:39 GMT+01:00 Marc Haber :
> On Tue, Nov 21, 2017 at 05:18:21PM +0100, Marc Haber wrote:
>> On the affected host, VMs freeze at a rate about two or three per day.
>> They just stop dead in their tracks, console and serial console become
>> unresponsive, ping stops, they don't
On Tue, Nov 21, 2017 at 05:18:21PM +0100, Marc Haber wrote:
> On the affected host, VMs freeze at a rate about two or three per day.
> They just stop dead in their tracks, console and serial console become
> unresponsive, ping stops, they don't react to virsh shutdown, only to
> virsh destroy.
I
On Tue, Nov 21, 2017 at 05:18:21PM +0100, Marc Haber wrote:
> On the affected host, VMs freeze at a rate about two or three per day.
> They just stop dead in their tracks, console and serial console become
> unresponsive, ping stops, they don't react to virsh shutdown, only to
> virsh destroy.
I
Hi,
I am running Debian stable with home-built kernels on a number of KVM
hosts and a bigger number of KVM VMs. With 4.14, I have an interesting
phenomenon on _one_ of my hosts, while all other hosts run fine. All
systems are reasonably similar to each other.
On the affected host, VMs freeze at
Hi,
I am running Debian stable with home-built kernels on a number of KVM
hosts and a bigger number of KVM VMs. With 4.14, I have an interesting
phenomenon on _one_ of my hosts, while all other hosts run fine. All
systems are reasonably similar to each other.
On the affected host, VMs freeze at
36 matches
Mail list logo