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

SamIchi

macrumors 68030
Original poster
Aug 1, 2004
2,716
137
I've been getting them a lot lately. I don't know what's causing it. Maybe someone who knows more about this stuff can decode this and tell me what the problem might be. In the first week of Leopard it was because of Azureus, but then I switched clients, and worked well until this week it's been acting up... Does this tell me anything?

Mon Dec 3 21:57:22 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)
0x53a57708 : 0x12b0e1 (0x455670 0x53a5773c 0x133238 0x0)
0x53a57758 : 0x39cd77 (0x48e03c 0x1 0x5394a01c 0xa05180)
0x53a57798 : 0x39d073 (0x301bdb00 0x53a577a0 0x53a577a8 0x52a79380)
0x53a577b8 : 0x9f5821 (0x301bdb00 0x0 0x20 0xa51f1c)
0x53a578e8 : 0x9fe9e5 (0x1 0x0 0x52a4a170 0x52a793fc)
0x53a57c08 : 0xa0393a (0x23bfa2c8 0x0 0x366b003 0xc845232d)
0x53a57de8 : 0xa04fb1 (0x23bfa2c8 0x0 0x53a57f08 0x127206)
0x53a57f18 : 0x41d149 (0x23bfa000 0x4422f00 0x1 0x19ccc1)
0x53a57f68 : 0x41c2a6 (0x4422f00 0x0 0x0 0x0)
0x53a57f98 : 0x41bf88 (0x42f6ec0 0x0 0x53a57fc8 0x125f51)
0x53a57fc8 : 0x19e2ec (0x42f6ec0 0x0 0x1a10b5 0x482efb4)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(300.22)@0x9d0000->0xa5afff
dependency: com.apple.iokit.IO80211Family(200.7)@0x8c3000
dependency: com.apple.iokit.IOPCIFamily(2.4)@0x67c000
dependency: com.apple.iokit.IONetworkingFamily(1.6.0)@0x68c000

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: MacBook1,1 (Mac-F4208CC8)
 
com.apple.driver.AirPort.Atheros(300.22)@0x9d0000->0xa5afff
dependency: com.apple.iokit.IO80211Family(200.7)@0x8c3000
dependency: com.apple.iokit.IOPCIFamily(2.4)@0x67c000
dependency: com.apple.iokit.IONetworkingFamily(1.6.0)@0x68c000

I believe your problem is airport.

Are you connected wirelessly?

Can you connect via cable and see if the problem is still there.

Turn off your wireless before putting it to sleep to see if that helps.

Perhaps Azureus wasn't the problem but exacerbating it.
 
com.apple.driver.AirPort.Atheros(300.22)@0x9d0000->0xa5afff
dependency: com.apple.iokit.IO80211Family(200.7)@0x8c3000
dependency: com.apple.iokit.IOPCIFamily(2.4)@0x67c000
dependency: com.apple.iokit.IONetworkingFamily(1.6.0)@0x68c000

I believe your problem is airport.

Are you connected wirelessly?

Can you connect via cable and see if the problem is still there.

Turn off your wireless before putting it to sleep to see if that helps.

Perhaps Azureus wasn't the problem but exacerbating it.

Hmm... Yea I connect wirelessly. Ethernet doesn't reach up to my room. Could it be because of too much bandwidth being used up?
 
Hmm... Yea I connect wirelessly. Ethernet doesn't reach up to my room. Could it be because of too much bandwidth being used up?

It is down to a bad driver/bad hardware (might want to phone apple). All the bandwidth usage would be doing is making it more frequent, it isn' the root cause of the problem.
 
It is down to a bad driver/bad hardware (might want to phone apple). All the bandwidth usage would be doing is making it more frequent, it isn' the root cause of the problem.

More than likely a bad driver problem on Apple's end, one of the big issues that Apple really needs to deal with.

Apple has finally been dealing with the issues nobody ever thought they'd take care of Nvidia-ATI conflict on Mac Pro, PCI deep sleep (took years), and these Airport issues that keep requiring patches on the router end ...
 
It is down to a bad driver/bad hardware (might want to phone apple). All the bandwidth usage would be doing is making it more frequent, it isn' the root cause of the problem.

I didn't have this problem when I had Tiger. Does Leopard have anything to do with it?
 
More than likely a bad driver problem on Apple's end, one of the big issues that Apple really needs to deal with.

That is what I was thinking especially with leopard release however I just wanted them to be fully aware of all the possibilities.

I didn't have this problem when I had Tiger. Does Leopard have anything to do with it?

Chances are that apple changed the driver in Leopard and it is buggy and you are seeing the result of this.
 
Not waking: looks familiar to me

Hi,
I had problems too with a computer not wanting to wake up.
Do you use bluetooth?
I figured out that in my case bluetooth is the problem. Combined with 10.5.1 it makes my mac freeze after a while and i have to do a forced reboot.
I have temporarily disconnected my bluetooth adapter and use my wired mouse again, hopefully in 10.5.2 the problem will be solved.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.