Sponsored Content
Full Discussion: Fast Data Access MMU Miss
Operating Systems Solaris Fast Data Access MMU Miss Post 302312672 by TonyFullerMalv on Saturday 2nd of May 2009 03:33:11 PM
Old 05-02-2009
The following:
Installation - Fast Data Access MMU Miss error at the {ok} prompt
seems to imply a memory or other hardware fault although I have seen this and concluded it was caused by corrupted data either over the network (tftp boot stage).

Is your boot-device set to the correct hard disk device in the OBP?
What result do you get when you run probe-scsi-all from the OBP and is the disk you get listed the same device that the devalias for disk is set to?
 

6 More Discussions You Might Find Interesting

1. Linux

MMU exception

I hope to post in the right forum, otherwise I apologize for this. if a MMU exception is caused by a process which tries to access to other memory segment (out of its own address space) what the kernel does in this case ? maybe kernel kills the "bad" process ? (2 Replies)
Discussion started by: Puntino
2 Replies

2. Programming

Read/Write a fairly large amount of data to a file as fast as possible

Hi, I'm trying to figure out the best solution to the following problem, and I'm not yet that much experienced like you. :-) Basically I have to read a fairly large file, composed of "messages" , in order to display all of them through an user interface (made with QT). The messages that... (3 Replies)
Discussion started by: emitrax
3 Replies

3. Ubuntu

fast data access mmu miss

hello, before i have install solaris 9, is good. I would like to install Ubuntu 10.04 on a Sun Blade 150 blade. I create cdrom iso burning with a 10x was open I made a boot ok: boot cdrom I get the following error: fast data access mmu miss i do probe-ide all reset-all always ... (2 Replies)
Discussion started by: philo_71
2 Replies

4. Shell Programming and Scripting

Do i miss counter or what

hello this script should show all users and space they used without problem : ls /home >> /root/users.txt cat /root/users.txt | while read line; do space=`du -s /home/$line` echo "$line space is $space" shift done but when i remove pipe ,script run without any output: ls /home... (4 Replies)
Discussion started by: nimafire
4 Replies

5. Solaris

Check kernel SHM_SHARE MMU

hiii, how can view the value of SHM_SHARE MMU on solaris 10? tnx or the answer (0 Replies)
Discussion started by: pietro1984
0 Replies

6. Solaris

Solaris 10 boot problem - ERROR: Last Trap: Fast Data Access MMU Miss

Hello, We have a T5140 server with Solaris 10 and its suddenly throwing "segmentation core" when I login into the server and not showing any output for commands like df, mount etc. so I had to reboot the server to fix this issue. Please note that there's no boot disk mirroring. But... (2 Replies)
Discussion started by: prvnrk
2 Replies
device_remap(1M)					  System Administration Commands					  device_remap(1M)

NAME
device_remap - administer the Solaris I/O remapping feature SYNOPSIS
/usr/platform/sun4v/sbin/device_remap [-v | -R dir] DESCRIPTION
Certain multi-node sun4v platforms, such as T5440 and T5240 servers, have an integrated PCI topology that cause the I/O device paths to change in a CPU node failover condition. The device remapping script, device_remap, remaps the device paths in /etc/path_to_inst file and the symlinks under /dev to match the hardware. OPTIONS
The following options are supported: -v Displays the /etc/path_to_inst and /dev symlink changes. -R dir Perform remapping on the /etc/path_to_inst and /etc/path_to_inst files in the root image at dir. USAGE
The primary function of device_remap is to remap the device paths in the /etc/path_to_inst file and the symlinks under /dev in a CPU node failover condition to match the hardware. After adding CPU node(s) or removing CPU node(s), boot the system to the OBP prompt and use the following procedure: 1. Boot either the failsafe miniroot using: boot -F failsafe , or an install miniroot using boot net -s or similar command. 2. Mount the root disk as /mnt. 3. Change directory to the mounted root disk: # cd /mnt 4. Run device_remap script: # /mnt/usr/platform/sun4v/sbin/device_remap 5. Boot the system from disk. All the error messages are self-explanatory, except for the error message "missing ioaliases node" which means the firmware on the system does not support device remapping. EXAMPLES
Example 1 Displaying Changes Following Failover The following command displays the path_to_inst and /dev changes following a CPU node failover. # device_remap -v Example 2 Changing Directory Prior to Any Changes The following command changes the directory on which the boot image is mounted prior to making any changes. # device_remap -R /newroot ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWkvm.v | +-----------------------------+-----------------------------+ |Interface Stability |Unstable | +-----------------------------+-----------------------------+ SEE ALSO
boot(1M), attributes(5) SunOS 5.11 24 Dec 2008 device_remap(1M)
All times are GMT -4. The time now is 03:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy