On Sun, Apr 02, 2006 at 11:59:45AM -0600, Eric D. Mudama wrote:
> On 4/2/06, Dan Aloni <[email protected]> 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
[email protected], [email protected], [email protected], [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
