All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Alexis Bruemmer <alexisb@us.ibm.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	"Tarte, Robert" <Robert_Tarte@adaptec.com>
Subject: Re: [PATCH] aic94xx: attaching to the sas transport class
Date: Sun, 19 Mar 2006 21:53:45 -0800	[thread overview]
Message-ID: <20060320055345.GA30532@us.ibm.com> (raw)
In-Reply-To: <1142695445.3241.4.camel@mulgrave.il.steeleye.com>

James Bottomley <James.Bottomley@SteelEye.com> wrote:
> On Fri, 2006-03-17 at 17:45 -0800, Alexis Bruemmer wrote:
> > -       sas_begin_event(DISCE_PORT_GONE, &port->disc.disc_event_lock,
> > -                       &port->disc.pending);
> > -
> 
> I'm afraid we can't really do this ... what it's actually doing is
> removing anything that would tamper with the infinite lifetimes (like
> port removal events).  What we have to do is go the other way and make
> all the object lifetimes consistent.

Well the reason this was removed was because we where running two cleanup
operations.

We are trying to make object lifetimes consistent. I was trying to
make the following call stack work. In taking a look I guess we altered
the functionality of sas_deform_port. I assume the comment above "all the
object lifetimes consistent" is trying to get these two cases to function.

pci_unregister_driver
	asd_pci_remove
		asd_unregister_sas_ha
			sas_unregister_ha
				sas_unregister_devices
					sas_unregister_domain_devices
						sas_unregister_dev
							sas_rphy_delete
				sas_unregister_ports
				sas_unregister_scsi_host
					sas_remove_host
						do_sas_phy_delete


Currently I only have debug output for "modprobe -r aic94xx" shown below.

[1009084.596267] sas_transport_init Entered
[1009084.639153] sas_attach_transport Entered
[1009086.362102] sas_phy_add Entered phy: c0000000f3c3c1d8
[1009086.370237] sas_phy_add Entered phy: c0000000f3c3c5f0
[1009086.372232] sas_phy_add Entered phy: c0000000f3c3ca08
[1009086.376454] sas_phy_add Entered phy: c0000000ef2bd9e8
[1009086.384611] sas_phy_add Entered phy: c0000000ef2bd5d0
[1009086.388846] sas_phy_add Entered phy: c0000000ef2bcda0
[1009086.393304] sas_phy_add Entered phy: c0000000ef2bc988
[1009086.396303] sas_phy_add Entered phy: c0000000f035f338
[1009086.401681] sas_rphy_add Entered rphy: c0000000f035e2d8
[1009086.423209] sas_rphy_add Entered rphy: c0000000efc65ae8
[1009095.405030] sas_rphy_delete Entered rphy: c0000000f035e2d8
[1009095.445964] sas_rphy_delete Entered rphy: c0000000efc65ae8
[1009095.494683] sas_remove_host Entered shost: c00000000f50a548
[1009095.494701] do_sas_phy_delete Entered phy: c0000000f3c3c1d8
[1009095.494715] sas_phy_delete Entered phy: c0000000f3c3c1d8
[1009095.501915] do_sas_phy_delete Entered phy: c0000000f3c3c5f0
[1009095.501931] sas_phy_delete Entered phy: c0000000f3c3c5f0
[1009095.503865] do_sas_phy_delete Entered phy: c0000000f3c3ca08
[1009095.503882] sas_phy_delete Entered phy: c0000000f3c3ca08
[1009095.507957] do_sas_phy_delete Entered phy: c0000000ef2bd9e8
[1009095.507973] sas_phy_delete Entered phy: c0000000ef2bd9e8
[1009095.515346] do_sas_phy_delete Entered phy: c0000000ef2bd5d0
[1009095.515365] sas_phy_delete Entered phy: c0000000ef2bd5d0
[1009095.521260] do_sas_phy_delete Entered phy: c0000000ef2bcda0
[1009095.521272] sas_phy_delete Entered phy: c0000000ef2bcda0
[1009095.536930] do_sas_phy_delete Entered phy: c0000000ef2bc988
[1009095.536946] sas_phy_delete Entered phy: c0000000ef2bc988
[1009095.542064] do_sas_phy_delete Entered phy: c0000000f035f338
[1009095.542078] sas_phy_delete Entered phy: c0000000f035f338
[1009095.599971] sas_release_transport Entered
[1009095.607762] sas_transport_exit Entered

-andmike
--
Michael Anderson
andmike@us.ibm.com

      reply	other threads:[~2006-03-20  5:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 22:38 [RFC] aic94xx: attaching to the sas transport class James Bottomley
2006-03-02 23:13 ` Mike Anderson
2006-03-03  2:16   ` Mark Rustad
2006-03-03  4:04     ` Randy.Dunlap
2006-03-03 16:51       ` Mark Rustad
2006-03-03 15:51     ` Stefan Richter
2006-03-03 18:24       ` Luben Tuikov
2006-03-03  4:34   ` James Bottomley
2006-03-04  1:47     ` Alexis Bruemmer
2006-03-03 10:26   ` Luben Tuikov
2006-03-03 16:12     ` Stefan Richter
2006-03-03 18:26       ` Luben Tuikov
2006-03-03 10:14 ` Luben Tuikov
2006-03-03 15:23   ` James Bottomley
2006-03-03 15:58     ` Stefan Richter
2006-03-03 16:26       ` James Bottomley
2006-03-03 17:03         ` Mike Anderson
2006-03-03 17:28           ` Jeff Garzik
2006-03-06 18:30       ` Douglas Gilbert
2006-03-03 18:20     ` Luben Tuikov
2006-03-06  8:26 ` Mike Anderson
2006-03-06 15:13   ` James Bottomley
2006-03-06 16:37     ` Jeff Garzik
2006-03-18  1:45 ` [PATCH] " Alexis Bruemmer
2006-03-18  2:05   ` Alexis Bruemmer
2006-03-18 15:24   ` James Bottomley
2006-03-20  5:53     ` Mike Anderson [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=20060320055345.GA30532@us.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=Robert_Tarte@adaptec.com \
    --cc=alexisb@us.ibm.com \
    --cc=linux-scsi@vger.kernel.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 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.