Support
All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.
Forum closed
This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview 

AuthorThread
User

07.12.2008 09:07:54
kernel traps when using Sony remote.
View

This posting is older than 6 months and can contain outdated information.
Hi!

Every few days I get a kernel trap when I'm using the Sony bluetooth remote. I haven't found a pattern by now.

The report looks like this: 
------------------------- 
Sun Dec 7 08:46:35 2008

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000000 PC=0x00000000247F30E0 
Latest crash info for cpu 0: 
Exception state (sv=0x24852a00) 
PC=0x247F30E0; MSR=0x00009030; DAR=0x00000000; DSISR=0x40000000; LR=0x247F5704; R1=0x2498FA10; XCP=0x0000000C (0x300 - Data access) 
Backtrace: 
0x7FFF0000 0x247F5704 0x00A301C0 0x00A30258 0x00A2B448 0x00A2D120 
0x00A217AC 0x00A16D74 0x00A16CD8 0x00A16294 0x00A462AC 0x00A462F0 0x00A467F8 0x0003F94C 
0x000B0654 
Kernel loadable modules in backtrace (with dependencies): 
com.apple.driver.IOBluetoothHIDDriver(2.1f17)@0x247ed000->0x247fafff 
dependency: com.apple.iokit.IOBluetoothFamily(2.1f17)@0xa10000 
dependency: com.apple.iokit.IOHIDFamily(1.5.3)@0x873000 
com.apple.iokit.IOBluetoothFamily(2.1f17)@0xa10000->0xa58fff 
Proceeding back via exception chain: 
Exception state (sv=0x24852a00) 
previously dumped as "Latest" state. skipping... 
Exception state (sv=0x246a0a00) 
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

BSD process name corresponding to current thread: kernel_task

Mac OS version: 
9F33

Kernel version: 
Darwin Kernel Version 9.5.0: Wed Sep 3 11:31:44 PDT 2008; root:xnu-1228.7.58~1/RELEASE_PPC 
System model name: PowerMac10,1 
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access 
Latest stack backtrace for cpu 0: 
Backtrace: 
0x0009B518 0x0009BEBC 0x00029DD8 0x000AF290 0x000B2AF8 
Proceeding back via exception chain: 
Exception state (sv=0x24852a00) 
PC=0x247F30E0; MSR=0x00009030; DAR=0x00000000; DSISR=0x40000000; LR=0x247F5704; R1=0x2498FA10; XCP=0x0000000C (0x300 - Data access) 
Backtrace: 
0x7FFF0000 0x247F5704 0x00A301C0 0x00A30258 0x00A2B448 0x00A2D120 
0x00A217AC 0x00A16D74 0x00A16CD8 0x00A16294 0x00A462AC 0x00A462F0 0x00A467F8 0x0003F94C 
0x000B0654 
Kernel loadable modules in backtrace (with dependencies): 
com.apple.driver.IOBluetoothHIDDriver(2.1f17)@0x247ed000->0x247fafff 
dependency: com.apple.iokit.IOBluetoothFamily(2.1f17)@0xa10000 
dependency: com.apple.iokit.IOHIDFamily(1.5.3)@0x873000 
com.apple.iokit.IOBluetoothFamily(2.1f17)@0xa10000->0xa58fff 
Exception state (sv=0 
------------------------- 
And that's my machine: 
------------------------- 
Model: PowerMac10,1, BootROM 4.8.9f1, 1 processor, PowerPC G4 (1.1), 1.42 GHz, 1 GB 
Graphics: kHW_ATIrv280Item, ATY,RV280, spdisplays_agp_device, 32 MB 
Memory Module: DIMM0/J11, 1 GB, DDR SDRAM, PC3200U-30330 
Modem: Jump, V.92, Version 1.0 
Bluetooth: Version 2.1.0f17, 2 service, 1 devices, 1 incoming serial ports 
Network Service: Ethernet (integriert), Ethernet, en0 
Parallel ATA Device: WDC WD2500BEVE-00WZT0, 232,89 GB 
Parallel ATA Device: MATSHITACD-RW CW-8124, 7,7 GB 
USB Device: Bluetooth USB Host Controller, Apple, Inc., full_speed, 500 mA 
USB Device: USB2.0 Hub, high_speed, 500 mA 
USB Device: iPod, Apple, high_speed, 500 mA 
USB Device: Mass Storage Device, Prolific Technology Inc., high_speed, 500 mA 
USB Device: USB2.0 Hub, high_speed, 500 mA 
USB Device: Hub in Apple Extended USB Keyboard, Mitsumi Electric, full_speed, 500 mA 
USB Device: USB-PS/2 Optical Mouse, Logitech, low_speed, 100 mA 
USB Device: Apple Extended USB Keyboard, Mitsumi Electric, full_speed, 250 mA 
USB Device: 2.0 Card Reader, PASS, high_speed, 500 mA 
USB Device: Cinergy Hybrid T USB XS, TerraTec Electronic GmbH, high_speed, 500 mA 
FireWire Device: OXFORD IDE Device 1, Macpower, 400mbit_speed

Is it a known issue?

Michael

P.S.: These traps occurred 5 times since 27.11. The last trap before was on May 17th.

Last edited: 07.12.2008 09:15:24 

These entries from the FAQ may be relevant to this topic:

Driver
General
Hardware - Apple® Remote
Hardware - Harmony® Smart Control
Hardware - Sony® BD Remote Control
Hardware - Wii™ Remote
Hardware - iPhone™ / iPod® touch / AJAX Remote
User

07.12.2008 17:22:17
Re: kernel traps when using Sony remote.
View

This posting is older than 6 months and can contain outdated information.
Thanks for your report. This is not a known problem. Since what you 
see happens in an Apple kernel extension for HID devices (which will 
not be used for the Sony BD Remote) and Remote Buddy also doesn't and 
can't access any functionality in the IOBluetoothHIDDriver, I can't 
see a connection to Remote Buddy.

I also tried to generate the cleartext version of the backtrace using 
the usual debug tools, but couldn't since using previously working 
ways to do this no longer work (the and Apple's new set of 
instructions (=> http://developer.apple.com/technotes/tn2002/tn2063.html) 
fail with a

kextload: cannot resolve dependencies for kernel extension /System/ 
Library/Extensions/IOBluetoothHIDDriver.kext

error message.

Since all of OS X Bluetooth code is strictly closed-source, only Apple 
will be able to get to the bottom of the problem. Apple has made a lot 
of changes to Bluetooth throughout the Leopard releases and I'm sure 
they continue to make more, so you should definately submit your crash 
report to Apple, so they become aware of the issue.

As you seem to have a lot of issues that noone else has previously 
reported: are you using any system modifications, any hacks like f.ex. 
haxies, any input managers or the like?

Are you using a Bluetooth USB stick or a Bluetooth module by Apple? 
Any other Bluetooth devices or software?

Best regards, 
Felix Schwarz 

User

11.12.2008 20:49:06
Re: kernel traps when using Sony remote.
View

This posting is older than 6 months and can contain outdated information.
Hi!

Thanks for your report. This is not a known problem.

 
Hmm :-(

I can't see a connection to Remote Buddy.

 
It only happens when I press a key on the bluetooth remote. So there must be a relationship in some way.

 

Since all of OS X Bluetooth code is strictly closed-source, only Apple 
will be able to get to the bottom of the problem. Apple has made a lot 
of changes to Bluetooth throughout the Leopard releases and I'm sure 
they continue to make more, so you should definately submit your crash 
report to Apple, so they become aware of the issue.

 
I did - everytime I had the traps.

As you seem to have a lot of issues that noone else has previously 
reported: are you using any system modifications, any hacks like f.ex. 
haxies, any input managers or the like?

 
No. AFAIK not.

Are you using a Bluetooth USB stick or a Bluetooth module by Apple?

 
I'm having the internal Bluetooth module of the Mac Mini.

Any other Bluetooth devices or software?

 
Not active. I'm syncing my mobile phone with it - but not at the same time.

Since it's not a known issue I will wait until it's a know one ;-) I reported the traps to Apple.

I will register Remote Buddy as soon as I don't crashes my system anymore.

Michael 

User

15.12.2008 11:34:17
Re: Re: kernel traps when using Sony remote.
View

This posting is older than 6 months and can contain outdated information.
Michael,

what is crashing on your system is Apple's IOBluetoothHIDDriver 
(com.apple.driver.IOBluetoothHIDDriver), a part of OS X that is 
usually responsible for handling Bluetooth HID devices such as mice 
and keyboards (including f.ex. most Sony Ericcson mobiles, which can 
emulate a Bluetooth HID keyboard). That driver is not used for the PS3 
remote, however.

Since

- the crash is happening in an Apple kernel module that isn't used by 
Remote Buddy at all and

- no code of Remote Buddy is part of the backtrace of the crash, 
either and

- all of the Apple kernel modules code involved in the crash you see 
are strictly closed source

- you are the only user who sees such a crash (which makes an indirect 
relation to Remote Buddy very unlikely, since if there was one, I'd 
have received a lot of reports about it already - even minor, 
cosmetical changes usually already result in anything from 5 to 20 
mails)

I can't really see Remote Buddy contributing or causing it. From the 
data I have at hand, what you see is a bug in OS X that only Apple can 
provide you a fix with for.

Best regards, 
Felix Schwarz