(In reply to comment #63 from Egbert Eich)
> For now I would rule out user space. From user space the Xserver
> cannot access memory unless it is explicitly mapped. You can find
> out the mapped memory ranges from /proc/<pid>/maps. It would be
> instructive to know which ranges show up there on the affected
> machines and compare them to an lspci -v output.
It could be some temporary mapping that goes away after a while, so that it doesn't show in /proc/<pid>/maps permanently, but yes, this of course can be tried.
Could please someone, who has access to affected hardware, provide output of
cat /proc/`pidof Xorg`/maps
lspci -v
commands, so that we can see if there is possibly some lethal overlap?
(In reply to comment #63 from Egbert Eich)
> For now I would rule out user space. From user space the Xserver
> cannot access memory unless it is explicitly mapped. You can find
> out the mapped memory ranges from /proc/<pid>/maps. It would be
> instructive to know which ranges show up there on the affected
> machines and compare them to an lspci -v output.
It could be some temporary mapping that goes away after a while, so that it doesn't show in /proc/<pid>/maps permanently, but yes, this of course can be tried.
Could please someone, who has access to affected hardware, provide output of
cat /proc/`pidof Xorg`/maps
lspci -v
commands, so that we can see if there is possibly some lethal overlap?