Quella che segue è una semplice domanda che per me è difficile da diagnosticare perché causa un blocco hardware che i daemon del sistema sembrano non essere in grado di registrare. Come utente esperto, ho il pieno controllo del mio sistema come root e mi aspetto, dalle prove circostanziali, che ciò sia correlato a un problema di driver audio con l'ultimo aggiornamento a 10.6.8 . Non so come risolvere il problema, comunque.
Per prima cosa, confrontiamo un caso standard di spegnimento improprio, in base a system.log , in cui ho tenuto premuto il pulsante di accensione per riavviare la macchina. Tieni presente che il nome host della mia casella in questi log è stato sostituito con hostname per impedire l'identificabilità.
Oct 18 12:20:29 hostname com.apple.launchd.peruser.364919944[304] (com.apple.PreferenceSyncAgent): fork() failed, will try again in one second: Resource temporarily unavailable
Oct 18 12:20:29 hostname postfix/sendmail[98904]: warning: fork: Resource temporarily unavailable
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Oct 18 12:21:31 localhost com.apple.kextd[10]: Can't create kext cache under / - owner not root.
Oct 18 12:21:20 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***
Ora, diamo un'occhiata a system.log durante uno di questi blocchi fissi:
Oct 18 14:27:18 localhost com.apple.kextd[10]: Can't create kext cache under / - owner not root.
Oct 18 14:27:09 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***
Oct 18 14:27:19 localhost DirectoryService[11]: Improper shutdown detected
Oct 18 14:27:20 localhost blued[15]: Apple Bluetooth daemon started
kernel.log , spegnimento improprio standard:
Oct 18 12:18:14 hostname kernel[0]: Sound assertion "0 != result" failed in AppleMikeyDevice at line 765 goto handler
Oct 18 12:18:14 hostname kernel[0]: Sound assertion "0 != result" failed in AppleMikeyDevice at line 795 goto handler
Oct 18 12:18:14 hostname kernel[0]: Sound assertion "0 != dispatchToStateMachinePosition ( dequeuedEvent )" failed in AppleMikeyDevice at line 721 goto handler
Oct 18 12:18:14 hostname kernel[0]: Sound assertion "0 != result" failed in AppleMikeyDevice at line 765 goto handler
Oct 18 12:18:14 hostname kernel[0]: Sound assertion "0 != result" failed in AppleMikeyDevice at line 795 goto handler
Oct 18 12:18:14 hostname kernel[0]: Sound assertion "0 != dispatchToStateMachinePosition ( dequeuedEvent )" failed in AppleMikeyDevice at line 721 goto handler
Oct 18 12:18:28 hostname kernel[0]: Sound assertion "0 != result" failed in AppleMikeyDevice at line 765 goto handler
Oct 18 12:18:28 hostname kernel[0]: Sound assertion "0 != result" failed in AppleMikeyDevice at line 795 goto handler
Oct 18 12:18:28 hostname kernel[0]: Sound assertion "0 != dispatchToStateMachinePosition ( dequeuedEvent )" failed in AppleMikeyDevice at line 721 goto handler
Oct 18 12:18:28 hostname kernel[0]: Sound assertion "0 != result" failed in AppleMikeyDevice at line 765 goto handler
Oct 18 12:18:28 hostname kernel[0]: Sound assertion "0 != result" failed in AppleMikeyDevice at line 795 goto handler
Oct 18 12:18:28 hostname kernel[0]: Sound assertion "0 != dispatchToStateMachinePosition ( dequeuedEvent )" failed in AppleMikeyDevice at line 721 goto handler
Oct 18 12:21:31 localhost kernel[0]: npvhash=4095
Oct 18 12:21:31 localhost kernel[0]: PAE enabled
Oct 18 12:21:31 localhost kernel[0]: 64 bit mode enabled
kernel.log , hard freeze:
Oct 18 13:45:19 hostname kernel[0]: CoreServicesUIAg[1076] Unable to clear quarantine 'Headers': 93
Oct 18 13:45:19 hostname kernel[0]: CoreServicesUIAg[1076] Unable to clear quarantine 'Resources': 93
Oct 18 13:45:19 hostname kernel[0]: CoreServicesUIAg[1076] Unable to clear quarantine 'Sparkle': 93
Oct 18 13:45:19 hostname kernel[0]: CoreServicesUIAg[1076] Unable to clear quarantine 'Current': 93
Oct 18 14:27:18 localhost kernel[0]: npvhash=4095
Oct 18 14:27:18 localhost kernel[0]: PAE enabled
Oct 18 14:27:18 localhost kernel[0]: 64 bit mode enabled
Tieni presente che i reclami di CoreServicesUIAg sono consistenti in entrambi i blocchi bloccati.
Non ho informazioni aggiuntive, nella misura in cui nessuna .hang o .crash sembra essere stata generata sul mio sistema e tutti gli altri registri sembrano a posto. Tuttavia, ho lasciato la workstation bloccata durante la notte e non ho subito lo stesso blocco hardware, e mi sembra che stia facendo proprio questo messaggio sulla macchina con audio disabilitato.
Addendum : la temperatura interna e altri parametri di diagnostica hardware sembravano riportare entro intervalli completamente tollerabili. L'ultima lettura che avevo ricevuto prima del secondo crash era da qualche parte nell'intervallo 54-55 ° C, che è piuttosto interessante per quanto riguarda le CPU.
Secondo addendum : questo articolo potrebbe essere correlato, ma non ho dati di test. Se questo è plausibile, tornerò semplicemente a 10.6.7 e vediamo cosa succede.
Sono disponibili informazioni per questo problema? In tal caso, esiste un semplice aggiornamento rapido o una soluzione che posso applicare alla mia macchina per ripristinare la stabilità senza tornare a una versione precedente?
Grazie in anticipo.