Comment 285 for bug 263555

(In reply to comment #52 from Jiri Kosina)
> If, however, userspace is corrupting the memory region (most probably X.Org),
> then this protection is rendered useless, but it still is worth trying so that
> we can potentially rule out either userspace or kernelspace code completely.

In fact, testing whether booting the system only in text-mode (so that xorg won't be started at all) also triggers the bug or not would also be a valuable test.