public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <safemode@speakeasy.net>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cerberus errors on 2.4.19 (ide dma related)
Date: 18 Aug 2002 05:13:33 -0400	[thread overview]
Message-ID: <1029662014.2966.19.camel@psuedomode> (raw)
In-Reply-To: <20020818090000.GA5154@ip68-4-77-172.oc.oc.cox.net>

On Sun, 2002-08-18 at 05:00, Barry K. Nathan wrote:
> On Sun, Aug 18, 2002 at 03:26:42AM -0400, Ed Sweetman wrote:
> > Ok, i reran the test with a little process of elimination.
> > The problem occurs only when dma is enabled on the promise controller's
> > harddrive. 
> [snip]
> 
> Looking at your dmesg, it seems you're using a Promise controller on a
> VIA chipset. AFAIK this is a known problem and the only known solution
> is to avoid the VIA/Promise combo.

there are a lot less bug reports than would be seen if it was strictly a
hardware problem. Promise controllers are by far the most popular and
readily available addon controllers and the amount of people using via
chipsets is significant for such a hardware problem to make a lot more
than a handful of people post problems directly related to the fact that
they use promise controllers on a via chipset. You'd get a lot of people
screaming and yelling.   It could just as easily be the promise driver
used with the via chipset.  The only people who know are those that work
with the ide drivers and hardware.  Are we dealing with a fundemental
flaw with via and promise combos or some driver bug ?   

as for the solution, it's not a solution unless it's strictly a hardware
conflict which i doubt.  That is, unless you know a place that trades
ide controllers and will take my promise controller and give me one that
works at equivalant speeds that the promise would have.  


assuming there aren't any such places.  I'm looking for real pointers as
to what's going on and how to fix it, not ways to avoid problems.  I
have ways to avoid the problem, they're not solutions to the problem
though. Thanks anyways. 


  reply	other threads:[~2002-08-18  9:09 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-18  6:44 cerberus errors on 2.4.19 (ide dma related) Ed Sweetman
2002-08-18  7:15 ` Ed Sweetman
2002-08-18  9:19   ` Andre Hedrick
2002-08-18 18:11     ` Ed Sweetman
2002-08-18 18:31     ` Ed Sweetman
2002-08-18  7:26 ` Ed Sweetman
2002-08-18  9:00   ` Barry K. Nathan
2002-08-18  9:13     ` Ed Sweetman [this message]
2002-08-18 17:50   ` Jonathan Lundell
2002-08-18 18:04     ` Ed Sweetman
2002-08-18  9:10 ` Alexander Viro
2002-08-18  9:16   ` Ed Sweetman
2002-08-18 18:10     ` Ed Sweetman
2002-08-18 18:20       ` Sean Neakums
2002-08-18 18:29         ` Ed Sweetman
2002-08-18 18:36           ` Sean Neakums
2002-08-18 21:53             ` Barry K. Nathan
2002-08-18 22:26               ` devfs Ed Sweetman
2002-08-18 22:47                 ` devfs Sean Neakums
2002-08-18 23:03                 ` devfs Alexander Viro
2002-08-18 23:15                   ` devfs Ed Sweetman
2002-08-21  4:49                     ` devfs Richard Gooch
2002-08-21  5:03                       ` devfs Ed Sweetman
2002-08-19  1:06                   ` devfs Olivier Galibert
2002-08-19  2:01                     ` devfs Greg KH
2002-08-18 23:18                 ` devfs Barry K. Nathan
2002-08-18 22:41           ` cerberus errors on 2.4.19 (ide dma related) Andrew Rodland
2002-08-18 22:55             ` Ed Sweetman
2002-08-19 21:46               ` Ed Sweetman
2002-08-18 19:53       ` Ed Sweetman
2002-08-18 20:07         ` Andre Hedrick
2002-08-18 20:29           ` Ed Sweetman
2002-08-23  0:03             ` Samuel Flory
2002-08-19  0:06       ` Denis Vlasenko

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=1029662014.2966.19.camel@psuedomode \
    --to=safemode@speakeasy.net \
    --cc=barryn@pobox.com \
    --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