From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: WARNING: at drivers/ata/libata-core.c:5988 ata_qc_issue()
Date: Thu, 24 Jan 2008 10:56:22 -0500 [thread overview]
Message-ID: <4798B526.4020709@rtr.ca> (raw)
In-Reply-To: <4798AE28.4000408@gmail.com>
Tejun Heo wrote:
> Mark Lord wrote:
>> Tejun,
>>
>> During testing with NCQ on sata_mv (patches coming shortly),
>> I found this gem in the syslog. This doesn't look like something
>> that a LLD could cause, but rather a race perhaps in libata-core.
>
> Hmmm... This isn't supposed to happen.
>
>> System is a 2.4GHz 32-bit Core2Quad, 2GB RAM (during this test),
>> running 2.6.24-rc6-git12 + newer sata_mv, with two sata_mv controller
>> cards, each with one NCQ drive performing heavy R/W activity.
>>
>> Other than that, I'm not sure what triggered this.
>
> Can you please tell me which version you were using? Or tell me which
> one of the three WARN_ON()'s in ata_qc_issue() was triggered? Thanks.
..
>> [ 289.892890] WARNING: at drivers/ata/libata-core.c:5988 ata_qc_issue()
..
The first one shown below, at drivers/ata/libata-core.c:5988:
> void ata_qc_issue(struct ata_queued_cmd *qc)
> {
> struct ata_port *ap = qc->ap;
> struct ata_link *link = qc->dev->link;
>
> /* Make sure only one non-NCQ command is outstanding. The
> * check is skipped for old EH because it reuses active qc to
> * request ATAPI sense.
> */
= WARN_ON(ap->ops->error_handler && ata_tag_valid(link->active_tag));
>
> if (qc->tf.protocol == ATA_PROT_NCQ) {
> WARN_ON(link->sactive & (1 << qc->tag));
>
..
next prev parent reply other threads:[~2008-01-24 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 15:20 WARNING: at drivers/ata/libata-core.c:5988 ata_qc_issue() Mark Lord
2008-01-24 15:26 ` Tejun Heo
2008-01-24 15:56 ` Mark Lord [this message]
2008-01-24 23:36 ` Tejun Heo
2008-01-24 23:52 ` Mark Lord
2008-01-24 23:57 ` Tejun Heo
2008-01-25 0:02 ` Mark Lord
2008-01-25 0:07 ` Tejun Heo
2008-01-25 4:01 ` Mark Lord
2008-01-25 4:08 ` Tejun Heo
2008-01-25 4:29 ` Mark Lord
2008-01-25 4:36 ` Tejun Heo
2008-01-25 7:20 ` Jeff Garzik
2008-01-25 7:18 ` Jeff Garzik
2008-01-25 15:01 ` James Bottomley
2008-01-25 15:18 ` Mark Lord
2008-01-25 15:29 ` James Bottomley
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=4798B526.4020709@rtr.ca \
--to=liml@rtr.ca \
--cc=htejun@gmail.com \
--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 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).