Kernel Panic in 10.2!
I just got my first kernel panic in Jaguar. I haven't had a kernel panic since 10.0 (and then only when I was using the public beta of DAVE). What is with that? I put my TiBook 500 to sleep at work, took it home and when I woke it up I I had a message in several languages telling me that I needed to restart my computer by holding down the power button. Less scary (although also less informative) than the old kernel panic yet with pretty much the same result. Anyone else experiencing in kernel panics in 10.2?
Comments
I myself the owner of the computer haven't noticed any problems with 10.2...
The last kernel panic I ever remember having was way back when 10.1 first came out. Other than that things have been pretty stable.
much better than kernel panics, but still irritating
What is a kernel panic? What is actually happening to cause it, I'm guessing it's a Unix thing.
Andrew
<strong>I also get kernel panics when I wake my G4 up from sleep in Mac OS 10.1.5.
What is a kernel panic? What is actually happening to cause it, I'm guessing it's a Unix thing.
</strong><hr></blockquote>
It means that the system failed at the most basic level, and the only option left is a reboot.
The older MacOS analog would the dreaded empty bomb dialog followed by a hard freeze.
I'm waiting for the .1 update. Jaguar sounds great, but it also sounds like a .0 release...
You can send your Kernel Panic to Apple. apple.com/macosx/feedback
Select "About This Mac" in the Apple Menu and select on More Info.... This opens the Apple System Profiler. You can also open it via the "Utilities" folder that is in the Application folder.
Look on the last tab. It says LOGS. There will be one called, aptly enough, Kernel Panic Log.
You can copy and paste that material.
Apple made it so that info gets stored into NVRAM a second before the whole system goes to shite.
By looking at the blurb, you can usually tell what is to blame.
For example, I got a Kernel Panic and this is what it says:
Wed Sep 4 19:33:18 2002
panic(cpu 0): lockmgr: pid 1465, thread 0x 366d000, not exclusive lock holder pid 1469 thread 0x 355ae34 unlocking, exclusive count 1
Latest stack backtrace for cpu 0:
Backtrace:
0x0008593C 0x00085D6C 0x00028B8C 0x001D4308 0x13F22E1C 0x13F22BF4 0x13F22E48 0x13F23638
0x13F229E0 0x13F2D3CC 0x13F24EE4 0x000BD898 0x001E2A4C 0x00203A1C 0x00092830 0xFFF8F8F8
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.smbfs(1.1)@0x13f14000
Proceeding back via exception chain:
Exception state (sv=0x139F3500)
PC=0x90004BCC; MSR=0x0000F030; DAR=0x01E55E36; DSISR=0x00002C1D; LR=0x00005D88; R1=0xBFFFEBE0; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 6.0:
Sat Jul 27 13:18:52 PDT 2002; root:xnu/xnu-344.obj~1/RELEASE_PPC
As you can see, there is com.apple.filesystems.smbfs in there and as it suggests (SMB windows file sharing), I got a kernel panic while looking for a Windows machine on my network.
So, now you can just copy n paste the Kernel Panics and send them to Apple for feedback.
One other time while playing a game I got the screen that I had to restart the computer. The new KP screen came up.
When I went to look at the logs, there was no sign of the KP I had just had.
Maybe OSX didnt have enough time to write to NVRAM, I really dont know.
Amorph: Build 6D46 of 10.2.1 seems to be quite an improvement. The only problems I had with Jaguar were:
- sometimes very, very slow at shutting down
[fixed with 6D46]
- sometimes black screen when returning from stand-by (e.g. machine probably crashed)
[fixed with 6D46, it appears]
- delays after first log in - also fixed
This is on an iBook 700. The update was a bit more than 16 Megs, so it's not too bad.
Thank god for builtin SMB now... good riddance Dave
then again, heh, the only KP I had in 10.2 was SMB related
<strong>Dave gave me at least 3 KPs also in 10.1
Thank god for builtin SMB now... good riddance Dave
then again, heh, the only KP I had in 10.2 was SMB related
I've had 2 or 3 KPs due to Samba. But I usually don't have probs with it.
Exactly the same thing just happened again!
when i get my dual g4 ..maybe
but at the moment my h/w aint up to the job, then again neither is the s/w
9.2 rules.
i've got an iBook700, which i've had 10.2 installed since the day it came out (8/24). it was running perfectly (no kernal panics) until 9/8, when i got my first kernal panic. this was then followed by a strange monitor problem (all garbled or no image at all). whenever this would happen, the computer would crash. i sent it into apple.. got it back 3 days later (go apple!). unfortunately it seems all they fixed was the monitor. since then, i've had about 3-4 kernel panics/day. i reinstalled 10.2, no change.. i took out the extra ram, no change... installed 10.1.5, worked perfectly!.. got daring and installed 10.2 again.. back to 3-4 kernel panics/day.
so my question is this.. has anyone else had so many kernel panics in 10.2?.. i find it hard to believe that it is a hardware problem, which occurred when my monitor went bad, since 10.1.5 works fine.
(i don't want to send it back to apple if it's simply a problem which will be fixed with an update to 10.2)
sorry to give you my iBook's recent life story, just hoping it would help in deciphering the problem.
thanks,
erik
<strong>
so my question is this.. has anyone else had so many kernel panics in 10.2?.. i find it hard to believe that it is a hardware problem, which occurred when my monitor went bad, since 10.1.5 works fine.
(i don't want to send it back to apple if it's simply a problem which will be fixed with an update to 10.2)
</strong><hr></blockquote>
I have only had those two, but I think I could have a lot more if I wanted. That is, I have a theory as to why I got the two I did (I think it doesn't like it if I unplug my USB floppy drive when it is asleep). I haven't gotten around to testing this theory because I don't like kernel panics.
The point is that usually if you are getting kernel panics they happen when you hit some particular piece of code, so you have to ask yourself if there is something different you are doing. You probably knew that already though. I guess the other possibility is that you have some bad RAM. That might explain both the kernel panics and the monitor. Something like a lightening strike could have fried both your RAM and your screen at the same time although it seems sort of unlikely. You probably knew all that but that is as much of an idea as I have.
-alcimedes