Sponsored Content
Full Discussion: Data Access Error
Top Forums UNIX for Advanced & Expert Users Data Access Error Post 10297 by Perderabo on Monday 12th of November 2001 09:36:25 AM
Old 11-12-2001
Your computer is complaining that it has a problem accessing a memory card. It may be correct and you may have a bad memory card. But some suns also erroneously issue this error message and there is a firmware patch to correct this.
 

9 More Discussions You Might Find Interesting

1. Solaris

solaris 8 hangs and data access error on reboot

Hi using solaris 5.8 on UltraSPARC-IIi 360MHz. I know it is an old hardware but similiar hardware is running fine. here is the issue, System booted : works okay for some time then display was hung so system was rebooted ..it gave data access error. again rebooted and it came up... (6 Replies)
Discussion started by: upengan78
6 Replies

2. Solaris

Fast Data Access MMU Miss

Hi All , I am unable to reinstall the OS on my Ultra Sparc 10. After the 1st CD is loaded when it goes for reboot its goes to ok prompt an its unable to boot. What could be reason for this behavior? while loading the OS its seems fine but unable to boot!! Then i tried changing the... (2 Replies)
Discussion started by: kumarmani
2 Replies

3. UNIX for Advanced & Expert Users

Linux: Access time of mapped data

Before I forget, I'm running on a RedHat 5 box with the following uname -a output: Linux gnc141c 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux Now on to my question. I'm using a tool that maps a Matlab .mat file using the Linux mmap functionality and then... (1 Reply)
Discussion started by: rusttree
1 Replies

4. 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

5. Solaris

Unable to login Solaris 10 Sparc - Data Access Error

Hello everyone, This is the first time I am installing Solaris. I have SunBlade 1500 Wrkstn. I installed Solaris 10 Sparc. The installation went successfully but I don't get the login screen. I get the following error message: Boot device: disk:a File and agrs:- Data Access Error Ok ... (4 Replies)
Discussion started by: mfsaeed
4 Replies

6. AIX

access data from a new disk was assigned another rootvg

Hello, I try to access to data after connect a new disk (hdisk1) to a AIX 7.1 system This new disk was assigned to a rootvg from another AIX 6.1 system. It seem not assigned to any vg but if I tried to assigned hdisk1 to rootvg i get : Data seem to be always here ... ouf ;-)... (4 Replies)
Discussion started by: Voran
4 Replies

7. Programming

Help with ISAM data access

We are using an ISAM database, it is called RTISAM and has been in place for many years. We access the data using AIX code and using FORTRAN programs. I have heard that there are ways to access this data via Visual Studio and C# with the use of either a FORTRAN dll or an ODBC driver. I'm... (2 Replies)
Discussion started by: KathyB148
2 Replies

8. Linux

Permissions and access to data

Hi Operating system Red Hat Enterprise 5.8, Data access Mac/PC environment on various OS levels. Access via smb I am trying to set up a data shared area where a user group can read and write to its own directory, but can only write to another groups directory. Example: I have set up two... (1 Reply)
Discussion started by: treds
1 Replies

9. 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
MEMORY_CS(4)						     Kernel Interfaces Manual						      MEMORY_CS(4)

NAME
memory_cs - MTD-aware PCMCIA memory card driver SYNOPSIS
insmod memory_cs.o [pc_debug=n] [mem_speed=n] [word_width=n] [force_size=n] DESCRIPTION
Memory_cs is the Card Services driver for PCMCIA memory cards, and also provides direct memory access for other types of cards. It pro- vides character-mode and block-mode for accessing any card's attribute and common memory address spaces, analogous to /dev/mem. Memory_cs will allocate a free major device number when it is loaded. It provides two types of minor devices: "direct" character-mode devices for raw access a card's entire PCMCIA common and attribute memory spaces, and "indirect" devices for accessing specific memory partitions via an appropriate Memory Technology Driver. The bitwise layout of minor device numbers is one memory device. 'x' is set if this is a direct- access device, 'a' is set for attribute memory, and 'rr' is the region number (for indirect devices). When memory_cs is bound to a card, it will report its major and minor device numbers to cardmgr(8). The default memory card initialization script creates character special device files for the direct common memory and attribute memory devices. It also creates character special devices for accessing the first attribute and common memory partitions, and a block device for accessing the first common memory partition. These devices have the following names: /dev/mem#c Common memory direct access, character special device. /dev/mem#a Attribute memory direct access, character special device. /dev/mem#c0c Common memory region 0, character special device. /dev/mem#c0b Common memory region 0, block special device. /dev/mem#a0c Attribute memory region 0, character special device. The block special device for a card's common memory can be used to create a filesystem on a card, and the device can be mounted in much the same way as a floppy disk. In some cases, you may need to explicitly specify the card's capacity when creating a filesystem. The character special devices can be used to read and write arbitrary numbers of bytes to arbitrary locations. For devices that need to be explicitly erased before writing, if a write request is aligned and sized on erase block boundaries for the target memory card, the driver will erase the target region before writing to the card. Since any PCMCIA card can be accessed as a memory card, memory_cs can be bound to any card regardless of function, and regardless of what other drivers might also be bound to that card. For example, this driver can be bound to a card and then used to read out the contents of the card's attribute memory. PARAMETERS
pc_debug=n Selects the PCMCIA debugging level. This parameter is only available if the module is compiled with debugging enabled. A non-zero value enables debugging. mem_speed=n Sets the access speed of the shared memory window for direct access devices, in nanoseconds. The default is 0 (i.e., no extra wait states). Values of up to 1000 are legal. word_width=n A flag indicating if direct access devices should be configured for 8-bit (if 0) or 16-bit (if 1) transfers. The default is 1 (16-bit). force_size=n Explicitly specifies the size of a simple SRAM card, skipping the default (and sometimes unreliable) size check. IOCTLS
These are defined in <pcmcia/memory.h>. MEMGETINFO This takes an argument of type (region_info_t *), defined in <pcmcia/bulkmem.h>. The structure will be filled in with memory region information for this device, such as access speed, erase block size, and JEDEC identifiers. MEMERASE This takes an argument of type (erase_info_t *), specifying the offset and length of a memory region to be erased. AUTHOR
David Hinds - dahinds@users.sourceforge.net SEE ALSO
cardmgr(8), pcmcia(5), memory_cb(4). pcmcia-cs 2000/06/12 21:24:48 MEMORY_CS(4)
All times are GMT -4. The time now is 07:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy