When I said I doubt the culprit was the Dev Studio I meant that to fix the problem, the Dev Studio probably doesn't need to change. Instead, I thought the hardware, firmware or OS needs to change.
But Phil has weighed in on this with much more information.
FYI, the mach kernel and AppleMPIC files have the same MD5 hash value on both OS X and OS X Server. You'll probably have the same problems with OS X Server. Still, it might be worth a try.
- Jeff
At 01:43 PM 8/19/2003, you wrote:--
The dual-proc G4 I was referring to is a desktop model, not an xserve. We are running OS X Server 10.2.6 on it.
So there is one possibility, the non-server version of OS X... and I suppose another could be the newer hardware.
We have other single-processor machines running OS X 10.2.6 and Witango, also without kernel panics.
Yes, so do I, that's definitely not the issue.
Hmm.. I do have a copy of OS X Server somewhere, maybe I'll try that. (heck, I'll try just about anything at this point... right now I pretty much have a useless dual G4, since I can't put it into production)
I'm no kernel developer, but I doubt the true culprit is the Dev Studio.
When I say it ran fine (for well over 2 weeks, actually) with just the OS, and when I installed and ran Dev Studio it Kernel panicked within 3 days, what logic can you use to come to the conclusion that Dev Studio does not have this issue? (apparently related to only the non-server version of the OS, or more recent versions of the hardware..)
Then, if I don't run Dev Studio it is again fine. I then installed WebStar and it is still stable for almost 2 weeks, but I then install and run WiTango App server and it will again Kernel panic within 3 days every time.. (and again, if I don't start the App server, it will not crash)
I have tried different physical RAM. I'm not sure how it could be any clearer that something that WiTango Dev Studio / App Server are doing is leading to the Kernel panics.
When I explained that to the Apple Technical Support people on the phone, they pretty clearly said they wouldn't do anything for me, period. They said I had to get the 3rd party developer to solve the problem.
To be fair, I also believe that it is more likely a bug in OS X. I still don't think software should be able to cause a kernel panic unless there is a bug in the OS, or there is a hardware problem. Since RAM now seems unlikely, I think I need to find another Dual G4 running OS X (non-server) and the App Server before I can send it back to our Apple Tech. (though I will ask him if he'll try to fix it anyway, once he's back from holidays in another week, simply for lack of anything else to try)
If there was any way that it even remotely looked like it wasn't the WiTango software, I would gladly go back to Apple Tech Support... but given the circumstances, I can't think of any way to even suggest to them that it might not be WiTango.. so if you could explain your line of thinking to me, that would be really helpful.
It might help to give the With folks the screen output of your kernel panics.
I have sent a few of the kernel panics to the With folks in a bug report and at least one email, but it's been several days now and no reply, so I'm not holding my breath on a resolution from them.
There's an Apple document on logging kernel panic messages at www.info.apple.com.
Ya, that was what I was referring to on one of my earlier posts. It pretty much sums up to say that if you have a kernel panic, you can submit it to the "Apple Discussions" and has a link to http://discussions.info.apple.com/ and that's it. Of all the discussions and links there, I thought the feedback one most relevant, but it certainly isn't clear.
Thanks again Jeff, I do appreciate the suggestions and ideas, and your time. I'm certainly not getting -any- help from Apple, and still waiting on With.
Cheers
- Andrew
Jeff,
Thanks once again for your suggestion. Unfortunately, I am only using one slot for the 512MB.
I think I got one of the last Dual G4s before the G5 came out. It's 1.4GHz.. but it does have the mirrored drive doors. You say you are using xserve though, right? Isn't that a somewhat different hardware/software configuration? My OS is currently 10.2.6, and it's not OS X server, just the regular OS X.
I think I submitted an Apple support message or something on this issue. It seemed more like feedback and indicated that I probably wouldn't get a response.
I tried phoning the Apple support line and they tried really hard to get me to talk to the software people, (WiTango) but I kept at him, since to me.. well, -any- software should not be able to cause a kernel panic, even if it tried.. because it's all protected and stuff, right? However, he finally just passed the phone on to someone else that simply said any software can cause a kernel panic. He then said that since it's clearly identified to a single piece of 3rd party software, that they have to fix it. I asked if there's -anything- Apple could do to help, and he said no.. that the developer (WiTango) can talk with Apple through their developer channels.
If it weren't for the fact that running Dev Studio without any other piece of software on the machine causes it to Kernel panic, then I would try Apache.. but I think because of that I can fairly safely say it's WiTango.
Seems like I have to wait to see when WiTango will reply. That's how it always works, right? Blame the other people until they can absolutely positively prove that it's not them.. then, maybe Apple will look at it. *sigh*
Thanks again..
Cheers
- Andrew
At 10:13 AM 8/19/2003, you wrote:On Monday, August 18, 2003, at 09:22 PM, Christian Platt wrote:
We are running xserve dual, tons of ram, apache, witango now for a while
(since 5 came out). Ist rock stable, I do not use studio on produktion, but
there is still an installation on it.
We do not use WebStar, but apache (I use webstar with os 9 version).
Two questions:
* RAM - you really need lots of it - how much do you have
* Webstar - this can also be a reason for failure - want to try apache?
Christian
I'm running webstar and since the plug-in issue was resolved, it's just fine with witango. no reports on the webstar list of dual processor machines crashing.
We use a dual 1 GHz G4, 1.75 GB RAM, apache and Witango 5.0.1.062 (first generation mirrored drive doors). We've had the machine for about 10 months and have had no kernel panics. The app server does crash under load, though (ODBC/OS X problems).
Since you're seeing kernel panics, this sounds like an issue for Apple support. I recall reports about mirrored drive door machines with the maximum of 2GB RAM installed having problems. If you're using all RAM slots, try removing a module and see if the kernel panics stop.
- Jeff
--
Jeff Bohmer VisionLink, Inc. _________________________________ 303.402.0170 www.visionlink.org _________________________________ People. Tools. Change. Community. ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
