10-27-2003 03:03 AM - edited 03-02-2019 11:16 AM
Hi
i have upgraded the RAM form 32MB to 128MB
i have removed the 32 MB and kept 128MB new RAM
when i switch it on back, iam getting this problem
any one can help me, it will be apprciated
System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)
Copyright (c) 1999 by cisco Systems, Inc.
Bad RAM at location 0xA0000000: wrote 0xA0000000, read 0xA0000008
System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)
Copyright (c) 1999 by cisco Systems, Inc.
Bad RAM at location 0xA0000000: wrote 0xA0000000, read 0xA0000008
hari
10-27-2003 02:09 PM
What device did you upgrade? It may not support that much memory, or it may not support the particular module you used.
10-28-2003 11:50 PM
Hi
i have not updated any thing,
it was year old box
after some time iam getting this error
*** Watch Dog Timeout ***
PC = 0x800001c0, SP = 0x60e3e178
*** TLB (Load/Fetch) Exception ***
Access address = 0x30800000
PC = 0xd4d4d4d4, Cause = 0x8008, Status Reg = 0x30410002
Failure detected during ROMMON start-up tests. Restart ROMMON.
System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)
Copyright (c) 1999 by cisco Systems, Inc.
Testing lower main memory - data equals address
Bad RAM at location 0xA0000004: wrote 0xA0000004, read 0x44BA0000
Testing lower main memory - data equals address
Bad RAM at location 0xA0000004: wrote 0xA0000004, read 0x44BA0000
System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)
Copyright (c) 1999 by cisco Systems, Inc.
Testing lower main memory - data equals address
Testing lower main memory - checkerboard
Testing lower main memory - inverse checkerboard
Clearing lower 32K memory for cache initialization
Clearing bss
Reading monitor variables from NVRAM
Enabling interrupts
Initializing TLB
Initializing cache
Reading cookie
Initializing main memory
Sizing NVRAM
Initializing required TLB entries
Configuring FLASH params
Initializing PCI subsystem
Exiting init
C3660 processor with 32768 Kbytes of main memory
Main memory is configured to 64 bit mode with parity disabled
*** TLB (Load/Fetch) Exception ***
Access address = 0xd4d4d4d4
PC = 0xbfc2d4ac, Cause = 0x8, Status Reg = 0x3041f003
*** Address Error (Load/Fetch) Exception ***
Access address = 0xffffffff
PC = 0xffffffff, Cause = 0x10, Status Reg = 0x3041f003
*** Address Error (Load/Fetch) Exception ***
Access address = 0xffffffff
PC = 0xffffffff, Cause = 0x10, Status Reg = 0x3041f003
monitor: command "boot" aborted due to exception
Testing lower main memory - data equals address
Testing lower main memory - checkerboard
Testing lower main memory - inverse checkerboard
Clearing lower 32K memory for cache initialization
Clearing bss
Reading monitor variables from NVRAM
Enabling interrupts
Initializing TLB
Initializing cache
Reading cookie
Initializing main memory
Sizing NVRAM
Initializing required TLB entries
Configuring FLASH params
Initializing PCI subsystem failed, opcode = 0x28
*** TLB (Store) Exception ***
Access address = 0xdcdcdcdc
PC = 0xbfc22fdc, Cause = 0xc, Status Reg = 0x3041f003
then , when make off and on
then iam getting
System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)
Copyright (c) 1999 by cisco Systems, Inc.
Bad RAM at location 0xA0000000: wrote 0xA0000000, read 0x5C5C5C5C
after 2 days if i make on, it works for 7 hours, and again the same problem
looking strange
not i dont have any modules installed in this
any suggestion will be good
hari
10-29-2003 06:55 AM
Hello,
have you put the original memory back into the same bank as where it was before ? When you use different SIMMs try to put the lower one (e.g. the 32MB DRAM) into the first available bank and the higher one into the second next available bank.
Regards,
GP
10-29-2003 03:37 PM
If you are using a 3660 (thought i saw that in the pasted output) you'll have to consider its memory installation requirements (http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis3600/hw_inst/hw_notes/3636mem.htm).
Bascially, for the 3660 you need a module in slot 0, and it has to be of larger capacity than the one in slot 1 if present.
You might be looking at a bad stick of ram, or maybe both sticks of ram are faulty. Either case, it seems like you are describing a hardware failure of some kind.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide