From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Linux IDE <linux-ide@vger.kernel.org>
Subject: ATA_PIIX - soft resetting port, port is slow to respond, machine "freezes" for a few seconds
Date: Sat, 01 Sep 2007 13:23:39 +0200 [thread overview]
Message-ID: <46D94BBB.9080403@wpkg.org> (raw)
I just upgraded from 2.6.18 distributed with Debian to 2.6.22.6.
I compiled ATA_PIIX directly in the kernel.
From time to time, the machine "freezes" for a couple of seconds, and
I'm getting the following logs (pasted below).
I didn't have anything like that with the old IDE.
The machine runs a 2 GB Transcend IDE flash disk.
Any ideas what it might be?
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd ca/00:10:47:64:1d/00:00:00:00:00/e0 tag 0 cdb 0x0 data 8192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting port
ata1.00: configured for MWDMA2
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd ca/00:10:47:64:1d/00:00:00:00:00/e0 tag 0 cdb 0x0 data 8192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting port
ata1.00: configured for MWDMA2
ata1: EH complete
ata1.00: limiting speed to MWDMA1:PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd ca/00:10:47:64:1d/00:00:00:00:00/e0 tag 0 cdb 0x0 data 8192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting port
ata1.00: configured for MWDMA1
ata1: EH complete
sd 0:0:0:0: [sda] 3985632 512-byte hardware sectors (2041 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't
support DPO or FUA
sd 0:0:0:0: [sda] 3985632 512-byte hardware sectors (2041 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't
support DPO or FUA
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2007-09-01 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 11:23 Tomasz Chmielewski [this message]
2007-09-01 12:00 ` ATA_PIIX - soft resetting port, port is slow to respond, machine "freezes" for a few seconds Joris
2007-09-01 12:26 ` Tomasz Chmielewski
[not found] ` <6b9952490709010707i33e49d19o2fa44f5bec4e367d@mail.gmail.com>
2007-09-01 20:49 ` Tomasz Chmielewski
2007-09-07 2:18 ` Tejun Heo
2007-09-07 2:17 ` Tejun Heo
2007-10-18 10:57 ` Tomasz Chmielewski
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=46D94BBB.9080403@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-ide@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.