Stallo wireless: TXQ MAX DEPTH?

1

Hai un nuovissimo iMac 27 "Mid 2011 - Core i5 e quando esegui il backup dei dati dal vecchio iMac, attraverso il wireless, la rete si blocca e poi si ferma, dopo alcuni minuti si riavvia.

Trovato questo problema più volte, cambiato da DHCP a DHCP con indirizzo manuale e senza fortuna.

In console, mostra (elencherà 2 log, in pratica lo stesso, ma ne ha molti altri):

log n. 1:

8/15/11 11:23:51.000 AM kernel: 452.012114: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:51.000 AM kernel: 452.012126: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:51.000 AM kernel: 452.215613: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:51.000 AM kernel: 452.216788: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:51.000 AM kernel: 452.216793: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:52.000 AM kernel: 452.625339: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:52.000 AM kernel: 452.626497: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:52.000 AM kernel: 452.626508: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:52.000 AM kernel: 452.932507: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:52.000 AM kernel: 452.933563: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:52.000 AM kernel: 452.933575: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:52.000 AM kernel: 452.982171: [3] TXQ MAX DEPTH!!!
8/15/11 11:23:52.000 AM kernel: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
8/15/11 11:23:52.000 AM kernel: 453.217553: setDISASSOCIATE ****STA SYNC DISASSOC SUCCESS  

log # 2:

8/15/11 12:40:51.000 PM kernel: 5072.454012: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:51.000 PM kernel: 5072.455714: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:51.000 PM kernel: 5072.455727: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:51.000 PM kernel: 5072.658185: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:51.000 PM kernel: 5072.659343: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:51.000 PM kernel: 5072.659355: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:52.000 PM kernel: 5072.863003: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:52.000 PM kernel: 5072.864160: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:52.000 PM kernel: 5072.864171: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:52.000 PM kernel: 5073.068132: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:52.000 PM kernel: 5073.069283: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:52.000 PM kernel: 5073.069295: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:52.000 PM kernel: 5073.682531: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:52.000 PM kernel: 5073.683721: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:52.000 PM kernel: 5073.683732: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:53.000 PM kernel: 5073.887015: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:53.000 PM kernel: 5073.888171: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:53.000 PM kernel: 5073.888182: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:53.000 PM kernel: 5074.296944: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:53.000 PM kernel: 5074.298100: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:53.000 PM kernel: 5074.298112: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:54.000 PM kernel: 5074.911379: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:54.000 PM kernel: 5074.912536: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:54.000 PM kernel: 5074.912548: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:54.000 PM kernel: 5075.526138: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:54.000 PM kernel: 5075.527208: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:54.000 PM kernel: 5075.527218: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:54.000 PM kernel: 5075.730286: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:54.000 PM kernel: 5075.731441: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:54.000 PM kernel: 5075.731453: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:55.000 PM kernel: 5076.140428: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:55.000 PM kernel: 5076.141569: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:55.000 PM kernel: 5076.141575: [3] TXQ MAX DEPTH!!!
8/15/11 12:40:55.000 PM kernel: en1: BSSID changed to 90:84:0d:dd:c4:b4
8/15/11 12:40:55.000 PM kernel: AirPort: RSN handshake complete on en1
8/15/11 12:43:30.000 PM kernel: (default pager): [KERNEL]: ps_allocate_cluster - send HI_WAT_ALERT
8/15/11 12:43:30.000 PM kernel: macx_swapon SUCCESS

Pensa che ciò accada solo quando copi file di grandi dimensioni (più grandi di 3.5gb) ...

Qualche idea?

    
posta Fernando M. Pinheiro 15.08.2011 - 17:48
fonte

1 risposta

2

Aggiornato a OS X Lion 10.7.1 risolto il problema. Nel link specifica "Migliora l'affidabilità delle connessioni Wi-Fi" che potrebbe essere questo problema.

Comunque, funziona davvero bene ora.

    
risposta data 19.08.2011 - 20:31
fonte

Leggi altre domande sui tag