COMWAKE states

[Elliott, Robert (Server Storage)]

* From the T10 Reflector (t10 at t10.org), posted by:
* "Elliott, Robert (Server Storage)" <Elliott at hp.com>
*
In SATA, the host phy state machine would jump to HP2B:HR_AwaitNoCOMINIT
|from any of those states.  In SAS, jumping to SP4:OOB_COMSAS would be
the equivalent and should be added to SAS-1.1.  For 1.0 we can claim the
Management Reset signal kicks in after a vendor-specific timeout sending
it back to SP0:OOB_COMINIT to try again.

--
Rob Elliott, elliott at hp.com
Hewlett-Packard Industry Standard Server Storage Advanced Technology
https://ecardfile.com/id/RobElliott




> -----Original Message-----
> From: Sheffield, Robert L [mailto:robert.l.sheffield at intel.com] 
> Sent: Monday, June 02, 2003 5:40 PM
> To: t10 at t10.org
> Subject: SP: COMWAKE states
> 
> 
> * From the T10 Reflector (t10 at t10.org), posted by:
> * "Sheffield, Robert L" <robert.l.sheffield at intel.com>
> *
> I have a question about what happens in the SP state machine 
> if the SP enters the COMWAKE part of SATA link initialization 
> (SP16, SP17, SP18), and the attached device, instead of 
> responding to COMWAKE with it's own COMWAKE, for one reason 
> or another reverts to sending COMINIT. It doesn't appear that 
> any of these states are monitoring COMINIT, and if COMWAKE is 
> not received, there doesn't appear to be a transition out of 
> these states. Is it possible to get hung in one of these 
> states if the attached SATA device reverts to COMINIT at the 
> wrong time?
> 
> 
> Bob Sheffield
> Intel Corporation - CH6-333
> Storage Components Division (SCD)
> 5000 W. Chandler Blvd
> Chandler, AZ 85226-3699
> Phone: 480-554-8597
> Fax: 480-554-6617
> 
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org
> 
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org