On 30/03/17 01:35, Ed Greshko wrote:
On 03/30/17 14:24, Paolo Galtieri wrote:
Folks,
I have 2 F25 systems that have been updated today. These 2 systems
share a monitor. One system is attached via a kvm switch to the
monitor, the other system is attached via hdmi. This morning and
twice this evening a problem has started to manifest itself. This
configuration has been working fine for several years. I will call
the systems A and B, system A is attached to the monitor via hdmi,
system B via VGA. If I switch to system A for a while and then try to
switch back to system B the monitor instead of staying on VGA cycles
from VGA to DVI to HDMI and returns to system A. I can ssh into
system B and everything looks fine, i.e. things that were running
under my user id are still running, e.g. chrome and firefox. I looked
at /var/log/messages and I see this:
Mar 29 23:00:02 jackstraw systemd: Stopping User Manager for UID 0...
Mar 29 23:00:02 jackstraw systemd: Stopped target Default.
Mar 29 23:00:02 jackstraw systemd: Stopped target Basic System.
Mar 29 23:00:02 jackstraw systemd: Stopped target Sockets.
Mar 29 23:00:02 jackstraw systemd: Closed D-Bus User Message Bus Socket.
Mar 29 23:00:02 jackstraw systemd: Stopped target Timers.
Mar 29 23:00:02 jackstraw systemd: Stopped target Paths.
Mar 29 23:00:02 jackstraw systemd: Reached target Shutdown.
Mar 29 23:00:02 jackstraw systemd: Starting Exit the Session...
Mar 29 23:00:02 jackstraw systemd: Received SIGRTMIN+24 from PID 17588
(kill).
This was at the time I switched from system A to system B. Each of
the other times I saw this problem I see the same set of messages in
the log file. Can someone explain what they mean and could they be
the cause of the problem?
I see the same messages on the other system, but there they were part
of other messages related to rebooting the system.
The only way I can recover is reboot the system.
Here's my video card info:
01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce
8500 GT] (rev a1)
Any assistance is appreciated.
Since everything is still running as it was it sounds similar to
problems with monitors not coming back from sleep.
Couple of questions.
1. Are you using the nouveau driver or the nVidia driver for your card?
2. Are you running GNOME under Wayland or X11?
If you are using X11, and since you can ssh into the system, what is
the output if you do...
ssh systemB
export DISPLAY=:0
xrandr
Using my system as an example, does doing something like this bring the
monitor back?
[egreshko@meimei ~]$ acer
Last login: Thu Mar 30 15:24:26 2017 from 192.168.1.18
[egreshko@acer ~]$ export DISPLAY=:0
[egreshko@acer ~]$ xrandr
Screen 0: minimum 8 x 8, current 1280 x 800, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
TV-0 disconnected (normal left inverted right x axis y axis)
LVDS-0 connected primary 1280x800+0+0 (normal left inverted right x axis
y axis) 331mm x 207mm
1280x800 59.91*+
HDMI-0 disconnected (normal left inverted right x axis y axis)
[egreshko@acer ~]$ xrandr --output LVDS-0 --off
[egreshko@acer ~]$ xrandr --output LVDS-0 --auto
With the last two kernels, using the nouveau driver, I am having graphic
issues. I can open a session but once the screen locks, then I cannot
get back to the desktop session.
Using KDE from sddm and Xorg. These are in the dmesg output.
[ 8.664136] nouveau 0000:01:00.0: NVIDIA G84 (084000a2)
[ 8.787588] nouveau 0000:01:00.0: bios: version 60.84.55.00.08
[ 8.808963] nouveau 0000:01:00.0: fb: 512 MiB GDDR3
[ 8.859472] nouveau 0000:01:00.0: DRM: VRAM: 512 MiB
[ 8.859476] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[ 8.859484] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[ 8.859488] nouveau 0000:01:00.0: DRM: DCB version 4.0
[ 8.859494] nouveau 0000:01:00.0: DRM: DCB outp 00: 02000300 00000028
[ 8.859499] nouveau 0000:01:00.0: DRM: DCB outp 01: 01000302 00000030
[ 8.859503] nouveau 0000:01:00.0: DRM: DCB outp 02: 04011310 00000028
[ 8.859507] nouveau 0000:01:00.0: DRM: DCB outp 03: 02011312 00000030
[ 8.859511] nouveau 0000:01:00.0: DRM: DCB outp 04: 010223f1 00c0c080
[ 8.859515] nouveau 0000:01:00.0: DRM: DCB conn 00: 1030
[ 8.859518] nouveau 0000:01:00.0: DRM: DCB conn 01: 2130
[ 8.859522] nouveau 0000:01:00.0: DRM: DCB conn 02: 0210
[ 8.859525] nouveau 0000:01:00.0: DRM: DCB conn 03: 0211
[ 8.859529] nouveau 0000:01:00.0: DRM: DCB conn 04: 0213
[ 8.865523] nouveau 0000:01:00.0: DRM: failed to create encoder
0/1/0: -19
[ 8.865528] nouveau 0000:01:00.0: DRM: TV-1 has no encoders, removing
[ 8.865830] nouveau 0000:01:00.0: hwmon_device_register() is
deprecated. Please convert the driver to use
hwmon_device_register_with_info().
[ 8.877852] nouveau 0000:01:00.0: DRM: MM: using CRYPT for buffer copies
[ 8.938575] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb:
0x70000, bo ffff936ca13d1c00
[ 8.940133] fbcon: nouveaufb (fb0) is primary device
[ 10.997450] nouveau 0000:01:00.0: DRM: EVO timeout
[ 12.997611] nouveau 0000:01:00.0: DRM: base-0: timeout
[ 14.997770] nouveau 0000:01:00.0: DRM: base-1: timeout
[ 15.059617] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[ 15.084223] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0
on minor 0
In previous troubleshooting attempts, some of DRM related messages
showed up in a terminal session I had open as well as the kde session
when it locked.
This was before the screen lock and just after a reboot.
Robin
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
