From: Jeff Garzik <jeff@garzik.org>
To: Zeno Davatz <zdavatz@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ata1 timeouts on 2.6.34-rc1
Date: Wed, 10 Mar 2010 13:37:11 -0500 [thread overview]
Message-ID: <4B97E6D7.1080909@garzik.org> (raw)
In-Reply-To: <40a4ed591003100943s74db8c55v610c6f9d822e9f77@mail.gmail.com>
On 03/10/2010 12:43 PM, Zeno Davatz wrote:
> On Wed, Mar 10, 2010 at 5:30 PM, Jeff Garzik<jeff@garzik.org> 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
next prev parent reply other threads:[~2010-03-10 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 10:08 ata1 timeouts on 2.6.34-rc1 Zeno Davatz
2010-03-10 14:31 ` Jeff Garzik
2010-03-10 15:41 ` Zeno Davatz
2010-03-10 16:30 ` Jeff Garzik
2010-03-10 17:43 ` Zeno Davatz
2010-03-10 18:37 ` Jeff Garzik [this message]
2010-03-10 19:52 ` Zeno Davatz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B97E6D7.1080909@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zdavatz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox