I get these same problems with an IDE system when my machine swaps during
heavy I/O.
-- Jeffrey HundstadRobert Johannes wrote:
> SNIPPET#################################################### > > ncr53c875-0-<0,0>: phase change 2-7 6@00fbc038 resid=1. > attempt to access beyond end of device > 08:04: rw=0, want=1414745929, limit=6197248 > attempt to access beyond end of device > 08:04: rw=0, want=538976289, limit=6197248 > attempt to access beyond end of device > 08:04: rw=0, want=538976289, limit=6197248 > > SNIPPET#################################################### > > That was just a snippet of the kind of errors I'm getting. Ok, I know > that for those of you who have been following the above topic are probably > getting tired of it, but I live with this situation everyday, and have > some insights I would like to air, that I've not seen aired yet (unless I > missed something; I know I did, I just don't know what). > > My system hardware is as follows: AMD k62 300, with Tekram DC390F scsi > card (with seagate ST39173WC), matrox G200 AGP card, FIC PA-2013 > mother board with 1mb cache, DEC500 ethernet and 64mb memory. This > hardware drives redhat 5.2, kernel 2.0.36. > > I've run kernels 2.0.36 through 2.2.13 with above configuration, and still > gotten those errors and file corruption. > > I've been running redhat 5.2 on this system, with slightly varying > hardware configuration, for just over a year now. I ONLY started getting > the above errors and file corruption in late October '99, which is when I > switched my vga hardware AND software, from using PCI S3_Virge/4mbram and > XF86-3.3.3 to using matrox AGP G200/8mbram with XF86-3.3.5. One time I > came back home, to find my system's boot sector wiped out, so I had to > re-install the distribution (lackily, I had backed-up my system). > > I've observed that I only get file corruption and the above errors when > I'm running in X and the system is fairly busy, say, when I'm compiling > something, or doing semi-intensive disk i/o. To test this theory, I > embarked on compiling glibc-2.1.2 and the latest version of gcc. I > compiled glibc while in console mode (no x running) without a single > glitch. I rebooted the system (just to use a fresh system) so I can > compile in X windows, and sure enough, about midway through the compile of > glibc, I got filesystem corruption and the above errors. I did the same > thing with gcc, and got similar results. Whenever I compile anything > fairly large in X, I get the above errors. > > It is this observation that has led me to post to this list, at least to > point out that I've a pattern here that is being caused by a specific > combination of interactions; i.e, using x and doing fairly intensive disk > i/o. Could it be the XF86-3.3.5 driver that's the cause of this problem? > Could it be conflict between XF86-3.3.5 and the scsi driver in the kernel, > conflict between the AGP and SCSI card. > > My observations have not been scientific, so I'm not claiming anything. > I'm simply stating observations that I think might be helpful in narrowing > down the problem. If this problem has been solved, please notify me of > what and where the fix is. > > Thanks > > Robert Johannes > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/