Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: Remco Douma
Remco Douma Author
User level: Level 1
5 points

OSX 10.5.3 still having kernel panic with Bluetooth audio

After upgrading to OSX 10.5.3 yesterday I thought I'd give bluetooth audio a chance again (I already had problems with 10.5.2, see http://discussions.apple.com/thread.jspa?threadID=1529536&tstart=0). After a while my machine crashed again (the screen turns grey and I was instructed to hold the power button). This time I was trying to listen to iTunes over the bluetooth headphones (so the Plantronics in headphone mode).

After restarting the problem report sent to Apple is:

Thu May 29 07:15:21 2008
panic(cpu 1 caller 0x001A8CD4): Kernel trap at 0x6987f932, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0xfffff000, CR3: 0x01b09000, CR4: 0x00000660
EAX: 0x00000002, EBX: 0x08794700, ECX: 0x136d8f20, EDX: 0xfffff000
CR2: 0xfffff000, EBP: 0x5d782948, ESI: 0x0b460300, EDI: 0x00000001
EFL: 0x00010286, EIP: 0x6987f932, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x5d782758 : 0x12b0fa (0x459294 0x5d78278c 0x133243 0x0)
0x5d7827a8 : 0x1a8cd4 (0x4627fc 0x6987f932 0xe 0x461fac)
0x5d782888 : 0x19ede5 (0x5d7828a0 0xa0a3aff1 0x5d782948 0x6987f932)
0x5d782898 : 0x6987f932 (0xe 0x48 0x5d780010 0xffff0010)
0x5d782948 : 0x6987f7d5 (0xb460300 0xf 0x28 0x83c6d00)
0x5d7829a8 : 0x6988191a (0xb460300 0x3 0x0 0x1)
0x5d7829d8 : 0x6901e14f (0x8794700 0x30006 0xb3f3c04 0x8794700)
0x5d7829f8 : 0x6901d74b (0x8794700 0x690286a8 0x1 0x0)
0x5d782a28 : 0x69021897 (0x8794700 0xb3f3c00 0x5d782a68 0x12fa53)
0x5d782a68 : 0x4212ad (0xb3f3c00 0x0 0x0 0x0)
0x5d782ab8 : 0x69021342 (0xc331640 0x69021388 0x0 0x0)
0x5d782ae8 : 0x43b9bf (0xb3f3c00 0x5d782b20 0x5d782b24 0x5d782b28)
0x5d782b78 : 0x43d825 (0x13ca984c 0xb3f3c00 0xe7bd598 0x0)
0x5d782bd8 : 0x43b428 (0xb3f3c00 0x3 0x5d782c20 0x0)
0x5d782cf8 : 0x18d918 (0xb3f3c00 0x3 0xe7bd598 0x0)
0x5d783db8 : 0x12d17e (0xe7bd570 0xb8295a0 0x0 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.IOBluetoothA2DPAudioDriver(2.1f17)@0x6987e000->0x69884fff
dependency: com.apple.iokit.IOBluetoothFamily(2.1f17)@0x68f89000
dependency: com.apple.iokit.IOAudioFamily(1.6.4b7)@0x69017000
com.apple.iokit.IOAudioFamily(1.6.4b7)@0x69017000->0x6902dfff
dependency: com.apple.kext.OSvKernDSPLib(1.1)@0x69014000

BSD process name corresponding to current thread: iTunes

Mac OS version:
9D34

Kernel version:
Darwin Kernel Version 9.3.0: Fri May 23 00:49:16 PDT 2008; root:xnu-1228.5.18~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F42388C8)

Is it just me who is having these problems? It really amazes me that I am just not able to use bluetooth audio - headset nor headphones - without this rather significant problem? And then I don't even begin about the mouse getting the hiccups the moment the headset is turned on. I would have expected lots of complaints about this?

MacBook Pro 2.4Ghz DuoCore, 4Gb RAM, OSX 10.5.3
Bluetooth Apple Mighty Mouse
Bluetooth Apple keyboard
Bluetooth Plantronics P590

MacBook Pro 2.4 Ghz Intel Core 2 Duo, Mac OS X (10.5.3), 4Gb RAM

Posted on May 29, 2008 3:38 AM

Reply
62 replies
User profile for user: Remco Douma
Remco Douma Author
User level: Level 1
5 points

May 29, 2008 4:01 AM in response to Julian Wright

Thanks for your thoughts.

I don't exclude the possibility of it being local to my system. But I find it rather unlikely. I just have a default MacBook Pro of half a year old and didn't do anything weird with it. Everything works as expected. I am using other bluetooth appliances without issues (mouse, keyboard). Sound is also working as expected (speakers, headphones).

And although I understand your suggestion of "reinstalling OSX" that is not a real practical approach to my problem. I have a perfectly running laptop that I depend upon for my everyday job, and I am not going to jeopardize that because I cannot use bluetooth audio. I don't have an extra hard disk lying around which I can try it on (and even if I would, I am not going to invest that much time in it).
Reply
User profile for user: Julian Wright
Julian Wright
User level: Level 8
35,014 points

May 29, 2008 4:30 AM in response to Remco Douma

Everything works as expected


Except Bluetooth Audio...

Just because the rest of your system is working perfectly doesn't mean your problem can't be due to just one corrupted Bluetooth Audio system file - one that isn't used during any other tasks.

File corruption can happen without you doing "anything weird with it". All it needs is one damaged block on your hard disk.

I have a perfectly running laptop


No you don't - you said you're getting kernal panics when using Bluetooth Audio functions.

I am not going to jeopardize that


That's why I suggested installing OS X on another disk - not your Main hard disk.

I don't have an extra hard disk lying around


Let's hope you don't have a major system crash from which you need to recover then!

and even if I would, I am not going to invest that much time in it


Doing a clean, basic install of OS X takes about 20 minutes, with no user interaction required once it gets going.

As you've posted about this problem a couple of times, I assumed it was important enough to you to want to try to find a solution. Apparently not. If you don't want to invest any time in this, why should anyone here invest any of their (free) time trying to help you either?
Reply
User profile for user: Remco Douma
Remco Douma Author
User level: Level 1
5 points

May 29, 2008 4:50 AM in response to Julian Wright

I don't agree with everything you write (for example: I expect OSX to detect corrupt system files, not requiring me to do a virgin install to compare behavior), but that doesn't matter and seems to be beyond the point here.

In my book logging a problem and trying to find a solution for it doesn't necessarily involve doing clean OS installs. I'm trying to solve a problem but do have my limits about the amount of effort I want to invest in that (indeed, no spare HD lying around, but do have my backups so in case of emergency I'll just buy one and go from there, no need to pick up the hammer if there's no nail).

Sorry for apparently having wasted your time, never intended to. Just didn't expect the first solution proposal to be an OS reinstall (maybe naive from my part, who knows!). And I also didn't expect that someone would draw the conclusion that not immediately picking up on their advice means that my problem is not important enough to me. For me "importance" comes in shades, not in black and whites. Ah well, you learn something every day.

Who knows I might pick up on your suggestion if I have some time to kill so thanks again.
Reply
User profile for user: Julian Wright
Julian Wright
User level: Level 8
35,014 points

May 29, 2008 6:16 AM in response to Remco Douma

Seems like your expectations are somewhat different to reality. What did you expect? Someone to wave their magic wand and miraculously fix your problem remotely with no input from you?

You've already established that this isn't a common problem, since no-one replied experiencing the same, or even suggesting a magical fix.

You've already established that otherwise your computer appears to be running normally. So you've got to be prepared to do a bit of troubleshooting to narrow down where the problem lies.

Kernel panics are the most severe of system crashes, which suggests something is fundamentally wrong somewhere in your system/setup, and the only way to narrow it down is to try different things until you find something which makes a difference.

File corruption (which isn't automatically detected by OS X, no matter what you'd expect) can be one cause of kernel panics. But, the Bluetooth system software is an integral part of the OS which cannot be re-installed separately, therefore the suggestion to try it on a fresh install.

+(Many people do have a separate bootable Mac OS X installation specifically for emergency situations. If you'd had that you could've tried it in a few minutes without having to install the whole OS.)+

Have you tried using the same headset on another Mac? (A friend, colleague, local Apple Store could help). This would at least establish whether the problem is specific to your Mac or not.

Have you tried using a different headset? (Maybe borrow one from someone). This would at least establish whether the problem is specific to your headset or not.

Unfortunately, troubleshooting uncommon problems is time consuming. I suggested one (relatively quick and easy) way to establish whether the problem was specific to your current OS installation. Sorry it wasn't quick and easy enough. Perhaps trying another Mac or headset will require less effort.
Reply
User profile for user: Remco Douma
Remco Douma Author
User level: Level 1
5 points

May 29, 2008 6:43 AM in response to Julian Wright

When did I suggest I expected a magic wand? I didn't "expect" anything, I am in the process of getting my bearings. I was trying to see if there are other people out there with the same issue. Maybe someone out there experienced the same but didn't post a question about it. Maybe they just decided it wasn't worth it and leave it be. Maybe they thought it "must be them". So I was hoping for some sign of "yes, me too!" or "yes, I had that, solved it as follows". Just peer input and of course yes - hopefully - some "magic fix" of course. I can at least hope. Hope is not the same as expect.

I did not say I find your proposal to narrow down the problem illogical. I just find it too much trouble at this stage. For me (personally!), the return of investment is not worth it. It's not simply the "clean reinstall". It's getting everything at least in such a working order that I can reproduce the problem (getting music in that iTunes, installing other apps I use to see if it is caused by a conflict between running Skype and iTunes for example), and then playing around with it for unknown amounts of time to see if/when it happens again. And I cannot do that while working, because it's the same machine I'm working on. So that means losing working hours just testing this. It has happened to me I could use the audio for hours without problems and then the problem occurs. Or it happens after minutes. So hunting this down the way you propose would involve lots of time (because 10 minutes of clean running doesn't mean the problem is not there, but might just not have occurred yet). And currently I am unwilling to invest that time to solve this problem, which is annoying, but not life threatening. What's wrong with that conclusion? I am just telling you that in my perception at this point, this is just way too much effort.

Like I said - I might go that way eventually. Just not now. Maybe for you this is trivial stuff - it would be for me if it were Windows - but for me it's not. I will have to see how I can do that (machine came originally with Tiger + Leopard upgrade disc, so will it install fresh? how does multiboot work? etc.). Never did that stuff (on Mac's). So I'm just saying that *for me* at this stage the effort doesn't outweigh the potential benefit. It's just too much trouble. And yes, a spare boot disk is a good idea, I realize that, so I will probably do that somewhere in the future. I always sort of understood that for rescue actions you could boot from the DVD (like on Windows) for repairs. But hey, I'm no Mac system guru (which is exactly one of the reasons holding me back to follow your suggestion at this stage), so maybe I'm wrong!

As for your other suggestions - thanks, I realize those are options.
Reply
User profile for user: mike231
mike231
User level: Level 1
0 points

Jun 1, 2008 9:01 PM in response to mike231

Just to add to my previous post: The BT input is only pulsing noise, nothing of my voice comes through. This happens on my iMac (Broadcom chip) only after the 10.5.3 update (at least I never noticed it before). We have another MacBook (Cambridge chip) also with 10.5.3 installed and no problems there (so far).
The headset works perfectly on my cell phone.
Reply
User profile for user: sr105
sr105
User level: Level 1
0 points

Jun 2, 2008 4:19 PM in response to Remco Douma

I think I have a similar problem. My MBP crashes (randomly) after waking from sleep and (it seems) during file transfers to my cel phone (via bluetooth). My phone is always near my laptop though rarely connected.

My questions:

1. Are any of you using Vmware/Bootcamp/WinXP and have you used the bluetooth adapter within XP? (I have, but apart from discovery and pairing, nothing else works including connect/disconnect)

2. Has anyone here been unable to POWER ON their MBP after this happened?
I'm trying to determine if I have the same issue, a different issue or possibly two separate issues.

I've had my MBP fail to POST a couple of times now after kernel panics. The very first time this happened, my laptop didn't even kernel panic. It just locked up. I left it alone for a few minutes just in case it was just *really busy*, but it was definitely locked up. When I tried to restart it, it wouldn't even POST. The sleep light would come on and then nothing. The screen didn't even power-up. Eventually by trying to power on with the battery removed and then replaced, I got the 3-beeps code indicating bad memory. I tried a few more times and then let it sit till the morning. In the morning, it booted just fine. Since then, random kernel panics (some could definitely be bluetooth related) and once more with the 3-beeps (didn't take as long to recover, though).

I tested the memory in single user mode with memtest and it passed, btw.

Apple Tech Support's suggestion that I re-install kind of irked me, if only because the laptop wouldn't even power on far enough to turn on the screen or even beep at me. The built-in firmware on the board failed and re-installing OS X is supposed to remedy that how?

Suggestions/Comments?
Reply

OSX 10.5.3 still having kernel panic with Bluetooth audio

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up