From: Christian <cjs@dhp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen
Date: Tue, 30 Sep 2008 18:04:15 -0400 [thread overview]
Message-ID: <20080930220415.GC5334@dhp.com> (raw)
I'm also experiencing the same issue..
These messages have been coming in from time to time (sometimes a couple per day). I've tried getting around with this with various kernel settings such as noapic with no luck.
The drives are running on a Supermicro 8 port SATA card (AOC-SAT2-MV8) that's plugged into a standard PCI slot (not pci-x).
01:07.0 SCSI storage controller: Marvell Technology Group Ltd. MV88SX6081 8-port SATA II PCI-X Controller (rev 09)
ata10.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
ata10.00: cmd 61/08:00:3f:59:70/00:00:74:00:00/40 tag 0 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata10.00: status: { DRDY }
ata10: hard resetting link
ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata10.00: max_sectors limited to 256 for NCQ
ata10.00: max_sectors limited to 256 for NCQ
ata10.00: configured for UDMA/133
ata10: EH complete
sd 9:0:0:0: [sdg] 1953525168 512-byte hardware sectors (1000205 MB)
sd 9:0:0:0: [sdg] Write Protect is off
sd 9:0:0:0: [sdg] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata11.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
ata11.00: cmd 60/18:00:bf:61:58/00:00:35:00:00/40 tag 0 ncq 12288 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata11.00: status: { DRDY }
ata11: hard resetting link
ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata11.00: max_sectors limited to 256 for NCQ
ata11.00: max_sectors limited to 256 for NCQ
ata11.00: configured for UDMA/133
ata11: EH complete
sd 10:0:0:0: [sdh] 1953525168 512-byte hardware sectors (1000205 MB)
sd 10:0:0:0: [sdh] Write Protect is off
sd 10:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 10:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata9.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
ata9.00: cmd 61/08:00:3f:59:70/00:00:74:00:00/40 tag 0 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata9.00: status: { DRDY }
ata9: hard resetting link
ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata9.00: max_sectors limited to 256 for NCQ
ata9.00: max_sectors limited to 256 for NCQ
ata9.00: configured for UDMA/133
ata9: EH complete
sd 8:0:0:0: [sdf] 1953525168 512-byte hardware sectors (1000205 MB)
sd 8:0:0:0: [sdf] Write Protect is off
sd 8:0:0:0: [sdf] Mode Sense: 00 3a 00 00
sd 8:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
next reply other threads:[~2008-09-30 22:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 22:04 Christian [this message]
[not found] <3E6D0C24877245C3A5A327129A7B4CA7@909927SOSLA>
[not found] ` <alpine.DEB.1.10.0809220404400.18908@p34.internal.lan>
[not found] ` <5A4A9A3B0AAA4A20A33BC2D578F5F75F@909927SOSLA>
[not found] ` <alpine.DEB.1.10.0809220828490.23159@p34.internal.lan>
[not found] ` <5419A02543384E69AF2BA82FF6E66C14@909927SOSLA>
[not found] ` <alpine.DEB.1.10.0809220903400.23159@p34.internal.lan>
[not found] ` <4B1ABD0393EF40FFB0A12242FE8356AF@909927SOSLA>
2008-09-22 13:19 ` exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen Justin Piszcz
2008-09-22 13:26 ` Justin Piszcz
2008-09-23 18:14 ` Gwendal Grignou
2008-09-23 20:59 ` Brian Rademacher
2008-09-25 15:17 ` Bill Davidsen
2008-09-29 8:13 ` Tejun Heo
2008-09-30 20:47 ` Tom Mortensen
2008-09-30 21:18 ` Justin Piszcz
2008-10-01 3:50 ` Mr. James W. Laferriere
2008-10-01 8:06 ` Justin Piszcz
2008-10-01 11:12 ` Justin Piszcz
2008-10-04 2:27 ` Tejun Heo
2008-10-04 8:11 ` Justin Piszcz
2008-10-05 0:23 ` Justin Piszcz
2008-10-05 0:29 ` berk walker
2008-10-10 19:13 ` Justin Piszcz
2008-10-10 19:27 ` Alan Cox
2008-10-01 15:09 ` Bill Davidsen
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=20080930220415.GC5334@dhp.com \
--to=cjs@dhp.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox