Support > Remote Buddy Forum > kernel panic os x 10.6.2, could it be because of candelair? // 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

24.11.2009 21:16:15

kernel panic os x 10.6.2, could it be because of candelair?

View

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

Since upgrading to 10.6.2 (and upgraded candelair to 1.0.2, driver version 1.7.2) my macmini kernel paniced twice. I have no idea if candelair is actually causing it because it happend just randomly and I cant understand the logs. The only thing I know is that candelair is the only difference from before, haven't installed anything else since upgrading to snow leopard.

I pasted the logs here: http://dpaste.com/hold/124686/

Any advice is welcome. Thanks!

Last edited: 24.11.2009 21:17:57

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

Driver

What is the task of the driver and what do I need it for? (FAQ015E0177)
The Setup Wizard already contains a summary on how the driver does help Remote Buddy to provide additional features and hardware support. If that summary was too short, here's some more info on each of the points:
- fix for Apple® Remote driver problems in OS X
  Since OS X 10.4.9 (that includes 10.4.10/10.4.11/10.5.x/..) many users have been experiencing that one button press on their remote does now trigger two reactions - once from any currently running application that supports the Apple® Remote, once the default system action. So, this problem is not specific to Remote Buddy. The driver provides a clean, system conform fix to this problem using only documented APIs.
- enabling of all features of built-in IR receivers
  Only with the Remote Buddy driver do you gain support for arbitrary length button presses for the Play and Menu buttons as well as minimized reaction times for all buttons. While this may sound like unimportant technical details, they actually do have a strong practical impact. If, for example, you want to map a function to the Play or Menu button, that you want to see executed for as long as you press that button, this was previously simply impossible to achieve. This limitation still applies to all other applications. It does not for Remote Buddy with the driver loaded.
- the emulation of a virtual Apple® Remote
  Control applications that have support for and listen to an Apple® Remote - with any remote control of your choice supported by Remote Buddy. And on any Mac®. This allows you to f.ex. use iAlertU side by side with Remote Buddy or accessing special functions and modes inside applications that would otherwise require these apps to have full control over the built-in IR receiver of your Mac® - and that your Mac® actually came with one.
- support for Bluetooth® remotes and external receivers
  It's not possible to reliably operate many Bluetooth® based remotes, like for example the Wii® Remote with a Mac® purely from userspace due to limitations in the operating system. The situation for many external receivers is similiar: some of their features - or the entire device - can only be supported with the help of a driver.

User

25.11.2009 09:48:37

Re: kernel panic os x 10.6.2, could it be because of candelair?

View

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

Thanks for the logs.

Short answer:
This is not related to Candelair.

Long answer:
This looks like an issue in the kernel to me. In both logs, the panic happens right in the kernel's own kernel_task:

-- snip --
panic(cpu 0 caller 0x2287c6): "stack_alloc: kernel_memory_allocate"@/SourceCache/xnu/xnu-1486.2.11/osfmk/kern/stack.c:168
-- snap --

If Candelair was the cause of the panic, it would be included in the backtrace like this (example taken from Apple's technote linked to below):

-- snip --
Kernel loadable modules in backtrace (with dependencies):
com.apple.dts.driver.PanicDriver(1.1)@0x223aa000->0x223abfff
-- snap --

Such a block, however, is entirely missing from your panic log.

Please be sure to submit these panic logs to Apple, so they are aware of it.

Since these panics occur in the memory management of the kernel, please also consider the possibility of bad, loose or failing RAM modules.

If you're interested, you can find more information on reading panic logs here:
http://developer.apple.com/mac/library/technotes/tn2002/tn2063.html

Best regards,
Felix Schwarz

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