Kernel Panic (Leopard 10.5.2 - iMac 1 month old!)

[miciolina]

Hi, I'm new to mac, I started about a month ago with my lovely iMac: 2.4ghz Intel Core Duo 4 GB RAM running Mac OS X Leopard 10.5.2.
This kernel panic happens randomly like perhaps a few times a day (sometimes more) when I do every kind of things.

Here is the report i got once i restarted my iMac;

Tue May 13 16:40:27 2008
panic(cpu 1 caller 0x0031678A): "btree_swap_node: about to write corrupt node!\n"@/SourceCache/xnu/xnu-1228.4.31/bsd/hfs/hfs_btreeio.c:197
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x5b02b7f8 : 0x12b0f7 (0x4581f4 0x5b02b82c 0x133230 0x0)
0x5b02b848 : 0x31678a (0x484588 0xeb90f80 0x1 0x23ac6252)
0x5b02b888 : 0x1fa244 (0x56c8fcf0 0x7f05804 0x0 0x0)
0x5b02b948 : 0x1fab7f (0x0 0x5b02b96c 0x0 0x0)
0x5b02b988 : 0x33e2eb (0x6a78e08 0x1 0x2 0x488694)
0x5b02ba18 : 0x32d22e (0xee83710 0x1 0x1 0x6b4de40)
0x5b02ba98 : 0x1f6039 (0x5b02bac8 0x246 0x5b02baf8 0x1da207)
0x5b02baf8 : 0x367ea6 (0xee83710 0x33 0x0 0x0)
0x5b02bf78 : 0x3dcf13 (0x6b4de40 0x7480680 0x74806c4 0x7662048)
0x5b02bfc8 : 0x19f1c3 (0x75ff4e0 0x0 0x1a20b5 0x78cf3c8)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb05928b8

BSD process name corresponding to current thread: mds

Mac OS version:
9C7010

Kernel version:
Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
System model name: iMac7,1 (Mac-F42386C8)

I'd sincerely appreciate if someone can help me out, because I don't know what's happening and I'm getting worried about my data.
Many thanks to everybody.



HELP! Happened again a minute ago...

Tue May 13 17:41:43 2008
panic(cpu 1 caller 0x0031678A): "btree_swap_node: about to write corrupt node!\n"@/SourceCache/xnu/xnu-1228.4.31/bsd/hfs/hfs_btreeio.c:197
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x54f57ca8 : 0x12b0f7 (0x4581f4 0x54f57cdc 0x133230 0x0)
0x54f57cf8 : 0x31678a (0x484588 0xc025d80 0x1 0x2000)
0x54f57d38 : 0x1fa244 (0x56c50630 0x7f94004 0x0 0x0)
0x54f57df8 : 0x1fab7f (0x0 0x2 0x54f57e38 0x327686)
0x54f57e38 : 0x3331b2 (0x6b08e08 0x52124c 0x0 0x6bb7e70)
0x54f57ea8 : 0x1f6791 (0x7703260 0x2 0x6613144 0x1f5d49)
0x54f57ee8 : 0x1e022c (0x7703260 0x2 0x6613144 0x0)
0x54f57f08 : 0x1daf8d (0x7703260 0x0 0x1 0x13696d)
0x54f57f48 : 0x1e0261 (0x1 0x1e01f4 0x0 0x138eb7)
0x54f57f78 : 0x3dcf13 (0x6bb7e70 0x6613040 0x6613084 0x685a4f0)
0x54f57fc8 : 0x19f1c3 (0x6618f80 0x1 0x1a20b5 0x7144000)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffff18

BSD process name corresponding to current thread: update

Mac OS version:
9C7010

Kernel version:
Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
System model name: iMac7,1 (Mac-F42386C8)

 

[ElectricSheep]

Boot off of the Mac OS X install disk and run Disk Utility. I may fail if the secondary catalog is also corrupt. If that happens, its time to copy as much data as you can off the drive and reformat it.

 

[theBB]

If it is only one month old, i would contact Apple. They can walk you through the debugging process. You might want to back up your files if you have not already done so before calling. There might be a hardware problem.

 

[miciolina]

If it is only one month old, i would contact Apple. They can walk you through the debugging process. You might want to back up your files if you have not already done so before calling. There might be a hardware problem.

Solved! Many thanks to everybody!
The problem was the Time Machine. I don't know why, but when TM starts, the system crashes.
Now I'm expecting some reason from Apple...

 

[ElectricSheep]

Turning off Time Machine may have only made the symptoms disappear, not the underlying problem. Have you run Disk Utility to verify all of your connected drives? I stress this because this error:

btree_swap_node: about to write corrupt node!

Indicates that one of your drives has a corrupt filesystem.

 

[merl1n]

Turning off Time Machine may have only made the symptoms disappear, not the underlying problem. Have you run Disk Utility to verify all of your connected drives? I stress this because this error:



Indicates that one of your drives has a corrupt filesystem.

I agree. The disk you are using for TM is hosed.

You can try using Disk Utility -> First Aid -> repair disk to try to fix it. If it fails, you can try to reformat it. If you select the disk (the physical device, not the volume) and click on the "info" button, see what the Partition Map states...if it is "master boot record" (or something like that), I suggest re-formatting by going to the partition tab, change "current" to "1 partition" (this enables the "options" button), go into options and select GUID partition scheme. Click ok and then apply. If it completes the format with no errors, you are good to go. If it fails the format, your disk has major problems (mechanical failure, bad media, etc.) and you should use another disk for TM backups.

 

[nrgband]

kernel panic

I have the same exact thing happening. Took my macbook pro 2.16 in to apple. They could not find the problem and suggested I have a bad drive.

Here's the thing though....

Last night I just backed up to a new LaCie Drive and rebooted from that drive. As soon as I run a TimeMachine backup the computer crashes, even from the LaCie drive. It seems to me there is some issue with TimeMachine.

I have TimeMachine running on 2 other computers and it works fine.

Any ideas on clearing out TimeMachine settings and preferences?

Thanks
Andy

 

[merl1n]

I have the same exact thing happening. Took my macbook pro 2.16 in to apple. They could not find the problem and suggested I have a bad drive.

Here's the thing though....

Last night I just backed up to a new LaCie Drive and rebooted from that drive. As soon as I run a TimeMachine backup the computer crashes, even from the LaCie drive. It seems to me there is some issue with TimeMachine.

I have TimeMachine running on 2 other computers and it works fine.

Any ideas on clearing out TimeMachine settings and preferences?

Thanks
Andy

/Library/Preferences/com.apple.TimeMachine.plist

 

[IJ Reilly]

Sorry, but reformatting is bad advice. Didn't anyone else notice that this Mac has 4 GB of RAM? Are we forgetting that the single, most common cause of kernel panics is bad RAM?

Try removing one RAM stick (I assume you have two), and see if the problem persists. If it does, try the other one alone. If you have the original RAM, try that one alone also.

Do not reformat. Please.

 

[SaSaSushi]

Sorry, but reformatting is bad advice. Didn't anyone else notice that this Mac has 4 GB of RAM? Are we forgetting that the single, most common cause of kernel panics is bad RAM?

Try removing one RAM stick (I assume you have two), and see if the problem persists. If it does, try the other one alone. If you have the original RAM, try that one alone also.

Do not reformat. Please.

If the OP's machine is crashing with the error:

panic(cpu 1 caller 0x0031678A): "btree_swap_node: about to write corrupt node!\n"@/SourceCache/xnu/xnu-1228.4.31/bsd/hfs/hfs_btreeio.c:197

which clearly indicates that the file system on the backup media is corrupt and causing the kernel panic, furthermore turning OFF Time Machine stops the kernel panics WHY would he have any cause to suspect his RAM?

Try first aid on the drive in Disk Utility.

Failing that reformat the drive you're using for Time Machine.

 

[Sun Baked]

All problems with time machine, even though the first crash looked like a spotlight update during the backup process.

Though likely even turning off spotlight on that drive likely will only reduce one of the issues.

 

[nrgband]

Kernel Panic (Leopard 10.5.2 - iMac 1 month old!)

I ran timemachine off of my original drive but backed up to a different drive other then then my time capsule. no problems....

I am doing a disk repair on the time capsule. If this does not work I will dump the backup on the time capsule and star a new file.

I know it's got to be in the backup file because my 2 other computers are not having a problem.

Running disk utility on Time capsule takes quite a while....

 

[IJ Reilly]

which clearly indicates that the file system on the backup media is corrupt and causing the kernel panic, furthermore turning OFF Time Machine stops the kernel panics WHY would he have any cause to suspect his RAM?

Fine, if you're totally certain -- but I'd have to ask how a corrupted backup drive could cause a kernel panic. This should certainly not be possible unless Apple made a huge programming error with Time Machine. Frequent kernel panics are more often the result of RAM issues than any other cause. That, and the fact that this Mac's RAM was upgraded, gives me cause to suspect it.

 

[nrgband]

Fixed the Problem!

The issue is with the .sparsebundle file on you backup drive. Remove that file and start a new backup and the kernel issue will be resolved.

 

[Panos D.]

Similar problem

Hi guys,

Sorry to bring this issue back but I have a similar problem with you, however after calling twice Apple i couldn t get any specific answer to what is happening to my mini mac. Here is a briefing of what happened...

I bought the mini with Tiger just before Leopard was released. It had 1gb of RAM but on the spot I asked them to upgrade it with 1 more so in total I have 2 gb now. Then I bought from apple Leopard a few days later and did and upgrade. The mac mini was working fine for almost a year but recently it started to crash with the screen going grey and a message saying "you need to restart your computer by holding down the switch on button" in several languages. This is a kernel panic as far as I know.

I decided to go for an archive and install of Leopard but the problem persisted. I then did a clean install (Leopard) but after a few days -and after installing all the programmes I had before- the same again with kernel panics. I run the hardware test -the short one/2mins- and everything appeared to be fine. I cleaned the cache and cookies with Onyx and still nothing. I run a software called preferential treatment and checked for system preferences problems. It found some and i deleted them. Of course I run disk utility and repaired permissions several times but again nothing. A guy from Apple told me to re-install Tiger and then upgrade to Leopard but I haven t done that.

It looks like that the Mac mini crashes when 5-7 applications are running. I used to work with many applications open but I never had this problem. Can it be a hardware problem?

The kernel panic report is as follows. Any help would be appreciated.

Fri Mar 27 15:51:37 2009
panic(cpu 1 caller 0x003AAF91): "sbflush: sb 0x4e9956c so 0x4e994c8 cc 0 mbcnt 0 mb 0x10000 mbtail 0 " "lastrecord 0x50000\n"@/SourceCache/xnu/xnu-1228.9.59/bsd/kern/uipc_socket2.c:1220
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x34137cf8 : 0x12b4f3 (0x45b13c 0x34137d2c 0x1335e4 0x0)
0x34137d48 : 0x3aaf91 (0x496450 0x4967c4 0x4e9956c 0x4e994c8)
0x34137d88 : 0x3aafd1 (0x4e9956c 0x216 0x34137de8 0x3b08b4)
0x34137da8 : 0x3a57b3 (0x4e9956c 0x0 0x1000246 0x2)
0x34137dd8 : 0x3a5835 (0x4e994c8 0x0 0x34137df8 0x0)
0x34137df8 : 0x3a6f5f (0x4e994c8 0x9 0x0 0x0)
0x34137e58 : 0x3a6fab (0x4e994c8 0x1 0x1d000 0x0)
0x34137e78 : 0x368add (0x4e994c8 0x34137ec8 0x0 0x0)
0x34137ee8 : 0x368ece (0x43f3670 0x58fd7b8 0x467f4f4 0x2)
0x34137f28 : 0x368f8a (0x0 0x43 0x34137f5c 0x1)
0x34137f78 : 0x3df460 (0x467f4f4 0x468bd40 0x468bd84 0xb41aac4)
0x34137fc8 : 0x1a0887 (0x43b14c0 0x0 0x1a30b5 0x43ae998)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffef28

BSD process name corresponding to current thread: launchd

Mac OS version:
9G55

Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
System model name: Macmini2,1 (Mac-F4208EAA)

Mac Mini Mac OS X (10.5.6) 1.83 Ghz / Intel Core 2 Duo / 2 GB

 

[merl1n]

It's hard to deduce what's happening from the Panic info.

Try these:

1. Do an SMC reset by disconnecting everything from the mini (including power) and waiting at least 15 seconds. Then connect only Power, keyboard, mouse and display (I don't know if you have any peripherals attached, but leave them disconnected).

2. Reset your PRAM.

3. Boot from the original DVD that came with your Mini and run the extended Apple Hardware tests.

4. Boot "Safe Boot" mode.

5. Boot normally and try duplicating the problem. If your Mini crashes again, post the new Kernel Panic info as well as the System log entries.

6. If all is well (no kernel panics), connect your external devices one at a time and repeat step 5.

A good utility to install is "AppleJack" and it's free. Once installed, you can run it in Single User Mode from the command line and do a complete test of your memory.

 

[Panos D.]

Thank you for the advice,

I followed your instructions, reset the PRAM and booted in safe mode, connected the external devices one by one.

The panics happen out of nowhere (at least once a week) so nothing happened yet. The fact is that when I did an erase and install of Leopard all my external devices where connected in the mini and that can mess up the set up of drives. I had totally forgotten about unplugging them. that s where these KP might come from. I hope I ll find out soon...

 

[chanmoss]

ipod causes kernel panic macbook pro 10.5.6

I got the 3rd generation ipod shuffle and plugged it into my computer and my computer had a kernel panic. I had to force restart. Turns out it was kernel panic when I plugged in my 30 gig video ipod, but my iphone was fine for whatever reason. To make a LONG story short (including prematurely having apple send me a new ipod shuffle--my bad), I called apple a bunch of times and we finally fixed my computer (and simultaneously the problem) by archive and reinstalling leopard from the disk (saving my user settings). Before doing this I tried: completely uninstalling itunes, including various preferences and such, reinstalling itunes, running disk utility for permissions and disk utility both in and out of safe mode, zapped perimeter ram, did the power reset thing, i feel like there was more too... lots of time on the phone with apple, lots of hassle, but the archive and reinstall seems to have worked. None of my ipods are giving me kernel panics anymore-Yay!

 

[laeeqhumam]

Try this option

Try this
hopefully ull get some insight.