public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John O'Donnell" <johnod@voicefx.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: IDE DMA problems on 2.4.0 with vt82c686a driver
Date: Thu, 11 Jan 2001 23:19:24 -0500	[thread overview]
Message-ID: <3A5E85CC.40606@voicefx.com> (raw)
In-Reply-To: <E14Gj32-0002ND-00@the-village.bc.nu>

Alan Cox wrote:

>> us who have via chipset motherboards, suggesting that it is limited 
>> to that chipset, that chipset is ubiquitous, or via chipset 
>> motherboard owners are generally the complaining type. no idea which 
>> applies there, either.
> 
> 
> Or there are a lot of them. 90% of scsi bug reports I get are adaptec 29xx
> driver. Thats not because the adaptec 29xx is the most sucky driver 8)
> 
> Firstly there are numerous reasons for CRC errors. At ATA100 even the track
> length and the capacitance of the connectors becomes an issue. It is quite
> possibly a driver issue. It could even be that specific combination of drives
> and ide controller is right on the edge of the spec limits and just slightly
> dipping over. It might be the odd power spike.
> 
> Providing the code is working sanely the odd CRC error shouldnt be a 
> problem and should be causing a command retry. The CRC checking used in ATA
> is very robust so unlike scsi parity errors which couldnt be ignored ATA
> ones on occassion are probably fine
> 
> ATA100 is another testimony to the fact that pigs can be made to fly given 
> sufficient thrust (to borrow an RFC)
> 
> Alan

I acquired a VIA Mobo (ASUS CUV4X) for home and it is workin pretty damn
spiffy with Linux - Even better with 2.4.0 with regards to IDE!!!
Once a month I boot WinDOS to play a game I can't play in Linux, THEN
my troubles begin!!!
parport_pc: Via 686A parallel port: io=0x378, irq=7, dma=3
VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:4.1
etc... etc... etc...
yadda yadda yadda ....

Alan,
My father repaired F-4 Phantoms in Vietnam.  He said the F-4 Phantom was
proof that if you put enough power behind a brick, it would fly!!!
Your comment remonded me of that - just had to share  :-)

-- 
<SomeLamer> what's the difference between chattr and chmod?
<SomeGuru> SomeLamer: man chattr > 1; man chmod > 2; diff -u 1 2 | less
	-- Seen on #linux on irc
=== Never ask a geek why, just nod your head and slowly back away.===
+==============================+====================================+
| John O'Donnell (Sr. Systems Engineer, Net Admin, Webmaster, etc.) |
| Voice FX Corporation (a subsidiary of Student Advantage)          |
| One Plymouth Meeting         |     E-Mail: johnod@voicefx.com     |
| Suite 610                    |           www.voicefx.com          |
| Plymouth Meeting, PA 19462   |         www.campusdirect.com       |
+==============================+====================================+

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-12  4:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 13:33 IDE DMA problems on 2.4.0 with vt82c686a driver James Brents
2001-01-11 14:38 ` dep
2001-01-11 14:49   ` Alan Cox
2001-01-11 13:09     ` [PATCH] dgrs.c: kmalloc release on failure Arnaldo Carvalho de Melo
2001-01-11 14:21       ` Arnaldo Carvalho de Melo
2001-01-12  4:19     ` John O'Donnell [this message]
2001-01-12  5:23     ` IDE DMA problems on 2.4.0 with vt82c686a driver Andre Hedrick
2001-01-12  8:05   ` Vojtech Pavlik
2001-01-11 14:41 ` Mark Hahn
2001-01-12  8:12   ` Vojtech Pavlik
2001-01-11 15:12 ` Doug McNaught

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A5E85CC.40606@voicefx.com \
    --to=johnod@voicefx.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox