From: Tejun Heo <htejun@gmail.com>
To: Kuan Luo <kluo@nvidia.com>
Cc: Jeff Garzik <jeff@garzik.org>, peer chen <peerchen@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide <linux-ide@vger.kernel.org>,
akpm <akpm@linux-foundation.org>,
Robert Hancock <hancockr@shaw.ca>
Subject: Re: [PATCH] sata_nv,adma: fix error when rmmod sata_nv
Date: Wed, 12 Dec 2007 17:18:19 +0900 [thread overview]
Message-ID: <475F994B.9090505@gmail.com> (raw)
In-Reply-To: <15F501D1A78BD343BE8F4D8DB854566B1BFE2AAB@hkemmail01.nvidia.com>
Kuan Luo wrote:
> hi,
> The below error happens when i rmmod sata_nv in adma mode on ck804
> chipset with 2.6.24 kernel.
> I traced the code and found that the driver attempts to write device mem
> that has been unmapped.
>
> Only simply removing the code" writew(0, mmio + NV_ADMA_CTL);" in the
> nv_adma_port_stop function or remove .port_stop field in nv_adma_ops,
> rmmod is ok.
>
> static void nv_adma_port_stop(struct ata_port *ap)
> {
> struct nv_adma_port_priv *pp = ap->private_data;
> void __iomem *mmio = pp->ctl_block;
>
> VPRINTK("ENTER\n");
> - writew(0, mmio + NV_ADMA_CTL);
> }
>
> Or
> Place pcim_iomap_regions before ata_pci_prepare_native_host in
> nv_init_one function.
> This can guarantee that the code "writew(0, mmio + NV_ADMA_CTL) " write
> device mem before the device mem is unmapped.
Which kernel version are you using? The following commit should have
fixed the problem. Please give a shot at 2.6.24-rc5. Thanks.
commit 32ebbc0c0d5d18c0135b55d1eb0029f48c54aff0
Author: Tejun Heo <htejun@gmail.com>
Date: Thu Nov 8 13:09:00 2007 +0900
libata: port and host should be stopped before hardware resources are
released
--
tejun
next prev parent reply other threads:[~2007-12-12 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 5:23 [PATCH] sata_nv,ahci: add the ahci legacy mode support to sata_nv Peer Chen
2007-09-25 7:08 ` Jeff Garzik
2007-09-25 7:52 ` Peer Chen
2007-09-25 8:13 ` Jeff Garzik
2007-09-25 9:08 ` Peer Chen
2007-10-12 21:17 ` Jeff Garzik
2007-10-16 8:08 ` peer chen
2007-10-19 2:56 ` Jeff Garzik
2007-10-19 6:58 ` peer chen
2007-10-19 7:25 ` Jeff Garzik
2007-10-22 1:55 ` peer chen
2007-11-10 4:04 ` Jeff Garzik
2007-11-10 5:00 ` Jeff Garzik
2007-11-10 19:00 ` Robert Hancock
2007-12-11 12:04 ` [PATCH] sata_nv,adma: fix error when rmmod sata_nv Kuan Luo
2007-12-12 8:18 ` Tejun Heo [this message]
2007-12-13 3:10 ` Kuan Luo
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=475F994B.9090505@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hancockr@shaw.ca \
--cc=jeff@garzik.org \
--cc=kluo@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peerchen@gmail.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.