Awesome crashing over night
I am running Awesome 3.4.10 on an Arch Linux box that I leave on over night locked with Xscreensaver. By morning I come in and get on the computer to find that it is sitting at SLiM login screen instead of the xscreensaver, I tried looking through Xorgs logs to see if I can find what might be happening but there is no .Xerrors file in my Home directory and the Xorg.0.log only has this: vendion ~ $ grep (WW) /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [124906.474] (WW) The directory /usr/share/fonts/OTF/ does not exist. [124906.475] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [124906.799] (WW) RADEON(0): Option Enable is not used [124906.799] (WW) RADEON(0): Option TwinView is not used [124906.799] (WW) RADEON(1): Option Enable is not used [124906.799] (WW) RADEON(1): Option TwinView is not used vendion ~ $ grep (EE) /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [124906.638] (EE) RADEON(1): reusing fd for second head SLiM's log file isn't very helpful ether: vendion ~ $ grep (WW) /var/log/slim.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) warning, (EE) error, (NI) not implemented, (??) unknown. vendion ~ $ grep (EE) /var/log/slim.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(1): reusing fd for second head (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(1): reusing fd for second head (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(1): reusing fd for second head Is there another log file that Awesome may be using that I should check?
Re: Awesome crashing over night
Have you checked uptime and/or dmesg? Maybe the machine reboots? -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Awesome crashing over night
On Thu, Oct 27, 2011 at 11:27 AM, Paweł Rumian gork...@gmail.com wrote: Have you checked uptime and/or dmesg? Maybe the machine reboots? Uptime is what I would expect it to be, been up for 2 days, dmesg doesn't have anything in it that looks like the system rebooted but it does look like the GPU freaked out at some point: [ 4473.682912] radeon :01:05.0: GPU lockup CP stall for more than 1msec There are several lines below it that looks like a stacetrace and I see where the GPU went through a soft reset, would this cause X11 to restart without any errors or warnings in the log?
Re: Awesome crashing over night
In my /etc/X11/xorg.conf.d/10-monitor.conf I am telling it not to use TwinView, instead I am using Xinerama. OptionTwinView 0 OptionXinerama 1 I guess it wouldn't hurt to remove the TwinView option line for my screens On Thu, Oct 27, 2011 at 11:05 AM, Joshua Weaver joshuawea...@gmail.comwrote: I don't think ATI uses TwinView... On Thu, Oct 27, 2011 at 7:18 AM, Adam Jimerson vend...@gmail.com wrote: I am running Awesome 3.4.10 on an Arch Linux box that I leave on over night locked with Xscreensaver. By morning I come in and get on the computer to find that it is sitting at SLiM login screen instead of the xscreensaver, I tried looking through Xorgs logs to see if I can find what might be happening but there is no .Xerrors file in my Home directory and the Xorg.0.log only has this: vendion ~ $ grep (WW) /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [124906.474] (WW) The directory /usr/share/fonts/OTF/ does not exist. [124906.475] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [124906.799] (WW) RADEON(0): Option Enable is not used [124906.799] (WW) RADEON(0): Option TwinView is not used [124906.799] (WW) RADEON(1): Option Enable is not used [124906.799] (WW) RADEON(1): Option TwinView is not used vendion ~ $ grep (EE) /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [124906.638] (EE) RADEON(1): reusing fd for second head SLiM's log file isn't very helpful ether: vendion ~ $ grep (WW) /var/log/slim.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) warning, (EE) error, (NI) not implemented, (??) unknown. vendion ~ $ grep (EE) /var/log/slim.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(1): reusing fd for second head (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(1): reusing fd for second head (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(1): reusing fd for second head Is there another log file that Awesome may be using that I should check?
Re: Awesome crashing over night
I'd suggest attaching turning on core files, attaching gdb, and doing a stack trace tomorrow morning with the inevitable core file that shows up. It looks like the log files aren't going to be useful here. On Thu, Oct 27, 2011 at 11:03 AM, Adam Jimerson vend...@gmail.com wrote: In my /etc/X11/xorg.conf.d/10-monitor.conf I am telling it not to use TwinView, instead I am using Xinerama. Option TwinView 0 Option Xinerama 1 I guess it wouldn't hurt to remove the TwinView option line for my screens On Thu, Oct 27, 2011 at 11:05 AM, Joshua Weaver joshuawea...@gmail.com wrote: I don't think ATI uses TwinView... On Thu, Oct 27, 2011 at 7:18 AM, Adam Jimerson vend...@gmail.com wrote: I am running Awesome 3.4.10 on an Arch Linux box that I leave on over night locked with Xscreensaver. By morning I come in and get on the computer to find that it is sitting at SLiM login screen instead of the xscreensaver, I tried looking through Xorgs logs to see if I can find what might be happening but there is no .Xerrors file in my Home directory and the Xorg.0.log only has this: vendion ~ $ grep (WW) /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [124906.474] (WW) The directory /usr/share/fonts/OTF/ does not exist. [124906.475] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [124906.799] (WW) RADEON(0): Option Enable is not used [124906.799] (WW) RADEON(0): Option TwinView is not used [124906.799] (WW) RADEON(1): Option Enable is not used [124906.799] (WW) RADEON(1): Option TwinView is not used vendion ~ $ grep (EE) /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [124906.638] (EE) RADEON(1): reusing fd for second head SLiM's log file isn't very helpful ether: vendion ~ $ grep (WW) /var/log/slim.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) warning, (EE) error, (NI) not implemented, (??) unknown. vendion ~ $ grep (EE) /var/log/slim.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(1): reusing fd for second head (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(1): reusing fd for second head (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(1): reusing fd for second head Is there another log file that Awesome may be using that I should check? -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
