Lan Barnes wrote:
On Mon, November 19, 2007 3:57 pm, James G. Sack (jim) wrote:
Lan Barnes wrote:
A while back Gus posted a quick tutorial on how I could check and set
DMA
in the CLI and I dutifully saved it god knows where.

Since I can't find it, could someone kindly point me to one or more DMA
URLs or manpages?

TIA,

google on
  site:kernel-panic.org hdparm dma
or, say
  site:kernel-panic.org dma gus

gives (for one)
   http://www.kernel-panic.org/pipermail/kplug-list/2005-October/080686.html



OK. Using that post (thanks Jim/Gus), and spilling /var/log/messages, I get:

[EMAIL PROTECTED] log]# grep -i dma messages
Nov 18 11:55:54 xena kernel: ivtv0 warning: ENC DMA ERROR b
Nov 18 13:00:59 xena kernel: ivtv0 warning: ENC DMA ERROR b
Nov 18 13:04:43 xena kernel: ivtv0 warning: ENC DMA ERROR b
Nov 18 16:54:38 xena kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 18 16:54:38 xena kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=131932869, sector=131932807
Nov 18 16:54:43 xena kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 18 16:54:43 xena kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=131932869, sector=131932815
Nov 18 16:54:49 xena kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 18 16:54:49 xena kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=131932869, sector=131932823
Nov 18 16:54:54 xena kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 18 16:55:23 xena kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=131932869, sector=131932831
Nov 18 16:55:23 xena kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 18 16:55:23 xena kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=131932869, sector=131932839
Nov 18 16:55:23 xena kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 18 16:55:23 xena kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=131932869, sector=131932847
Nov 18 16:55:23 xena kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 18 16:55:23 xena kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=131932869, sector=131932855
Nov 18 16:55:23 xena kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 18 16:55:23 xena kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=131932869, sector=131932863
Nov 18 16:55:23 xena kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Nov 18 16:55:23 xena kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=131932869, sector=131932863
Nov 18 16:57:55 xena kernel:   DMA             0 ->     4096
Nov 18 16:57:56 xena kernel: VP_IDE: VIA vt8235 (rev 00) IDE UDMA133
controller on pci0000:00:11.1
Nov 18 16:57:56 xena kernel:     ide0: BM-DMA at 0xfc00-0xfc07, BIOS
settings: hda:DMA, hdb:DMA
Nov 18 16:57:56 xena kernel:     ide1: BM-DMA at 0xfc08-0xfc0f, BIOS
settings: hdc:DMA, hdd:DMA
Nov 18 16:57:56 xena kernel: hda: 156301488 sectors (80026 MB) w/2048KiB
Cache, CHS=65535/16/63, UDMA(33)
Nov 18 16:57:56 xena kernel: hdb: 488397168 sectors (250059 MB) w/8192KiB
Cache, CHS=30401/255/63, UDMA(33)
Nov 18 16:57:56 xena kernel: , UDMA(100)
Nov 18 16:57:57 xena kernel: , UDMA(66)
Nov 18 19:08:06 xena kernel: ivtv0 warning: ENC DMA ERROR b
[EMAIL PROTECTED] log]# hdparm -i /dev/hda

/dev/hda:

 Model=ST380020ACE, FwRev=3.39, SerialNo=5GC113ZQ
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=unknown, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=4047/16/255, CurSects=16511760, LBA=yes, LBAsects=156301488
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5
 AdvancedPM=yes: unknown setting WriteCache=enabled
 Drive conforms to: ATA-1 X3T9.2 781D prior to revision 4:  ATA/ATAPI-1
ATA/ATAPI-2 ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5 ATA/ATAPI-6

 * signifies the current active mode

So I'm reading this to say, yesterday I had serious DMA issues, but today
I don't. And in that time, IIRC, I rebooted for unrelated reasons, because
I was unaware of any problems yesterday (the Chargers looked awful, but I
figured that was them). *maybe* a little grainy when watching TV through
myth, but recorded playback (already in mpeg format) was OK.

The hdparam from today seems to me to say that I have *udma2 running, so
I'm cool, right? Except figuring out what went squirrelly yesterday might
be nice.

Of course, I am a blind man in a shadowy cave surrounded by the all-seeing
in this stuff, so if anyone wants to set me straight, I'm cool with that.

And a personal note to Gus, I know you think VIA MBs suck dead bunnies,
and I'm happy to yield the point, but what's it gonna be this year, a new,
good MB or a couple of Christmas presents for the Kids? After all,
remember my myth mantra: It's Only TV. And that it seems to work most of
the time.

You still have DMA problems, it's just that they are being covered up by slowing everything down. The hard drive is supposed to support up to UDMA mode 5. The kernel algorithm specified for the IDE drivers specifies an automatic backoff when errors are encountered.

The errors for the ivtv driver indicate that there are DMA problems with your PVR-150 card also.

Not all VIA motherboards are bad, it's only certain ones. As a matter of fact, I just changed my MythTV motherboard to that one I mentioned in another thread about the Walmart PC. The board is working great. Specs on the board are here: <http://www.via.com.tw/en/initiatives/empowered/pc2500_mainboard/index.jsp>

Gus


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to