May 3 12:11:26 ditec-desur-03 kernel: [ 27.557725] [drm] Initialized drm 1.1.0 20060810
May 3 12:11:26 ditec-desur-03 kernel: [ 27.583940] ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 17 (level, low) -> IRQ 17
May 3 12:11:26 ditec-desur-03 kernel: [ 27.584009] [drm] Initialized radeon 1.29.0 20080528 on minor 0
May 3 12:11:27 ditec-desur-03 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
May 3 12:11:27 ditec-desur-03 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
May 3 12:11:27 ditec-desur-03 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_search
May 3 12:11:27 ditec-desur-03 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
May 3 12:11:27 ditec-desur-03 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
May 3 12:11:27 ditec-desur-03 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu
May 3 12:11:28 ditec-desur-03 kernel: [ 29.617163] [drm] Setting GART location based on new memory map
May 3 12:11:28 ditec-desur-03 kernel: [ 29.617163] [drm] Loading R300 Microcode
May 3 12:11:28 ditec-desur-03 kernel: [ 29.617163] [drm] Num pipes: 2
May 3 12:11:28 ditec-desur-03 kernel: [ 29.617163] [drm] writeback test succeeded in 1 usecs
May 3 12:11:32 ditec-desur-03 kernel: [ 34.196520] warning: `ntpd' uses 32-bit capabilities (legacy support in use)
May 3 12:12:22 ditec-desur-03 kernel: [ 85.256864] Not cloning cgroup for unused subsystem ns
May 3 12:29:15 ditec-desur-03 kernel: [ 1154.518992] [drm] Num pipes: 2
May 3 12:29:20 ditec-desur-03 kernel: [ 1159.312972] [drm] Loading R300 Microcode
May 3 12:29:20 ditec-desur-03 kernel: [ 1159.312972] [drm] Num pipes: 2
May 3 12:45:25 ditec-desur-03 kernel: imklog 3.18.6, log source = /proc/kmsg started.
May 3 12:45:25 ditec-desur-03 rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2294" x-info="http://www.rsyslog.com"] restart
May 3 12:45:25 ditec-desur-03 kernel: imklog 3.18.6, log source = /proc/kmsg started.
May 3 12:45:25 ditec-desur-03 rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2294" x-info="http://www.rsyslog.com"] restart
May 3 12:45:26 ditec-desur-03 kernel: imklog 3.18.6, log source = /proc/kmsg started.
May 3 12:45:26 ditec-desur-03 rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2294" x-info="http://www.rsyslog.com"] restart
May 3 12:45:55 ditec-desur-03 anacron[2898]: Job `cron.daily' terminated
May 3 12:45:55 ditec-desur-03 anacron[2898]: Normal exit (1 job run)
May 3 13:17:01 ditec-desur-03 /USR/SBIN/CRON[4082]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 3 14:17:01 ditec-desur-03 /USR/SBIN/CRON[4139]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 3 15:17:01 ditec-desur-03 /USR/SBIN/CRON[4208]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 3 15:18:49 ditec-desur-03 kernel: [12985.683782] hda-intel: Invalid position buffer, using LPIB read method instead.
May 3 16:06:52 ditec-desur-03 ntpd[2768]: kernel time sync status change 4001
May 3 16:17:01 ditec-desur-03 /USR/SBIN/CRON[4330]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 3 16:23:58 ditec-desur-03 ntpd[2768]: kernel time sync status change 0001
May 3 17:17:01 ditec-desur-03 /USR/SBIN/CRON[4514]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 3 17:32:17 ditec-desur-03 ntpd[2768]: kernel time sync status change 4001
May 3 17:49:23 ditec-desur-03 ntpd[2768]: kernel time sync status change 0001
May 3 18:17:01 ditec-desur-03 /USR/SBIN/CRON[4659]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 3 18:23:33 ditec-desur-03 ntpd[2768]: kernel time sync status change 4001
May 3 18:40:37 ditec-desur-03 ntpd[2768]: kernel time sync status change 0001
May 3 19:17:01 ditec-desur-03 /USR/SBIN/CRON[4681]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
apt/ daemon.log dmesg.4.gz kern.log.4.gz popularity-contest.0 syslog.6.gz
aptitude daemon.log.1 dpkg.log lastlog popularity-contest.1.gz syslog.7.gz
aptitude.1.gz daemon.log.2.gz dpkg.log.1 lpr.log popularity-contest.2.gz unattended-upgrades/
aptitude.2.gz daemon.log.3.gz dpkg.log.2.gz mail.err popularity-contest.3.gz user.log
aptitude.3.gz daemon.log.4.gz dpkg.log.3.gz mail.info popularity-contest.4.gz user.log.1
auth.log debug exim4/ mail.log popularity-contest.5.gz user.log.2.gz
auth.log.1 debug.1 faillog mail.warn popularity-contest.6.gz user.log.3.gz
auth.log.2.gz debug.2.gz fontconfig.log messages pycentral.log user.log.4.gz
auth.log.3.gz debug.3.gz fsck/ messages.1 samba/ wtmp
auth.log.4.gz debug.4.gz gdm/ messages.2.gz syslog wtmp.1
bacula/ dmesg installer/ messages.3.gz syslog.1 Xorg.0.log
boot dmesg.0 kern.log messages.4.gz syslog.2.gz Xorg.0.log.old
btmp dmesg.1.gz kern.log.1 news/ syslog.3.gz
btmp.1 dmesg.2.gz kern.log.2.gz ntpstats/ syslog.4.gz
cups/ dmesg.3.gz kern.log.3.gz popularity-contest syslog.5.gz
Em 3 de maio de 2010 11:20, Eduardo Lagares
> Gunther,
Eu não tenho esse problema, mas aposto que o Fagner Patrício vai
adorar sua resposta.
--
>
> Seu problema pode estar na temperatura do processador. Verifique nos logs do seu sistema operacional ou veja qual a temperatura dele no Setup.
>
> Uma vez tive um problema desses, o cooler não estava funcionando bem e meu processador estava esquentando muito, ficava ligado durante um período, mas vez ou outra desligava.
>
>
> Eduardo Lagares
>
>
>
> --- Em seg, 3/5/10, Debiminho <debiminho@gmail.com> escreveu:
>
> De: Debiminho <debiminho@gmail.com>
> Assunto: Re: Debian Desligando sozinho!!
> Para: gunfurtado@gmail.com
> Cc: "Debian" <debian-user-portuguese@lists.debian.org>
> Data: Segunda-feira, 3 de Maio de 2010, 10:52
>
> 2010/5/3 Gunther Furtado <gunfurtado@gmail.com>:
> > Em 3 de maio de 2010 09:19, Fagner Patricio
> > <fagner.patricio@gmail.com> escreveu:
> >> Ola!!!
> >>
> >> Meu caso e um pouco estranho, me debian esta desligando sozinho e eu nao sei
> >> o motivo, sempre ocorre assim, durante o dia fuciona normalmente, mas uma
> >> vez ou outra eu deixo o sistema ligado durante a noite fazendo algum
> >> serviço, mas quando eu chego de manda o computador esta desligado, eu tenho
> >> mais ou menos a ideia do que possa esta acontecendo, mas nao sei aonde
> >> verificar, o sistema e configurado por padrao ( nao sei onde se meche nisso
> >> ) para depois de um certo tempo ele travar a tela, eu acho que depois de um
> >> tempo da tela travada o sistema deve se desligar sozinho, mas aonde eu posso
> >> ver se isso e verdade?
> >
> > gnome? kde? lxde? xfce? cli?
> >
> >>
> >> Desculpa a falta de acentos meu teclado deu problema.
> >>
>
> Pode "re"configurar o teclado, na consola com o comando;
> $sudo dpkg-reconfigure console-data
>
> No Gnome em;
> Sistema->Preferências->Teclado = [Disposições]
>
> Quanto ao problema talvez uma visita aos logs possa dar uma
> pista em /var/log/messages ...
>
>
> Até Já
> Silvino
>
>
> --
> To UNSUBSCRIBE, email to debian-user-portuguese-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: AANLkTikrqiAHnIU5VyxQpwz3MrIcTot4lOSmEWTg_6uJ@mail.gmail.com" target="_blank">http://lists.debian.org/AANLkTikrqiAHnIU5VyxQpwz3MrIcTot4lOSmEWTg_6uJ@mail.gmail.com
>
>
>
"...agora, só nos sobrou o futuro...", visto em www.manuchao.net
Gunther Furtado
Curitiba - Paraná - Brasil
gunfurtado@gmail.com
--
To UNSUBSCRIBE, email to debian-user-portuguese-REQUEST@lists.debian.orgArchive: r2pe8a2deac1005031017r433f9d0ex2b168fc34136b1eb@mail.gmail.com" target="_blank">http://lists.debian.org/r2pe8a2deac1005031017r433f9d0ex2b168fc34136b1eb@mail.gmail.com
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org