Strange messages from ses(4)

[Alan Somers]

On Thu, Jan 23, 2014 at 5:50 AM, Dmitry Sivachenko <trtrmitya at gmail.com> wrote:
> Hello!
>
> I have a machine running stable/10 and  mfi1: <Dell PERC H800 Adapter> controller with two disk bundles connected to it
> (15 disks each).
>
> From time to time the following messages appear:
>
> Jan 23 07:19:19 agata kernel: ses0: pass1: Element descriptor: '000'
> Jan 23 07:19:19 agata kernel: ses0: pass1: SAS Device Slot Element: 1 Phys at Slot 0, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f48
> Jan 23 07:19:19 agata kernel: ses0: pass2: Element descriptor: '001'
> Jan 23 07:19:19 agata kernel: ses0: pass2: SAS Device Slot Element: 1 Phys at Slot 1, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f49
> Jan 23 07:19:19 agata kernel: ses0: pass3: Element descriptor: '002'
> Jan 23 07:19:19 agata kernel: ses0: pass3: SAS Device Slot Element: 1 Phys at Slot 2, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f4a
> Jan 23 07:19:19 agata kernel: ses0: pass4: Element descriptor: '003'
> Jan 23 07:19:19 agata kernel: ses0: pass4: SAS Device Slot Element: 1 Phys at Slot 3, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f4b
> Jan 23 07:19:19 agata kernel: ses0: pass5: Element descriptor: '004'
> Jan 23 07:19:19 agata kernel: ses0: pass5: SAS Device Slot Element: 1 Phys at Slot 4, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f4c
> Jan 23 07:19:19 agata kernel: ses0: pass6: Element descriptor: '005'
> Jan 23 07:19:19 agata kernel: ses0: pass6: SAS Device Slot Element: 1 Phys at Slot 5, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f4d
> Jan 23 07:19:19 agata kernel: ses0: pass7: Element descriptor: '006'
> Jan 23 07:19:19 agata kernel: ses0: pass7: SAS Device Slot Element: 1 Phys at Slot 6, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f4e
> Jan 23 07:19:19 agata kernel: ses0: pass8: Element descriptor: '007'
> Jan 23 07:19:19 agata kernel: ses0: pass8: SAS Device Slot Element: 1 Phys at Slot 7, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f4f
> Jan 23 07:19:19 agata kernel: ses0: pass9: Element descriptor: '008'
> Jan 23 07:19:19 agata kernel: ses0: pass9: SAS Device Slot Element: 1 Phys at Slot 8, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f50
> Jan 23 07:19:19 agata kernel: ses0: pass10: Element descriptor: '009'
> Jan 23 07:19:19 agata kernel: ses0: pass10: SAS Device Slot Element: 1 Phys at Slot 9, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f51
> Jan 23 07:19:19 agata kernel: ses0: pass11: Element descriptor: '010'
> Jan 23 07:19:19 agata kernel: ses0: pass11: SAS Device Slot Element: 1 Phys at Slot 10, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f52
> Jan 23 07:19:19 agata kernel: ses0: pass12: Element descriptor: '011'
> Jan 23 07:19:19 agata kernel: ses0: pass12: SAS Device Slot Element: 1 Phys at Slot 11, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f53
> Jan 23 07:19:19 agata kernel: ses0: pass14: Element descriptor: '012'
> Jan 23 07:19:19 agata kernel: ses0: pass14: SAS Device Slot Element: 1 Phys at Slot 12, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f54
> Jan 23 07:19:19 agata kernel: ses0: pass13: Element descriptor: '013'
> Jan 23 07:19:19 agata kernel: ses0: pass13: SAS Device Slot Element: 1 Phys at Slot 13, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f55
> Jan 23 07:19:19 agata kernel: ses0: pass15: Element descriptor: '014'
> Jan 23 07:19:19 agata kernel: ses0: pass15: SAS Device Slot Element: 1 Phys at Slot 14, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f56
> Jan 23 07:19:19 agata kernel: ses0: pass16: Element descriptor: '015'
> Jan 23 07:19:19 agata kernel: ses0: pass16: SAS Device Slot Element: 1 Phys at Slot 15, Not All Phys
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: SATA device
> Jan 23 07:19:19 agata kernel: ses0:  phy 0: parent 5003048000366f7f addr 5003048000366f57
>
>
> What does it mean?

The ses(4) driver prints that message whenever it sees the "NOT ALL
PHYS" bit in the SAS protocol specific descriptor in the Additional
Element Status page.  According to the SES-3 spec, revision 6:

The NUMBER OF PHY DESCRIPTORS field indicates how many phy descriptors
are in the phy descriptor list.
A NOT ALL PHYS bit set to one indicates that all phys in the SAS
device or SATA device may or may not be
described. A NOT ALL PHYS bit set to zero indicates that all phys in
the SAS device or SATA device are
described.
NOTE 6 - The NOT ALL PHYS bit may be set to one for SAS devices with
multiple ports, where the enclosure
services process only has access to information about the phys in one
of the ports (e.g., in the same SAS
domain as the enclosure services process

It sounds pretty trivial.  I would pay it no mind.  BTW, a good tool
to help debug issues like this is "sg_ses" from the sg3_utils port.

-Alan

>
> Thanks in advance.
> _______________________________________________
> freebsd-scsi at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe at freebsd.org"