Re: STANDBY IMMEDIATE failed on NVIDIA MCP5x controllers when system suspend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello again,

On Tue, 2013-03-12 at 10:34 +0800, Aaron Lu wrote:
> The device that is responsible for PM operations for the disk is named
> something like sd X:0:0:0, where X is the host number, and is normally
> attached under the ata port number+1. So sd 2:0:0:0 is attached to ata
> port 3(if there are USB disks, things may change). And the ata port
> device is reponsible for ata port level PM operations like power off
> the
> port etc., and its device is named as atax, where x is its port
> number.
> So you can see from the log, only after sd 4:0:0:0 and sd 2:0:0:0
> failed
> in their ->suspend function, ata5 and ata3's suspend functions start
> to
> run, and then sata_nv 0000:00:05.1 starts to run.

Yes, but 1 thing completes before disks are suspended:

[ 7378.237631] sata_nv 0000:00:05.2: __device_suspend: starts
[ 7378.249333] sata_nv 0000:00:05.2: __device_suspend: done

And then sd 2:0:0:0 starts to suspend.

This might be correct seen from a dependency point of view. But what if
the HW designer was a bit lazy (or saved a bit of logic), and performs
some sort of shutdown when the first function (0000:00:05.2) is
suspended? That would require all disks attached to be dependent on all
functions.

If it is the case (which would not surprise me), is it possible to
describe such dependencies in the PM?

Thanks,

/pedro

--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux