You are not logged in.

#1 2009-10-01 12:57:18

flpmorais
Member
Registered: 2009-10-01
Posts: 4

X failing after 2 or 3 hours of using

hi, i've been using linux for some time now, i've used ubuntu, suse, fedora and now, arch. and sorry for my english by the way, but i'm not a native english speaker.

With the help from some tutorials i managed to setup my system nicely in my eeepc 1000HE, all works fine but one thing. It doesn't really interferes that much with my work but it's still anoying.

I have my system completely up-to-date and the latest stable release with slim login manager and lxde by the way.

The issue now:

After about 2 hours using my computer, i start getting some flashes. The screen just goes black for some miliseconds and when that happens i already now what's coming next. 10 minutes later the X just stops. The screen goes completely black and i'm able to do nothing. It also happens if i turn on the computer and come back a couple of hours later and start using it, even if the computer is just turned on doing nothing during that time.

I tried ctrl+alt+f2, login and restart x.. No can do! i reboot the computer on the terminal and i have another 2 hours without any problems at all... strange -.-'

I browsed for a solution and i found nothing, do any of you guys have a clue on what's happening?

thank you in advance.
Filipe Morais

Offline

#2 2009-10-01 13:08:21

arkham
Member
From: Stockholm
Registered: 2008-10-26
Posts: 516
Website

Re: X failing after 2 or 3 hours of using

What about your logs? Especially /var/log/everything.log


"I'm Winston Wolfe. I solve problems."

~ Need moar games? [arch-games] ~ [aurcheck] AUR haz updates? ~

Offline

#3 2009-10-01 13:08:43

Misfit138
Misfit Emeritus
From: USA
Registered: 2006-11-27
Posts: 4,189

Re: X failing after 2 or 3 hours of using

Sounds like it could be a hardware problem. Try a live USB distro to verify?

Offline

#4 2009-10-03 14:12:07

flpmorais
Member
Registered: 2009-10-01
Posts: 4

Re: X failing after 2 or 3 hours of using

Oct  3 15:46:05 DoomsdayDevice kernel: ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 87
Oct  3 15:48:05 DoomsdayDevice kernel: ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 87
Oct  3 15:50:05 DoomsdayDevice kernel: ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 87
Oct  3 15:52:05 DoomsdayDevice kernel: ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 87
Oct  3 15:54:05 DoomsdayDevice kernel: ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 87
Oct  3 15:56:05 DoomsdayDevice kernel: ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 87
Oct  3 15:57:29 DoomsdayDevice shutdown[4084]: shutting down for system reboot
Oct  3 15:57:31 DoomsdayDevice init: Switching to runlevel: 6
Oct  3 15:57:31 DoomsdayDevice NetworkManager: <info>  (ra0): device state change: 8 -> 3
Oct  3 15:57:31 DoomsdayDevice NetworkManager: <info>  (ra0): deactivating device (reason: 38).
Oct  3 15:57:31 DoomsdayDevice dhcpcd: received SIGTERM, stopping
Oct  3 15:57:31 DoomsdayDevice dhcpcd: ra0: removing interface
Oct  3 15:57:31 DoomsdayDevice kernel: mtrr: no MTRR for d0000000,10000000 found
Oct  3 15:57:31 DoomsdayDevice NetworkManager: <info>  ra0: canceled DHCP transaction, dhcp client pid 1630
Oct  3 15:57:31 DoomsdayDevice kernel: ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
Oct  3 15:57:31 DoomsdayDevice kernel: ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
Oct  3 15:57:31 DoomsdayDevice NetworkManager: <WARN>  nm_dhcp_manager_handle_event(): Received DHCP event from unexpected PID 1630 (expected 0)
Oct  3 15:57:32 DoomsdayDevice NetworkManager: <WARN>  nm_signal_handler(): Caught signal 15, shutting down normally.
Oct  3 15:57:32 DoomsdayDevice NetworkManager: <info>  (eth0): now unmanaged
Oct  3 15:57:32 DoomsdayDevice NetworkManager: <info>  (eth0): device state change: 2 -> 1
Oct  3 15:57:32 DoomsdayDevice NetworkManager: <info>  (eth0): cleaning up...
Oct  3 15:57:32 DoomsdayDevice NetworkManager: <info>  (eth0): taking down device.
Oct  3 15:57:32 DoomsdayDevice NetworkManager: <info>  (ra0): now unmanaged
Oct  3 15:57:32 DoomsdayDevice NetworkManager: <info>  (ra0): device state change: 3 -> 1
Oct  3 15:57:32 DoomsdayDevice NetworkManager: <info>  (ra0): cleaning up...
Oct  3 15:57:32 DoomsdayDevice NetworkManager: <info>  (ra0): taking down device.
Oct  3 15:57:32 DoomsdayDevice NetworkManager: <info>  exiting (success)
Oct  3 15:57:32 DoomsdayDevice nm-system-settings: disconnected from the system bus, exiting.
Oct  3 15:57:32 DoomsdayDevice nm-dispatcher.action: Disconnected from the system bus, exiting.
Oct  3 15:57:33 DoomsdayDevice syslog-ng[1244]: Termination requested via signal, terminating;
Oct  3 15:57:33 DoomsdayDevice syslog-ng[1244]: syslog-ng shutting down; version='3.0.4'
Oct  3 15:58:12 DoomsdayDevice syslog-ng[1245]: syslog-ng starting up; version='3.0.4'

x stoped at 15.57 some seconds before reboot.
no clue on what's happeing. xorg.0.log provides no usefull info also
I tried both ubuntu and fedora for a while before arch on this computer without any problems at all (except a driver not working in fedora and ubuntu beeing slow as hell). Also windows xp worked fine. it's not hardware, but just to be sure i tried backtrack (which was the only image i had avaliable) for a while today without problems. any other guesses?
if you want i can paste more logs

Offline

Board footer

Powered by FluxBB