Santa rosa ram question

Hey
I was wondering which ram bank was bank 1 and which was bank 0. when I upgraded my ram I get one bank that won't recognize the ram. I know it is not the ram because when I change the spots the ram are in then it shows up in the other spot. any help as to what i can do to get both ram banks working would be great.
thanks
bill

Be sure you press firmly with considerable force to seat them.

Similar Messages

Santa rosa macbook+4gb ram PLZ HELPPPPP

i have a santa rosa macbook (on the box it says it supports up to 4gb) and i was trying to upgrade ram to 4gb from the default 1gb. So i bought 2X 2gb comstar ram from futureshop.
the problem is that when i try to put both of the new sticks for a total of 4 gb, the macbook will turn on but the screen will be black and the sleep indicator light on.
however, when i only put one 2gb in and leave the other slot filled with default 512mb stick for a total of 2.5gb, it will turn on properly and recognize it as 2.5 gb.
I've tried switching ram and slots numerously to determine if it's the slot or ram fault, but it doesn't work whever it's 4gb and works if it's 2.5gb.

Hello everybody,
Today unfortunately I got 4GB (2x2GB) Corsair low latency (VSA4GSDSKIT667C4) and I'm having the same problem as some of you, the system just handle up to 3GB. I tried many different combination but no luck at the moment. What is going on? Corsair is selling something that doesn't have any guarantee. I'm very disappointed and upset.
My MacBook specs:
Model Name: MacBook
Model Identifier: MacBook3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: *3 GB* (old module + 2GB corsair)
Bus Speed: 800 MHz
Boot ROM Version: MB31.008E.B02
SMC Version: 1.24f2
Serial Number: W87503EHZ66
Chipset Model: GMA X3100
Good luck!

Santa Rosa

I actually have two quick questions -
I just read something about Santa Rosa Macbook Pros, what exactly is it? And how do I know if mine is one of them. I purchased mine in September of 2007.
Second question is whats te max amount of RAM i can upgrade to? 2gb right?
Thanks

Templeton Peck wrote:
*"what exactly is it?"*
MacBook Pros that contain Intel's "Santa Rosa" chipset.
Which for the pedantic among us is actually none of them, as MBPs only contain 2 of the 3 chips that make up Intel's "Santa Rosa platform" IIRC

Brand-new Santa Rosa MBP, Kernel Panics related to Airport

Brand new MBP (2.4GHz 15"), anytime I do anything online I get a kernel panic. I am connecting to a WPA-2 network that is supporting stable connections to several other computers, including another (albeit older) MBP. I have no third-party sw installed, I have no peripherals attached, I have installed all available updates, I have run disk verify/repair and permission repair via the install disk and the problem persists. I have also physically inspected the RAM modules to make sure they're situated properly.
The console log shows mbuf failures (I can only access the log if I have the airport off) that are similar to the problem Apple identified in 10.4.8 but were supposedly solved w/ 10.4.9 (see http://docs.info.apple.com/article.html?
artnum=303712).
So two questions: anyone else out there experiencing this on a WPA-2 or other network? If so, any fixes that don't involve me having to return this computer to Apple? If this is a QA issue that could have been prevented through better testing prior to release...

Hey Don (and others)
I bought a new Santa Rosa MPB yesterday and am suffering the same issues. My office uses WPA (not sure about the specifics) and within the first hour of ownership (of my FIRST Apple machine ever) I suffered kernel panics.
I get back to my workplace from the local Apple Store, get all set up and online. I run all the software updates fine. Next, I shut the lid and proudly carry my new Mac to a meeting. Open the lid and notice I can't get online. I stop and start the wireless and immediately get a kernel panic.
Restart, and it happens again.
Restart, and I can get online finally. With the help of some coworkers I get to the panic.log file and notice the panic happens around the Airport.
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2572b9f8 : 0x128d08 (0x3cc224 0x2572ba1c 0x131de5 0x0)
0x2572ba38 : 0x1a4a55 (0x3d2638 0x0 0xe 0x3d1e5c)
0x2572bb48 : 0x19aeb4 (0x2572bb60 0x2572bb68 0xb92ebbb4 0x6)
0x2572bbf8 : 0x3b3c5e1e (0x17 0x23e1a107 0x6 0x3e77a380)
0x2572bdd8 : 0x3b3c8059 (0x23b052c8 0x1 0x4b285c 0x6)
0x2572bf08 : 0x39b543 (0x23b05000 0x4174b00 0x1 0x3c341e8)
0x2572bf58 : 0x39a715 (0x4174b00 0x135eb4 0x0 0x3c341e8)
0x2572bf88 : 0x39a44b (0x40e9200 0x0 0xee6ae98 0x13818b)
0x2572bfc8 : 0x19ad2c (0x40e9200 0x0 0x19e0b5 0x42bee60) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(230.8.5)@0x3b394000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x634000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5a4000
dependency: com.apple.iokit.IO80211Family(160.2)@0x3b375000
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386
Later I discovered that the office uses WPA. So I bring the MBP home and connect via my WEP encrypted WiFi, and haven't had the same problem once (so far it's been over 24 hours, with many "sleeps" in the meantime).
I did have another panic, waking up out of a 'deep sleep' this morning (after having had the lid shut for 6 hours)...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleACPIPlatform(1.0.10)@0x606000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5f2000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x602000
ACPI seems to have crashed something, hoping I can recreate this tomorrow morning.
At this point, I'm just glad to see I'm not the only owner of a the new MBP's suffering the same WPA-related crashes. Also, I do wonder if I got a replacement if it would solve anything, though I'm up for trying and may try tomorrow.
Overall, a bit frustrated (especially since after craving a MBP for months and holding out for the new models, to have these issues).
Oh, I also have a 2.4ghz 15"
-r-

MBP Santa Rosa Airport Issues w/ Leopard

Hi everyone,
I've noticed a few "quirks" since upgrading to Leopard. Whenever my Macbook Pro (Santa Rosa, 2.4 GHz, 17", 4GB RAM) is searching for a wireless network to join, the system becomes completely unresponsive. The mouse pointer stutters and jumps around the screen and it's impossible to precisely control its movement. When I can finally manage to click on the Airport icon in the menu bar and select the appropriate network to join, the problems stop as soon as a connection to a wireless network is established. It only happens when the system is searching for a Network. I should mention that it does this when I am at work (where I connect via 802.1x and TTLS) and at home (where I connect via an Airport Express Router).
Also, my computer no longer automatically connects to my work network (it does at home, though) after a restart or waking from sleep). I have my MBP set to prompt me for a password when it wakes from sleep, but it's near next to impossible to enter in the password because the system hangs so badly as it tries to establish a network connection. Of course, it doesn't connect unless I manage to click the Airport icon and specify the network I wish to join. Anyone have any thoughts on this?
All of this is a little frustrating since the latest updates to Airport in Tiger fixed all of the connection issues I had had previously with my MBP. When I first bought the machine I had many issues with network connections (as did many thousands of others who bought this model). I was wondering if other MBP Santa Rosa owners have observed similar behavior since upgrading to Leopard, and if so, does anyone have any suggestions as to how to fix this issue?
I should also mention that my Mac Mini C2D 1.83GHz (latest model) has no such issues so I think this is something that is still linked to this particular model of MBP.
Many thanks!

I am moving this over here, from the boot camp section. Hopefully this is more the location that this needs to be in. Well, my problem is not as extreme as some, but still an annoyance. I installed Leopard the first day, and immediately had HUGE airport issues. The computer would lose my hub. I run an Airport Extreme with an Express as a WDS. The computer would see the express, but lose the extreme completely. So no internet. If I messed with it long enough, I could get the computer to recognize the extreme, but as soon as the computer went to sleep, it would lose it again. I installed the keychain update, and the situation didn't get much better. Most of the time I get the "You are not connected to the Internet" error in Safari, and when I run network diagnostics the computer "finds" the internet again, and I get a "Network configuration change detected" message and all my lights go green.
After I installed the Keychain update, I repaired disk permissions. Any ideas?

Santa Rosa MBP Application Crashes with EXC_BAD_ACCESS (0x0001)

I am having Application crashing problems with my brand new Santa Rosa MBP that arrived today. This machine is a 2.4 GHz 17" MBP with Hi-Res Glossy display and it came with 2 GB of RAM. I upgraded it to 4 GB but this problem occurs with the original chips or the new 2 x 2 GB chips.
So far the applications that crash are Pages, Keynote, Aperture, Parallels Desktop, and iWeb. Other things I have tried are all right for now. Excerpts from the CrashReporter log of Aperture are below. All applications are crashing with an identical EXCBADACCESS (0x0001) and KERNPROTECTIONFAILURE (0x0002) at ... (this number differs for individual applications). Any ideas?
Bryan
Host Name: brycv
Date/Time: 2007-07-05 20:49:02.460 -0700
OS Version: 10.4.10 (Build 8R2232)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [82]
Version: 1.5.3 (1.5.3)
PID: 1196
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 <<00000000>> 0x00000000 0 + 0
1 com.apple.Aperture 0x00003149 0x1000 + 8521
2 com.apple.Aperture 0x0000323e 0x1000 + 8766
3 com.apple.Aperture 0x0000336e 0x1000 + 9070
4 com.apple.Aperture 0x0000294e 0x1000 + 6478
5 com.apple.Aperture 0x00002875 0x1000 + 6261
Thread 1:
0 libSystem.B.dylib 0x900248c7 semaphorewait_signaltrap + 7
1 com.apple.ColorSync 0x915a86cf pthreadSemaphoreWait(t_pthreadSemaphore*) + 35
2 com.apple.ColorSync 0x915c2de0 CMMConvTask(void*) + 60
3 libSystem.B.dylib 0x90024227 pthreadbody + 84
Thread 2:
0 libSystem.B.dylib 0x900248c7 semaphorewait_signaltrap + 7
1 libGLProgrammability.dylib 0x9418afdb glvmDoWork + 150
2 libSystem.B.dylib 0x90024227 pthreadbody + 84
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x010f7020 ebx: 0x92b217da ecx: 0x01872000 edx: 0x00000011
edi: 0xbffffbd8 esi: 0x01872000 ebp: 0xbffffc08 esp: 0xbffffbdc
ss: 0x0000001f efl: 0x00010246 eip: 0x00000000 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
MacBook Pro 17" 2.4 GHz Mac OS X (10.4.10)
MacBook Pro 17" 2.4 GHz Mac OS X (10.4.10)
MacBook Pro 17" 2.4 GHz Mac OS X (10.4.10)

I am also having this problem with Adobe Bridge CS3, and QuickTime but only if I try to open a video file. It seems to be a problem when I access anything that wants to deal with the video hardware in the machine. I am planning on calling Apple tomorrow but any help would be appreciated.

Santa Rosa MBP, Kernel Panics fixed by 10.4.10 Update v1.1

A friend of mine who has the new 2.4GHz MBP just ran the 10.4.10 v1.1, and he no longer has KPs. Has anyone else tried this with their SR MBPs?
I just got my 7th machine last night. I noticed that Apple has made the AC adapter smaller (similar to PB's). Who knows, maybe they changed something from the first release? Anyways, I tested it on battery, and within about 15 min, a KP while surfing the net! I will give the v1.1 a try when I get home tonight. will report back.
SR MBP owners, pls let me know if there's any fix out there that I am not be aware of. Thank you!

I run mine on battery all the time. Out on the deck, airports, hotspots, office buildings, hotels. Never had an issue with KP's.
I purchased mine through PowerMax on a trade-in deal for my old Core Duo model. They are located in Oregon I believe.
Something very wrong with being on 7. This is my 3rd one and only because I voluntarily keep upgrading them. Had a 15" Core Duo traded up for a 17" Core Duo and now a 17" Santa Rosa. Never had a single problem with any of them.
Apple certainly isn't problem free, the same as any other manufacturer isn't.
But honestly..if your on #7 I would have to start thinking that the problem is something other than the MBP. Some software...configuration...combination of hardware....something. I mean you would pretty much have to be the worlds unluckiest person I would think to have 7 bad ones.
Honestly, I really do mean no offense, but you might want to start looking at other factors. Are you using 3rd party RAM in it? Have you tried other routers? Or just one you have at home? What security protocols are you using? What software have you loaded from the default configuration.
I guess anything is possible, but statistically it would seem improbable that 7 of them could be suffering from the same problem.

MacBook Pro - with Santa Rosa - Kernel Panics

The local Apple store has replaced my new Santa Rosa MacBook Pro once already and when I received the machine, I did a brand new install and then transferred my files over. They told me that if I still get Kernel Panics on this second machine to go ahead and do an Archive and Install or Full Install option.
Until Time Machine is out, what is the best backup method for keeping all files and settings if you want to do a complete new install and format?
Does anyone think a brand new install will fix this? Also, this machine is getting a lot less KP's than the previous Santa Rosa MBP got. Any ideas why?
Here is my panic.log below. Does anyone have any ideas what this Unresolved Kernel Panic Means?
Sat Jun 9 23:57:50 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x012cf000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x3c41d5fe, ECX: 0x00000000, EDX: 0x0000000e
CR2: 0x00000000, EBP: 0x2580ba78, ESI: 0x0409da00, EDI: 0x80000000
EFL: 0x00010202, EIP: 0x00000000, CS: 0x00000008, DS: 0x25800010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2580b828 : 0x128d08 (0x3cc224 0x2580b84c 0x131de5 0x0)
0x2580b868 : 0x1a4a55 (0x3d2638 0x0 0xe 0x3d1e5c)
0x2580b978 : 0x19aeb4 (0x2580b990 0x202 0x2580b9e8 0x1416ad)
0x2580ba78 : 0x56222d (0x409da00 0xe 0x0 0xffff)
0x2580bae8 : 0x55bddd (0x409da00 0x3f54480 0x0 0x38181e)
0x2580bb08 : 0x389cae (0x3f54480 0xe0000100 0x409da00 0x1)
0x2580bb48 : 0x38a97b (0x409da00 0xe0000100 0x3f54480 0x1)
0x2580bb78 : 0x38a8da (0x409da00 0x3ea5c00 0x1 0x0)
0x2580bbb8 : 0x5601cc (0x409da00 0x3ea5c00 0x1 0x0)
0x2580bbd8 : 0x561a64 (0x409da00 0x3ea5c00 0x1 0x0)
0x2580bc08 : 0x5619b4 (0x409da00 0x409da00 0x1 0x561228)
0x2580bc38 : 0x56b340 (0x409da00 0x3ea5c00 0x1 0x0)
0x2580bc88 : 0x56b54d (0x3ea5c00 0x409da00 0x2580bce8 0x202bd0c)
0x2580bcb8 : 0x56ee2d (0x3ea5c00 0x202 0x2580bcd8 0x39a515)
0x2580bcd8 : 0x39be5c (0x3ea5c00 0x1 0x0 0x0)
0x2580bd18 : 0x3b2cf3 (0x3ef0340 0x56ee3e 0x1 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOHIDFamily(1.4.11)@0x555000
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386
Wed Jun 13 07:24:00 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x3d176ec8, CR3: 0x0133a000, CR4: 0x000006e0
EAX: 0x00cfcf00, EBX: 0x0040cbe1, ECX: 0x00cfcfcf, EDX: 0x0000cf00
CR2: 0x3d176ec8, EBP: 0x25bcbb58, ESI: 0x3d176ec8, EDI: 0x00000006
EFL: 0x00010006, EIP: 0x0037ee27, CS: 0x00000008, DS: 0x00000010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25bcb888 : 0x128d08 (0x3cc224 0x25bcb8ac 0x131de5 0x0)
0x25bcb8c8 : 0x1a4a55 (0x3d2638 0x0 0xe 0x3d1e5c)
0x25bcb9d8 : 0x19aeb4 (0x25bcb9f0 0x0 0x25bcba08 0x131d98)
0x25bcbb58 : 0x37f2ed (0x109380 0x3ccf4000 0x0 0x2)
0x25bcbc18 : 0x1ac351 (0x3d35c8 0x1 0x0 0x120)
0x25bcbc48 : 0x5e13ce (0x5e11ae 0x3 0x612160 0x0)
0x25bcbca8 : 0x5d6446 (0x400b800 0x2 0x25bcbc7c 0x4006a40)
0x25bcbcc8 : 0x3abf47 (0x405c300 0x4b063c 0x3 0x260000)
0x25bcbd08 : 0x3bb2f2 (0x400b800 0x3f21d4 0x3fae348 0x391c89)
0x25bcbd48 : 0x394663 (0x3fae100 0x4 0x1d 0x2)
0x25bcbd88 : 0x394b99 (0x3fae100 0x0 0x25bcbdc8 0x0)
0x25bcbda8 : 0x395a78 (0x3fae100 0x3f86c00 0xb 0x1)
0x25bcbde8 : 0x394bc2 (0x3fae100 0x407d500 0x25bcbe28 0x0)
0x25bcbe08 : 0x395a78 (0x407da00 0x3f86c00 0xb 0x1)
0x25bcbe48 : 0x394bc2 (0x407da00 0x40d3d00 0x25bcbe88 0x0)
0x25bcbe68 : 0x395a78 (0x4091c80 0x3f86c00 0xb 0x1) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleACPIPlatform(1.0.10)@0x5d5000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5c1000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x5d1000
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386
Wed Jun 13 08:37:37 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x3d21f9c8, CR3: 0x0133a000, CR4: 0x000006e0
EAX: 0x00baba00, EBX: 0x0040cbe1, ECX: 0x00bababa, EDX: 0x0000ba00
CR2: 0x3d21f9c8, EBP: 0x25563b78, ESI: 0x3d21f9c8, EDI: 0x00000006
EFL: 0x00010002, EIP: 0x0037ee27, CS: 0x00000008, DS: 0x00000010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x255638a8 : 0x128d08 (0x3cc224 0x255638cc 0x131de5 0x0)
0x255638e8 : 0x1a4a55 (0x3d2638 0x0 0xe 0x3d1e5c)
0x255639f8 : 0x19aeb4 (0x25563a10 0x0 0x25563a28 0x131d98)
0x25563b78 : 0x37f2ed (0x109380 0x3cbd9000 0x0 0x1)
0x25563c38 : 0x1ac351 (0x3d35c8 0x1 0x0 0x120)
0x25563c68 : 0x5e13ce (0x5e11ae 0x3 0x612160 0x0)
0x25563cc8 : 0x5d6446 (0x3d19800 0x2 0x25563c9c 0x3d02400)
0x25563ce8 : 0x3abf47 (0x3d6a300 0x4b063c 0x3 0x248000)
0x25563d28 : 0x3bb2f2 (0x3d19800 0x3f21d4 0x25563d88 0x394211)
0x25563d68 : 0x39459b (0x3cbc100 0x4 0x1d 0x2)
0x25563da8 : 0x395a78 (0x3cbc100 0x3c94c00 0xb 0x1)
0x25563de8 : 0x394bc2 (0x3cbc100 0x3d8b500 0x25563e28 0x0)
0x25563e08 : 0x395a78 (0x3d8ba80 0x3c94c00 0xb 0x1)
0x25563e48 : 0x394bc2 (0x3d8ba80 0x3dc9680 0x25563e88 0x0)
0x25563e68 : 0x395a78 (0x3dc9e80 0x3c94c00 0xb 0x1)
0x25563ea8 : 0x394bc2 (0x3dc9e80 0x3ddca00 0x25563ee8 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleACPIPlatform(1.0.10)@0x5d5000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5c1000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x5d1000
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386
Thu Jun 14 00:28:21 2007
panic(cpu 0 caller 0x0035CF4B): mget MCHECK: m_type=ffffb954 m=375bca00
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x259c3be8 : 0x128d08 (0x3cc224 0x259c3c0c 0x131de5 0x0)
0x259c3c28 : 0x35cf4b (0x3ed024 0xffffb954 0x375bca00 0x19a319)
0x259c3c48 : 0x3638c3 (0x1 0xe 0x4 0x376dfa00)
0x259c3c88 : 0x22f11d (0x259c3cac 0x14 0x14 0x0)
0x259c3cf8 : 0x240c7a (0x477fa00 0x259c3d2c 0x3764f134 0x37648d00)
0x259c3d48 : 0x2410ce (0x1c 0x0 0x3b9aca00 0x1)
0x259c3e08 : 0x22f364 (0x3764f100 0x14 0x3c 0x19a001)
0x259c3e48 : 0x230dc5 (0x3764f100 0x14 0x11 0x0)
0x259c3f58 : 0x21e53a (0x3764f100 0x375bcc00 0x44707c 0x1a37c0)
0x259c3f98 : 0x204df7 (0x4d1000 0x375bcc00 0x375bccfc 0x1a373d)
0x259c3fc8 : 0x19ad2c (0x0 0x0 0x10 0x4937f40) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386

Hi Kaleb,
I got a similar problem with my MacBook Pro. Kernel panic with Airport atheros driver. My router is Linksys WRT300n. A brand new install didn't fix the problem. This is the panic.log of the most recent KP.
Tue May 22 15:50:17 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x14306c68, CR3: 0x01745000, CR4: 0x000006e0
EAX: 0x14306c60, EBX: 0x00000098, ECX: 0x00000098, EDX: 0x14306c60
CR2: 0x14306c68, EBP: 0x14b7bd28, ESI: 0x26610a00, EDI: 0x00000004
EFL: 0x00010206, EIP: 0x0035b0dc, CS: 0x00000008, DS: 0x03a50010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x14b7bb18 : 0x128d08 (0x3cb134 0x14b7bb3c 0x131de5 0x0)
0x14b7bb58 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x14b7bc68 : 0x19ada4 (0x14b7bc80 0x0 0x4b0c9c 0x199ef1)
0x14b7bd28 : 0x2b611a94 (0x26610a00 0xfffffffc 0x6 0x2b9de300)
0x14b7bf08 : 0x39a463 (0x12e182c8 0x32f6180 0x1 0x37fc4a8)
0x14b7bf58 : 0x399635 (0x32f6180 0x135eb4 0x0 0x37fc4a8)
0x14b7bf88 : 0x39936b (0x37e6f80 0x0 0x450 0x1303)
0x14b7bfc8 : 0x19ac1c (0x37e6f80 0x0 0x10 0x0) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(223.47.4)@0x2b5e0000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x2ab68000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x249b6000
dependency: com.apple.iokit.IO80211Family(154.1)@0x2b5c3000
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Thu May 24 20:11:02 2007
panic(cpu 0 caller 0x0035C2B2): mbuf address out of range 0x14306c60
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x14003ab8 : 0x128d08 (0x3cb134 0x14003adc 0x131de5 0x0)
0x14003af8 : 0x35c2b2 (0x3eb8f4 0x14306c60 0x14003b68 0x1416ad)
0x14003b18 : 0x23abdb (0x1 0x2 0x2c0208 0xd6e31900)
0x14003c28 : 0x239783 (0x31edc9c 0x3f10d055 0x3f10d5fd 0xa3aaa8c0)
0x14003e08 : 0x22e364 (0x25b6ae00 0x14 0x14 0x6)
0x14003e48 : 0x22fdc5 (0x25b6ae00 0x14 0x6 0x0)
0x14003f58 : 0x21d53a (0x25b6ae00 0x25b6ae00 0x44507c 0x1a3010)
0x14003f98 : 0x203df7 (0x2c52804 0x25b6ae00 0x25a7181a 0x1)
0x14003fc8 : 0x19ac1c (0x0 0x0 0x10 0x2fe64c0) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Fri May 25 21:05:50 2007
panic(cpu 0 caller 0x0035BFBD): mbuf address out of range 0x18306c60
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13fd3d18 : 0x128d08 (0x3cb134 0x13fd3d3c 0x131de5 0x0)
0x13fd3d58 : 0x35bfbd (0x3eb8f4 0x18306c60 0x13fd3d88 0xd14c)
0x13fd3d78 : 0x35c815 (0x1 0x1 0xa1aaa8c0 0x10000e0)
0x13fd3db8 : 0x21da6e (0x25a07c00 0x1c 0x27b7940 0x0)
0x13fd3e08 : 0x22e32c (0x25a07c00 0x14 0x14 0x2)
0x13fd3e48 : 0x22fdc5 (0x25a07c00 0x14 0x2 0x0)
0x13fd3f58 : 0x21d53a (0x25a07c00 0x25a07c00 0x44507c 0x1a3010)
0x13fd3f98 : 0x203df7 (0x2bf6804 0x25a07c00 0x25a9e81a 0x1)
0x13fd3fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x2b3e718) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Sat May 26 18:06:48 2007
panic(cpu 0 caller 0x0035C2B2): mbuf address out of range 0xe28c
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x1457bab8 : 0x128d08 (0x3cb134 0x1457badc 0x131de5 0x0)
0x1457baf8 : 0x35c2b2 (0x3eb8f4 0xe28c 0x1457bb68 0x1416ad)
0x1457bb18 : 0x23abdb (0x1 0x2 0x2c0208 0xd6e31900)
0x1457bc28 : 0x239783 (0x3225e08 0xe26725f3 0xe2672b4b 0xa3aaa8c0)
0x1457be08 : 0x22e364 (0x25a37800 0x14 0x14 0x6)
0x1457be48 : 0x22fdc5 (0x25a37800 0x14 0x6 0x0)
0x1457bf58 : 0x21d53a (0x25a37800 0x25a37800 0x44507c 0x1a3010)
0x1457bf98 : 0x203df7 (0x2bcbe04 0x25a37800 0x25aa881a 0x1)
0x1457bfc8 : 0x19ac1c (0x0 0x0 0x10 0x2ad0540) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Sun May 27 09:52:05 2007
panic(cpu 0 caller 0x0035C30A): mbuf address out of range 0x16dd6c60
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13e7ba08 : 0x128d08 (0x3cb134 0x13e7ba2c 0x131de5 0x0)
0x13e7ba48 : 0x35c30a (0x3eb8f4 0x16dd6c60 0x124fe004 0x2be9004)
0x13e7ba68 : 0x35c6aa (0x25b15500 0x25b6b100 0x13e7ba88 0x124e74bc)
0x13e7ba88 : 0xa0e98e (0x25b15500 0x25b15500 0x124fe004 0x80)
0x13e7bb68 : 0xa238f5 (0x124fe004 0x25b15500 0x30 0x35ac8a17)
0x13e7bd28 : 0xa2daf5 (0x35ac8a17 0x25aee800 0xffff 0x376ec560)
0x13e7bf08 : 0x39a463 (0x124e72c8 0x29fc300 0x1 0x26f8a7c)
0x13e7bf58 : 0x399635 (0x29fc300 0x135eb4 0x0 0x26f8a7c)
0x13e7bf88 : 0x39936b (0x2a06440 0x0 0x13e7bfc8 0x203e3e)
0x13e7bfc8 : 0x19ac1c (0x2a06440 0x0 0x19e0b5 0x2ee4ed4) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(223.47.4)@0x9fc000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6bf000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x582000
dependency: com.apple.iokit.IO80211Family(154.1)@0x7fb000
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Sun Jun 3 19:48:03 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x16dd6c68, CR3: 0x00e1c000, CR4: 0x000006e0
EAX: 0x16dd6c60, EBX: 0x0000009a, ECX: 0x0000009a, EDX: 0x16dd6c60
CR2: 0x16dd6c68, EBP: 0x144dbd28, ESI: 0x25a5b800, EDI: 0x00000004
EFL: 0x00010206, EIP: 0x0035b0dc, CS: 0x00000008, DS: 0x02b30010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x144dbb18 : 0x128d08 (0x3cb134 0x144dbb3c 0x131de5 0x0)
0x144dbb58 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x144dbc68 : 0x19ada4 (0x144dbc80 0x0 0x144dbc98 0x3801e3)
0x144dbd28 : 0xa2da94 (0x25a5b800 0xfffffffc 0x6 0x3796e710)
0x144dbf08 : 0x39a463 (0x124e72c8 0x29f5980 0x1 0x2b3acec)
0x144dbf58 : 0x399635 (0x29f5980 0x135eb4 0x0 0x2b3acec)
0x144dbf88 : 0x39936b (0x2b271c0 0x0 0x8000 0xf0b)
0x144dbfc8 : 0x19ac1c (0x2b271c0 0x0 0x19e0b5 0x2eda6c8) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(223.47.4)@0x9fc000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6bf000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x582000
dependency: com.apple.iokit.IO80211Family(154.1)@0x7fb000
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Sun Jun 3 20:51:21 2007
panic(cpu 0 caller 0x0035C2B2): mget MCHECK: m_type=6c60 m=25ae2800
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13eabc18 : 0x128d08 (0x3cb134 0x13eabc3c 0x131de5 0x0)
0x13eabc58 : 0x35c2b2 (0x3eb83c 0x6c60 0x25ae2800 0xa20181)
0x13eabc78 : 0xa043c3 (0x1 0x2 0x13eabcc8 0xa4a4e0)
0x13eabcc8 : 0xa0acca (0x124f9004 0x2 0x1 0x0)
0x13eabcf8 : 0xa06f05 (0x124e74bc 0x0 0x1 0xa4a07f)
0x13eabd28 : 0xa2e08b (0x124e74bc 0x13eabeec 0x13eabd48 0x325)
0x13eabf08 : 0x39a463 (0x124e72c8 0x2a12880 0x1 0x258e8b0)
0x13eabf58 : 0x399635 (0x2a12880 0x135eb4 0x0 0x258e8b0)
0x13eabf88 : 0x39936b (0x2a18bc0 0x0 0x8000 0x3403)
0x13eabfc8 : 0x19ac1c (0x2a18bc0 0x0 0x19e0b5 0x258e8b0) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(223.47.4)@0x9fc000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6bf000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x582000
dependency: com.apple.iokit.IO80211Family(154.1)@0x7fb000
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
I tried WPA, WPA2, WEP. TKIP, AES. 802.11b, 802.11g and 802.11n... with the same issue -> Kernel Panic...
I have no answer from my Apple resellers in France. Alone in the dark :'-(
BUT everything goes well since I stop using the '$' in the pre-shared key and the SSID. I haven't experience any new KP since 03/06 with a intensive Airport use... I hop this can help you.
Core 2 Duo MacBook Pro 15" • 120GB HD • 1GB RAM Mac OS X (10.4.9)

Installation Mountain Lion on Mac model Santa Rosa is possible?

Hi,
I want install on my macbook Santa Rosa the new Mountain Lion. Is possible? My Mac has 4GB ram...

Check that your computer is compatible with Mountain Lion.
To check the model number hold down the option/alt key, go to the Apple menu and select System Information.
iMac (Mid 2007 or newer) model number 7,1 or higher
MacBook (Late 2008 Aluminum, or Early 2009 or newer) model number 5,1 or higher
MacBook Pro (Mid/Late 2007 or newer) model number 3,1 or higher
MacBook Air (Late 2008 or newer) model number 2,1 or higher
Mac mini (Early 2009 or newer) model number 3,1 or higher
Mac Pro (Early 2008 or newer) model number 3,1 or higher
Xserve (Early 2009) model number 3,1 or higher
Your Mac needs:
OS X v10.6.8 or OS X Lion already installed
2 GB or more of memory
8 GB or more of available space
Check to make sure your applications are compatible. Application Compatibility
If you have applications that you want to use that aren't compatible, you can retain Snow Leopard and create a new partition to install Mountain Lion on or you can run Snow Leopard server in a virtual mode.
If your computer isn't compatible, you might be able to upgrade to Lion. Computer Compatibility - Lion
If you can/do upgrade, I recommend you make a copy of the installer and move it out of your Applications folder. The installer self-destructs. The copy will keep you from having to download the installer again.

Identifying a Santa Rosa MacBook

Hi
I plan on buying a blackbook in the next couple of days from an Apple Reseller (military exchange store). ITs the same price as the one on the Apple website, but I want to make sure the mac I get is the most recent...and the one that their shipping directly from Apple.
Are there any was of telling if it is in fact a Santa Rosa macbook? It does come with Leopard, I know that much.
thanks.

Apple MacBook MB063LL/A 13.3" Notebook PC (2.16 GHz Intel Core 2 Duo Processor, 1 GB RAM, 160 GB Hard Drive, 8x SuperDrive) Black. GMA 950 graphics processor with 64MB of DDR2 SDRAM shared with main memory
Apple MacBook MB063LL/B 13.3" Notebook PC (2.2 GHz Intel Core 2 Duo Processor, 1 GB RAM, 160 GB Hard Drive, 8x Super Drive) Black Intel GMA X3100 graphics processor with 144MB of DDR2 SDRAM shared with main memory
As you can see the Santa Rosa is all new and lots more bang for your buck.

Is this a "MacBook Pro Santa Rosa"

Hey
I´ve been offered 4 GB ram at a really good price, but I dont know if they will work because it has to be a "Santa Rosa"? How do I figure out if my model fits this describtion?
Thanks!
Mikkel Braginsky

Gasp. Really?!? Next thing, you'll be telling us that the Ti-book wasn't actually made from titanium. Did George Washington really chop down that cherry tree or not? When does it end.........
Seriously, far fewer people can relate to Merom. But I'll bet lots more refer to Penryn than "Santa Rosa Refresh", as the Penryn-containing platform is technically code-named. In any case, that's all these things are - code names for convenience.

Santa Rosa MacBook - PC2-4200/DDR2 533 works

Checked it out myself. I read the Intel PM965/GM965 (Santa Rosa) spec, which says both "667 and 533 MHz" DDR2 memory is supported, and that if memory speed is mixed in separate slots that it will revert to the slower speed. I know Apple only recommends PC2-5300, but I thought I'd report back my experiment.
I tried it out myself with one 512 MB Hynix PC2-5300 module (factory installed in my MacBook) along with a 512 MB Samsung PC2-4200 module (from a PC notebook), and System Profiler identifies both modules as DDR2 533MHz.
I used to also believe that for true "dual channel" operation, you would as much as possible to be identical. The Santa Rosa datasheet says that only capacity is critical for full dual-channel operation, and that partial dual-channel operation is possible if the modules aren't matched for size. Also - dual-channel apparently doesn't mean full parallel operation, but that they can be "interleaved" such that one channel can be accessed (read or write requested) in advance while the other channel is still accepting/outputting data - sort of pipelining read or write requests. It's not exactly the same as having a full 128-bit memory bus, which is what I used to think was the case.
I'm not sure if this holds true for the previous generation of MacBooks, but I wouldn't be surprised if it were.

Hyde244 wrote:
So basically as long as it is all at the same bus speed, different RAM brands can be interchanged without any effect?
That's my impression from reading the Intel datasheet.

What is a Santa Rosa MBP?

Sorry for my ignorance, but I just bought a MBP 17" 2.4Ghz with 4GB RAM and 7200RPM HD and I've read a lot about the "Santa Rosa" and I'm lost. What is it? and how can you tell? Thanks

It's the most recent incarnation of the MBP line that is using a different chipset than previous models. This chipset is nick-named 'Santa Rosa' by Intel. Hence the new MBPs are called the Santa Rosa models. They can be easily identified by their CPU speeds - 2.2 and 2.4 GHz.
If you open System Profiler you will also see that the Machine ID is 3,1 to identify the first of the Santa Rosa models.

Mac Book Santa Rosa 13" 2.2 GHz, HDD upgrade

Hello,
I would like to change the hard drive of my MacBook Santa Rosa 13" 2.2 GHz.
I would like to go fo an SSD Drive. I checked and find out that the kingston have got a good price.
There is something that is quite annoying me though, they propose model with Serial ATA III and serial ATA II. I tought Serial ATA III was compatible with older technology. So my questions are:
Why do they propose two versions (especially when the SATA II version is more expensive) ?
Will a SATA III SSD will work in my old macbook ? any idea of the perf ?
Thanks a lot,
Regards,
Julien

Before 2009, all SATA Macs only supported 1.5 Gbps SATA.
Starting in 2010 they started supporting higher speed SATA.
During 2009, Apple provided firmeware updates for 2009 models that didn't support higher speed SATA to support it. That said, many SATA drives offer a jumper to slow down the bus speed so older machines can support them. Until the unibody models, only the 17" MacBook Pro supported higher than 9.5mm drive heights..
If the drive in question has to be thinner, naturally it might cost more because of the shrinking of components..
Slower speed SATA drives are becoming less common, thus can become more expensive as supply is outweighed by demand.
Before you jump the SSD bandwagon, remember, there is no technology that can totally wipe the drive, unlike with platter drives. If your machine is sold in the future, be sure not to put any personally identifying data on it, once you switch to SSD, unless they erasing technology improves. .

Santa Rosa MBPro 2.4 - starts, but then only kernel panics

Trying to solve this problem, appeared suddenly, now every time I start up the MBPro, I get a kernel panic and the Restart Your Mac message. Appears 10-20 seconds after the little wheel starts spinning under the Apple.
Anyway, I couldn't get any farther, even though I tried different RAM, put in a new hard disk, tried 3 different operating systems. Re. the OS, both Tiger and Snow Leopard seemed to work a little bit, i.e., maybe a half hour or so. Then the kernel panics started again at boot. Now I can't even install an OS. Current OS is Snow Leo, which I installed from an external hard disk.
Anyway, I checked with Apple Hardware Test. I booted from the Apple Hardware Test (original disks were 10.4, don't think that should matter if I have 10.6 installed now, right?). I did the Extended Testing, which took just under an hour, including 25-30 minutes just for the memory test. But everything checked out, including memory.
The suggestion the test provided was "if the test results determine that a hardware problem does not exist, consult the manual or Help system that came with your computer for further troubleshooting".
Obviously can't use Help, as I can't boot the computer.
The manual is pretty concise too, not much help there.
Could this be a software problem? If so, what? I've had the kernel panics with 3 different OS.
What about Airport? I've found a couple threads where people report "airport-enduced kernel panics in Santa Rosa Macbook Pros". Pretty specific.
They referred to a kext in the Airport software causing the kernel panics, maybe a kext specifically for Atheros.
My problem is, I wouldn't be able to go in an remove the kext, as I can't boot the computer.
Does this sound plausible? If so, would it help at all to remove the Airport card? i.e., if there's a conflict between it and the kext? I could always use a USB key for wifi, if that helped solve the problem.
I could try to boot in Firewire disk mode and remove the kext.
Any suggestions?

moonshot61 wrote:
N.B. interesting to note that the last time I ran AHT this same memory module checked out okay.
RAM has so many circuits, and millions of varying combinations of what's being used at one time, that it is far from uncommon for bad RAM not to be detected, especially by testing software available to most end-users.
I have swapped the 1 RAM bank that was installed with another, and am now running AHT in Extended mode, with Looping enabled.
Good plan.
Does that code seem to show a MEMORY problem?
Yes.
Have there been any problems with the memory SLOTS on the Macbook Pro?
Yes. There have been at least some problems with every part of every electronic/mechanical device ever made, and MBPs are no exception.
ie., like with the Powerbook G4s a few years ago.
I have not seen anywhere near that number of incidents posted here.
I think the RAM tested out okay on another Mac, but I've done so many tests and changes recently that I can't remember. I've got a few 1GB RAM banks for the MBPro and will try those one by one.
Not to state the obvious, but you need to do this in an organized manner, otherwise your results will not be valid (you may test the same module in the same memory bank or not test one at all, in which case you'd be wasting your time). You've got the right idea for testing, but you're going to need to label things/and or organize the results. And sometimes two RAM modules work fine independently, but don't play well together, so stick with the one-module-at-a-time approach until you find one that works over a period of time and with all the apps you normally use. After that you can get into combinations and see what works and/or what doesn't.
Message was edited by: tjk

Santa rosa ram question

Similar Messages

Maybe you are looking for