Hi,
I’m trying to solve a pattern of kernel panics.
G4 Mirror Door Drive:
• OS 10.4.11
• Dual 1.25
• 1.5 GB RAM
• 1 internal drive, 80 GB, available free space 21 GB
• 1 partition
They’re increasing - from every few months to every week.
Might anyone be able to interpret the panic.logs below, to guess at the cause?
I note that the details are nearly identical for the panics of Sept. 4 and today, Sept. 12.
• KERNEL PANIC OF SEPT. 12 (TODAY):
Logs - /Library/logs - panic.log
Sun Sep 12 12:20:23 2022
panic(cpu 1 caller 0x000E83E4): vnode_put(32a0bdc): iocount < 1
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000E83E4 0x000E8390 0x0010DECC 0x0010E144 0x0010E368
0x000FBA54 0x000E249C 0x000E2030 0x000F51A0 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30
0x00000000
Proceeding back via exception chain:
Exception state (sv=0x37FA9780)
PC=0x90001B2C; MSR=0x0000F030; DAR=0x000FF014; DSISR=0x42000000; LR=0x00005488; R1=0xF007EB30; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********
• KERNEL PANIC OF SEPT. 4:
Logs - /Library/logs - panic.log
Sun Sep 4 15:27:18 2022
panic(cpu 0 caller 0x000E83E4): vnode_put(33ba738): iocount < 1
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000E83E4 0x000E8390 0x0010DECC 0x0010E144 0x0010E368
0x000FBA54 0x000E249C 0x000E2030 0x000F51A0 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30
0x463D2231
Proceeding back via exception chain:
Exception state (sv=0x38020C80)
PC=0x90001B2C; MSR=0x0000F030; DAR=0x000FF014; DSISR=0x42000000; LR=0x00005488; R1=0xF007EB30; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********
• FROM Console - /var/log - crashreporter.log:
...
Fri May 20 16:08:29 2022 crashdump[114]: crashdump invoked as panicdump
Sat Jul 16 17:57:13 2022 crashdump[110]: crashdump invoked as panicdump
Tue Aug 16 17:07:45 2022 crashdump[117]: crashdump invoked as panicdump
Sun Sep 4 15:27:18 2022 crashdump[107]: crashdump invoked as panicdump
Mon Sep 12 12:20:23 2022 crashdump[110]: crashdump invoked as panicdump
_________________________________________________________________________
• Can anyone decipher the logs above, to suggest a cause?
_________________________________________________________________________
– Panics seem to have occurred within 1 to 60 seconds of saving ordinary .rtf word documents ... or clicking to close a document (red button at upper left of document window)
– Panics have occurred both online and offline (TenFourFox)
• One (of two) FW 400 ports is non-working
• One (of two) USB 2.0 ports is working but has sloppy fit (cable relaxes to one side)
• One (of one) FW 800 port is working and tight
– Aside from the panics, computer is stable
– Fan is a smooth quiet sound, except on the three or four very hottest summer days
– No new software has been added
– No changes made inside the case, except careful dusting, including the front air intakes
– G4 runs from a high-quality, true sine wave UPS
– Keeps correct date/time
But battery is not later than 2012
– No memory leaks
Watching “Activity Monitor,” especially later in the day
– Keyboard (wired Macally) and wired mouse are about 6 years old ... worn, but comfortable
A close reading of historical crashreporter.log (goes back to 2008) shows frequent “crashdump started” events with previous owner, up to this year.
The “crashdump started” have occurred from once every few weeks, to three times daily -- but without triggering a kernel panic.
These crashdumps are hidden (unless one reads the log in real time).
_________________________________________________________________________
I’ve been slowly eliminating possible causes, including:
- Disconnected new StarTech USB 2.0 hub
- Synchronized date/time of Brother all-in-one and the desktop
(Brother was showing about 1 minute ahead of desktop time)
- Only turn on Brother all-in-one when needed ... and then don’t shut Brother down til G4 is off
(Turning Brother off while G4 on, was discovered to cause kernel panic every time, in past years, with G4 QuickSilver. Seems to be a flaw in Brother driver)
- Disabled AppleWorks Auto-Save
- Run Maintenance about weekly
All suggestions will be most gratefully appreciated!
Thank you!
Bob
I’m trying to solve a pattern of kernel panics.
G4 Mirror Door Drive:
• OS 10.4.11
• Dual 1.25
• 1.5 GB RAM
• 1 internal drive, 80 GB, available free space 21 GB
• 1 partition
They’re increasing - from every few months to every week.
Might anyone be able to interpret the panic.logs below, to guess at the cause?
I note that the details are nearly identical for the panics of Sept. 4 and today, Sept. 12.
• KERNEL PANIC OF SEPT. 12 (TODAY):
Logs - /Library/logs - panic.log
Sun Sep 12 12:20:23 2022
panic(cpu 1 caller 0x000E83E4): vnode_put(32a0bdc): iocount < 1
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000E83E4 0x000E8390 0x0010DECC 0x0010E144 0x0010E368
0x000FBA54 0x000E249C 0x000E2030 0x000F51A0 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30
0x00000000
Proceeding back via exception chain:
Exception state (sv=0x37FA9780)
PC=0x90001B2C; MSR=0x0000F030; DAR=0x000FF014; DSISR=0x42000000; LR=0x00005488; R1=0xF007EB30; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********
• KERNEL PANIC OF SEPT. 4:
Logs - /Library/logs - panic.log
Sun Sep 4 15:27:18 2022
panic(cpu 0 caller 0x000E83E4): vnode_put(33ba738): iocount < 1
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000E83E4 0x000E8390 0x0010DECC 0x0010E144 0x0010E368
0x000FBA54 0x000E249C 0x000E2030 0x000F51A0 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30
0x463D2231
Proceeding back via exception chain:
Exception state (sv=0x38020C80)
PC=0x90001B2C; MSR=0x0000F030; DAR=0x000FF014; DSISR=0x42000000; LR=0x00005488; R1=0xF007EB30; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********
• FROM Console - /var/log - crashreporter.log:
...
Fri May 20 16:08:29 2022 crashdump[114]: crashdump invoked as panicdump
Sat Jul 16 17:57:13 2022 crashdump[110]: crashdump invoked as panicdump
Tue Aug 16 17:07:45 2022 crashdump[117]: crashdump invoked as panicdump
Sun Sep 4 15:27:18 2022 crashdump[107]: crashdump invoked as panicdump
Mon Sep 12 12:20:23 2022 crashdump[110]: crashdump invoked as panicdump
_________________________________________________________________________
• Can anyone decipher the logs above, to suggest a cause?
_________________________________________________________________________
– Panics seem to have occurred within 1 to 60 seconds of saving ordinary .rtf word documents ... or clicking to close a document (red button at upper left of document window)
– Panics have occurred both online and offline (TenFourFox)
• One (of two) FW 400 ports is non-working
• One (of two) USB 2.0 ports is working but has sloppy fit (cable relaxes to one side)
• One (of one) FW 800 port is working and tight
– Aside from the panics, computer is stable
– Fan is a smooth quiet sound, except on the three or four very hottest summer days
– No new software has been added
– No changes made inside the case, except careful dusting, including the front air intakes
– G4 runs from a high-quality, true sine wave UPS
– Keeps correct date/time
But battery is not later than 2012
– No memory leaks
Watching “Activity Monitor,” especially later in the day
– Keyboard (wired Macally) and wired mouse are about 6 years old ... worn, but comfortable
A close reading of historical crashreporter.log (goes back to 2008) shows frequent “crashdump started” events with previous owner, up to this year.
The “crashdump started” have occurred from once every few weeks, to three times daily -- but without triggering a kernel panic.
These crashdumps are hidden (unless one reads the log in real time).
_________________________________________________________________________
I’ve been slowly eliminating possible causes, including:
- Disconnected new StarTech USB 2.0 hub
- Synchronized date/time of Brother all-in-one and the desktop
(Brother was showing about 1 minute ahead of desktop time)
- Only turn on Brother all-in-one when needed ... and then don’t shut Brother down til G4 is off
(Turning Brother off while G4 on, was discovered to cause kernel panic every time, in past years, with G4 QuickSilver. Seems to be a flaw in Brother driver)
- Disabled AppleWorks Auto-Save
- Run Maintenance about weekly
All suggestions will be most gratefully appreciated!
Thank you!
Bob
