From: Joel Cant <lkml@linuxmod.co.uk>
To: John Wong <kernel@implode.net>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Promise IDE DMA issue
Date: Mon, 03 Jan 2005 22:22:58 +0000 [thread overview]
Message-ID: <41D9C5C2.5010606@linuxmod.co.uk> (raw)
In-Reply-To: <20050103215250.GA9409@gambit.implode.net>
John Wong wrote:
>Latest 1.009 BIOS flashed last night. I'll try out some BIOS settings,
>but the settings work fine with Windows XP. That's why I think it could
>be something with the driver. This is with the PDC202XX_NEW on kernel
>2.6.10 The DMA timeout happens sporadically, but as of yet, has yet to
>reoccur. The change from 1.008 to 1.009 mentions nothing about the
>Promide IDE.
>
>John
>
>On Mon, Jan 03, 2005 at 01:00:59PM -0500, Jeff Garzik wrote:
>
>
>>John Wong wrote:
>>
>>
>>>I recently upgraded fron a nVidia nForce2 MCP-T based A7NX-DX
>>>motherboard to an A8V DX, Via K8T800 Pro. Now occassionally, I get
>>>DMA issues on a drive attached to a Promise 133 TX2 controller (20269).
>>>
>>>
>>I would try fiddling with BIOS settings, and make sure you have the
>>latest BIOS.
>>
>> Jeff
>>
>>
>>
>>
>>
>>
Sounds simlar to the problems i'm having with the channels resetting
under heavy load, and then fudging DMA, and i'm not the only one havign
these issues, seems its a common problem with these cards, not sure if
theres been some slight changes in the chip itself or wether there is a
fault with the kernel driver, as you say, it seems that the problem does
not occour under windows.
Joel
next prev parent reply other threads:[~2005-01-03 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 17:37 Promise IDE DMA issue John Wong
2005-01-03 18:00 ` Jeff Garzik
2005-01-03 21:52 ` John Wong
2005-01-03 22:22 ` Joel Cant [this message]
2005-01-04 0:27 ` John Wong
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=41D9C5C2.5010606@linuxmod.co.uk \
--to=lkml@linuxmod.co.uk \
--cc=jgarzik@pobox.com \
--cc=kernel@implode.net \
--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