Created attachment 119420 [details] Xorg and jouralctl logs during crash with hwcursor, and no crash with swcursor Hardware: IBM ThinkPad A21p OS: BunsenLabs Linux Hydrogen-rc1 (based on Debian Jessie) Using the hwcursor on the r128 driver causes X.org to crash and restart LightDM when the cursor is moved over a window that has had text typed into it. It will also crash if the cursor is already over a window when text starts being typed into it. Setting Option "SWcursor" "true" in my 04-device.conf file prevents the crash, but is not an optimal cursor configuration. Attached is a .tar.gz of the output from journalctl and Xorg both during a crash with hwcursor, and without a crash with swcursor. lspci output for the video device: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rage Mobility 128 AGP 2X/Mobility M3 (rev 02) Subsystem: IBM IBM Thinkpad A22p Files modified in /usr/share/X11/xorg.conf.d/ 04-device.conf: Section "Device" ### Available Driver options are:- ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", ### <string>: "String", <freq>: "<f> Hz/kHz/MHz", ### <percent>: "<f>%" ### [arg]: arg optional #Option "NoAccel" # [<bool>] #Option "SWcursor" # [<bool>] #Option "Dac6Bit" # [<bool>] #Option "Dac8Bit" # [<bool>] #Option "DMAForXv" # [<bool>] #Option "ForcePCIMode" # [<bool>] #Option "CCEPIOMode" # [<bool>] #Option "CCENoSecurity" # [<bool>] #Option "CCEusecTimeout" # <i> #Option "AGPMode" # <i> #Option "AGPSize" # <i> #Option "RingSize" # <i> #Option "BufferSize" # <i> #Option "EnablePageFlip" # [<bool>] Option "Display" "BIOS" # <str> Option "PanelWidth" "1600" # <i> Option "PanelHeight" "1200" # <i> #Option "ProgramFPRegs" # [<bool>] Option "UseFBDev" "false" # [<bool>] #Option "VideoKey" # <i> #Option "ShowCache" # [<bool>] #Option "VGAAccess" # [<bool>] #Option "AccelMethod" # <str> #Option "RenderAccel" # [<bool>] Identifier "Card0" Driver "r128" BusID "PCI:1:0:0" EndSection --- 04-monitor.conf: Section "Monitor" Identifier "Monitor0" VendorName "IBM" ModelName "Monitor Model" HorizSync 30-95 VertRefresh 58-76 EndSection --- 04-screen.conf Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 Modes "1600x1200" "800x600" "640x480" EndSubSection EndSection
I was unaware that there would be interplay between a hardware cursor and text. Here are some things to try: * Turning off text compositing with Option "ExaNoComposite" "true" in 04-device.conf. * Turning off EXA altogether. * Disabling the 1600x1200 mode to see if the problem goes away when there are less stringent memory demands on the card. Also, a lot of the cursor code changed between 6.9.2 and 6.10.0 because of how RandR handles things. If you can compile 6.10.0 (and get past the problems that other people seem to be having) that might fix it.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-r128/issues/6.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.