> [EMAIL PROTECTED]:~$ sudo ./intel_reg_dumper
.> /intel_reg_dumper: error while loading shared libraries: libpciaccess.so.0: 
cannot open shared object file: No such file or directory

Fixed by (duh) installing the libpciaccess0 package.

The register and page table dump is attached, and it's quite revealing.
My result is basically the same as Peter's analysis of eeejey's register dump.

The coordinates of my display corruption, (1024..1679, 736) and (0..655,
959) correspond _exactly_ with page table entries 1537 and 1982.  This
is calculated from DSPABASE and DSPASTRIDE.

The cause of the corruption is without doubt, page table entry 1537,
shown in context:

pagetable entry 1534, value 0x83fdfe001
pagetable entry 1535, value 0x83fdff001
pagetable entry 1536, value 0x83fe00001
pagetable entry 1537, value 0x83ffbe001    <-  anomaly
pagetable entry 1538, value 0x83fe02001
pagetable entry 1539, value 0x83fe03001
pagetable entry 1540, value 0x83fe04001

Page table entry 1982 maps to the same physical page, and this is why
both areas of the display always show the same pixels:

pagetable entry 1979, value 0x83ffbb001
pagetable entry 1980, value 0x83ffbc001
pagetable entry 1981, value 0x83ffbd001
pagetable entry 1982, value 0x83ffbe001

The page table after 1982 is all over the place, despite being in the
middle of the framebuffer.  This doesn't cause screen artifacts, but it
might be indicative of other problems which are hidden, if it's not
supposed to be like this:

pagetable entry 1983, value 0x836d55001
pagetable entry 1984, value 0x836d20001
pagetable entry 1985, value 0x836d4d001
pagetable entry 1986, value 0x836d4e001
pagetable entry 1987, value 0x836d66001
pagetable entry 1988, value 0x836dcf001

Also as with Peter's comment, the suspect entry's value is 0x83ffbe001,
and it is used by many later page table entries too.  (But it's not the
only value which is used by many page table entries; 0x8371cc001 is
also.)

So there we go.  Corrupt page table (or erroneous allocation) is the
reason for the display corruption, but what is the reason for the
corrupt page tables?

-- 
screen artifacts after resume, part row of pixels in error (945GM)
https://bugs.launchpad.net/bugs/91966
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to