Re: High system load when burning audio CDs on VIA686B

2002-11-26 Thread David Bell
On Tue, 2002-11-26 at 15:37, Len Sorensen wrote:
> I see NOTHING there that indicates if dma is on or off, only what is
> supported.  The * does NOT indicate linux is using dma.
> /proc/ide/hd?/settings does, as might hdparm device, by itself.
> 
> Your method most certainly does not.

Sorry about that, It seems I wanted hdparm -v, not hdparm -i:

Maxtor 7200RPM hard drive:

[15:53:45][root@david:/home/david]# hdparm -v /dev/hda

/dev/hda:
 multcount= 16 (on)
 I/O support  =  1 (32-bit)
 unmaskirq=  1 (on)
 using_dma=  1 (on)
 keepsettings =  0 (off)
 nowerr   =  0 (off)
 readonly =  0 (off)
 readahead=  8 (on)
 geometry = 4998/255/63, sectors = 80293248, start = 0
 busstate =  1 (on)

Pioneer 106S DVD-ROM:

[15:53:47][root@david:/home/david]# hdparm -v /dev/hdc

/dev/hdc:
 HDIO_GET_MULTCOUNT failed: Input/output error
 I/O support  =  3 (32-bit w/sync)
 unmaskirq=  0 (off)
 using_dma=  1 (on)
 keepsettings =  0 (off)
 HDIO_GET_NOWERR failed: Input/output error
 readonly =  0 (off)
 BLKRAGET failed: Input/output error
 HDIO_GETGEO failed: Invalid argument
 busstate =  1 (on)

Lite-On 24x CD-RW:

[15:54:28][root@david:/home/david]# hdparm -v /dev/hdd

/dev/hdd:
 HDIO_GET_MULTCOUNT failed: Input/output error
 I/O support  =  3 (32-bit w/sync)
 unmaskirq=  0 (off)
 using_dma=  1 (on)
 keepsettings =  0 (off)
 HDIO_GET_NOWERR failed: Input/output error
 readonly =  0 (off)
 BLKRAGET failed: Input/output error
 HDIO_GETGEO failed: Invalid argument
 busstate =  1 (on)

...As you can see (I hope), DMA is enabled on all of these devices.

Thanks.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: High system load when burning audio CDs on VIA686B

2002-11-26 Thread David Bell
Yes, DMA is enabled on all drives:

[12:50:51][root@david:/home/david]# hdparm -i /dev/hda

/dev/hda:

 Model=Maxtor 6E040L0, FwRev=NAR61590, SerialNo=E10RVGWE
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=80293248
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4
 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive Supports : ataATA-1 ATA-2 ATA-3 ATA-4 ATA-5 ATA-6 ATA-7

[12:50:56][root@david:/home/david]# hdparm -i /dev/hdc

/dev/hdc:

 Model=Pioneer DVD-ROM ATAPIModel DVD-106S 011, FwRev=E1.14, SerialNo=
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=13395, BuffSize=64kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4
 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3
udma4
 AdvancedPM=no
 Drive Supports : Reserved : ATA-1 ATA-2 ATA-3 ATA-4 ATA-5

[12:51:32][root@david:/home/david]# hdparm -i /dev/hdd

/dev/hdd:

 Model=LITE-ON LTR-24102B, FwRev=5S54, SerialNo=
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=0kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=yes, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4
 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2
 AdvancedPM=no

I'm running 2.4.19, though, I've had this problem with 2.4.17 as well.

On Tue, 2002-11-26 at 10:21, Len Sorensen wrote:
> Have you checked if dma is enabled?  It could help a lot (both on the HD
> and on the cd burner).  Other times apparently dma on the cd burner is
> bad and ust on the hd is good.  You probably need a 2.4 kernel to get
> dma support on that chipset.  I have seen some comments about never
> using anything other than HDs on a promise controller, although I
> haven't seen any info about why that is the recomendation.
> 
> uname -a: gives your kernel version
> cat /proc/ide/hd?/settings: gives current, min and max settings for each
>   ide device.
> 
> Len Sorensen
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




High system load when burning audio CDs on VIA686B

2002-11-26 Thread David Bell
I have been having this very annoying problem of very high system load
when burning audio CDs.  When burning a full audio CD at 24x, I have
seen the load average reach 20 -- This, on a single processor AMD
Thunderbird system.  top shows 90%+ system proc usage, and, although the
burn works, and the CDs are playable (probably due to burn-proof), this
problem still nags at me.  If I drop the burn speed down to 4x, the
system is usable, but, the system proc time is hovering around 50%, and,
naturally, the burn is unnecessarily slow.  ...I have no problems
whatsoever when burning data CDs [in Linux], or when burning audio CDs
with Nero in Win2k.  I have run cdrecord with extra verbosity and debug
flags and haven't noticed any errors, nor has there been any mention of
trouble from the system logs.  After googling around a bit, I found this
thread:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&threadm=ao9tne%2425nr%241%40FreeBSD.csie.NCTU.edu.tw&rnum=3&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26safe%3Doff%26q%3Daudio%2Bsystem%2Bload%26btnG%3DGoogle%2BSearch%26meta%3Dgroup%253Dmailing.comp.cdwrite

...Which describes my problem perfectly.  My system stats:

AMD Thunderbird 1ghz, overclocked to 1377mhz and perfectly stable
512MB of Crucial CAS2 PC133 memory
Epox 8kta3-Pro motherboard, VIA KT133A chipset with 686B IDE controller
Lite-On 24x CD-RW drive

Is this an issue in the kernel or cdrecord?
Is it expected to be fixed soon?
If not, if I put the burner on a Promise IDE controller card, would the
problems subside?

Thanks!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]