> From: Eric Sproul
> Sent: Monday, December 09, 2013 2:20 PM
>
> needs more work".  Make sure you have
> driver/storage/[email protected],5.11-0.151006:20130906T160306Z which
> contains the fix.

Looks like I've just got 0.5.11-0.151006 right now, I installed from the
latest 151006 release media at the time, but I don't think I've updated
since, so I'm probably a little out of date on 151006 updates. I'll be
updating to 151008 shortly, so will pull it in that way.

> work to get that done, in https://www.illumos.org/issues/4018 and we
> have *that* stuff in r151008.

Cool, more to look forward to :). Where is the libtopo data exposed? Does it
end up in the fault management log, or can you dump it with prtconf -v? Hmm,
actually, looking at the fault management log, even with the current version
while the error logged via syslog did not include the wwn, the fault
management error log does, so I guess even in this version I would have had
enough information to figure it out:

Dec 09 2013 05:18:23.195493496 ereport.io.scsi.cmd.disk.tran
nvlist version: 0
        class = ereport.io.scsi.cmd.disk.tran
        ena = 0xee88d202d6401401
        detector = (embedded nvlist)
        nvlist version: 0
                version = 0x0
                scheme = dev
                device-path =
/pci@0,0/pci8086,3c0a@3,2/pci1000,30c0@0/iport@1/disk@w50014ee603347e67,0
        (end detector)

        devid = id1,sd@n50014ee603347e67
        driver-assessment = retry
        op-code = 0x28
        cdb = 0x28 0x0 0x2 0x1b 0xe 0x48 0x0 0x0 0xc0 0x0
        pkt-reason = 0x4
        pkt-state = 0x0
        pkt-stats = 0x10
        __ttl = 0x1
        __tod = 0x52a5c31f 0xba6fe78

Thanks much.



-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com

Reply via email to