Messages in this thread | | | From | Steve Brueggeman <> | Subject | Re: Athlon PSE/AGP Bug | Date | Tue, 22 Jan 2002 16:32:07 -0600 |
| |
Yep, that was the first thing that crossed my mind.
I had a floppy with memtest86 installed on it, and it ran for 4 hours without any errors. Since I've seen memtest86 find bad bits on memory modules that normally worked for me, I figured that this must surely indicate that my segfaults are not related to bad memory subsystem.
Also, while I expect setting the command line option mem=nopentium would slow things down slightly, I don't think that they'd be so slow as to hide the bad memory. Also, the segfaults happen VERY reliably without the mem=nopentium option, and have not happened even once, WITH the mem=nopentium option.
One more curious thing is, I've got 64MB GForce-2 MX, and the largest I can set my AGP aparature size to is 64MB. Maybe a boundary condition thing???
On Tue, 22 Jan 2002 21:13:42 +0100, you wrote:
>Steve Brueggeman <brewgyman@mediaone.net> writes: > >> Forgot to mention, I got the segfaults compiling kernels while running >> linux-2.4.17, I was in console, and did not have Frame Buffer, or drm drivers >> loaded. I did have the SiS AGP compiled into the kernel though. > >On my new system at home, I got similar segfaults. Running memtest86 >revealed that one of the RAM modules had a problem--and if I swapped >them, the BIOS startup code wouldn't even expand the actual BIOS code >every other system boot. After removing the offending RAM module (and >later replacing it) the problems were completely gone and haven't >returned yet... > >Fortunately, I didn't know of the PSE/AGP bug back then. This made >debugging much, much easier. ;-)
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |