From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932737Ab0CJShR (ORCPT ); Wed, 10 Mar 2010 13:37:17 -0500 Received: from mail-gy0-f174.google.com ([209.85.160.174]:44214 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755122Ab0CJShP (ORCPT ); Wed, 10 Mar 2010 13:37:15 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Mn4JBlVP9svnhHJyfoBdN21gU+LURmzVncAcz2X/duTMtA5VCkHSYwEVyF/RbEiKD7 I11OF7DHoCzFql76ft6KLe4/3ZdO8xGzGwWSivmBSZ5JzD8FpsBCxgv15E6Kc0q0ugdd CyYmBbchSYr5lM/LngfuLjlnghD2b3sBkn8og= Message-ID: <4B97E6D7.1080909@garzik.org> Date: Wed, 10 Mar 2010 13:37:11 -0500 From: Jeff Garzik User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc11 Thunderbird/3.0.3 MIME-Version: 1.0 To: Zeno Davatz CC: linux-kernel@vger.kernel.org Subject: Re: ata1 timeouts on 2.6.34-rc1 References: <40a4ed591003100208v67b61ca5sd7a3ab8da99e975e@mail.gmail.com> <4B97AD5B.5080802@garzik.org> <40a4ed591003100741i3f62c180k99fc85b2c57ab210@mail.gmail.com> <4B97C93B.9050002@garzik.org> <40a4ed591003100943s74db8c55v610c6f9d822e9f77@mail.gmail.com> In-Reply-To: <40a4ed591003100943s74db8c55v610c6f9d822e9f77@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/10/2010 12:43 PM, Zeno Davatz wrote: > On Wed, Mar 10, 2010 at 5:30 PM, Jeff Garzik wrote: >> On 03/10/2010 10:41 AM, Zeno Davatz wrote: >>> >>> Mar 10 13:30:01 zenogentoo cron[12528]: (root) CMD (test -x >>> /usr/sbin/run-crons&& /usr/sbin/run-crons ) >>> Mar 10 13:33:32 zenogentoo sudo: zeno : TTY=pts/0 ; PWD=/home/zeno >>> ; USER=root ; COMMAND=/usr/bin/emerge --sync >>> Mar 10 13:33:48 zenogentoo ata1: clearing spurious IRQ >>> Mar 10 13:34:19 zenogentoo ata1: lost interrupt (Status 0x50) >>> Mar 10 13:34:19 zenogentoo ata1.00: exception Emask 0x0 SAct 0x0 SErr >>> 0x0 action 0x6 frozen >>> Mar 10 13:34:19 zenogentoo ata1.00: failed command: READ DMA >>> Mar 10 13:34:19 zenogentoo ata1.00: cmd >>> c8/00:08:d5:20:cb/00:00:00:00:00/e9 tag 0 dma 4096 in >>> Mar 10 13:34:19 zenogentoo res 40/00:00:00:00:00/00:00:00:00:00/00 >>> Emask 0x4 (timeout) >>> Mar 10 13:34:19 zenogentoo ata1.00: status: { DRDY } >>> Mar 10 13:34:19 zenogentoo ata1: soft resetting link >>> Mar 10 13:34:19 zenogentoo ata1.00: configured for UDMA/133 >>> Mar 10 13:34:19 zenogentoo ata1.00: device reported invalid CHS sector 0 >>> Mar 10 13:34:19 zenogentoo ata1: EH complete >>> Mar 10 13:35:55 zenogentoo ata1: clearing spurious IRQ >>> Mar 10 13:36:26 zenogentoo ata1: lost interrupt (Status 0x50) >>> Mar 10 13:36:26 zenogentoo ata1.00: exception Emask 0x0 SAct 0x0 SErr >>> 0x0 action 0x6 frozen >>> Mar 10 13:36:26 zenogentoo ata1.00: failed command: WRITE DMA >>> Mar 10 13:36:26 zenogentoo ata1.00: cmd >>> ca/00:10:1d:ad:52/00:00:00:00:00/e6 tag 0 dma 8192 out >>> Mar 10 13:36:26 zenogentoo res 40/00:00:00:00:00/00:00:00:00:00/00 >>> Emask 0x4 (timeout) >>> Mar 10 13:36:26 zenogentoo ata1.00: status: { DRDY } >>> Mar 10 13:36:26 zenogentoo ata1: soft resetting link >>> Mar 10 13:36:26 zenogentoo ata1.00: configured for UDMA/133 >>> Mar 10 13:36:26 zenogentoo ata1.00: device reported invalid CHS sector 0 >>> Mar 10 13:36:26 zenogentoo ata1: EH complete >>> Mar 10 13:40:01 zenogentoo cron[12707]: (root) CMD (test -x >>> /usr/sbin/run-crons&& /usr/sbin/run-crons ) >>> Mar 10 13:48:05 zenogentoo sudo: zeno : TTY=pts/0 ; PWD=/home/zeno >>> ; USER=root ; COMMAND=/usr/bin/emerge portage >>> Mar 10 13:49:22 zenogentoo ata1: clearing spurious IRQ >>> Mar 10 13:49:53 zenogentoo ata1: lost interrupt (Status 0x50) >>> Mar 10 13:49:53 zenogentoo ata1.00: exception Emask 0x0 SAct 0x0 SErr >>> 0x0 action 0x6 frozen >>> Mar 10 13:49:53 zenogentoo ata1.00: failed command: WRITE DMA >>> Mar 10 13:49:53 zenogentoo ata1.00: cmd >>> ca/00:08:05:21:df/00:00:00:00:00/ef tag 0 dma 4096 out >>> Mar 10 13:49:53 zenogentoo res 40/00:00:00:00:00/00:00:00:00:00/00 >>> Emask 0x4 (timeout) >>> Mar 10 13:49:53 zenogentoo ata1.00: status: { DRDY } >>> Mar 10 13:49:53 zenogentoo ata1: soft resetting link >>> Mar 10 13:49:53 zenogentoo ata1.00: configured for UDMA/133 >>> Mar 10 13:49:53 zenogentoo ata1.00: device reported invalid CHS sector 0 >>> Mar 10 13:49:53 zenogentoo ata1: EH complete >>> >>> Let me know if I can supply you with anymore information. Also see >>> attached lspci-v file. >>> >> need full dmesg from boot, not just error snippet. > > This is the first message I get after boot that concerns ata: Not -after- boot, full dmesg including boot, please. Run /bin/dmesg just after booting. Jeff