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 will update then). If you don't hear from me again
> in this bug report, then you can safely assume that 4.14.19+ lived on
> the test machine until its planned decommissioning during the 4.15.5
> rollout.

I regret to say that one of the VMs running on the host running 4.14.19+
has just suffered a "BUG: soft lockup - CPU#1 stuck for 58s!" which is
an atypical behavior for the issue I had previously, but might have a
common cause. 4.15.5 is currently building on my build host, and I'll
move to that kernel asap.


Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Reply via email to