From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id olLzOhpCYV+lIQAA0tVLHw (envelope-from ) for ; Tue, 15 Sep 2020 22:37:14 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id oP4mNRpCYV9jJgAAbx9fmQ (envelope-from ) for ; Tue, 15 Sep 2020 22:37:14 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 4195294050F for ; Tue, 15 Sep 2020 22:37:14 +0000 (UTC) Received: from localhost ([::1]:44308 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kIJZX-0004hb-Ou for larch@yhetil.org; Tue, 15 Sep 2020 18:37:11 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:58300) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kIJZO-0004hC-3U for bug-guix@gnu.org; Tue, 15 Sep 2020 18:37:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:49232) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kIJZN-00024W-Qf for bug-guix@gnu.org; Tue, 15 Sep 2020 18:37:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kIJZN-0005cL-MW for bug-guix@gnu.org; Tue, 15 Sep 2020 18:37:01 -0400 X-Loop: help-debbugs@gnu.org Subject: bug#43344: "basic" system tests fail (and all the other ones) on guix master Resent-From: Mark H Weaver Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Tue, 15 Sep 2020 22:37:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43344 X-GNU-PR-Package: guix X-GNU-PR-Keywords: To: Danny Milosavljevic , Mathieu Othacehe Received: via spool by 43344-submit@debbugs.gnu.org id=B43344.160020936621526 (code B ref 43344); Tue, 15 Sep 2020 22:37:01 +0000 Received: (at 43344) by debbugs.gnu.org; 15 Sep 2020 22:36:06 +0000 Received: from localhost ([127.0.0.1]:60778 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kIJYF-0005aY-Iv for submit@debbugs.gnu.org; Tue, 15 Sep 2020 18:36:06 -0400 Received: from world.peace.net ([64.112.178.59]:42454) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kIJYB-0005aJ-9W for 43344@debbugs.gnu.org; Tue, 15 Sep 2020 18:35:49 -0400 Received: from mhw by world.peace.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIJY4-0001Sz-K1; Tue, 15 Sep 2020 18:35:40 -0400 From: Mark H Weaver In-Reply-To: <20200914183037.624cc347@scratchpost.org> References: <20200911195058.6dc013b4@scratchpost.org> <877dsw7alf.fsf@gnu.org> <20200914183037.624cc347@scratchpost.org> Date: Tue, 15 Sep 2020 18:34:21 -0400 Message-ID: <87y2laactz.fsf@netris.org> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 0.0 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-Spam-Score: -1.0 (-) X-BeenThere: bug-guix@gnu.org List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: 43344@debbugs.gnu.org Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: "bug-Guix" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of bug-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=bug-guix-bounces@gnu.org X-Spam-Score: -1.01 X-TUID: JrLOcA8MUwsH Hi, Danny Milosavljevic writes: > On Mon, 14 Sep 2020 15:26:52 +0200 > Mathieu Othacehe wrote: > >> Anything special with your hardware? KVM support disabled maybe? > > The culprit had been the Linux kernel update to 5.8.8. > > After downgrading to 5.8.7 it works just fine--no other changes done. > > Previously, I had tried also to add wipefs -a before the parted--that > hadn't helped either. That's useful information, but we should not stay frozen on the 5.8.7 kernel for much longer. 5.8.8 contains many bug fixes, some of which might fix potentially exploitable flaws. It would be useful to know if this problem still occurs with 5.8.9, which has since come out. If so, we should do a bisection between 5.8.7 and 5.8.8 to find out which upstream commit introduced the problem. Would anyone like to investigate this further? Mark