Pak Budi, Regarding the network interface error: What kind of WP51 is this? WP51A, B and C have le0 as on-board ethernet interface. WP51D and E have hme0 as on-board ethernet. WP51F has eri0 as on-board ethernet and hme0 as 2nd ethernet. On a 51D or 51E box it is common to have le0 errors as one or more of Foxboro's QFs have incorrectly caused le0 to be configured 51D/E workstations. If this is the case, the le0 error can be safely ignored. Regarding the panic: Was this a one-off fault or does this occur regularly? A panic from a recursive mutex_enter error means that something requested a locked object (mutex) that it was already using. Mutexes are not re-entrant by the same thread. If you already own the mutex, you cannot own it again. This is likely a software, driver or kernel problem. If you still have the crash files, consider asking Foxboro to do a panic and stack trace to see what software caused the fault. Regards, Kevin FitzGerrell On 7/13/07, budi t jatmiko <budi.tjatmiko@xxxxxxxxx> wrote: > I had similar problem, while rebooting WP51 message showed up : > Configuring network interfaces: hme0 hme1ifconfig: plum: le0: no such > interface > > Panic [cpu0]/thread=0x30023ec0: recursive mutex_enter: mutex 6003da20 caller > 10081d40 > Syncing file system.... > Fast Data Acces MMU Miss > Ok > > And the system back to reboot again > I read from sun solaris error message, le0 is a network card onboard > (motherboard?) > Until now we still trying to fix it but not solved. > What do you think about this problem? > > Regards, > Budi TJ > PERTAMINA's Dumai Refinery > Indonesia > > _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave