Re: [foxboro] FW: FW: AW51D Problem
- From: "budi t jatmiko" <budi.tjatmiko@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Fri, 13 Jul 2007 07:26:55 +0700
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
On 7/13/07, Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx> wrote:
>
> MMU is a chip on the motherboard, however Sun says that most MMU
> problems are not motherboard related. Are you getting this error
> while booting from HD or from CD?
>
> Is this workstation exactly as originally shipped from Foxboro or have
> any components been changed?
>
> Is there anything that led up to this fault? Like changing the HD
> from another workstation to this one? Is this a fresh install or a
> workstation that has been in service for a while?
>
> Consider re-seating memory modules and PCI cards.
>
> When you do a probe from the OK prompt do you see any data access errors?
>
> Regards,
>
> Kevin FitzGerrell
>
> On 7/12/07, Kashif Ijaz <kashifijaz93@xxxxxxxxxxx> wrote:
> > One message that is recently starting coming is "Fast Data access MMU
> Miss".
> > It is not coming up and dies while rebooting.
> >
> > If anyone has any idea about it!!!
> >
> > Regards,
> >
> > Kashif Ijaz
> >
>
>
_______________________________________________________________________
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
Other related posts:
