Problema resolvido ...
Gwibber foi quem consumiu meus recursos ... Tive que desmarcar as configurações: "Iniciar quando logar"
Por que quando eu conecto meu netbook à Internet via LAN ou Wifi, todo o sistema fica lento? Mesmo quando inativo, o monitor da CPU mostra 100% de uso quando conectado. Eu tive esse problema cerca de meio ano agora, desde que eu instalei o Ubuntu 11.10.
Atualmente, estou usando o Ubuntu 12.04 LTS em um netbook Toshiba NB-105 Satellite com 1 GB de RAM e um processador Intel Atom de 1 GHz.
Aqui está o meu syslog
:
$ tail -n 30 /var/log/syslog
May 23 02:45:28 jesselan-NB-105 kernel: [17552.933099] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
May 23 02:45:28 jesselan-NB-105 kernel: [17552.935345] sd 6:0:0:0: [sdb] Asking for cache data failed
May 23 02:45:28 jesselan-NB-105 kernel: [17552.935360] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 23 02:46:20 jesselan-NB-105 kernel: [17604.643371] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
May 23 02:46:20 jesselan-NB-105 kernel: [17604.649520] sd 6:0:0:0: [sdb] Asking for cache data failed
May 23 02:46:20 jesselan-NB-105 kernel: [17604.649547] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 23 02:47:11 jesselan-NB-105 kernel: [17656.349121] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
May 23 02:47:11 jesselan-NB-105 kernel: [17656.351373] sd 6:0:0:0: [sdb] Asking for cache data failed
May 23 02:47:11 jesselan-NB-105 kernel: [17656.351392] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 23 02:48:03 jesselan-NB-105 kernel: [17708.069032] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
May 23 02:48:03 jesselan-NB-105 kernel: [17708.071240] sd 6:0:0:0: [sdb] Asking for cache data failed
May 23 02:48:03 jesselan-NB-105 kernel: [17708.071254] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 23 02:48:55 jesselan-NB-105 kernel: [17759.901056] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
May 23 02:48:55 jesselan-NB-105 kernel: [17759.903757] sd 6:0:0:0: [sdb] Asking for cache data failed
May 23 02:48:55 jesselan-NB-105 kernel: [17759.903774] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 23 02:49:48 jesselan-NB-105 kernel: [17812.913124] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
May 23 02:49:48 jesselan-NB-105 kernel: [17812.915338] sd 6:0:0:0: [sdb] Asking for cache data failed
May 23 02:49:48 jesselan-NB-105 kernel: [17812.915365] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 23 02:50:40 jesselan-NB-105 kernel: [17864.205232] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
May 23 02:50:40 jesselan-NB-105 kernel: [17864.207449] sd 6:0:0:0: [sdb] Asking for cache data failed
May 23 02:50:40 jesselan-NB-105 kernel: [17864.207461] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 23 02:51:34 jesselan-NB-105 kernel: [17918.353070] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
May 23 02:51:34 jesselan-NB-105 kernel: [17918.355337] sd 6:0:0:0: [sdb] Asking for cache data failed
May 23 02:51:34 jesselan-NB-105 kernel: [17918.355347] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 23 02:52:25 jesselan-NB-105 kernel: [17969.913237] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
May 23 02:52:25 jesselan-NB-105 kernel: [17969.915480] sd 6:0:0:0: [sdb] Asking for cache data failed
May 23 02:52:25 jesselan-NB-105 kernel: [17969.915506] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 23 02:53:17 jesselan-NB-105 kernel: [18021.721949] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
May 23 02:53:17 jesselan-NB-105 kernel: [18021.724196] sd 6:0:0:0: [sdb] Asking for cache data failed
May 23 02:53:17 jesselan-NB-105 kernel: [18021.724210] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Seguindo a sugestão do agc93 para verificar quais processos em execução são mais intensivos em CPU, parece que é o gwibber.service seguido pelo Google Chrome e pelo Ubuntu One. O que devo fazer sobre isso?
Problema resolvido ...
Gwibber foi quem consumiu meus recursos ... Tive que desmarcar as configurações: "Iniciar quando logar"