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

Kernel Panic --Help?

B

Browzilla

macrumors member
Original poster
Aug 6, 2007
39
0
So I was doing, well, nothing much. Macbook Pro, 2.2 standard config. Adium, Firefox, iTunes running, and it made me reboot, then I got this.

Code: 
panic(cpu 0 caller 0x003BEE66): OSObject::refcount: Attempting to retain a freed object
Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0x25e8bbb8 : 0x128d08 (0x3cc0ec 0x25e8bbdc 0x131de5 0x0) 
0x25e8bbf8 : 0x3bee66 (0x3f2670 0x3f264c 0x4d70cc4 0x493a680) 
0x25e8bc18 : 0x3c1cf1 (0x4d70cc0 0x4b0958 0x38 0x3c197a) 
0x25e8bc48 : 0x3c1e4a (0x4c25780 0x493a680 0x0 0x3c20a5) 
0x25e8bc68 : 0x3c2840 (0x493a680 0x0 0x0 0x0) 
0x25e8bca8 : 0x3c28ad (0x493a680 0x4d0c180 0x4d19a00 0x1628d8) 
0x25e8bce8 : 0x3875d8 (0x4938fc0 0x0 0x25e8bd28 0x3c1fb8) 
0x25e8bd08 : 0x38adf7 (0x4931580 0x4c23480 0x0 0x4931580) 
0x25e8bd28 : 0x3b23e4 (0x4931580 0x4c23480 0x25e8bd58 0x3bef8f) 
0x25e8bd78 : 0x188511 (0x4931580 0x553ccb4 0x553ccc8 0x11cc32) 
0x25e8bdb8 : 0x12b4c3 (0x4ffd1b4 0x553cc98 0x0 0x0) 
0x25e8bdf8 : 0x124b17 (0x4ffd100 0x0 0x18 0x25e8bedc) 
0x25e8bf08 : 0x195a42 (0x25e8bf44 0x0 0x0 0x0) 
0x25e8bfc8 : 0x19b32e (0x5200bc0 0x0 0x19e0b5 0x440f1e8) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb011e428

Kernel version:
Darwin Kernel Version 8.10.3: Wed Jun 27 23:29:36 PDT 2007; root:xnu-792.23.3~1/RELEASE_I386

Model: MacBookPro3,1, BootROM MBP31.0070.B02, 2 processors, Intel Core 2 Duo, 2.2 GHz, 2 GB
Graphics: GeForce 8600M GT, GeForce 8600M GT, PCIe, 128 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), 1.1.9.3
Bluetooth: Version 1.9.1f18, 2 service, 0 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5
Serial ATA Device: FUJITSU MHW2120BH, 111.79 GB
Parallel ATA Device: HL-DT-ST DVDRW  GSA-S10N
USB Device: Built-in iSight, Apple Inc., Up to 480 Mb/sec, 500 mA
USB Device: Keyboard Hub, Apple, Inc., Up to 480 Mb/sec, 500 mA
USB Device: USB Receiver, Logitech, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Keyboard, Apple, Inc, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 1.5 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA

Only recent changes I've made were installing and configuring a mouse driver about an hour ago. It worked fine for that hour or so though...I don't know whether or not it's related.

Anyone know what caused this? Freak occurence or will this potentially be a repeating thing?
 
From the Panic :

USB Device: USB Receiver, Logitech, Up to 1.5 Mb/sec, 100 mA

That's a bit slow for USB 2.0.Even though USB is backwards compatible the OP may have something thats USB 2.0 plugged into the 1.1 Logitech device and the kernel panicked when it couldn't reconnect it.

Just a guess like I said..Don't shoot me please.:)

In any case I'd disconnect the Logitech device and re-boot.
Process of elimination.
 
Peace said:
From the Panic :

USB Device: USB Receiver, Logitech, Up to 1.5 Mb/sec, 100 mA

That's a bit slow for USB 2.0.Even though USB is backwards compatible the OP may have something thats USB 2.0 plugged into the 1.1 Logitech device and the kernel panicked when it couldn't reconnect it.

Just a guess like I said..Don't shoot me please.:)
Click to expand...
I still don't see Logitech as the cause from the panic log.

Input devices show up at 1.5 MB/s in OS X.

I understand that the mouse drivers were installed recently. There aren't any references to the input devices in the log though.
 
Peace said:
Yes there is.I misunderstood the Logitech input device as a hub rather than a mouse.

It's probably the Logitech mouse driver then.
Click to expand...
I see how you misunderstood me. Yes, the wireless device receiver is listed. I don't see any mention of the driver though. I don't think it's the direct cause of the kernel panic.

I've imaged the Logitech Control Center onto at least 50 different machines with no problems at all. I wouldn't be so quick to blame them. ;)
 
In all my experiences, Logitech usually works fine. The drivers all seem to run right, I downloaded them from their site today, so they're new, and the mouse works fine.

It may matter, it may not, but the mouse is running through the new aluminum keyboard's USB ports.
 
Logitech has its problems... However the Logietch problem usually shows up in Console. The list of data at the bottom of the posted log is a reference to the machine's specifications, not necessarily the error. Nevertheless, the wise young Peace is right in that trial and error or a process of elimination is usually the easiest way to find the culprit. :)
 
And I can say the same on the other end.

I agree with removing all peripherals in an attempt to isolate it. I've found that the top of the error report is a bit more important here. :p
 
mad jew said:
Agreed! :D

After removing the mouse and drivers I'd probably swap out the RAM to test if there's a bad stick. :)
Click to expand...
Good grief someone has one kernel panic and we need to disassemble the machine, right?

Might as well throw in a repair disk permissions as well. :rolleyes:

I'd wait to see if there's a recurrence before taking any drastic action.

Peace said:
Really?
:D

I still say the Logitech device is the problem.

Lets put a side bet on it shall we? :p
Click to expand...
Fine by me.
 
Fair call. I usually let the first one slide, although I haven't had even one for quite some time... That number combination seems to usually correlate with RAM though, in my small and very limited experience. Azuerus also places the RAM under a bit of strain and so that's when I'd expect to see RAM-related kernel panics, if ever. Browzilla kinda asked what we thought the cause might be so I'm just putting this out there... ;)

Alternatively I guess Browzilla could mash it with a hammer and take it back to Apple claiming it was attacked by a giant Dell-wielding sperm whale. Those things can be vicious. I saw one eat a whole family of kelp once! I'll admit I don't like his chances of getting it replaced after that though.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back