Bug #2707
closed
physical memory corruption with intel gpu 4500HD
Added by jorisgio over 10 years ago.
Updated over 5 years ago.
Description
When running xorg, a memory corruption happens on the physical page at 0x80000000, leading to random crash depending on where the page is mapped.
Removing this page from the physical pool used by virtual memory makes the box stable.
Files
Nobody apparently encountered this issue on Linux so far; the driver is more suspect than the GPU itself.
Some suggestions from danvet@
- tried the usual triage with disabling rendering and stuff?
- if that doesn't indicate anything then I'd dump gtt ptes for the suspect entry
- if that doesn't help grab a linux live distro, make sure it doesn't happen and then grab register dumps with intel_reg_dumper on both linux and bsd and compare
- Related to Bug #2709: xorg crash with X86_64_GENERIC added
- Related to Bug #2705: panic: assertion "pv->pv_m == p" in pmap_remove_pv_pte added
- Related to deleted (Bug #2705: panic: assertion "pv->pv_m == p" in pmap_remove_pv_pte)
- Related to Bug #2705: panic: assertion "pv->pv_m == p" in pmap_remove_pv_pte added
The reason for this is that we do not reserve memory in the IO memory rman on bootup. I have a patch for this, but it freezes the computer on boot at the moment, so it's useless as it is. It is basically a port from FreeBSD's nexus.c on amd64.
- Status changed from New to Feedback
This should have been fixed with 97d69dfd2be7514f21a7ff7979e44e17fbb3ddb and d69e20aa8bfb20a9eeee308c09cdf56b4076e12f
- Status changed from Feedback to Resolved
Has been resolved by profmakx.
Also available in: Atom
PDF