All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: febo@delenda.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: 'vintage' via dma bug
Date: Tue, 18 Jul 2006 14:40:52 -0400	[thread overview]
Message-ID: <20060718184052.GA9679@redhat.com> (raw)
In-Reply-To: <001001c6aa99$0476a380$fc01a8c0@EFFEPUNTO>

On Tue, Jul 18, 2006 at 08:36:00PM +0200, febo@delenda.net wrote:
 > I have the misfortune to run a rather old PIII machine with a VIA chipset, 
 > a Fedora Core 1 distro with 2.4.22 kernel and two PATA hard mirrored hard 
 > disk, on two separate channels, both set to primary. I've experienced some 
 > data corruption lately and after much googling I've found that 4-5 years 
 > ago some via chipset experienced a similar problem with dma transfers, 
 > especially with hard disk configured the very same way as my setup. The bug 
 > was fixed, I gather, in 2.4.4. I've upgrade the kernel to 2.6.10 (the 
 > latest Fedora legacy core *TWO* kernel, with fingers crossed) but the 
 > corruption problems usually start to pop up only after a few weeks of 
 > uptime, especially under relatively heavy load.
 > I couldn't find more precise pointers after all these years so I'd like to 
 > know if that bug really affected my chipset, and if 2.6.10 is a valid 
 > solution.. 

I'm puzzled why you upgraded from one end-of-life'd distro to
another ancient end-of-life'd distro.   You're more likely to get
interest from the upstream developers if you're running
something recent.  Even _I_ don't remember what was good/bad
in the Fedora kernels from that era, and I built them :-)

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-07-18 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 18:36 'vintage' via dma bug febo
2006-07-18 18:40 ` Dave Jones [this message]
2006-07-18 19:02   ` febo

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=20060718184052.GA9679@redhat.com \
    --to=davej@redhat.com \
    --cc=febo@delenda.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.