Please take a look on linux kernel, there is a kernel bug which triggers
when you use DRI on an AMD processor. There is a good chance you hit this.
The problem is related to large page support being incorrectly enabled on
these processors.
Take a look at this article:
http://www.vnunet.com/News/1128504
Steve
On Mon, 2002-01-21 at 12:17, Luis Montes wrote:
> Hi there,
> First of all I want to say that the following problem
> notwithstanding, I have been very happy with linux XFS. I've been
> using it successfully for a while now. But I've recently upgraded
> some of my hardware, and there might be some issues that cause the
> the whole system to crash and burn in the most awful way:
>
> My system is as follows:
>
> Hardware:
> AMD Athlon XP 1700 @ 1.4 something GHz
> ECS K7S5A Motherboard with the SIS 735 chipset
> 128 MB of PC133 SDRAM memory
> ATI all-in-wonder Rage 128 agp
> Two caviar IDE HD
> CDROM, DVD,SBLive! sound card.
>
> Sofware:
> Linux Slackware 8
> 2.4.17 kernel with the xfs-2.4.17-all-i386.bz2 and the 2.4.17-1 rml
> patch
> gcc 2.95.3, used for all compilations
> There are 6 different partitions all with XFS installed.
> xfree86 4.1.99-5 from cvs with DRI enabled and latest ATI-gatos
> drivers
> except for some other user software everything else is from the
> standard Slackware install.
>
> The problem:
> I was just finished installing DRI, and was running glxgears to test
> it. Then when I tried to list a directory in one of the xfs
> partitions it reported input/output error. I rebooted and the root
> filesystem was corrupted beyond repair with the wnsuing kernel panic.
> I rebooted using other slackware install on the other disk (this one
> very standard, on an ext2 fs, but with the same xfs-capable kernel)
> and tried mounting the xfs filesystems on the xfs disk. Three are
> damaged beyond repair (one actually seems to appear as an ext3!
> filesystem) and the other three are fine. I would chalk this
> corruption to some bad interaction between my chipset and the HD's
> (I had another XFS corruption trying to set the DMA mode on this same
> HD). But trying to mount one of the damaged fs's actually produces a
> couple of "unable to handle kernel paging request" errors and the
> system just freezes. It seems repeatable, three times I tried
> mounting that filesystem and thre three times I got thar fault. Is
> this something you guys might want to look more closely? It's been a
> long long while since I had any kernel problems, and I just read in
> the FAQ that I might first run ksymoops. I will need to fix it some
> time soon, though, my wife isn't thrilled that nothing at home seems
> to be working these days ;) How should I gather info on this error
> before I go and reformat this HD?
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx
|