public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Adam McKenna" <adam-dated-1006069566.ee3370@flounder.net>
To: linux-kernel@vger.kernel.org
Subject: Re: DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset
Date: Mon, 12 Nov 2001 23:46:04 -0800	[thread overview]
Message-ID: <20011112234604.C29675@flounder.net> (raw)
In-Reply-To: <20010724182512.B4614@flounder.net> <E15POk0-00020K-00@the-village.bc.nu>
In-Reply-To: <E15POk0-00020K-00@the-village.bc.nu>

On Wed, Jul 25, 2001 at 02:30:20PM +0100, Alan Cox wrote:
> > >From what I've been able to find on Google, there are several other people
> > with this problem;  Has anyone come up with a solution?  I have ServerWorks
> > OSB4 support compiled into the kernel, but this happens with or without it.
> 
> The OSB4 support in Linus 2.4 tree is out of date. The chances are that is
> not the cause of the DMA timeout - but do try the 2.4.6-ac5 tree
> 
> And no there is no 2.4.6-ac5-xfs tree I know of, if you need that you'll
> have to merge stuff

Apologies for the followup to the ancient post, but I've looked at the
differences between the serverworks.c in the current 2.4.14 kernel and the 
most recent -ac patch, and there are less than 30 lines changed.  Does this 
mean that the OSB4 support in the Linus kernel is now up to date?

I ask because I'm still having major problems with the OSB4 chipset on
2.4.14.  I've had to disable DMA completely on my boxes to avoid IDE errors
and fs corruption.  Does anyone know of a patch that addresses the issues
with this chipset?

--Adam
-- 
Adam McKenna <adam@flounder.net>   | GPG: 17A4 11F7 5E7E C2E7 08AA
http://flounder.net/publickey.html |      38B0 05D0 8BF7 2C6D 110A

  reply	other threads:[~2001-11-13  7:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25  1:25 DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Adam McKenna
2001-07-25  3:08 ` Rico Tudor
2001-07-26 16:11   ` Facing problem Dipak Biswas
2001-07-26 17:28     ` Fwd: " Dipak Biswas
2001-07-25 13:30 ` DMA problem (?) w/ 2.4.6-xfs and ServerWorks OSB4 Chipset Alan Cox
2001-11-13  7:46   ` Adam McKenna [this message]
2001-11-13  9:51     ` Alan Cox
2001-11-13 10:30       ` Adam McKenna
2001-11-13 11:04         ` Alan Cox
2001-11-27  8:25           ` Adam McKenna
2001-07-25 15:46 ` Larry Sendlosky
  -- strict thread matches above, loose matches on Subject: below --
2001-07-29 21:50 Marvin Justice
2001-07-29 22:29 ` Ignacio Vazquez-Abrams
2001-07-29 22:37 ` Alan Cox

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=20011112234604.C29675@flounder.net \
    --to=adam-dated-1006069566.ee3370@flounder.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