site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com David -- Thanks for for the information - Im trying this list as it wasnt clear to me where to ask questions about daemons such as hwmond - and Id seen previous questions about hwmond on this list - also as you will see from this post there are definite kernel issues As for using hwmond for your purpose, you could do a few things: HTH, -- Chris ------------------ 6 Infinite Loop M/S 306-2MS Cupertino CA 95014 phone: (408) 974-4033 fax: (408) 862-7577 email: sarcone@apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This is a good list to ask in general, but this particular daemon is not in Darwin. Any kernel issues you find (panics/hangs) should be filed via bugreporter.apple.com and include the /Library/Logs/panic.log file or a dump of the panic information spewed to your console (don't know if you changed boot-args or not). however there seems to be a possible issue that Im hitting a Darwin kernel bug with my program - every so often the odd Xserve G5 node will panic - from the kernel core dump it seems one of the processes active at the time of the panic is my version of hwmond (im still running Apples hwmond) - this is fairly infrequent e.g. over 14 days for 96 nodes something like 5-6 have paniced at random intervals - my version of hwmond is looping every 60 seconds using IOServiceGetMatchingServices/IORegistryEntryCreateCFProperty to extract data from IOHWSensor and AppleFCU class objects - supposedly only reading kernel values If this is all you are doing, you should file a bug. The system should never panic and if it does, it's a bug. You're doing the equivalent of 'ioreg -c Foo' and you probably could reproduce your panic calling 'ioreg' in a script, so you should definitely file a bug. one possible explanation is that there is some interference between hwmond and myhwmond - both of them obviously trying to hit the same hardware registers (although its still a rare event) Access to these registers should be serialized if they need be, so that would be a bug if it leads to a panic... - hence if I can get the information from hwmond may be I dont need to do the IOService scanning in my program and maybe the issue will go away others are of course there is some kernel bug/race condition which Im hitting - or some issue in the IOKit library - the traceback always seems to be in routines labelled as object serialisation or it could be some interrupt issue I dont understand enough of Darwin kernel dumps to determine if the issue is simply from a program running at the time or its actually doing interrupt processing at the time of the panic of course its not clear to me what the current stability of Darwin is on XServe G5 nodes - there are significant new features in these machines which might lead to kernel issues - only machines with ECC etc. - issues with the 64 bit nature of the processors and the 32 bit version of Darwin - could even be of course processor errata Before positing theories about RAM or chip errata, how about just filing a bug and letting someone inside Apple track it down a bit? Seems like you have a reproducible enough case to warrant a bug. - File an enhancement request bug report to ask for a supported means of getting data from hwmond like Server Monitor does. - If you are an ADC member and have a "ticket" available, ask DTS for help in getting a supported method of retrieving this info. - Ask for hwmond to be open-sourced (not sure where this request would go, maybe KVV can help out here). This email sent to site_archiver@lists.apple.com