From: Dan Aloni <da-x@monatomic.org>
To: "Eric D. Mudama" <edmudama@gmail.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>, Mark Lord <lkml@rtr.ca>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: sata_mv: module reloading doesn't work
Date: Tue, 4 Apr 2006 00:57:29 +0300 [thread overview]
Message-ID: <20060403215729.GA17731@localdomain> (raw)
In-Reply-To: <311601c90604021059jcdf56e4ja35e3507ab291179@mail.gmail.com>
On Sun, Apr 02, 2006 at 11:59:45AM -0600, Eric D. Mudama wrote:
> On 4/2/06, Dan Aloni <da-x@monatomic.org> wrote:
> > Hello,
> >
> > I'm testing the sata_mv driver to see whether reloading (rmmod
> > - insmod) works, and it seems something is broken there. The
> > first insmod goes okay - however all the insmods that follow
> > emit error=0x01 { AddrMarkNotFound } and status=0x50 { DriveReady
> > SeekComplete } from all the drives.
>
> More to Jeff/Mark etc... wouldn't this be expected? 0x50/0x01 is the
> contents of a reset signature FIS. If the module was removed, and
> upon insmod the bus came back up, the drive would complete ASR or
> COMRESET processing and post a signature FIS. Is the phy disabled
> when sata_mv is removed?
Okay, finally got to test sata_mv with kexec, perhaps this can shed
some light on the matter.
* Normal boot
* insmod sata_mv
* all is okay, as expected
* Did kexec
* insmod sata_mv
* all is okay!
Good! It means that sata_mv doesn't mess things on its initialization
sequence.
* Normal boot
* insmod sata_mv
* all is okay, as expected
* rmmod sata_mv
* insmod sata_mv
* all is bad, as expected
* kexec
* insmod sata_mv
* all is bad!
Conclusion: sata_mv's shutdown does something bad.
--
Dan Aloni, Linux specialist
XIV LTD, http://www.xivstorage.com
da-x@monatomic.org, da-x@colinux.org, da-x@gmx.net, dan@xiv.co.il
next prev parent reply other threads:[~2006-04-03 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 15:56 sata_mv: module reloading doesn't work Dan Aloni
2006-04-02 16:05 ` Mark Lord
2006-04-02 16:14 ` Dan Aloni
2006-04-02 16:21 ` Mark Lord
2006-04-02 19:05 ` Dan Aloni
2006-04-02 17:59 ` Eric D. Mudama
2006-04-02 22:44 ` Dan Aloni
2006-04-03 21:57 ` Dan Aloni [this message]
2006-04-04 2:47 ` Mark Lord
2006-04-04 5:24 ` Dan Aloni
2006-04-04 6:08 ` Dan Aloni
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=20060403215729.GA17731@localdomain \
--to=da-x@monatomic.org \
--cc=edmudama@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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).