From: Robert Hancock <hancockr@shaw.ca>
To: Neil Schemenauer <nas@arctrix.com>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, Allen Martin <AMartin@nvidia.com>,
B.Steinbrink@gmx.de
Subject: Re: sata_nv ADMA controller lockup investigation
Date: Tue, 20 Mar 2007 17:24:00 -0600 [thread overview]
Message-ID: <46006D10.2010205@shaw.ca> (raw)
In-Reply-To: <20070320220132.GA10984@python.ca>
Neil Schemenauer wrote:
> Not sure if this helps. I'm getting this reset with 2.6.21-rc4.
> After the reset the controller seems to work again.
>
...
> ata2.00: ATA-7: Maxtor 6V300F0, VA111630, max UDMA/133
> ata2.00: 586114704 sectors, multi 16: LBA48 NCQ (depth 31/32)
...
> ata2: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x0 next cpb idx 0x0
> ata2: CPB 1: ctl_flags 0x1f, resp_flags 0x2
> ata2: timeout waiting for ADMA IDLE, stat=0x400
> ata2: timeout waiting for ADMA LEGACY, stat=0x400
> ata2.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x2 frozen
> ata2.00: cmd 61/00:08:72:44:22/02:00:21:00:00/40 tag 1 cdb 0x0 data 262144 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: configured for UDMA/133
> ata2: EH complete
> SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
That one looks like a drive-side issue. CPB resp_flags 2 indicates the
drive accepted the command and the controller is still waiting for a
response.
Could be that this is another drive that needs to be added to the NCQ
blacklist, some similar Maxtor models seem to have issues..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
prev parent reply other threads:[~2007-03-20 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 4:30 sata_nv ADMA controller lockup investigation Robert Hancock
2007-02-15 10:46 ` Jeff Garzik
2007-02-16 4:52 ` Robert Hancock
2007-03-20 22:01 ` Neil Schemenauer
2007-03-20 23:24 ` Robert Hancock [this message]
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=46006D10.2010205@shaw.ca \
--to=hancockr@shaw.ca \
--cc=AMartin@nvidia.com \
--cc=B.Steinbrink@gmx.de \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nas@arctrix.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;
as well as URLs for NNTP newsgroup(s).