Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Arip

macrumors regular
Original poster
Nov 22, 2005
186
0
Buenos Aires, Argentina
Since i upgraded my system (fresh clean install) to leopard, i've noticed that it was more reliable with tiger

a few days ago, i left my MBP turned on for the night, and since then, every night i left it turned on, the MPB doesn't respond when i came back:

this is the legend that appears after a hard reset:

Code:
Tue Dec  4 11:55:43 2007
panic(cpu 0 caller 0x0039CD77): "m_free: freeing an already freed mbuf"@/SourceCache/xnu/xnu-1228.0.2/bsd/kern/uipc_mbuf.c:2742
Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x3421b708 : 0x12b0e1 (0x455670 0x3421b73c 0x133238 0x0) 
0x3421b758 : 0x39cd77 (0x48e03c 0x1 0x4033601c 0x3421b768) 
0x3421b798 : 0x39d073 (0x3021f100 0x3421b7a0 0x3421b7a8 0x4032d298) 
0x3421b7b8 : 0x905821 (0x3021f100 0x0 0x20 0x961f1c) 
0x3421b8e8 : 0x90e9e5 (0x1 0x0 0x402f2610 0x4032d314) 
0x3421bc08 : 0x91393a (0x23a082c8 0x0 0x0 0x2) 
0x3421bde8 : 0x914fb1 (0x23a082c8 0x1 0x14274003 0x0) 
0x3421bf18 : 0x41d149 (0x23a08000 0x41cac00 0x1 0x19ccc1) 
0x3421bf68 : 0x41c2a6 (0x41cac00 0x48bbf64 0x48bbf3c 0x13ea59) 
0x3421bf98 : 0x41bf88 (0x41c3580 0x0 0x44609a0 0x3c37998) 
0x3421bfc8 : 0x19e2ec (0x41c3580 0x0 0x1a10b5 0x48bbf20) 
Backtrace terminated-invalid frame pointer 0
      Kernel loadable modules in backtrace (with dependencies):
         com.apple.driver.AirPort.Atheros(300.22)@0x8e0000->0x96afff
            dependency: com.apple.iokit.IO80211Family(200.7)@0x8c2000
            dependency: com.apple.iokit.IOPCIFamily(2.4)@0x648000
            dependency: com.apple.iokit.IONetworkingFamily(1.6.0)@0x658000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9B18

Kernel version:
Darwin Kernel Version 9.1.0: Wed Oct 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386
System model name: MacBookPro1,1 (Mac-F425BEC8)


Can any one help me?
 
Based on the log you posted, something AirPort-related is causing a kernel panic in Leopard. Since I'm not sure if the root cause is software- or hardware-related, I'll just give the generic advice for solving Mac problems:

Have you applied all the updates for Leopard? Several have been released since the initial retail launch.
Have you verified your hard disk, and fixed any errors that were found?
Have you ever booted your Mac in verbose mode? This gives a bunch of diagnostic information that can be useful in solving problems. (To invoke verbose mode hold down both the Command (sometimes called the clover or apple key) and the V key immediately after you hear the startup chime, and release them after text starts to appear.)
 
Based on the log you posted, something AirPort-related is causing a kernel panic in Leopard. Since I'm not sure if the root cause is software- or hardware-related, I'll just give the generic advice for solving Mac problems:

Have you applied all the updates for Leopard? Several have been released since the initial retail launch.
Have you verified your hard disk, and fixed any errors that were found?
Have you ever booted your Mac in verbose mode? This gives a bunch of diagnostic information that can be useful in solving problems. (To invoke verbose mode hold down both the Command (sometimes called the clover or apple key) and the V key immediately after you hear the startup chime, and release them after text starts to appear.)


thanks wrldwzrd89!
i had installed all Leopard updates
Ive done disk repair and also repaired permissions

but i have never booted up in verbose mode, ill do it right now

again, thanks for the help!
 
When you booted verbosely, did you notice anything similar to what you saw in the log you posted above?
Also, check Console for relevant error messages - these will also give me some clues as to what's going on. Console is the Mac OS X log viewer, and is located in your Utilities folder.
 
i dont know what to look on the Console Log


i got my mbp tilt again right now while i was listening to itunes

and when i restarted it, i got the same error windows, with the same log


im getting crazy, dont know what to do, should i go back to tiger?

i spent 300 buks on Leopard, and i want to kill myself!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.