Support > Remote Buddy Forum > kernel panic 1.0rc2 // IOSPIRIT [EN]

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

Author

Thread

User

26.04.2007 15:25:45

kernel panic 1.0rc2

View

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

After installing the latest version with the kernel patch, I restarted Remote Buddy and got this kernel panic.

*********

Thu Apr 26 08:10:26 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0xb80224f2, CR3: 0x00da0000, CR4: 0x000006e0
EAX: 0x00000003, EBX: 0x0533bd00, ECX: 0x0396fed4, EDX: 0x0385f2d0
CR2: 0x00000003, EBP: 0x25023d18, ESI: 0x00000000, EDI: 0x0051d862
EFL: 0x00010206, EIP: 0x0039ace0, CS: 0x00000008, DS: 0x04ae0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25023ae8 : 0x128d08 (0x3cb134 0x25023b0c 0x131de5 0x0)
0x25023b28 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x25023c38 : 0x19ada4 (0x25023c50 0x51d862 0x0 0x25023cd8)
0x25023d18 : 0x51dad2 (0x533bd00 0x51d862 0x4cd1d00 0x0)
0x25023d48 : 0x56fa78 (0x3e78d00 0x4cd1d00 0x0 0x1a3010)
0x25023d68 : 0x3b19ee (0x4cd1d00 0x4ae69c 0x25023db8 0x197fe1)
0x25023d88 : 0x1885ec (0x4cd1d00 0x1dcd6500 0x25023df8 0x4aecd74)
0x25023db8 : 0x12b4c3 (0x38c34b4 0x5f608a8 0x0 0x0)
0x25023df8 : 0x124b17 (0x38c3400 0x0 0x18 0x25023edc)
0x25023f08 : 0x195a42 (0x25023f44 0x0 0x0 0x0)
0x25023fc8 : 0x19b21e (0x3800120 0x0 0x19e0b5 0x3968b8c) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0080288
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBUserClient(2.7.0)@0x56c000
dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x517000
com.apple.iokit.IOUSBFamily(2.6.5)@0x517000

Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386

*********

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

Hardware - Apple® Remote

After uninstalling/quitting Remote Buddy, my Mac® no longer reacts to the Apple® Remote. (FAQ015E0241)
To enable you to use all capabilities of the IR Receiver of your Mac®, Remote Buddy is using its own driver. In contrast, all other applications with integrated Apple® Remote support usually use the OS X Apple® Remote subsystem.

As long as you're running Remote Buddy, Remote Buddy and its driver are responsible for turning the received button presses into actions. As soon as you quit Remote Buddy, this task is again handled by the OS X Apple® Remote subsystem.

If other applications don't use the interface to the OS X Apple® Remote subsystem correctly, this can lead to the effect that nothing happens when you press a button on your Apple® Remote. For as long as you're running Remote Buddy, issues like this are covered by Remote Buddy and it's driver and are therefore not visible to you. However, as soon as you quit Remote Buddy, the OS X Apple® Remote subsystem is back in control and any issues caused in it by other applications become visible.

Therefore Remote Buddy is neither the cause of the issue nor is it responsible for it. Instead, the cause of the issue exists independently of Remote Buddy. It's located elsewhere and can also only be solved there.

Although our products can't cause any such issues, we're regularly contacted about such issues and asked for help. In order to make locating and fixing the cause of such issues as easy and efficient as possible, we've developed a free diagnostics tool: Remote Control Diagnostics. It can locate issues with a single click and will provide you with information about the issue as well as with instructions on how you can fix it.
After updating to OS X 10.6.2, my Apple® Remote is no longer available for selection in Remote Buddy. (FAQ015E0236)
Please update your copy of Remote Buddy to version 1.15 or later.

Hardware - Sony® BD Remote Control

I'm having problems with the Sony® PS3 BD Remote under OS X® 10.8/10.9. (FAQ015E0246)
There's a bug in the Bluetooth®-stack of OS X® 10.8/10.9 in the context of pairing a Sony® PS3 BD Remote. OS X® 10.8/10.9 will ask you to enter a PIN code when you try to connect your remote control. This problem is known by Apple®.

If you pair your Sony® PS3 BD Remote with your Mac® for the first time
1. Use Remote Buddy's Setup Wizard to pair your remote control
2. Restart your Mac® directly after the pairing was successful, while the remote is still connected.
3. The remote should now work without problems.
If you've already paired the Sony® PS3 BD Remote with your Mac®
1. 10.9 only: Try entering 0000 as PIN and reboot. If you're lucky, that was all you needed to do. If this does not solve your issue, please continue with the steps that follow.
2. First, we'll need to remove the Link Key of your Mac® from the memory of your remote control. Since this remote control can only store one Link Key, it's as easy as pairing the remote control with another Mac®. To do so, open System Preferences > Bluetooth on another Mac® and pair your remote with it.
3. All steps that follow should be performed on the Mac® that you want to use your remote control with.
4. Remove - if it exists - the entry of your remote control at Remote Buddy > Preferences > Hardware ® Bluetooth Receiver. The entry usually is titled "BD Remote".
5. If existant, remove the device "BD Remote" from System Preferences > Bluetooth.
6. Delete the Bluetooth preferences files by entering the following in Terminal.app and hitting return (Warning: this deletes all information about all paired Bluetooth® devices):
```
sudo rm /Library/Preferences/com.apple.Bluetooth.plist
sudo rm ~/Library/Preferences/com.apple.Bluetooth.plist
sudo rm ~/Library/Preferences/ByHost/com.apple.Bluetooth.*.plist
```
  Please enter your admin password when requested. Then restart your Mac®.
7. Use Remote Buddy's Setup Wizard to pair your remote control
8. Restart your Mac® directly after the pairing was successful, while the remote is still connected.
9. The remote should now work without problems.

User

26.04.2007 15:27:56

Re: kernel panic 1.0rc2

View

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

Oops, running 10.4.9 on a MacBook Core2 Duo with 2GB of Ram.

User

26.04.2007 15:58:02

Re: kernel panic 1.0rc2

View

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

Thanks James for the log output.

Remote Buddy's kernel extension doesn't appear in the backtrace, so
I'm not sure whether it really is Remote Buddy that leads to the
kernel panic. Did you run any other software that uses the USB bus at
the same time? EyeTV, Parallels, any other software?

I'll hopefully find the time to have an indepth look at the kernel
panic log later today and see whether the user space part of Remote
Buddy could be causing this (as IOUSBUserClient turns up in the log,
which is attached to a IOUSBDevice on access from user space).

Best regards,
Felix

Am 26.04.2007 um 15:25 schrieb James Ehrler:

After installing the latest version with the kernel patch, I
restarted Remote Buddy and got this kernel panic.

*********

Thu Apr 26 08:10:26 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type
14=page fault), registers:
CR0: 0x8001003b, CR2: 0xb80224f2, CR3: 0x00da0000, CR4: 0x000006e0
EAX: 0x00000003, EBX: 0x0533bd00, ECX: 0x0396fed4, EDX: 0x0385f2d0
CR2: 0x00000003, EBP: 0x25023d18, ESI: 0x00000000, EDI: 0x0051d862
EFL: 0x00010206, EIP: 0x0039ace0, CS: 0x00000008, DS: 0x04ae0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25023ae8 : 0x128d08 (0x3cb134 0x25023b0c 0x131de5 0x0)
0x25023b28 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x25023c38 : 0x19ada4 (0x25023c50 0x51d862 0x0 0x25023cd8)
0x25023d18 : 0x51dad2 (0x533bd00 0x51d862 0x4cd1d00 0x0)
0x25023d48 : 0x56fa78 (0x3e78d00 0x4cd1d00 0x0 0x1a3010)
0x25023d68 : 0x3b19ee (0x4cd1d00 0x4ae69c 0x25023db8 0x197fe1)
0x25023d88 : 0x1885ec (0x4cd1d00 0x1dcd6500 0x25023df8 0x4aecd74)
0x25023db8 : 0x12b4c3 (0x38c34b4 0x5f608a8 0x0 0x0)
0x25023df8 : 0x124b17 (0x38c3400 0x0 0x18 0x25023edc)
0x25023f08 : 0x195a42 (0x25023f44 0x0 0x0 0x0)
0x25023fc8 : 0x19b21e (0x3800120 0x0 0x19e0b5 0x3968b8c) No mapping
exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0080288
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBUserClient(2.7.0)@0x56c000
dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x517000
com.apple.iokit.IOUSBFamily(2.6.5)@0x517000

Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007;
root:xnu-792.18.15~1/RELEASE_I386

*********

--
Felix Schwarz
felix.schwarz@iospirit-gmbh.de

Postal address:
IOSPIRIT GmbH, Berckhauser Straße 11, 90409 Nürnberg, Germany

Phone: +49 (0)911 / 3677 423
Fax: +49 (0)911 / 3677 424
Homepage: http://www.iospirit.com/

CEO: Felix Schwarz

Trade register number and place of registration:
HRB 21960, Amtsgericht Nürnberg

User

26.04.2007 17:29:47

Re: kernel panic 1.0rc2

View

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

Sorry, nothing that I know of was accessing the USB port at the time and parallels was shut down.

User

27.04.2007 20:02:01

Re: Re: kernel panic 1.0rc2

View

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

Hello James,

thanks for the info. Having had to spend quite some time on my tax
declaration today, I didn't find time to dive deeper into your kernel
log just yet, but I hope to find it over the weekend.

Best regards,
Felix

User

30.04.2007 14:49:02

Re: Re: kernel panic 1.0rc2

View

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

Hello James,

thanks again for your report. Just to give you some feedback:

I could successfully track down the problem to a bug in the
UserClient part of Apple's IOUSBInterface service object. While I
could reproduce your kernel panic within a 100 x launch/quit cycle,
the release yesterday didn't show any problems at all even after
running a 2500 x launch/quit cycle over the course of a day.

The release published yesterday works around the bug in a way so that
the kernel panic can no longer occur.

I'll file a bug with Apple as soon as I find some time to put
together some sample code for them to contribute to the overall
stability of Mac OS X.

Best regards,
Felix

User

30.04.2007 17:08:24

Re: kernel panic 1.0rc2

View

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

Sorry you had to waste your time on an Apple bug, but thanks for reporting it and getting a workaround.

Just ordered my copy today!

User

02.05.2007 12:44:02

Re: Re: kernel panic 1.0rc2

View

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

Thanks for your support!

Best regards,
Felix

Remote Buddy
Support
1. Overview
2. Manuals
3. FAQs
4. Forums
1. Lost license code
2. Support inquiry
IOSPIRIT
1. About us
2. Blog
3. Labs
4. Developers
1. Contact
2. Press releases
3. Imprint
4. Jobs