site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Mon, 2006-03-27 at 18:34 -0800, Terry Lambert wrote:

On Mar 27, 2006, at 12:58 PM, Ochal Christophe wrote:

...

Hi all,

First & foremost, my apologies if this gets through multiple times, i tried reaching the mailinglist from another email account & failed miserably.

Recently, one of my clients started experiancing kernel panics on all of his macs (2 powerbooks & 2 G5's). All machines run OSX 10.3.9 These are the kernel panic logs: Machine 1 (PowerBook): *********

You are supposed to file a bug for this sort of thing; this list is not for technical support questions.

I tried filing a bug, but wasn't able to log into the bugreporter, will try again later tonight.

From the looks of things, at least one of the machines (looks like the laptop) has bad memory.

The machine has been tested at our office, no reproducable crashes occured, even under heavy systemload, hardware test also didn't pick up on any ram issue's. The weird thing is that all 4 machines started experiancing the same kernel panics on the same day, the only known change i know of, is that the SAN's connected to the Win2K server have been moved to a different location (fysical move), and their network manager insists nothing else was changed, nor were there any updates applied to the server. Since this also happened the 8th of March (the day the kernel panics started occurring on all four macs) leads me to think that it's really a software issue/glitch somewhere, i'm in the dark however, when it comes to solving these. In the 8 years i've been working with & on macs i never had a problem like this

The other machine looks to be running a third party KEXT, which is leaking memory in one of the zones (my guess would be AntiVirus software, since in the past they tried to replace system call entry points with their own code drived from OpenDarwin; if we made a change in one of those routines in a point release, they inevitably lead to memory leaks/panics because of the stale code not *exactly* matching the update version).

I'd have to check the machine, but it was delivered without any AV software to the costumer, i'll see what i can find out

It also looks like someone has tuned some of the administrative limits on the number of open fd's up on one of the machines, far past the amount of memory available for such things (a couple of the panics are NULL pointer dererferences following an allocation failure in the M_FILE zoen, which would not occur unless the administrative limits on the machine had been explicitly changed).

Where would one change such a setting?

If you want help beyond that, you will need to file a bug, and likely need to be prepared for two machine debugging.

I'm willing to do that, however, the costumer seems to be expecting all this to be for free, and fixable in a matter of days *sigh*

Since you are running Panther, however, it's unlikely that the answer will be something other than "Upgrade to Tiger; most of this code was rewritten".

That route has already been suggested to the costumer, but rejected because "it would cost money" _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com