From: Mark Lord <liml@rtr.ca>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-ide@vger.kernel.org, nico@cam.org, buytenh@wantstofly.org
Subject: Re: sata_mv on Orion: mv_err_intr when shutting down
Date: Fri, 13 Jun 2008 08:42:44 -0400 [thread overview]
Message-ID: <48526B44.4060600@rtr.ca> (raw)
In-Reply-To: <20080612181851.GA19874@deprecation.cyrius.com>
Martin Michlmayr wrote:
> * Martin Michlmayr <tbm@cyrius.com> [2008-05-12 21:15]:
>> * Martin Michlmayr <tbm@cyrius.com> [2008-05-12 17:46]:
>>>> The code that triggers this was fixed up more after -rc1, so if you can
>>>> still get messages like that with, say -rc2 or later, then please post them.
>>> Cool. I'll let you know in case the message doesn't go away with rc2.
>> I still get the same message with rc2.
>
> Just saw it again with 2.6.26-rc6:
>
> [42949509.440000] Power down.
> [42949509.440000] qnap_ts209_power_off: triggering power-off...
> [42949509.460000] ata1: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen
> [42949509.460000] ata1: edma_err_cause=02000020 pp_f
..
Mmm.. I don't know how this can happen, even if it does happen.
Unless perhaps the plaform code doesn't do a (driver).remove() call,
which is where we disable the interrupt you see above.
This *is* a "platform" (non-PCI) device, right?
That being the case, can you stick a printk() into mv_platform_remove()
so we can see whether or not it gets called before "power down" ?
Something like this:
--- old/drivers/ata/sata_mv.c 2008-05-30 19:36:52.000000000 -0400
+++ linux/drivers/ata/sata_mv.c 2008-06-13 08:42:02.000000000 -0400
@@ -3186,6 +3186,7 @@
struct mv_host_priv *hpriv;
struct resource *res;
int n_ports, rc;
+ printk(KERN_INFO "%s(%p)\n", __func__, pdev);
if (!printed_version++)
dev_printk(KERN_INFO, &pdev->dev, "version " DRV_VERSION "\n");
@@ -3258,7 +3259,9 @@
struct device *dev = &pdev->dev;
struct ata_host *host = dev_get_drvdata(dev);
+ printk(KERN_INFO "%s(%p) enter\n", __func__, pdev);
ata_host_detach(host);
+ printk(KERN_INFO "%s(%p) exit\n", __func__, pdev);
return 0;
}
next prev parent reply other threads:[~2008-06-13 12:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 13:26 sata_mv on Orion: mv_err_intr when shutting down Martin Michlmayr
2008-05-12 15:39 ` Mark Lord
2008-05-12 15:46 ` Martin Michlmayr
2008-05-12 19:15 ` Martin Michlmayr
2008-06-12 18:18 ` Martin Michlmayr
2008-06-13 12:42 ` Mark Lord [this message]
2008-06-13 16:12 ` Frans Pop
2008-06-13 16:56 ` Mark Lord
2008-06-13 17:10 ` Frans Pop
2008-06-13 19:01 ` Nicolas Pitre
2008-06-13 19:20 ` Mark Lord
2008-06-13 19:31 ` Nicolas Pitre
2008-06-15 2:18 ` Tejun Heo
2008-06-15 9:41 ` Frans Pop
2008-06-15 10:54 ` Byron Bradley
2008-06-15 13:44 ` Mark Lord
2008-06-22 14:37 ` Martin Michlmayr
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=48526B44.4060600@rtr.ca \
--to=liml@rtr.ca \
--cc=buytenh@wantstofly.org \
--cc=linux-ide@vger.kernel.org \
--cc=nico@cam.org \
--cc=tbm@cyrius.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 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.