Sunay Tripathi wrote: > Darren, > > Is this the same system where you earlier had the snoop/vnic issue?
It is indeed. > Seems like there is something strange with this system. Any chance > you can give access to the system itself rather than just core dump? That's going to be ... difficult this week. Next week will be easier. Darren > > Thanks, > Sunay > > Darren Reed wrote: >> I give you... >> >> # dladm show-link >> LINK CLASS MTU STATE OVER >> e1000g0 phys 1500 up -- >> # dladm create-vnic -l e1000g0 vnic0 >> dladm: vnic creation over e1000g0 failed: object already exists >> # ifconfig vnic0 plumb >> ifconifg: cannot open link "vnic0": DLPI link does not exist >> >> I've opened CR#6798106 for this... >> >> Now while booting, there were messages on the console about >> e1000g1 and e1000g2 failing to plumb (I'd reconfigured those >> NICs out.) The error messages were about DL_ATTACH_REQ, etc, >> failing. Those error messages aren't are recorded in /var/adm/messages >> nor dmesg output :-( Seems like 4116990...although I'd call >> that a bug, not an RFE...so CR#6798099. >> >> So what led to this... >> >> I was running with e1000g0,1,2 and then halted the vm. >> Removed all three NICs, then added back in a new e1000g0. >> Booted... >> >> I don't know how it got into this state with vnic0... >> >> And it is reproducible over a reboot :-D >> I'll upload a crash dump if someone wants to look at the >> various kernel structures and find my vnic0 :) >> >> btw, when we get this error: >> e1000g1: DL_ATTACH_REQ failed: DL_SYSERR (errno 22) >> >> Why isn't it enacted upon? >> Why are we doing a DL_BIND_REQ and more if the attach fails? >> >> e1000g1: DL_BIND_REQ failed: DL_OUTSTATE >> e1000g1: DL_PHYS_ADDR_REQ failed: DL_OUTSTATE >> e1000g1: DL_UNBIND_REQ failed: DL_OUTSTATE >> >> Darren >> >> _______________________________________________ >> crossbow-discuss mailing list >> crossbow-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss > >
