Thank you for your advice (all of you). We actually used
hdparm to put it into pio mode, but your suggestion will be
a more permanent solution.
However, it looks as if there may be two mechanisms in play.
The copy from one computer to another one over NFS came to a stop
after a few files (of 16 Mb each), but we had no disk corruption.
Then we discovered that alsa could not be stopped. It actually turned
out that any attemp to stop alsa would hang the PC to such a degree
that we had to press reset. We then brought it up without starting
alsa. We then tried to copy many files over the net, and now it worked
without any disk corruption or system hang-up.
There seems to be a connection between the alsa sound system and DMA.
We would like to see if the dma mode will work when the alsa system
is not started.

Has anybody had a bad expirience with alsa and DMA corruption?

 -- Bjarne Thomsen


On Thu, 2002-04-11 at 09:51, Mark Williamson wrote:
> I have seen this problem so many times..  you will have to switch off
> DMA on the IDE devices..  this is done by editing the /etc/lilo.conf
> file and by adding "ide=nodma" to the append line..
> 
> e.g
> 
> image=/boot/vmlinuz                                                                  
>         label=linux                                                                  
>   root=/dev/hda2                                                                     
>     initrd=/boot/initrd.img
>       #this is were the change is made
>         append="quiet devfs=mount ide=nodma"
>         vga=788
>         read-only    
> 
> 
> Once you have edited the lilo.conf don't forget to run the lilo command,
> or the changes will do nothing..
> 
> Cheers
> Mark
> 
> On Thu, 2002-04-11 at 04:21, Bjarne Thomsen wrote:
> > I have a colleague who has just gotten a PC
> > based on the ASUS A7V266-E motherboard and
> > an 80GB IBM IDE disk for fast numerical work.
> > He is running LM 8.2 without modifications.
> > The IDE disk is partitioned into ext3 and xfs
> > partitions. / and /usr are ext3 are ext3,
> > the rest are xfs. In addition he has mounted
> > file systems on two different computers (A and B) using NFS.
> > 
> > He has 3 times consistently been able to crash the
> > OS resulting in a file corruption on the IDE disk.
> > 
> > This happened 3 out of 3 times when he copied a 16Mb
> > file from the file system on computer A to the file
> > system on computer B by the program cp on the PC
> > running LM 8.2. It has every time been an ext3 or ext2
> > file system that has been corrupted (maybe a coincidence).
> > 
> > Ist this problem caused by
> > (a) the VIA chipset?
> > (b) the AMD processor?
> > (c) the UDMA setting?
> > (d) the IDE driver?
> > (e) the ext2/ext3 FS?
> > (f) the NFS system?
> > (g) or something else?
> > 
> > We should appreciate very much if any of you
> > could give us any advice on how to proceed.
> > 
> > We have the advantage that we know how to
> > produce the corruption?
> > 
> >   -- Bjarne Thomsen
> > 
> > 
> > 
> > 
> > 
> > 
> > ----
> > 
> 
> > Want to buy your Pack or Services from MandrakeSoft? 
> > Go to http://www.mandrakestore.com
> 
> 
> 
> ----
> 

> Want to buy your Pack or Services from MandrakeSoft? 
> Go to http://www.mandrakestore.com



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to