Single character display corruption with radeon driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux Mint |
New
|
Undecided
|
Unassigned |
Bug Description
Using the open source equivalent of fglrx, ie using the radeon driver at /lib/modules/
Here are some examples of text that had 1 char display corrution, last char shown is the one that was corrupt:Version: 4.1.1
forums.linuxm
forums.
URL : http://
Are there any usage restricti
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_6
Server
Wireshark says "There
Wireshark says "There are
Wireshark says "There are no inte [ie all of last 3 e's corrupt]
Jul 30, 2014 ... Platform-Specific
amd64-microcode not install
arm64: Tell irq work about self IPI
Bull
GPG
AndEngine - Forums • Pixel Pe
Connection to
Radeon OSS
Device drivers and
Nvidi
http://
http://
alca
ATI/A
documente
Server
Overv
Overv
Overv
Overv [possibly easier to repeat this (in firefox) by changing to a tab that hasn't been used recently, then back]
- https:/
User-Ag
/usr/shar
/usr/share/initr [both r's]
Maybe it is assuming recently rendered char is still in a cache, when it isn't - larger char might restrict the repetition to be
more recent.
The only place where it was repeatable every time was in synaptic-
1. It was Mint 17.
2. Install an R7 260X and the radeon driver, and use cinnamon all day, or use the synaptic option as above.
3. Occasionally 1 character was displayed wrong (using copy-paste on it still got the correct character).
4. The characters should have displayed using their normal glyphs.
5. Sometimes (except always if given enough time), or always in the synaptic case.
I got PROTECTION_ FAULT_ADDR 0x00000000 PROTECTION_ FAULT_STATUS 0x00000000 PROTECTION_ FAULT_ADDR 0x00000000 PROTECTION_ FAULT_STATUS 0x00000000 PROTECTION_ FAULT_ADDR 0x00000000 PROTECTION_ FAULT_STATUS 0x00000000
Oct 24 15:31:48 linux kernel: [79948.020461] VM fault (0x00, vmid 0) at page 0, read from '' (0x00000000) (0)
Oct 24 15:31:48 linux kernel: [79948.020469] radeon 0000:01:00.0: GPU fault detected: 146 0x09080404
Oct 24 15:31:48 linux kernel: [79948.020472] radeon 0000:01:00.0: VM_CONTEXT1_
Oct 24 15:31:48 linux kernel: [79948.020476] radeon 0000:01:00.0: VM_CONTEXT1_
Oct 24 15:31:48 linux kernel: [79948.020479] VM fault (0x00, vmid 0) at page 0, read from '' (0x00000000) (0)
Oct 24 15:31:48 linux kernel: [79948.020486] radeon 0000:01:00.0: GPU fault detected: 146 0x08e80404
Oct 24 15:31:48 linux kernel: [79948.020490] radeon 0000:01:00.0: VM_CONTEXT1_
Oct 24 15:31:48 linux kernel: [79948.020493] radeon 0000:01:00.0: VM_CONTEXT1_
Oct 24 15:31:48 linux kernel: [79948.020497] VM fault (0x00, vmid 0) at page 0, read from '' (0x00000000) (0)
Oct 24 15:31:48 linux kernel: [79948.020504] radeon 0000:01:00.0: GPU fault detected: 146 0x09084404
Oct 24 15:31:48 linux kernel: [79948.020508] radeon 0000:01:00.0: VM_CONTEXT1_
Oct 24 15:31:48 linux kernel: [79948.020511] radeon 0000:01:00.0: VM_CONTEXT1_
which may have been related to this bug, or it may have been a different bug with the same driver.