From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C64B51381F3 for ; Thu, 1 Aug 2013 07:37:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 84507E0C04; Thu, 1 Aug 2013 07:37:37 +0000 (UTC) Received: from vergina.dyndns.org (cust-218-222.on4.ontelecoms.gr [92.118.218.222]) by pigeon.gentoo.org (Postfix) with ESMTP id 4300DE0B42 for ; Thu, 1 Aug 2013 07:37:36 +0000 (UTC) Received: from [192.168.0.1] (viper.vergina.dyndns.org [192.168.0.1]) by viper.vergina.dyndns.org (Postfix) with ESMTP id B151110F; Thu, 1 Aug 2013 10:37:34 +0300 (EEST) Message-ID: <51FA103E.8030201@asyr.hopto.org> Date: Thu, 01 Aug 2013 10:37:34 +0300 From: Thanasis User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130628 Thunderbird/17.0.7 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 MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org CC: Paul Hartman Subject: Re: [gentoo-user] ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen References: <51F9534A.6010504@asyr.hopto.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 20e19ae5-15b0-48d4-914f-65842f544e67 X-Archives-Hash: cde3a494cb6d259a93b7aa72aac6108a on 08/01/2013 12:59 AM Paul Hartman wrote the following: > If no disks are attached, I wonder if something is probing it? > > I checked my dmesg and every time I plug in my eSATA enclosure, I see > this very similar message: > > [156541.724580] ata7: exception Emask 0x10 SAct 0x0 SErr 0x4040000 > action 0xe frozen > [156541.724587] ata7: irq_stat 0x00000040, connection status changed > [156541.724593] ata7: SError: { CommWake DevExch } > [156541.724604] ata7: hard resetting link > [156551.725559] ata7: softreset failed (device not ready) > [156551.725567] ata7: hard resetting link > > (and then a bunch of lines initializing all of the disks in the enclosure). > Me too. That's exactly how I use this Sata port, so it must be related to the way the kernel handles/probes it. BTW, I use a cable which is sata <-> eSata, i.e. sata for the motherboard side and eSata for the external disk side, and I keep the cable connected to the motherboard and the disk connected to the cable. I just power on the eSata external disk enclosure whenever I need to use the disk, and before switching the power off, I just unmount the disk. Is that a correct procedure?