From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: recent master hardware problems
Date: Mon, 05 Dec 2016 21:28:51 +0100
Message-ID: <87h96i15oc.fsf@gnu.org>
References: <87zikdpgkx.fsf@we.make.ritual.n0.is> <87h96ljo71.fsf@gmail.com>
	<87y3zx9hit.fsf@we.make.ritual.n0.is>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45783)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cDzsf-00082B-VS
	for guix-devel@gnu.org; Mon, 05 Dec 2016 15:28:58 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cDzsc-0003eE-Rq
	for guix-devel@gnu.org; Mon, 05 Dec 2016 15:28:58 -0500
In-Reply-To: <87y3zx9hit.fsf@we.make.ritual.n0.is> (ng0@libertad.pw's message
	of "Sat, 03 Dec 2016 15:08:58 +0000")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: ng0 <ng0@libertad.pw>
Cc: guix-devel@gnu.org

ng0 <ng0@libertad.pw> skribis:

> Chris Marusich <cmmarusich@gmail.com> writes:
>
>> ng0 <ng0@libertad.pw> writes:
>>
>>> I'm not sure how to describe this bug. I've just build and
>>> reconfigured a system update. All went well, but then I
>>> rebooted.
>>> Everything loads, until:
>>> =E2=80=A6
>>> floppy0: no floppy controllers found  (ok, this is normal and expected)
>>> ata8: SATA link down (SStatus 0 SControl 0)
>>>
>>> So.. I guess either the harddrive on connection 8 decided to die
>>> over night, or something changed in the kernel or some other
>>> related driver/software.
>>>
>>> I have no time to debug this, but I'll come back to it.
>>
>> Did rolling back your system fix the issue?
>>
>> --=20
>> Chris
>
> Yes. So it's not an hardware failure.

Did you try using the same kernel version as before?

Ludo=E2=80=99.