From: Mark Lord <liml@rtr.ca>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Linux IDE <linux-ide@vger.kernel.org>, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: sata_mv BUG: at drivers/ata/sata_mv.c:1236 mv_qc_issue()
Date: Wed, 23 May 2007 09:24:54 -0400 [thread overview]
Message-ID: <465440A6.5080904@rtr.ca> (raw)
In-Reply-To: <46540376.6000700@wpkg.org>
Tomasz Chmielewski wrote:
..
> The error I mentioned before - BUG: at drivers/ata/sata_mv.c:1236
> mv_qc_issue() - happened on /dev/sda drive.
>
> As it appears, my /dev/sdb drive just dies (has multiple badblocks). It
> causes similar errors when I tried to dd if=/dev/ero of=/dev/sdb.
>
> It triggered two bugs:
>
> BUG: at drivers/ata/sata_mv.c:657 mv_start_dma()
Heh.. that one is just the driver being way too clever for itself.
This fix (below) should take care of it.
> BUG: at drivers/ata/sata_mv.c:1201 mv_qc_issue()
That one should be harmless, and is likely a side-effect of
not completely resetting the engine & variables after an error.
This whole driver needs a lot of TLC, something I just might
be into doing shortly. Meanwhile:
This patch removes some unhelpful paranoia from sata_mv.c,
now choosing to actually *recover* rather than simply complain.
Signed-off-by: Mark Lord <mlord@pobox.com>
---
--- linux/drivers/ata/sata_mv.c.orig 2007-04-26 12:02:46.000000000 -0400
+++ linux/drivers/ata/sata_mv.c 2007-05-23 09:18:42.000000000 -0400
@@ -650,11 +650,8 @@
*/
static void mv_start_dma(void __iomem *base, struct mv_port_priv *pp)
{
- if (!(MV_PP_FLAG_EDMA_EN & pp->pp_flags)) {
- writelfl(EDMA_EN, base + EDMA_CMD_OFS);
- pp->pp_flags |= MV_PP_FLAG_EDMA_EN;
- }
- WARN_ON(!(EDMA_EN & readl(base + EDMA_CMD_OFS)));
+ writelfl(EDMA_EN, base + EDMA_CMD_OFS);
+ pp->pp_flags |= MV_PP_FLAG_EDMA_EN;
}
/**
prev parent reply other threads:[~2007-05-23 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 10:20 sata_mv BUG: at drivers/ata/sata_mv.c:1236 mv_qc_issue() Tomasz Chmielewski
2007-05-23 9:03 ` Tomasz Chmielewski
2007-05-23 13:24 ` Mark Lord [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=465440A6.5080904@rtr.ca \
--to=liml@rtr.ca \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=mangoo@wpkg.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).