On Tue, Mar 28, 2017 at 05:41:49PM -0400, Tejun Heo wrote:
> > But as I said, I don't belive this is a problem in the SAS transport or the
> > SAS drivers, but a device core or transport class.
>
> So, what's most likely happening is that the parent device or kobject
> which contains the
Hello,
On Fri, Mar 24, 2017 at 05:53:54PM +0100, Johannes Thumshirn wrote:
> [ +Cc Tejun ]
>
> On Fri, Mar 24, 2017 at 11:44:55AM +, John Garry wrote:
> > To be clear, was this the same test with isci which you initially reported?
>
> Yes, just echo into the PCI device's sysfs remove file
[ +Cc Tejun ]
On Fri, Mar 24, 2017 at 11:44:55AM +, John Garry wrote:
> To be clear, was this the same test with isci which you initially reported?
Yes, just echo into the PCI device's sysfs remove file and it'll trigger the
problem.
I did some archeology and it seems as if commit bcdde7e
On Wed, May 20, 2015 at 07:00:53PM -0400, Dan Williams wrote:
> Praveen reports:
>
> After some debugging this is what I have found
>
> sas_phye_loss_of_signal gets triggered on phy_event from mvsas
> sas_phye_loss_of_signal calls sas_deform_port
> sas_deform_port
On Wed, May 20, 2015 at 07:00:53PM -0400, Dan Williams wrote:
Praveen reports:
After some debugging this is what I have found
sas_phye_loss_of_signal gets triggered on phy_event from mvsas
sas_phye_loss_of_signal calls sas_deform_port
sas_deform_port posts a
Praveen reports:
After some debugging this is what I have found
sas_phye_loss_of_signal gets triggered on phy_event from mvsas
sas_phye_loss_of_signal calls sas_deform_port
sas_deform_port posts a DISCE_DESTRUCT event
(sas_unregister_domain_devices-
6 matches
Mail list logo
