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.

Similar Messages

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-

Problem with Santa Rosa MBP-Unable to Boot

I have a Santa Rosa MBP with the maximum of 4GB of memory.
About 4 months ago I was unable to boot it because there was no video at all. The Genius Bar stated it was a problem with the video in the hardware and kept it for about a week to install a new Logic Board.
I got it back but within a couple days began having new problems. The Wi-Fi would connect but there was no internet on safari, mail, etc. i went to the Apple store again and the Genius Bar was unable to fix it and said it was a problem deep inside the OS. What I did since I had already bought Snow Leopard I did an upgrade from Leopard to Snow Leopard and it solved the problem.
It has worked well the last 3 months or so when my MBP started slowing down. It would sometimes take 10 minutes just to get from the login screen after typing in my password to my desktop where I can use it. Programs would open slow, close slow. My dashboard opens but I can't do anything with it. It has only gotten worse with time and now the computer won't even boot. It gets to the grey Apple with the progress indicator and stays there with the fan running but never goes further.
Fortunately I had done a mirrored backup from Super Duper. I had begun to think it was a hard drive problem. I tried booting from this backup that was made before the problem got very bad and it also runs the same way. I then took this backup to another MBP I have and it worked perfectly. I don't think it's a hard drive problem now. I then thought it may be a memory problem. I used the DVD that came with the MBP to do a hardware test which passed.
I think I have no choice but to go back to the Genius Bar. The problem is with purchasing the additional AppleCare my AppleCare just expired about 3 weeks ago. Yet I know this logic board was put in around 4 months ago and if I'm correct when something like that is done it's often a refurbished board, not new. Either way I had the issue with Wi-Fi just after the replacement and I went back to Apple for it. I think it was related and now this problem. I don't want to have to buy a new MBP but yet I'm convinced all these problems started with the logic board replacement.
Do any of you have other ideas of what the problem could be? Is it possible something I could fix? I have tried a PRAM reset with no luck. Would Apple cover something like this?
Thank you for your help.

Hi,
Looks like partition 2 is set to active after running diskpart script. Here are the details:
DISKPART> list volume
Volume ### Ltr Label        Fs     Type        Size     Status     Info
Volume 0     C   OSDisk       NTFS   Partition    465 GB Healthy
Volume 1                      NTFS   Partition    300 MB Healthy
Volume 2     D   Win7_2.1.6_ NTFS   Removable     14 GB Healthy
DISKPART> select partition 2
Partition 2 is now the selected partition.
DISKPART> detail partition
Partition 2
Type : 07
Hidden: No
Active: Yes
Offset in Bytes: 499792216064
Volume ### Ltr Label        Fs     Type        Size     Status     Info
* Volume 1                      NTFS   Partition    300 MB Healthy

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.

MBP Kernel Panics, log posted, ideas?

MBP kernel panics and panic log
I received a MBP at the end of march, build week 10, 2.0 GHz, 2 GB of kensington memory added. I have been getting occasional kernel panics (screen greys, computer asks for restart), mostly while running itunes through an airport express/extreme network to my home stereo. Sunday, I ran apple hardware test in looping mode for 4 hours, no indicated problem. Then, I ran Memtest in single user mode for 3 hours, with no indicated problem. No noise problems that my 51 year old ears can hear, no automatic restarts, but the computer does get much hotter than my old trusty 1 GHz Ti PB.
Below is the panic log. Any of experts around here have suggestions? Hate to send in the 'puter if I don't have to.
thanks,
Jack
Fri Mar 24 20:08:40 2006
panic(cpu 0 caller 0x0034EDF2): mbuf address out of range 0x2c4208
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x24a23b04 : 0x128b5e (0x3bb0bc 0x24a23b28 0x131bbc 0x0)
0x24a23b44 : 0x34edf2 (0x3da7ac 0x2c4208 0x130fc68 0x13f5f5)
0x24a23b64 : 0x22e223 (0x1 0x2 0x24a23b74 0x18)
0x24a23c44 : 0x22d010 (0x4161b70 0x34 0x1 0x8301a8c0)
0x24a23e14 : 0x221bb3 (0x3699fa00 0x14 0x24a23f14 0x3bb702f1)
0x24a23e54 : 0x223637 (0x3699fa00 0x14 0x6 0x0)
0x24a23f64 : 0x210cb5 (0x3699fa00 0x3699fa00 0x42ab5c 0x135798)
0x24a23fa4 : 0x1f73a1 (0x3a68004 0x3699fa00 0x3696501a 0x1)
0x24a23fd4 : 0x197a21 (0x0 0x0 0x3434278 0x49f000) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.5.2: Mon Feb 13 16:31:48 PST 2006; root:xnu-792.8.37.obj~1/RELEASE_I386
Sat Mar 25 13:14:03 2006
panic(cpu 0 caller 0x00350A7E): mbuf address out of range 0x2c4208
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x250abae4 : 0x128b5e (0x3bb0bc 0x250abb08 0x131bbc 0x0)
0x250abb24 : 0x350a7e (0x3da7ac 0x2c4208 0x250abb44 0x19cae2)
0x250abb64 : 0x22e191 (0x3698cf00 0x0 0x5a8 0x1)
0x250abc44 : 0x22d010 (0x4778228 0x34 0x1 0x8301a8c0)
0x250abe14 : 0x221bb3 (0x3696ac00 0x14 0x250abf14 0x3b5fe2f1)
0x250abe54 : 0x223637 (0x3696ac00 0x14 0x6 0x0)
0x250abf64 : 0x210cb5 (0x3696ac00 0x3696ac00 0x42ab5c 0x135798)
0x250abfa4 : 0x1f73a1 (0x3a85004 0x3696ac00 0x3699981a 0x1)
0x250abfd4 : 0x197a21 (0x0 0x0 0x3283f90 0x49f000) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.5.2: Mon Feb 13 16:31:48 PST 2006; root:xnu-792.8.37.obj~1/RELEASE_I386
Thu Mar 30 18:50:49 2006
panic(cpu 1 caller 0x0030F498): BlockAllocateContig: allocation overflow on "Jack Whaleyb
Thu Mar 30 18:54:18 2006
panic(cpu 0 caller 0x0030F498): BlockAllocateContig: allocation overflow on "Jack Whaleyb
Sun Apr 2 19:16:24 2006
panic(cpu 0 caller 0x0034EE4C): mbuf address out of range 0x1ff48000
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x24bbbbc4 : 0x128b5e (0x3bb0bc 0x24bbbbe8 0x131bbc 0x0)
0x24bbbc04 : 0x34ee4c (0x3da7ac 0x1ff48000 0x300 0x36967800)
0x24bbbc24 : 0x34f1f3 (0x36967800 0x408208c 0xffff 0xffff)
0x24bbbc44 : 0x22ceaf (0x36967800 0x11d 0x1 0x8301a8c0)
0x24bbbe14 : 0x221bb3 (0x36967800 0x14 0x24bbbf14 0x3bb712f1)
0x24bbbe54 : 0x223637 (0x36967800 0x14 0x6 0x0)
0x24bbbf64 : 0x210cb5 (0x36967800 0x36967800 0x42ab5c 0x135798)
0x24bbbfa4 : 0x1f73a1 (0x3a79e04 0x36967800 0x369ce81a 0x1)
0x24bbbfd4 : 0x197a21 (0x0 0x0 0x3283318 0x34ee6000) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.5.2: Mon Feb 13 16:31:48 PST 2006; root:xnu-792.8.37.obj~1/RELEASE_I386
Fri Apr 7 18:48:51 2006
panic(cpu 0 caller 0x00351267): mbuf address out of range 0x80
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x24de3b84 : 0x128b5e (0x3bbeb8 0x24de3ba8 0x131bbc 0x0)
0x24de3bc4 : 0x351267 (0x3db914 0x80 0x24de3c04 0x196fd0)
0x24de3c04 : 0x356a27 (0x368a7000 0x297 0x24de3c44 0x22ff2a)
0x24de3c44 : 0x22cde5 (0x3aa16bc 0x21f0 0x1 0x8301a8c0)
0x24de3e14 : 0x222007 (0x368c5000 0x14 0x51819a88 0x435)
0x24de3e54 : 0x223a8b (0x368c5000 0x14 0x6 0x0)
0x24de3f64 : 0x211109 (0x368c5000 0x368c5000 0x42cb5c 0x135798)
0x24de3fa4 : 0x1f773d (0x3a19604 0x368c5000 0x3689d01a 0x1)
0x24de3fd4 : 0x197a21 (0x0 0x0 0x354a0d0 0x4a1000) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386
Sun Apr 9 18:30:31 2006
panic(cpu 0 caller 0x00351267): mbuf address out of range 0x80
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x24d03b84 : 0x128b5e (0x3bbeb8 0x24d03ba8 0x131bbc 0x0)
0x24d03bc4 : 0x351267 (0x3db914 0x80 0x24d03c04 0x196fd0)
0x24d03c04 : 0x356a27 (0x3688d800 0x10 0x24d00010 0x3681a500)
0x24d03c44 : 0x22cde5 (0x3ab59d4 0x21f0 0x1 0x8301a8c0)
0x24d03e14 : 0x222007 (0x3681a500 0x14 0x24d03f14 0x930506)
0x24d03e54 : 0x223a8b (0x3681a500 0x14 0x6 0x0)
0x24d03f64 : 0x211109 (0x3681a500 0x3681a500 0x42cb5c 0x135798)
0x24d03fa4 : 0x1f773d (0x3a35204 0x3681a500 0x3681881a 0x1)
0x24d03fd4 : 0x197a21 (0x0 0x0 0x3547f90 0x34fc7000) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386

I had issues with my previous PowerBook G4. It would all the suddent get very hot. I suspected that something was not right with the CPU cooling. I opened up the PowerBook and found one of the screws that would hold the cooling assembly down loose. after tightening that screw the temperatures returned to normal...
I can imagine that your MBP has something similar going on as well. Or maybe your environment is hotter that mine here. I work at a pretty well air conditioned place, so my laptops always run very cool here.

Santa Rosa MBP - DVI to VGA Projector problems

When hooking up a Sharp PG M20X using a [DVI toVGA cable] and a [VGA to DVI adaptor] the MBP sees the projector, but the projector cannot see the computer.
This is a problem because, I may find myself in situations where this is the only configuration for hooking my MBP up to a projector.
Note:
1. A G4 Powerbook works fine with this configuration.
2. The MacBook Pro drives the Sharp PG M20X projector DVI to DVI - without problems
3. The MacBook Pro drives a DVI to VGA CRT monitor - using a [VGA to DVI adaptor] - without problems.
Is there a solution?
Thanks
I have a 2.4 GHz Santa Rosa C2D MacBook Pro Mac OS X (10.4.10) Sharp PG M20X Projector (DVI-input)

I think I solved this problem.
It was in issue for me. My second monitor would only display the Windows XP screen when it was loading, then it would black out. I couldn't even move my mouse arrow to the other side. Then I fixed it, here's how (running Windows XP SP3):
1. Start > Control Panel > Appearance and Themes
2. Display
3. Go to tab "settings"
4. Double click the blue image with the "2" inside it. This is the second monitor, adjacent to your first, or primary, monitor. The blue box may be a desaturated, greyish blue, meaning that the monitor is disabled. Click it and it a box will pop up asking if you want to enable the monitor. Click OK, and then like magic, your monitor is resurected in it's Windows Glory! From there, adjust the resolution, and it should work perfectly.
This isn't a Boot Camp compatability issue, it's just a problem with the lack of familiarity that users of OS X have with using XP.
Have a nice day!
Message was edited by: BlakeTron
Message was edited by: BlakeTron

Wireless Kernel Panics Fixed with Airport Update

It has been 48 hours - not one kernel panic due to wirless. (and I have downloaded plenty of files, the first thing to trigger shutdown)
My heart has sunk a few times when the LCD looked like the gray veil was about to drop, relief just web page changing. I hope this lasts. The irony is that I love my MBP even more, my faith in Apple has been restored, (bit like making up - lol). I have to mention that Apple Australia were quick to reply to my email. Thank you, Apple.
Very glad I retrieved my MBP before they started taking it apart - it could be that lack of logic board stock actually saved this MBP.
Good Luck all, hope Airport Patch fixes your problem, I am curious, if Apple are aware this patch has fixed this problem, they must know what caused it in the first place.
Karina

nswered

10.5.2 and santa rosa mbp cinema display issue

not only did the update hang... It took disconnecting everything and reseting the pram just to get it past the initial white screen.. once it booted the display on the mbp flickered like 7 times seemingly adjusting it's color profile over and over. I plugged in my 30 inch and it appeared to be working fine.. but then i noticed that the brightness of the display on the santa rosa wasn't responding at all.. and neither were the keyboard keys that usually control the brightness of the cinema display.
So I decided to reboot.. well. what do you know, won't reboot again unless I unplug not only the cinema display, but the firewire and usb extensions that go with it, and my fire800 external... I'm not sure which it is as I'm not going to test it risking anything.. it's something though.. it seems like a power issue... and I'm worried it could get worse.. if i don't restart and unplug everything the fans speed up all the way and it just sits..
I am not going to reboot for a while now.. hopefully until there is a solution.. help?
and not to mention I was hoping for a fix with 10.5.2.. try calibrating your color in expert mode.. there's not even a button on the right slider.. I was told that this in their database, and escalated by two separate geniuses.. over 2 months ago..

not any ideas?

MBP kernel panics on startup - won't get past grey screen

So out of nowhere my unibody MBP (specs, etc below) locked up yesterday while I was watching a video using VLC. It stopped responding to anything so I held down the power button until it turned off. I waited about 10 minutes and turned it back on. Grey screen with spinning cog showed up for about a minute and then kernel panic. Held down power button until it turned off. Tried repeatedly - same results. Won't boot into Safe Mode - still get a kernel panic everytime. It will let me boot the machine into Target Disk Mode. It will boot from my Snow Leopard install disk where I ran Disk Utility and "repaired disk" and "repaired disk permissions" on both the drive and the volume. All the "repair disk" and "repair disk permissions" ended with messages in green type saying that the disk/permissions appear to be OK.
I have an external FW drive used for TM backups for the machine. A fair amount of data has been added since the last TM backup (which was less than 30 days ago) that, ideally, I'd like to not lose by resorting to restoring from a TM backup. It's not the end of the world if the last (roughly) 30 days of data/changes ends up being lost, but I'm willing to work on getting it back up and running without doing an erase and install and then restoring from a TM backup if at all possible.
Definitely if any other information or data is needed from me in order for anyone to assist, please let me know what it is and I'll do my best to provide it.
All help/assistance is greatly appreciated. Thanks in advance!
J
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro5,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.66 GHz
Number of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: MBP51.007E.B06
SMC Version (system): 1.41f2
Below is what comes up when it kernel panics at the grey screen:
panic(cpu 1 caller 0x47f5ad): "Process 1 exec of /sbin/launchd failed, errno 13\n"@/SourceCache/xnu/xnu-1504.15.3/bsd/kern/kern_exec.c:3145
Debugger called: <panic>
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x51383e48 : 0x21b837 (0x5dd7fc 0x51383e7c 0x223ce1 0x0)
0x51383e98 : 0x47f5ad (0x5cf950 0x831c08 0xd 0x0)
0x51383ef8 : 0x4696d2 (0x76e1d20 0x1fe 0x736cee0 0x80000001)
0x51383f38 : 0x48fee5 (0x72b7b7c 0x50f46000 0x51383f88 0x226e2f)
0x51383f68 : 0x219432 (0x72b7b7c 0xffffff7f 0x51383f88 0x2a45c9)
0x51383fa8 : 0x2aacb4 (0xffffffff 0x1 0x22f8f5 0x227c4b)
0x51383fc8 : 0x2a1976 (0x0 0x0 0x2a17ab 0x6e24060)
BSD process name corresponding to current thread: init
Mac OS version:
Not yet set
Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacBookPro5,1 (Mac-F42D86A9)
System uptime in nanoseconds: 69666095555

As (bad) luck would have it, I don't have the discs that came with the machine . Isn't that always the way?
At any rate, I figured that would be a suggestion and searched the web for looking to see if what I need (AHT) could possibly be downloaded. Looks like some folks have found a way/location to download AHT from the web from some of the posts I've seen, but I've come up empty handed.

MBP Kernel Panic when connecting to HDTV (DVI)

I have a 15" MacBook Pro that has been working perfectly since I got it. I tried today to connect it to my Hitachi 51" HDTV (via DVI) and got an instant Kernel Panic. I used my 15" Powerbook with this HDTV without any issues.
I've searched and found folks with kernel panics when waking their MBP if the RAM is faulty, but nothing at all about issues when connecting an external display. I am running with all the latest updates, firmware update, etc.
I don't have any problems connecting to a 23" Cinema display or to a 19" Samsung LCD, but I tried several times to connect to the HDTV and got a kernel panic each time. I changed resolutions on one try and still got the same issue (720x480 so the TV would see it as 480p). I even tried booting up with the display already connected and it kernel panic'd when it tried to switch into the full OS X GUI.
The specific error is in the panic.log is:
Sat Jun 10 16:23:48 2006
panic(cpu 0 caller 0x0019CAEF): Unresolved kernel trap (CPU 0, Type 0=divide error), registers:
CR0: 0x80010033, CR2: 0x35863000, CR3: 0x00d6e000, CR4: 0x000006e0
EAX: 0x00000001, EBX: 0x00000000, ECX: 0x251a36fc, EDX: 0x00000000
ESP: 0x251a360c, EBP: 0x251a36d8, ESI: 0x00000000, EDI: 0x00000000
EFL: 0x00010247, EIP: 0x0078ca44, CS: 0x00000008, DS: 0x0a8c0010
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.kext.ATINDRV(4.2.6)@0x771000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.3)@0x574000
dependency: com.apple.iokit.IONDRVSupport(1.4.3)@0x58f000
com.apple.iokit.IONDRVSupport(1.4.3)@0x58f000
dependency: com.apple.iokit.IOPCIFamily(2.0)@0x565000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.3)@0x574000
So definitely something with the graphics subsystem. Anyone have any hints?
MacBook Pro 2GHz 2GB RAM ATI x1600 256MB Mac OS X (10.4.6)

What happens if you boot from the DVD that came with the MBP instead of booting from your hard drive? It could have something to do with your configuration.

Santa Rosa Macbook fan noise fix, sort of

I don't know how many of you guys noticed this, but when I got the new Santa Rosa MB it was definitely louder than my previous C2D Macbook. Even when idle doing nothing.
I found out that the lowest rpm on the new Santa Rosa goes at 1800, which in a quiet room at night is way to loud personally.
In order to fix it just download fan control 1.2 and then put the lowest RPM setting to 1000. For me that instantly made the MB super quiet again.
Hope that helps to those that wish more silence out of the Santa Rosa books.

I made an appointment at the Apple Store I got it from (4 days after I purchased). I told them about the weird clicking noise and they took it to the back (store was pretty loud) and came back in a few minutes and offered to exchange it since I was within my 14 days. The new one is way quieter and only makes fan noise with intensive processes (as expected). Doing some research after the fact, I believe my issue was the ticking/clicking one described here: http://www.appledefects.com/wiki/index.php?title=MacBook#.22Mooing.22fan_noise.2C_Ticking.2FClicking_Fannoise Overall, they handled it pretty well (I was prepared to field an inquisition about this manufacturing flaw, luckily I didn't have to and they recognized the problem pretty quickly), and I'm finally enjoying my new MacBook.

New SR MBP Kernel Panics?

In the past two days I've had 2 kernel panics during normal use. Looking at the log it doesn't seem like the two are related though. Anyway, I don't remember what I was doing yesterday at the time it happened other than browsing the internet. Today after leaving my computer on and using it sporadically I just opened Camino and the gray screen/multilingual message came up telling me to restart or shut down. It's not like I'm always having problems when I open or run Camino either, since it was working fine earlier in the day.
I ran Disk Utility and repaired the disk and permissions, which found no errors. I also ran the Apple Hardware Test which completed without error. I haven't added anything to my computer in terms of hardware either.
Anyway, the log is as follows:
Mon Jul 2 23:23:43 2007
panic(cpu 0 caller 0x3CAFF808): ntfs_pagein error = 2
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25f6bb68 : 0x128d08 (0x3cc0a4 0x25f6bb8c 0x131de5 0x0)
0x25f6bba8 : 0x3caff808 (0x3cb00658 0x2 0x0 0x20000)
0x25f6bc28 : 0x1e5fc6 (0x25f6bc4c 0x1 0x1000 0x20000)
0x25f6bc88 : 0x374de6 (0x82d3f78 0x4d30cc0 0x0 0x20000)
0x25f6bcf8 : 0x186ecb (0x82d3f78 0x4d30cc0 0x0 0x20000)
0x25f6bd48 : 0x15ee4f (0x771c334 0x20000 0x0 0x1000)
0x25f6bdf8 : 0x16133c (0x5718c38 0x20000 0x0 0x1)
0x25f6bf48 : 0x1a4cc8 (0x5507790 0x3f6000 0x0 0x1)
0x25f6bfc8 : 0x19ade4 (0x54bc220 0x0 0x10 0x0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffd608
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.ntfs(1.2.1)@0x3caf9000
Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386
Wed Jul 4 00:35:35 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x2570dee4, CR3: 0x0134f000, CR4: 0x000006e0
EAX: 0x2570dee0, EBX: 0x05aead68, ECX: 0x072e747c, EDX: 0x00000000
CR2: 0x2570dee4, EBP: 0x2570bb18, ESI: 0x00000008, EDI: 0x2570bdb4
EFL: 0x00010246, EIP: 0x001c4f64, CS: 0x00000008, DS: 0x00000010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2570b8c8 : 0x128d08 (0x3cc0a4 0x2570b8ec 0x131de5 0x0)
0x2570b908 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
0x2570ba18 : 0x19aeb4 (0x2570ba30 0x4d6150 0x2570ba3c 0x1)
0x2570bb18 : 0x1ccb59 (0x2570bdb4 0x2570dee0 0x457fad4 0x2570bf08)
0x2570bb88 : 0x1cd4af (0x2570bdb4 0x100 0x2570bdd4 0x0)
0x2570bc38 : 0x1d91d5 (0x2570bdb4 0x297 0x2570bc68 0x50b8714)
0x2570bd68 : 0x1d9636 (0xbfffed50 0x0 0x0 0x0)
0x2570bf28 : 0x1d96cb (0xbfffed50 0x0 0x0 0x0)
0x2570bf58 : 0x37ad83 (0x48275dc 0x6353408 0x635344c 0x0)
0x2570bfc8 : 0x19b28e (0x4c7b660 0x0 0x19e0b5 0x4c7b660) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffedc8
Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386
What could be causing this problem and what should I do to fix it?
Thanks for the help.
Macbook Pro 2.2ghz SR Mac OS X (10.4.10)

A Kernel Panic is basically a Blue Screen of Death for OS X. You normally get a message and you have to turn the power off and turn it back on.
They are extremely annoying and normally do not happen very often in OS X. The issue can be fixed if Apple Engineers will fix it. However, there is no ETA on a patch.

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.

MBP Kernel Panic - USB issue?

Hi,
We have a MBP mid-2009 model that seems to be undergoing frequent kernel panics, and all the logs show a similar type of report. Can anyone diagnose the following? I think it may be a USB issue.
Interval Since Last Panic Report: 136168 sec
Panics Since Last Report:          1
Anonymous UUID: B4E48BA2-0FCF-4000-B365-B146A4B4F3E2
Tue Jan 17 11:38:31 2012
panic(cpu 0 caller 0x9d4c9b): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0x7face000 0x0a5480a2, D0, P2/4
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x551c1c38 : 0x21b837 (0x5dd7fc 0x551c1c6c 0x223ce1 0x0)
0x551c1c88 : 0x9d4c9b (0xbea28c 0xc5a800 0xbf8e60 0x0)
0x551c1d28 : 0xaef608 (0x8e6b404 0x9268004 0x100 0x29456a)
0x551c1d78 : 0xae6601 (0x9268004 0x100 0x551c1da8 0x9c4778)
0x551c1da8 : 0x16fb9a6 (0x9268004 0x100 0x438004ee 0x1)
0x551c1ee8 : 0xb0e2b5 (0x9268004 0x937a004 0x0 0x0)
0x551c1f28 : 0x9dde7c (0x9268004 0x937a004 0x0 0x0)
0x551c1fc8 : 0x9da55b (0x0 0x9 0x0 0x0)
0x551c2178 : 0x9dc6e7 (0x0 0x600d600d 0x7027 0x551c21a8)
0x551c2248 : 0xc8610d (0xc1d00041 0xbeef0003 0x11334d80 0x71)
0x551c22e8 : 0xc86685 (0x462c1000 0x11334d80 0x10845804 0x0)
0x551c2328 : 0xc5dec3 (0x462c1000 0x11334d80 0x10845804 0x0)
0x551c2358 : 0xc85cba (0x462c1000 0x11334d80 0x10845804 0xca71dc)
0x551c2378 : 0xc5d418 (0x462c1000 0x11334d80 0x10845804 0x1)
0x551c2398 : 0xc86630 (0x462c1000 0x10845800 0x0 0x0)
0x551c23d8 : 0xc60905 (0x462c1000 0x10845800 0x0 0x0)
0x551c2418 : 0xc5e325 (0x462c1000 0x46480000 0x4627d000 0x8dec5c0)
0x551c2468 : 0xcb14e9 (0x462c1000 0x46480000 0x4627d000 0x8dec5c0)
0x551c24f8 : 0xca2c9b (0x8dec5c0 0x112d7800 0x0 0x1)
0x551c2558 : 0xca2f02 (0x46480000 0x46480788 0x112d7800 0x0)
0x551c25a8 : 0xca33d6 (0x46480000 0x46480788 0x551c28cc 0x551c286c)
0x551c28e8 : 0xca01a1 (0x46480000 0x46480788 0x1 0x8bfd800)
0x551c2908 : 0xc6788f (0x46480000 0x46480788 0x0 0x0)
0x551c2938 : 0xca1c64 (0x46480000 0x551c2a7c 0x78d0d234 0x464800d0)
0x551c2978 : 0xc6bc93 (0x46480000 0x551c2a7c 0xc4 0x20000001)
0x551c2ab8 : 0xca55d8 (0x46480000 0x1 0x551c2bcc 0x551c2bc8)
0x551c2b68 : 0xc67fe1 (0x46480000 0x1 0x551c2bcc 0x551c2bc8)
0x551c2be8 : 0x56da06 (0x46480000 0x0 0x551c2e3c 0x551c2c74)
0x551c2c38 : 0x56e2a5 (0xcf6720 0x46480000 0xeab8388 0x1)
0x551c2c88 : 0x56eb59 (0x46480000 0x10 0x551c2cd0 0x0)
0x551c2da8 : 0x286638 (0x46480000 0x10 0xeab8388 0x1)
0x551c3e58 : 0x21dbe5 (0xeab8360 0x873b5a0 0x1fcee8 0x5d43)
0x551c3e98 : 0x210a86 (0xeab8300 0x0 0x93eaea0 0x98193f0)
0x551c3ef8 : 0x216f84 (0xeab8300 0x0 0x0 0x0)
0x551c3f78 : 0x295c57 (0x90a5e68 0x0 0x0 0x0)
0x551c3fc8 : 0x2a256d (0x90a5e64 0x1 0x10 0x90a5e64)
Kernel Extensions in backtrace (with dependencies):
com.apple.GeForce(6.4.0)@0xc5c000->0xd12fff
            dependency: com.apple.NVDAResman(6.4.0)@0x96e000
            dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000
            dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x928000
            dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000
com.apple.nvidia.nv50hal(6.4.0)@0x15c5000->0x19d9fff
            dependency: com.apple.NVDAResman(6.4.0)@0x96e000
com.apple.NVDAResman(6.4.0)@0x96e000->0xc5bfff
            dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x928000
            dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000
            dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
10K549
Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 9331425210758
unloaded kexts:
com.apple.driver.AppleUSBUHCI       4.2.0 (addr 0x1491000, size 0x65536) - last unloaded 181336276515
loaded kexts:
com.apple.driver.AppleBluetoothMultitouch        54.3
com.apple.driver.AppleHWSensor      1.9.3d0
com.apple.filesystems.autofs     2.1.0
com.apple.driver.AGPM     100.12.31
com.apple.driver.AppleMikeyHIDDriver      1.2.0
com.apple.driver.AppleHDA       2.0.5f14
com.apple.driver.AppleUpstreamUserClient        3.5.7
com.apple.driver.AppleMCCSControl         1.0.20
com.apple.driver.AppleMikeyDriver    2.0.5f14
com.apple.driver.AudioAUUC    1.57
com.apple.driver.AppleIntelHDGraphics     6.4.0
com.apple.driver.AppleIntelHDGraphicsFB         6.4.0
com.apple.driver.SMCMotionSensor 3.0.1d2
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AudioIPCDriver        1.1.6
com.apple.driver.ACPI_SMC_PlatformPlugin     4.7.0a1
com.apple.GeForce   6.4.0
com.apple.driver.AppleGraphicsControl     2.10.6
com.apple.driver.AppleLPC        1.5.1
com.apple.kext.AppleSMCLMU 1.5.2d10
com.apple.driver.AppleUSBTCButtons       201.6
com.apple.driver.AppleUSBCardReader    2.6.1
com.apple.driver.AppleUSBTCKeyboard    201.6
com.apple.driver.AppleIRController    303.8
com.apple.BootCache        31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib     1.0.0d1
com.apple.iokit.SCSITaskUserClient 2.6.8
com.apple.iokit.IOAHCIBlockStorage 1.6.4
com.apple.driver.AppleUSBHub         4.2.4
com.apple.driver.AppleFWOHCI         4.7.3
com.apple.driver.AirPortBrcm43224   428.42.4
com.apple.iokit.AppleBCM5701Ethernet    3.0.5b8
com.apple.driver.AppleEFINVRAM    1.4.0
com.apple.driver.AppleSmartBatteryManager     160.0.0
com.apple.driver.AppleAHCIPort        2.1.7
com.apple.driver.AppleUSBEHCI       4.2.4
com.apple.driver.AppleACPIButtons 1.3.6
com.apple.driver.AppleRTC        1.3.1
com.apple.driver.AppleHPET     1.5
com.apple.driver.AppleSMBIOS          1.7
com.apple.driver.AppleACPIEC 1.3.6
com.apple.driver.AppleAPIC      1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 142.6.0
com.apple.security.sandbox       1
com.apple.security.quarantine   0
com.apple.nke.applicationfirewall      2.1.14
com.apple.driver.AppleIntelCPUPowerManagement 142.6.0
com.apple.driver.AppleUSBHIDKeyboard 141.5 - last loaded 104418465449
com.apple.driver.AppleBluetoothHIDKeyboard 141.5
com.apple.driver.AppleHIDKeyboard 141.5
com.apple.driver.IOBluetoothHIDDriver      2.4.5f3
com.apple.driver.AppleMultitouchDriver     207.11
com.apple.driver.DspFuncLib    2.0.5f14
com.apple.driver.AppleProfileReadCounterAction      17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction      10
com.apple.driver.AppleProfileKEventAction        10
com.apple.driver.AppleProfileCallstackAction    20
com.apple.driver.AppleSMBusController    1.0.10d0
com.apple.iokit.IOFireWireIP      2.0.3
com.apple.iokit.IOSurface 74.2
com.apple.iokit.IOBluetoothSerialManager         2.4.5f3
com.apple.iokit.IOSerialFamily   10.0.3
com.apple.iokit.IOAudioFamily 1.8.3fc2
com.apple.kext.OSvKernDSPLib        1.3
com.apple.driver.AppleHDAController        2.0.5f14
com.apple.iokit.IOHDAFamily    2.0.5f14
com.apple.iokit.AppleProfileFamily    41
com.apple.driver.IOPlatformPluginFamily 4.7.0a1
com.apple.driver.AppleSMBusPCI     1.0.10d0
com.apple.driver.AppleBacklightExpert      1.0.1
com.apple.driver.AppleSMC       3.1.0d5
com.apple.nvidia.nv50hal 6.4.0
com.apple.NVDAResman 6.4.0
com.apple.iokit.IONDRVSupport         2.2.1
com.apple.iokit.IOGraphicsFamily      2.2.1
com.apple.driver.BroadcomUSBBluetoothHCIController     2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController   2.4.5f3
com.apple.iokit.IOBluetoothFamily     2.4.5f3
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.8
com.apple.iokit.IOUSBMassStorageClass 2.6.7
com.apple.driver.AppleUSBMultitouch       207.7
com.apple.iokit.IOUSBHIDDriver        4.2.0
com.apple.driver.AppleUSBMergeNub       4.2.4
com.apple.driver.AppleUSBComposite       3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice          2.6.8
com.apple.iokit.IOBDStorageFamily   1.6
com.apple.iokit.IODVDStorageFamily         1.6
com.apple.iokit.IOCDStorageFamily   1.6.1
com.apple.driver.XsanFilter        402.1
com.apple.iokit.IOAHCISerialATAPI   1.2.6
com.apple.iokit.IOSCSIArchitectureModelFamily         2.6.8
com.apple.iokit.IOFireWireFamily       4.2.6
com.apple.iokit.IOUSBUserClient       4.2.4
com.apple.iokit.IO80211Family 320.1
com.apple.iokit.IONetworkingFamily 1.10
com.apple.iokit.IOAHCIFamily   2.0.6
com.apple.iokit.IOUSBFamily     4.2.4
com.apple.driver.AppleEFIRuntime    1.4.0
com.apple.iokit.IOHIDFamily      1.6.6
com.apple.iokit.IOSMBusFamily         1.1
com.apple.kext.AppleMatch        1.0.0d1
com.apple.security.TMSafetyNet         6
com.apple.driver.DiskImages     289
com.apple.iokit.IOStorageFamily         1.6.3
com.apple.driver.AppleACPIPlatform 1.3.6
com.apple.iokit.IOPCIFamily      2.6.5
com.apple.iokit.IOACPIFamily    1.3.0

Under the keyboard, hey? So you have a Titanium Powerbook. You should update your profile to include the model and CPU size of your Powerbook to help get more accurate assistance. Crucial is a reputable brand of RAM. They also offer a lifetime warranty.
The clips: I used to have a Titanium Powerbook, but it was a few years ago. If MY memory serves me right the clips move to the outside of the RAM modules. Due to the heat and never being removed they may have semi-welded themselves into position. One trick would be to heat the computer up and try to remove them while it is warm/hot. Just plug it in and run some CPU intensive apps for a while, then turn it off, remove the battery, ground the computer and give them another try. Grounding (earthing) the computer to remove static is not difficult. After you have removed the battery just touch the metal case and grab a metal window or door frame. That will ground any static in the machine. Also, if you are working on carpet take your shoes and socks off to avoid more static build up. You could even go as far to stand on a rubber bathroom mat while working on the computer, but replacing RAM should only take a few minutes. If you still have difficulties getting the RAM stick out go to a site called The Powerbook Medic and look for tips on removing sticks from a Titanium.
Hope the new RAM stops the panics.
SR.

1 Kernel Panic Fix - Downgrade Motu Driver

Just wanted to add a topic to the forums to let people know about an issue I've discovered with the audio drivers from MOTU.
It seems as though their latest driver update (1.4.7) for any of the firewire consoles (entitled - *MOTU 828/896/828mk2/896HD/Traveler - 1.4.7*) is not compatible with OS 10.4.x Tiger. After installing this driver the system may have a classic kernel panic after a restart.
All you need to do is un-install version 1.4.7 of the driver and download + install version 1.4.1 available here
Hope this helps anyone with a similar issue. It seems a common cause for kernel panics is an incompatible driver for 3rd party hardware.

Thanks for the tip.

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

Similar Messages

Maybe you are looking for