On Wed, Feb 21, 2018 at 03:57:31PM +0100, Marc Haber wrote:
> I then applied 2a266f23550be997d783f27e704b9b40c4010292 to 4.14.19,
> resulting in 4.4.19+, and this one has been running flawlessly for two
> days (and 0 minutes, incidentally) now. I will stay on 4.14.19+ until
> 4.15.5 comes out (and
On Mon, Feb 19, 2018 at 06:31:16AM +0100, Salvatore Bonaccorso wrote:
> On Sun, Feb 18, 2018 at 11:34:21AM +0100, Marc Haber wrote:
> > On Sun, Feb 18, 2018 at 10:15:43AM +0100, Salvatore Bonaccorso wrote:
> > > Looking today through the kernel archive, I noticed an answer from
> > > Paolo Bonzini,
Hi Marc,
On Sun, Feb 18, 2018 at 11:34:21AM +0100, Marc Haber wrote:
> On Sun, Feb 18, 2018 at 10:15:43AM +0100, Salvatore Bonaccorso wrote:
> > Looking today through the kernel archive, I noticed an answer from
> > Paolo Bonzini, <62aa6b81-5456-07dc-cf64-e46747d3a...@redhat.com>,
> > claiming thi
On Sun, Feb 18, 2018 at 10:15:43AM +0100, Salvatore Bonaccorso wrote:
> Looking today through the kernel archive, I noticed an answer from
> Paolo Bonzini, <62aa6b81-5456-07dc-cf64-e46747d3a...@redhat.com>,
> claiming this is fixed by
>
> https://git.kernel.org/linus/2a266f23550be997d783f27e704b9b
Source: linux
Source-Version: 4.15~rc8-1~exp1
Hi Marc,
On Sun, Feb 11, 2018 at 02:44:44PM +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,
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 doin
On Mon, Dec 25, 2017 at 10:02:48PM +, Ben Hutchings wrote:
> Given that commit fb1522e099f0 was merged after -rc7 I assume it's an
> important fix, though the commit message doesn't spell that out. So I
> think that whenever bisect asks you to test a version that doesn't
> contain it, you shou
On Wed, 2017-12-27 at 12:18 +0100, Marc Haber wrote:
> On Mon, Dec 25, 2017 at 10:02:48PM +, Ben Hutchings wrote:
> > It's on a branch that started at 4.13-rc7 but wasn't merged into
> > mainline until after 4.13. Comparing the two of them, 569dbb88e80d has
> > the addition of commit fb1522e09
Marc Haber wrote:
> On Mon, Dec 25, 2017 at 10:02:48PM +, Ben Hutchings wrote:
>> Given that commit fb1522e099f0 was merged after -rc7 I assume it's an
>> important fix, though the commit message doesn't spell that out. So I
>> think that whenever bisect asks you to test a version that doesn'
On Mon, Dec 25, 2017 at 10:02:48PM +, Ben Hutchings wrote:
> It's on a branch that started at 4.13-rc7 but wasn't merged into
> mainline until after 4.13. Comparing the two of them, 569dbb88e80d has
> the addition of commit fb1522e099f0 "KVM: update to new mmu_notifier
> semantic v2". So I wo
On Mon, 2017-12-25 at 14:15 +0100, Marc Haber wrote:
[...]
> I tried bisecting the kernel between 4.13 and 4.14, but the results are
> inconclusive to me:
>
> - 569dbb88e80deb68974ef6fdd6a13edb9d686261 is good
> - ddf720f86efe38cb3ef88b2eaad9ea8ad7c6f798 is bad
> - ddf720f86efe38cb3ef88b2eaad9ea8a
Package: src:linux
Version: 4.14.2-1
Severity: normal
Tags: upstream
Hi,
starting with kernel 4.14, the majority of mv KVM virtualization hosts
has become unstable. This behavior has been present in every 4.14
kernel, regardless of self-compiled or the Debian kernel. I am reporting
this in Debian
12 matches
Mail list logo
