From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 3224A138334 for ; Mon, 22 Jul 2019 10:30:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 29F3FE085A; Mon, 22 Jul 2019 10:30:10 +0000 (UTC) Received: from mx07-00178001.pphosted.com (mx08-00178001.pphosted.com [91.207.212.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A87ECE0844 for ; Mon, 22 Jul 2019 10:30:09 +0000 (UTC) Received: from pps.filterd (m0046660.ppops.net [127.0.0.1]) by mx08-00178001.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x6MARQki027234 for ; Mon, 22 Jul 2019 12:30:07 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=st.com; h=subject : to : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=STMicroelectronics; bh=A7FiKljYD86YoaIvdBco3RVz/bXx0Kv+jK96xa2Cxrw=; b=TeCqtpXwavIEWTBo5WzRKWXFV8DxA7TvJPXHRpXfzPKN8DILTpYqkGA5HfwCdE6yLFmu pMcstosBSN5DT+smWe+K+CJQarlhZ7yrb9Ys0iOKOqJgQsLGm+xq9VhxbbzYUZhkxkgn jSR7UGpnfUVAbJLMqBExHtsCZWiMuFTdL7uWLuB6ed22AyqsZBsvuJPOvc0syX2reP6w 3QQrqGUFeInqM7awMRQGmVCICmO0mry/HmA2amWKDjqCUMB1rX4c7XfPcbkP+W1DOBST Kxbz7ooe+om+OKQE9IxVKDISVqMdQ/QKrR9VVViplRnZ1AjFCYzt2CxhSIXKeBl4H+Z5 5g== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx08-00178001.pphosted.com with ESMTP id 2tur39b8ar-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 22 Jul 2019 12:30:07 +0200 Received: from zeta.dmz-eu.st.com (zeta.dmz-eu.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id C154F3A for ; Mon, 22 Jul 2019 10:30:06 +0000 (GMT) Received: from Webmail-eu.st.com (sfhdag7node2.st.com [10.75.127.20]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 7E0232A24 for ; Mon, 22 Jul 2019 10:30:06 +0000 (GMT) Received: from [10.50.186.1] (10.75.127.47) by SFHDAG7NODE2.st.com (10.75.127.20) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 22 Jul 2019 12:30:06 +0200 Subject: Re: [gentoo-user] hw problems To: References: From: Raffaele Belardi Message-ID: <7bbf9439-cf9e-0ae1-0bac-b56a79e6c159@st.com> Date: Mon, 22 Jul 2019 12:29:26 +0200 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.9.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.75.127.47] X-ClientProxiedBy: SFHDAG8NODE2.st.com (10.75.127.23) To SFHDAG7NODE2.st.com (10.75.127.20) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-07-22_08:,, signatures=0 X-Archives-Salt: e02c0fb8-aa7b-4b90-a2f4-4a507c1f094c X-Archives-Hash: 4ff22e8c6eca13e73c0f65a2ffcbca26 Adam Carter wrote: > On Mon, Jul 22, 2019 at 7:47 PM > wrote: > > Hi, > > Since last week my gentoo installation start to randomly freeze. The > first I've detected was during huge disk usage, another was during > hibernation, etc. I think it might be related to HDD problems, but I > want to be sure. In kernel log there are some errors, but I'm not able > to decide if those causes the freezing or not (I've saw such messages > earlier too, so I'm not sure). So, is there a good diagnostic tool to > check HW and mainly HDD? What I need to decide is if buying new HDD will > fix the issue or not > > > Install smartmontools then > > # smartctl -a /dev/sda > > I think Adam answered the OP but I just wanted to understand the kernel log: - the errors are from device pcieport 0000:00:1c.0 - according to "pci 0000:00:1c.0: [8086:9d14] type 01 class 0x060400", this is should be a PCI bridge. So the error may come from the bridge itself or from a device attached to the bridge, I suppose? - the disk is attached to ata1: "ata1.00: ATA-10: ST2000LM015-2E8174, SDM1, max UDMA/133" - ata1 is "ata1: SATA max UDMA/133 abar m2048@0xd1133000 port 0xd1133100 irq 122" Is there a way to understand where the ata1 is physically attached to? In other words, can one tell from the log if the error comes from the ata1 device or something else? thanks, raffaele