From: Allen Martin <AMartin@nvidia.com>
To: "'Jesse Allen'" <the3dfxdude@hotmail.com>, b@netzentry.com
Cc: linux-kernel@vger.kernel.org
Subject: RE: NForce2 pseudoscience stability testing (2.6.0-test11)
Date: Wed, 3 Dec 2003 21:11:37 -0800 [thread overview]
Message-ID: <DCB9B7AA2CAB7F418919D7B59EE45BAF49F874@mail-sc-6.nvidia.com> (raw)
> -----Original Message-----
> From: Jesse Allen [mailto:the3dfxdude@hotmail.com]
> Sent: Wednesday, December 03, 2003 6:46 PM
> To: b@netzentry.com
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
>
> I suppose I could try right now. I don't have a pci ide with
> me right now, but I do have pci scsi cards. But doesn't
> running with the generic ide driver basically prove the same
> thing? APIC & Generic IDE: works, PIC & nForce IDE: works,
> APIC & nForce IDE: deadlocks. It's not like we are expecting
> faulty nforce ide hardware, or are we?
I don't think there's any faulty nForce IDE hardware or we would have heard
about it from windows users (and we haven't).
The problem with comparing the nForce IDE driver against the generic IDE
driver is that the generic IDE driver won't enable DMA, so the interrupt
rate will be much different. If there's some interrupt race condition in
APIC mode, disabling DMA may mask it.
Also are people who are having problems using rounded or flat cables? It's
possible the problem could be related to DMA CRC errors. Switching to flat
cables can help with that.
-Allen
next reply other threads:[~2003-12-04 5:11 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 5:11 Allen Martin [this message]
2003-12-04 20:04 ` NForce2 pseudoscience stability testing (2.6.0-test11) Jesse Allen
2003-12-04 20:41 ` Craig Bradney
2003-12-04 20:55 ` Craig Bradney
2003-12-04 22:03 ` Bob
2003-12-05 0:07 ` OOps? was: " Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 13:07 Dan Creswell
2003-12-04 12:17 b
2003-12-04 15:19 ` Craig Bradney
2003-12-04 16:32 ` Josh McKinney
2003-12-04 17:08 ` Julien Oster
2003-12-04 17:55 ` Josh McKinney
2003-12-05 13:28 ` Pat Erley
2003-12-04 9:09 b
2003-12-04 8:59 b
2003-12-04 5:37 b
2003-12-04 7:00 ` Craig Bradney
2003-12-04 2:57 b
2003-12-04 1:41 b
2003-12-04 2:45 ` Jesse Allen
2003-12-04 7:42 ` Prakash K. Cheemplavam
2003-12-04 4:45 ` Josh McKinney
2003-12-04 11:47 ` ross.alexander
[not found] <fa.nmlihqm.16j6n38@ifi.uio.no>
[not found] ` <fa.f27m7i8.1vk0j84@ifi.uio.no>
2003-12-04 1:08 ` walt
2003-12-03 1:32 Allen Martin
2003-12-03 1:23 b
2003-12-03 1:30 ` Ian Kumlien
2003-12-03 0:58 Allen Martin
2003-12-03 1:09 ` Ian Kumlien
[not found] <3FCD21E1.5080300@netzentry.com>
2003-12-03 0:28 ` Craig Bradney
2003-12-03 0:48 ` Prakash K. Cheemplavam
2003-12-03 8:15 ` Craig Bradney
2003-12-03 17:09 ` bill davidsen
[not found] ` <200312031709.MAA18860@gatekeeper.tmr.com>
2003-12-03 17:37 ` Prakash K. Cheemplavam
2003-12-03 0:47 ` Ian Kumlien
[not found] <WSA7.6D.39@gated-at.bofh.it>
[not found] ` <WTYM.3ua.7@gated-at.bofh.it>
[not found] ` <WVoa.73O.17@gated-at.bofh.it>
2003-11-30 13:06 ` Lenar Lõhmus
2003-11-29 10:25 bug in -test11 make xconfig Christopher Sawtell
2003-11-29 11:18 ` NForce2 pseudoscience stability testing (2.6.0-test11) Craig Bradney
2003-11-29 16:34 ` Julien Oster
2003-11-29 16:47 ` Craig Bradney
2003-11-29 16:54 ` Craig Bradney
2003-12-07 11:32 ` Jussi Laako
2003-12-07 15:49 ` Prakash K. Cheemplavam
2003-12-01 18:30 ` Pavel Machek
2003-12-01 20:20 ` Craig Bradney
[not found] <001a01c3b515$b6030de0$0f00a8c0@client.attbi.com>
2003-11-28 15:13 ` ross.alexander
2003-11-28 16:46 ` Alistair John Strachan
2003-11-28 18:13 ` Julien Oster
2003-11-28 18:24 ` Prakash K. Cheemplavam
2003-11-29 2:55 ` Josh McKinney
2003-11-29 16:33 ` Julien Oster
2003-11-29 17:15 ` Josh McKinney
2003-12-02 10:13 ` ross.alexander
2003-12-02 21:12 ` Josh McKinney
2003-12-03 16:23 ` Julien Oster
2003-11-28 18:00 ` Julien Oster
2003-11-28 18:18 ` Prakash K. Cheemplavam
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=DCB9B7AA2CAB7F418919D7B59EE45BAF49F874@mail-sc-6.nvidia.com \
--to=amartin@nvidia.com \
--cc=b@netzentry.com \
--cc=linux-kernel@vger.kernel.org \
--cc=the3dfxdude@hotmail.com \
/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;
as well as URLs for NNTP newsgroup(s).