Out of the blue, I noticed that I couldn't mount *.dmg files anymore this morning (Disk Copy would come up and quit immediately). I figured it might help to log out and back in, but after I logged out, I was presented a blue screen instead of the login window. I found out that loginwindow keeps crashing every 30 secs. I have file sharing enabled, so I can look at the logs, but unfortunately, ssh is disabled.
I know there are threads about similar problems in this forum, but none of them helped much so far.
Here's what I tried so far:
- Booted from CD and used Disk Utiliy to repair the Volume and Permissions (the Volume actually still has a problem, but since I can mount it via filesharing, I assume that's another problem)
- removed /Library/Preferences/com.apple.loginwindow.plist and ~/Library/Preferences/com.apple.loginwindow.plist
Right now I'm at my wits end and would really appreciate some advice on what to do (No, I don't want to reinstall :-)
I'm appending what I found in the logs, just in case anyone can make more sense out of them than I can.
Oh, I'm on a GHz PowerBook with 10.2.4, BTW.
Thanks in advance,
-sapporo.
---
# system.log
Feb 21 21:13:45 calculon crashdump: Crash report written to: /Library/Logs/CrashReporter/loginwindow.crash.log
Feb 21 21:13:47 calculon crashdump: Crash report written to: /Library/Logs/CrashReporter/loginwindow.crash.log
Feb 21 21:13:47 calculon init: getty repeating too quickly on port /dev/console, sleeping
# repeated every 30 seconds
---
# /Library/Logs/CrashReporter/loginwindow.crash
Date/Time: 2003-02-21 21:16:28 +0100
OS Version: 10.2.4 (Build 6I32)
Host: calculon.local.
Command: loginwindow
PID: 625
Exception: EXC_BREAKPOINT (0x0006)
Code[0]: 0x00000001Code[1]: 0x8fe01280
Thread 0 Crashed:
#0 0x8fe01280 in halt
#1 0x8fe0329c in load_library_image
#2 0x8fe06134 in load_images_libraries
#3 0x8fe05b28 in load_dependent_libraries
#4 0x8fe026f4 in load_executable_image
#5 0x8fe01410 in _dyld_init
PPC Thread State:
srr0: 0x8fe01280 srr1: 0x0002f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x8fe0a064 ctr: 0x8fe3aefc mq: 0x00000000
r0: 0x8fe0a03c r1: 0xbffffbd0 r2: 0x6f6e732f r3: 0xffffffff
r4: 0xffffffff r5: 0x000000fb r6: 0x0000290a r7: 0x726e6f20
r8: 0x66696c65 r9: 0x00000000 r10: 0xbffff94b r11: 0x00000026
r12: 0x88004442 r13: 0x00000000 r14: 0x0000dfd0 r15: 0x00000000
r16: 0xbffffed4 r17: 0x00000001 r18: 0x00001614 r19: 0x00004280
r20: 0x00000001 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x0008f3c8 r25: 0x00000002 r26: 0x00000002 r27: 0x00000000
r28: 0x90a8089c r29: 0x00000000 r30: 0x8fe484d8 r31: 0x8fe09ecc
sapporo
02-22-2003, 08:30 AM
Just for the record: The problem was filesystem-related, and I was able to repair my disk by mounting it in target disk mode and repeatedly running Norton Disk Doctor.
-sapporo.