Hi Mark, I am encountering an e1000g error on Nevada snv_87. I am not sure whether it is the same as you stated.
The fault message is: SUNW-MSG-ID: PCIEX-8000-0A, TYPE: Fault, VER: 1, SEVERITY: Critical EVENT-TIME: Wed Jun 4 20:09:18 CST 2008 PLATFORM: To Be Filled By O.E.M., CSN: To Be Filled By O.E.M., HOSTNAME: solaris SOURCE: eft, REV: 1.16 EVENT-ID: 61eb4b03-9def-635d-ba3d-ef5ac0401db8 DESC: A problem was detected for a PCIEX device. Refer to http://sun.com/msg/PCIEX-8000-0A for more information. AUTO-RESPONSE: One or more device instances may be disabled IMPACT: Loss of services provided by the device instances associated with this fault REC-ACTION: Schedule a repair procedure to replace the affected device. Use fmdump -v -u <EVENT_ID> to identify the device or contact Sun for support. SUNW-MSG-ID: PCIEX-8000-0A, TYPE: Fault, VER: 1, SEVERITY: Critical EVENT-TIME: Wed Jun 4 20:10:17 CST 2008 PLATFORM: To Be Filled By O.E.M., CSN: To Be Filled By O.E.M., HOSTNAME: solaris SOURCE: eft, REV: 1.16 EVENT-ID: b75b3279-ec5e-6c1a-8cec-f679bc4dc4f0 DESC: A problem was detected for a PCIEX device. Refer to http://sun.com/msg/PCIEX-8000-0A for more information. AUTO-RESPONSE: One or more device instances may be disabled IMPACT: Loss of services provided by the device instances associated with this fault REC-ACTION: Schedule a repair procedure to replace the affected device. Use fmdump -v -u <EVENT_ID> to identify the device or contact Sun for support. On Fri, Jun 6, 2008 at 1:24 AM, James Carlson <[EMAIL PROTECTED]> wrote: > Mark Kaiman writes: >> I would be happy to submit bug reports as Calum suggested above. I'm not one >> of those people who just want to complain - I'd like to help Sun improve the >> product so I can actually use it. Is there a URL for bug reports? > > For the OpenSolaris distribution itself, use bugzilla: > > http://defect.opensolaris.org/ > > For things in SXCE, use the bugster database interface: > > http://bugs.opensolaris.org/ > >> If you can suggest anything that would get wireless or wired networking to >> work beyond what I've already tried, I'll give it a go. I am actually >> looking for a Solaris consultant in my town. I will pay some money to >> someone with expertise who might be able to help. I am a total newb but I've >> learned a bit about Solaris already. Its a nice contrast to OS X, where >> terminal commands are not necessary. > > I'm surprised that your e1000g driver doesn't work. If nothing else, > a simple interface like that ought to function. > > One known problem with e1000g is that the new FMA support can cause it > to erroneously report itself as faulty, resulting in failures. If > "fmadm faulty" shows a "Critical" error, then this problem has hit > you. The workaround is to plumb the interface with the undocumented > DLPI_DEVONLY environment variable set. > > -- > James Carlson, Solaris Networking <[EMAIL PROTECTED]> > Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 > _______________________________________________ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
