Attack of the Kernel Panic!!!

sk7

Registered
I’m so frustrated right now :mad: . I came home last night from work and was met w/ a kernel panic. I rebooted and it still happened. I then repaired permissions, repaired the disks, tested the RAM modules, unplugged all non-essential hardware, and did a safe boot and still got a kernel panic. No new software or hardware has been recently added to my machine.

I’m running Tiger OS on a PowerMac G4 (Mirrored Doors) DP1.25 w/ the lasted updates as of Nov 15, 2005. Any assistance would be well appreciated ;) . The kernel panic I received was as follows…

Resetting files and devices
panic(cpu 0 caller 0x00102164): jnl transaction too big (1044992 >= 1048064 bytes, bufsize 4096, tr 0x21cbfb0 bp 01e1cd770)

Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095bb0 0x0002683c 0x00102164 0x002478f8 0x00246f00 0x00245258 0x00245320
0x002453d4 0x00246150 0x0022ae54 0x0022b068 0x00239558 0x002390dc 0x000fc4bc 0x000ee14c
0x002a9bf4 0x000abe30 0x00000000

Proceeding back via exception chain:
Exception state (sv=0x21283780)
PC=0x9001b12c; MSP=0x0000f030; DAR=0x220d5000; DSISR=0x42000000; LR=0x00002eec; R1=0xbffffd60; XCP=0x00000030 (0xc00 – System call) :confused:

THANK YOU IN ADVANCE! :D
 
'jnl transaction too big' indicates a Journal file problem. Turn off Journaling and see what happens.
 
I just finished restoring from a backup. However, I think your right after reading a couple of postings online stating that "jnl" is associated the Journal file.

I wonder if there is a way to limit the Journal file size or periodically delete it. Anyway thanks a million for confirming this, hopefully this won't happen a 3rd time.
Thanks again.

-sk7
 
Back
Top