You are not logged in.

#1 2010-09-23 20:09:06

Skyalmian
Member
Registered: 2009-06-28
Posts: 121

[SOLVED] Xorg.0.log "timer = 0x..." Flooding

[    34.299] timer = 0x291ce60
[    35.181] timer = 0x28852c0
[    36.671] (II) fglrx(0): Preparing normal LeaveVT...
[    36.844] (II) AIGLX: Suspending AIGLX clients for VT switch
[    36.844] (II) fglrx(0): Backup framebuffer data.
[    36.844] (II) fglrx(0): Backup complete.
[    76.437] (II) fglrx(0): Preparing normal EnterVT...
[    76.437] (II) Open ACPI successful (/var/run/acpid.socket)
[    76.437] (II) AIGLX: Resuming AIGLX clients after VT switch
[    76.986] (II) fglrx(0): UVD2 feature is available
[    77.456] (--) SynPS/2 Synaptics TouchPad: touchpad found
[    77.456] (II) fglrx(0): Hot-plug event occurs on device: 1:5:0 
[    80.641] (II) config/udev: removing device Logitech USB-PS/2 Optical Mouse
[    80.641] (II) Logitech USB-PS/2 Optical Mouse: Close
[    80.641] (II) UnloadModule: "evdev"
[   104.197] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse1)
[   104.197] (II) No input driver/identifier specified (ignoring)
[   104.200] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event8)
[   104.200] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
[   104.200] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[   104.200] (**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event8"
[   104.213] (II) Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
[   104.213] (II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
[   104.213] (II) Logitech USB-PS/2 Optical Mouse: Found relative axes
[   104.213] (II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
[   104.213] (II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
[   104.213] (**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
[   104.213] (**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[   104.213] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE)
[   104.213] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
[   104.213] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
[   104.213] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
[   104.213] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
[   104.213] (II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
[   108.394] timer = 0x2885550
[   109.052] timer = 0x27fa9e0
[   109.987] timer = 0x2885550
[   111.343] (II) fglrx(0): Preparing normal LeaveVT...
[   111.457] (II) AIGLX: Suspending AIGLX clients for VT switch
[   111.457] (II) fglrx(0): Backup framebuffer data.
[   111.458] (II) fglrx(0): Backup complete.
[   112.470] (II) fglrx(0): Preparing normal EnterVT...
[   112.470] (II) Open ACPI successful (/var/run/acpid.socket)
[   112.470] (II) AIGLX: Resuming AIGLX clients after VT switch
[   113.016] (II) fglrx(0): UVD2 feature is available
[   113.477] (--) SynPS/2 Synaptics TouchPad: touchpad found
[   113.484] (II) fglrx(0): Hot-plug event occurs on device: 1:5:0 
[   113.563] timer = 0x27cc270
[   115.595] timer = 0x2945430
[   115.605] timer = 0x2945430

As of the past few days this began (the timer = 0x... above, only it fills the major majority of the log rapidly). I don't know how to stop it...have not found anything on this via Scroogle... I changed two things recently, one being the router wireless security from WEP to WPA2-Personal, and xorg.conf tweaks (I had manually set up the mouse in xorg.conf and only switched to 10-evdev.conf after finding the sample file below)...

Oh, interesting...seems to do with the movement of the mouse for one... As root in /var/log in Thunar and I see the filesize jump in multiple KB every second when I move it around, then stop when I stop...

/etc/X11/xorg.conf

Section "ServerLayout"
    Identifier     "Default Layout"
    Screen      0  "aticonfig-Screen[0]-0" 0 0
EndSection

Section "Files"

        # paths to defoma fonts
    FontPath     "/usr/share/X11/fonts/misc"
    FontPath     "/usr/share/X11/fonts/cyrillic"
    FontPath     "/usr/share/X11/fonts/100dpi/:unscaled"
    FontPath     "/usr/share/X11/fonts/75dpi/:unscaled"
    FontPath     "/usr/share/X11/fonts/Type1"
    FontPath     "/usr/share/X11/fonts/CID"
    FontPath     "/usr/share/X11/fonts/100dpi"
    FontPath     "/usr/share/X11/fonts/75dpi"
    FontPath     "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
    FontPath     "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
    Load  "evdev"
    Load  "GLcore"
    Load  "i2c"
    Load  "bitmap"
    Load  "ddc"
    Load  "dri"
    Load  "extmod"
    Load  "freetype"
    Load  "glx"
    Load  "int10"
    Load  "type1"
    Load  "vbe"
EndSection

Section "Monitor"
    Identifier   "aticonfig-Monitor[0]-0"
    Option        "VendorName" "ATI Proprietary Driver"
    Option        "ModelName" "Generic Autodetecting Monitor"
    Option        "DPMS" "true"
EndSection

Section "Device"
    Identifier  "aticonfig-Device[0]-0"
    Driver      "fglrx"
    BusID       "PCI:1:5:0"
EndSection

Section "Screen"
    Identifier "aticonfig-Screen[0]-0"
    Device     "aticonfig-Device[0]-0"
    Monitor    "aticonfig-Monitor[0]-0"
    DefaultDepth     24
    SubSection "Display"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

Section "DRI"
    Mode         0666
EndSection

Section "Extensions"
    Option        "Composite" "Enable"
EndSection

/etc/X11/xorg.conf.d/10-evdev.conf

# Catchall classes for input devices
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.

Section "InputClass"
    Identifier "evdev pointer catchall"
    MatchIsPointer "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
EndSection

Section "InputClass"
    Identifier "evdev keyboard catchall"
    MatchIsKeyboard "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
        
        # Keyboard layouts
    #Option "XkbLayout" "us, bg"
    #Option "XkbVariant" ", phonetic"
    #Option "XkbOptions" "grp:alt_shift_toggle, grp_led:scroll, terminate:ctrl_alt_bksp"
EndSection
    
Section "InputClass"
    Identifier "evdev touchpad catchall"
    MatchIsTouchpad "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
EndSection

Section "InputClass"
    Identifier "evdev tablet catchall"
    MatchIsTablet "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
EndSection

Section "InputClass"
    Identifier "evdev touchscreen catchall"
    MatchIsTouchscreen "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
EndSection

-_-

Last edited by Skyalmian (2010-11-04 20:53:05)

Offline

#2 2010-10-05 06:04:48

Skyalmian
Member
Registered: 2009-06-28
Posts: 121

Re: [SOLVED] Xorg.0.log "timer = 0x..." Flooding

Bah. This makes tty1 basically worthless for program output, because it always overtakes everything else... -_-

Offline

#3 2010-10-06 16:05:35

Blasku
Member
Registered: 2010-10-06
Posts: 2

Re: [SOLVED] Xorg.0.log "timer = 0x..." Flooding

Hi!
I've just registered so I can say that I suffer from the same problem too on a Debian amd64 linux (kernel 2.6.35.7). What I've found out is that if you start X with the open source radeon driver instead of fglrx, the Xorg log won't be spammed with these "timer = 0x*" type messages.
I'm sorry that I wrote into this topic as an outsider, but this is the only forum topic Google comes up with when I enter 'Xorg log "timer = 0x"', and this is definitely not just a 'newbie' issue. I think it's some bigger problem with fglrx or xserver again.
As soon as you tried starting X without fglrx, please write what you've experienced! Thanks!

Offline

#4 2010-10-08 13:15:15

Blasku
Member
Registered: 2010-10-06
Posts: 2

Re: [SOLVED] Xorg.0.log "timer = 0x..." Flooding

It seems that this is a trivial thing after all, and it isn't exactly a bug (although I do find it quite stupid to spam "timer = 0x..." in Xorg.0.log just because of this): vertical refresh was set to "always on" in Catalyst Control Center so I could finally watch films without the annoying tearing. And this is what caused the timer flooding. I'd be grateful if Skyalmian responded to this post of mine at least, so I'd know that turning off vertical refresh solved his problem too...

Offline

#5 2010-11-04 20:52:50

Skyalmian
Member
Registered: 2009-06-28
Posts: 121

Re: [SOLVED] Xorg.0.log "timer = 0x..." Flooding

In my case, the solution was, after waiting two (2) months for the ATI Catalyst driver to be compatible with xorg-server version 1.9.x, I updated both by re-enabling [testing] and commenting out [xorg18] repositories, and the flooding suddenly went away.

Good to know that was the during-then solution, though! I wish I had thought of that; oh well. smile

Offline

Board footer

Powered by FluxBB