Xorg.log flooded with DFP-0 connected messages

Graphics / Linux Linux
1

When the monitor is in “sleep” mode, i.e. when the xset standby interval has elapsed, the Xorg.0.log file is flooded with the following block of 8 lines. Repeats approximately every 2 seconds. So that overnight, for example, when the computer is on but the monitor in standby, the Xorg.0.log file builds by roughly 650K bytes per hour. Maybe harmless, but certainly a nuisance. And if a bug report is needed do you really want 50 to 100 Megabytes of this message repeating…

[ 4632.304] (–) NVIDIA(GPU-0): HP 2009 (DFP-0): connected
[ 4632.304] (–) NVIDIA(GPU-0): HP 2009 (DFP-0): Internal TMDS
[ 4632.304] (–) NVIDIA(GPU-0): HP 2009 (DFP-0): 330.0 MHz maximum pixel clock
[ 4632.304] (–) NVIDIA(GPU-0):
[ 4632.319] (–) NVIDIA(GPU-0): HP 2009 (DFP-0): connected
[ 4632.319] (–) NVIDIA(GPU-0): HP 2009 (DFP-0): Internal TMDS
[ 4632.319] (–) NVIDIA(GPU-0): HP 2009 (DFP-0): 330.0 MHz maximum pixel clock
[ 4632.319] (–) NVIDIA(GPU-0):

You will see that there are 2 identical blocks of 4 lines separated by just 15 milliseconds.

How can I turn this “feature” off? I tried [Option “ModeDebug” “false”] in xorg.conf to no effect.

[Linux 3.16.7 x86_64 / Nvidia driver 367.44 / GTX 750Ti] info.

2

It is related to the 367 driver, I have the exact same Graphics Card and was getting the exact same messages I went down to the previous release of the driver 340.98 and I have not received any messages in my logs since I switched!

I downloaded the 340 package rebooted into non graphical mode, ./NVIDIA-… --uninstall
so that i can remove the currently installed driver.

Immediately after I installed the 340 driver and seems to be going smooth without any log messages filling up the logs which is nice!

Hope this helps!

Alex

3

This EXACT problem is occurring on two of my workstations now. It is odd, because we are all running the same video card, similar motherboards, same distro (gentoo) with nearly identical packages installed, and yet only 2 of my 4 workstations are experiencing this:

…
[495281.510] (–) NVIDIA(GPU-0):
[495281.523] (–) NVIDIA(GPU-0): AOC 2752H (DFP-1): connected
[495281.523] (–) NVIDIA(GPU-0): AOC 2752H (DFP-1): Internal TMDS
[495281.523] (–) NVIDIA(GPU-0): AOC 2752H (DFP-1): 340.0 MHz maximum pixel clock
[495281.523] (–) NVIDIA(GPU-0):
[495281.537] (–) NVIDIA(GPU-0): AOC 2752H (DFP-1): connected
[495281.537] (–) NVIDIA(GPU-0): AOC 2752H (DFP-1): Internal TMDS
[495281.537] (–) NVIDIA(GPU-0): AOC 2752H (DFP-1): 340.0 MHz maximum pixel clock
[495281.537] (–) NVIDIA(GPU-0):
…

It is sometimes taking 10-15 minutes for the machines to finish writing to the logs and allowing a login. Do I really have to revert all the way back to the 340 driver?? We are on 396.24. Or Should I ditch the official driver for noveau?

I’ve tried swapping cables around, but no change. I also believe it might be related to the monitors as that is the one thing in common between the two failing workstations and the two working ones.

Seriously though, this is unacceptable so I need to figure something out. Please help!!!

4

What DE are you running?

5

DE? Desktop? XFCE, the problem started when we switched login managers to lightdm

6

Hmm… Could it be because of the ACPI daemon?? I just realized that both of the problem workstations were not running the daemon, whereas the working workstations all have ‘acpid’ running. I can’t believe I didn’t pay it notice before, but right before the looping log message there is typically this:

…
[449471.173] (II) NVIDIA(0): Setting mode “DVI-I-1: nvidia-auto-select @1920x1080 +1920+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”
[449471.323] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[449471.323] (II) NVIDIA(0): may not be running or the “AcpidSocketPath” X
[449471.323] (II) NVIDIA(0): configuration option may not be set correctly. When the
[449471.323] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[449471.323] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[449471.323] (II) NVIDIA(0): details, please see the “ConnectToAcpid” and
[449471.323] (II) NVIDIA(0): “AcpidSocketPath” X configuration options in Appendix B: X
[449471.323] (II) NVIDIA(0): Config Options in the README.
…

I kind of hope it isn’t this simple of a fix as I have been spending a little bit of time on this every single day for a few weeks now, all while ignoring that error. BUT if this does solve things (and it seems to help so far) then at least hopefully other people that encounter this error can be pointed in the right direction to fix it a lot faster than I did.

Let me explain why I cannot immediately identify this as a fix: The looping log message would really only occur after the workstations were locked for long periods of time. So typically in our office, this was during the first unlock at the start of the work day. Any other times during the day, the unlock process didn’t seem to have a problem. Therefore, I cannot confirm this behavior has been resolved until tomorrow. I did a lock/unlock of the screens and saw the same behavior whether the ‘acpid’ was running or not. But I am going to leave it running over night and report back in the morning if that solved the problem tomorrow morning. Hopefully this resolved it!!

7

Ugh :( This did not resolve it for on workstation but the other one now seems fine (although it did get rid of the message on both). So… maybe it is related, maybe not.

Any thoughts from the Nvidia Dev team?!??

8

Sry for nekrobump, but I had the same issue just now so it seems still relevant.

For me the issue was that I had a script running in the background which periodically runs xrandr, and by doing that this log is produced.

9

Hi,

I’m having the same issue as the OP. My Xorg.0.log is flooded with the same kind of logs:

[  2942.817] (--) NVIDIA(GPU-0): 
[  2942.863] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): connected
[  2942.863] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): Internal TMDS
[  2942.863] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): 330.0 MHz maximum pixel clock
[  2942.863] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): supports NVIDIA 3D Vision stereo.
[  2942.863] (--) NVIDIA(GPU-0): 
[  3285.402] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): connected
[  3285.402] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): Internal TMDS
[  3285.402] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): 330.0 MHz maximum pixel clock
[  3285.402] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): supports NVIDIA 3D Vision stereo.
[  3285.402] (--) NVIDIA(GPU-0): 
[  3285.446] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): connected
[  3285.446] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): Internal TMDS
[  3285.446] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): 330.0 MHz maximum pixel clock
[  3285.446] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): supports NVIDIA 3D Vision stereo.
[  3285.446] (--) NVIDIA(GPU-0): 
[  3382.010] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): connected
[  3382.010] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): Internal TMDS
[  3382.010] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): 330.0 MHz maximum pixel clock
[  3382.010] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): supports NVIDIA 3D Vision stereo.
[  3382.010] (--) NVIDIA(GPU-0): 
[  3382.054] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): connected
[  3382.054] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): Internal TMDS
[  3382.054] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): 330.0 MHz maximum pixel clock
[  3382.054] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): supports NVIDIA 3D Vision stereo.
[  3382.054] (--) NVIDIA(GPU-0):

This can go like this for several minutes and that affects the performance of the PC because while that is happening if I’m whatching a video I get dropped frames and if I move my mouse around I get a stuttering move and jumps. These are the error logs (this is just a pipe and grep with Razer):

[  2270.954] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2271.456] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2277.132] (EE) event8  - Razer Razer Viper Ultimate Dongle: client bug: event processing lagging behind by 30ms, your system is too slow
[  2278.518] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2523.155] (EE) event8  - Razer Razer Viper Ultimate Dongle: client bug: event processing lagging behind by 92ms, your system is too slow
[  2523.649] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2530.842] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2623.107] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2627.736] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2628.369] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2628.503] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2630.952] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2630.952] (II) event8  - Razer Razer Viper Ultimate Dongle: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.

I really looks like this in the log file:

[  2896.615] (--) NVIDIA(GPU-0): 
[  2896.615] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2896.659] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): connected
[  2896.659] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): Internal TMDS
[  2896.659] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): 330.0 MHz maximum pixel clock
[  2896.659] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): supports NVIDIA 3D Vision stereo.
[  2896.659] (--) NVIDIA(GPU-0): 
[  2896.660] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2896.705] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2898.053] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): connected
[  2898.053] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): Internal TMDS
[  2898.053] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): 330.0 MHz maximum pixel clock
[  2898.053] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): supports NVIDIA 3D Vision stereo.
[  2898.053] (--) NVIDIA(GPU-0): 
[  2898.097] (II) event8  - Razer Razer Viper Ultimate Dongle: SYN_DROPPED event - some input events have been lost.
[  2898.141] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): connected
[  2898.141] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): Internal TMDS
[  2898.141] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): 330.0 MHz maximum pixel clock
[  2898.141] (--) NVIDIA(GPU-0): BenQ XL2410T (DFP-0): supports NVIDIA 3D Vision stereo.

I have two monitors: HP x27q at 2560x1440p @165Hz and Benq XL2410t at 1920x1080p @120Hz
Processor: Intel i5 6600k
Graphics Card: Nvidia Gtx 1070
Nvidia drivers: 535.104.05
OS: Manjaro (Arch Linux) on MATE Desktop.

My Xorg.conf looks like this:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 530.41.03

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "BenQ XL2410T"
    HorizSync       30.0 - 140.0
    VertRefresh     56.0 - 120.0
#    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVIDIA GeForce GTX 1070"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
 #   Option 	   "ModeValidation" "NoMaxPClkCheck"
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-4"
    Option         "metamodes" "DVI-D-0: 1920x1080_120 +2560+360 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-2: 2560x1440_165 +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On, AllowGSYNCCompatible=On}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Please help, as I said it is very frustrating to use the PC while that is happening, until the logs stop and then the PC runs smoothly.

edit: I upload the nvidia-bug-report.log.gz
nvidia-bug-report.log.gz (332.4 KB)

10

Follow up to my previous message:

After a lot of testing and trial and error it appears to be a hardware related issue as I have tried to use an HDMI cable instead the DVI-D connection and that seems to stop the errors (3 days in a row with zero errors).

I have ordered a new DVI-D cable in case the cable was malfunctioning. I hope the problem is the cable and not the DVI connection in either side (graphics card output port or monitor input port) is somehow broken.

What I don’t understand is that I have a dual boot with Windows 10 and don’t have any issue there, so somehow the driver can do something about a monitor being constantly detected as disconnected and connected again.