Re: [Dorset] Keep being logged out
I seem to remember there was a change of the default acceleration method in the Intel driver a while back (on Arch) to SNA which caused some problems on old Intel laptops for me. I definitely have one with 915 graphics, and I think it was affected (it's retired now so I can't check). https://wiki.archlinux.org/index.php/intel_graphics#SNA_issues Perhaps this change has recently appeared in the Debian world too? On 30 June 2017 at 10:05, Ralph Corderoy wrote: > Hi Tim, > > > Jun 26 16:01:28 lunar1 kernel: drm/i915: Resetting chip after gpu hang > > Jun 26 16:01:38 lunar1 kernel: drm/i915: Resetting chip after gpu hang > > Jun 26 16:01:38 lunar1 org.a11y.atspi.Registry[2747]: XIO: fatal IO > > error 11 (Resource temporarily unavailable) on X server ":0" > > Jun 26 16:01:38 lunar1 org.a11y.atspi.Registry[2747]: after 9703 > > requests (9703 known processed) with 0 events remaining. > > Jun 26 16:01:38 lunar1 polkitd(authority=local)[791]: Unregistered > > Authentication Agent for unix-session:499 (system bus name :1.388, > > object path /org/gnome/PolicyKit1/Authenticati > > > > I am using an Intel onboard graphics, so does this look like a Graphics > > issue? > > Starting to. Look for other drm/i915 mentions and see if they correlate > with your X session ending? > > Have you always had this problem with SolydX EE on that machine? If > not, were any relevant packages upgraded around the time it began? > > Cheers, Ralph. > > -- > Next meeting: Bournemouth, Tuesday, 2017-07-04 20:00 > Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ > New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING > Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR > -- Next meeting: Bournemouth, Tuesday, 2017-07-04 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
Re: [Dorset] Keep being logged out
Hi Tim, > Jun 26 16:01:28 lunar1 kernel: drm/i915: Resetting chip after gpu hang > Jun 26 16:01:38 lunar1 kernel: drm/i915: Resetting chip after gpu hang > Jun 26 16:01:38 lunar1 org.a11y.atspi.Registry[2747]: XIO: fatal IO > error 11 (Resource temporarily unavailable) on X server ":0" > Jun 26 16:01:38 lunar1 org.a11y.atspi.Registry[2747]: after 9703 > requests (9703 known processed) with 0 events remaining. > Jun 26 16:01:38 lunar1 polkitd(authority=local)[791]: Unregistered > Authentication Agent for unix-session:499 (system bus name :1.388, > object path /org/gnome/PolicyKit1/Authenticati > > I am using an Intel onboard graphics, so does this look like a Graphics > issue? Starting to. Look for other drm/i915 mentions and see if they correlate with your X session ending? Have you always had this problem with SolydX EE on that machine? If not, were any relevant packages upgraded around the time it began? Cheers, Ralph. -- Next meeting: Bournemouth, Tuesday, 2017-07-04 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
Re: [Dorset] Keep being logged out
On 26/06/17 19:35, Ralph Corderoy wrote: Hi Tim, (my PC runs 24\7) Logged out of an X desktop session, I presume. Do you leave anything "chunky" running on it when you walk away, e.g. Firefox or Chrome? With web pages open and Javascript enabled? I have use gkrellm system monitor which shows I have a a current uptime of 6 days 11hrs. I'm unfamiliar with that. Does it show anything else interesting that you can match against your "logout" time, e.g. as shown by last(1). Perhaps memory usage creeps higher and the kernel's OOM kills something vital to the desktop? If it doesn't then you could leave `dstat -tcdngy 10 >dstat.log' running, e.g. in screen(1), or on another VT, and look back at that. I have looked at various log files and cannot see any thing of significance. ~/.xsession-errors{,.old} might be worth a look, especially near the end. Does your system catch core dumps and stash them somewhere, e.g. coredumpctl(1) might list them? This command may give a clue. $ cat /proc/sys/kernel/core_pattern |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e $ And what about journalctl(1)'s output in the lead up to the log out? Quite a few log files seem missing nowadays, with their output in that instead. Perhaps something's dying due to a bug and you just happen not to be there so far. Cheers, Ralph. I think this might be significant, bit from my .xsession-errors.old log * [calGoogleSessionManager] Creating session %20xendis...@gmail.com prpl-gtalk: Error during SRV: Lookup failed. gkrellm: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. Gdk-Message: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. Gdk-Message: light-locker: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. Gdk-Message: firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. Gdk-Message: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. xfwm4: Fatal IO error 104 (Connection reset by peer) on X server :0.0. wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. Gdk-Message: thunderbird: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. The first line about the gmail session was about 15:07 this afternoon, I believe the "desktop" crashed around 15:50-ish Based on detail in other logs . Bear in mind that I was not using the PC from around 15:07 until about 18:00. Firefox is running with 8 open tabs, Thunderbird is also running, Gkrellem are the only desktop application running. Free memory normally sits around 1.5gb (4GB installed) and will drop if I open around 12+ tabs. Only around 300mb of swap is in use (5.5gb available). Other than pushing Firefox I have not seen anything else start to hammer the processor, might experiment tonight and close Firefox before bed and see what happens. I found this after trying journalctl * Jun 26 16:01:28 lunar1 kernel: drm/i915: Resetting chip after gpu hang Jun 26 16:01:38 lunar1 kernel: drm/i915: Resetting chip after gpu hang Jun 26 16:01:38 lunar1 org.a11y.atspi.Registry[2747]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Jun 26 16:01:38 lunar1 org.a11y.atspi.Registry[2747]: after 9703 requests (9703 known processed) with 0 events remaining. Jun 26 16:01:38 lunar1 polkitd(authority=local)[791]: Unregistered Authentication Agent for unix-session:499 (system bus name :1.388, object path /org/gnome/PolicyKit1/Authenticati ** I am using an Intel onboard graphics, so does this look like a Graphics issue? Regards Tim -- Next meeting: Bournemouth, Tuesday, 2017-07-04 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST O
Re: [Dorset] Keep being logged out
Hi Tim, > (my PC runs 24\7) Logged out of an X desktop session, I presume. Do you leave anything "chunky" running on it when you walk away, e.g. Firefox or Chrome? With web pages open and Javascript enabled? > I have use gkrellm system monitor which shows I have a a current > uptime of 6 days 11hrs. I'm unfamiliar with that. Does it show anything else interesting that you can match against your "logout" time, e.g. as shown by last(1). Perhaps memory usage creeps higher and the kernel's OOM kills something vital to the desktop? If it doesn't then you could leave `dstat -tcdngy 10 >dstat.log' running, e.g. in screen(1), or on another VT, and look back at that. > I have looked at various log files and cannot see any thing of > significance. ~/.xsession-errors{,.old} might be worth a look, especially near the end. Does your system catch core dumps and stash them somewhere, e.g. coredumpctl(1) might list them? This command may give a clue. $ cat /proc/sys/kernel/core_pattern |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e $ And what about journalctl(1)'s output in the lead up to the log out? Quite a few log files seem missing nowadays, with their output in that instead. Perhaps something's dying due to a bug and you just happen not to be there so far. Cheers, Ralph. -- Next meeting: Bournemouth, Tuesday, 2017-07-04 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
[Dorset] Keep being logged out
I have a strange problem, my PC is randomly logging me out. This so far has only happened when I am not using the PC, sometimes over night (my PC runs 24\7) sometimes with as little as 2 hours not being used like today. I know it is just logging me out and not rebooting as I have use gkrellm system monitor which shows I have a a current uptime of 6 days 11hrs. I am using SolydX EE (which was based on Debian Testing but since Stretch become stable I have changed my repo's to stable). I have looked at various log files and cannot see any thing of significance. I don't have the XFCE Power Manager loaded so it is not linked to Power Manger (It has not been installed since I installed SolydX) Any thoughts? -- Next meeting: Bournemouth, Tuesday, 2017-07-04 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR