[mloiterman]

This morning my wife woke up to an odd kernel panic. Machine was just idle...everyone was asleep. I did a single user boot afterwards, /sbin/fsck -yf and repaired permissions. No problems were found in the fsck, but there were a few files messed up on the permissions repair. Machine has been totally trouble free since we got it a few months ago.

iMac 17in G5, 512 of RAM, and Airport Express.

Here is the ouput from the repair permissions:

Repairing permissions for “Macintosh HD”
Determining correct file permissions.
We are using special permissions for the file or directory ./System/Library/Filesystems/cd9660.fs/cd9660.util. New permissions are 33261
Permissions differ on ./private/var/log/install.log, should be -rw-r--r-- , they are -rw-r-----
Owner and group corrected on ./private/var/log/install.log
Permissions corrected on ./private/var/log/install.log
Permissions differ on ./private/var/log/wtmp, should be -rw-r--r-- , they are -rw-r-----
Owner and group corrected on ./private/var/log/wtmp
Permissions corrected on ./private/var/log/wtmp
The privileges have been verified or repaired on the selected volume

Here is the panic.log.

Thu Dec 16 05:24:38 2004




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000003742334E PC=0x0000000000BE2554
Latest crash info for cpu 0:
Exception state (sv=0x00EDEA00)
PC=0x00BE2554; MSR=0x00009030; DAR=0x3742334E; DSISR=0x40000000; LR=0x00BE2FA8; R1=0x0D0DBB10; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00BE2FA8 0x00BE2F0C 0x00BCC1C4 0x0027DC90 0x0027F964 0x0007B1D4 0x00021668
0x0001BCE8 0x0001C0F0 0x00094358 0x006B6FF0
backtrace terminated - frame not mapped or invalid: 0xBFFFDD70

Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(3.3.4)@0xbc5000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x395000
dependency: com.apple.iokit.IOGraphicsFamily(1.3.3)@0x4b2000
dependency: com.apple.NVDAResman(3.3.4)@0x4e7000
dependency: com.apple.iokit.IONDRVSupport(1.3.3)@0x4d1000
com.apple.NVDAResman(3.3.4)@0x4e7000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x395000
dependency: com.apple.iokit.IOGraphicsFamily(1.3.3)@0x4b2000
dependency: com.apple.iokit.IONDRVSupport(1.3.3)@0x4d1000
Proceeding back via exception chain:
Exception state (sv=0x00EDEA00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x235BE780)
PC=0x900074C8; MSR=0x0000F030; DAR=0xE075C000; DSISR=0x42000000; LR=0x90007018; R1=0xBFFFDD70; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.6.0:
Sun Oct 10 12:05:27 PDT 2004; root:xnu/xnu-517.9.4.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000836E4 0x00083BC8 0x0001EDA4 0x00090C60 0x0009406C
Proceeding back via exception chain:
Exception state (sv=0x00EDEA00)
PC=0x00BE2554; MSR=0x00009030; DAR=0x3742334E; DSISR=0x40000000; LR=0x00BE2FA8; R1=0x0D0DBB10; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00BE2FA8 0x00BE2F0C 0x00BCC1C4 0x0027DC90 0x0027F964 0x0007B1D4 0x00021668
0x0001BCE8 0x0001C0F0 0x00094358 0x006B6FF0
backtrace terminated - frame not mapped or invalid: 0xBFFFDD70

Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(3.3.4)@0xbc5000
dependency: com.app`
*********

[osxrules]

Kernel panics aren't as bad as they are made out and you don't really have to check your filesystem or do repairs. I've had a few and I just restart and forget about it.

I suppose it depends on specific panics but mine have all been caused by my graphics card as has your one. Most system updates now have updated graphics drivers so Apple are finding problems with them all the time.

It's unlikely that you'll get a panic often but check system updates to see if new drivers are available. There are new ones in 10.3.7.

[Big Mac]

As osxrules stated, one kernel panic is not a terrible problem. KPs have nothing to do with permissions issues, and the entry you saw about different permissions is normal. It does seem to be a graphics card issue - most likely a Nvidia driver bug. You may as well send the log to Apple, but don't lose sleep over this.