From: Ben Collins <bcollins@debian.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Willy Tarreau <willy@w.ods.org>,
Jason Papadopoulos <jasonp@boo.net>,
linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: Linux 2.4.21-rc3 : IDE pb on Alpha
Date: Sat, 31 May 2003 11:24:17 -0400 [thread overview]
Message-ID: <20030531152417.GY13766@phunnypharm.org> (raw)
In-Reply-To: <20030527180403.A2292@jurassic.park.msu.ru>
On Tue, May 27, 2003 at 06:04:03PM +0400, Ivan Kokshaysky wrote:
> On Tue, May 27, 2003 at 02:31:52PM +0200, Willy Tarreau wrote:
> > Sorry, I pasted the .config that I used just after, and which allowed me to
> > boot. Later I set CONFIG_BLK_DEV_ALI15X3 again and CONFIG_BLK_DEV_IDEDMA_PCI,
> > but I left CONFIG_IDEDMA_PCI_AUTO disabled. I now can boot and enable DMA
> > later. That's weird, but it works.
>
> Perhaps not that weird. From my experience, ALi DMA is sensitive to
> some of "PIO timings". That is, if SRM hasn't initialized the chipset
> properly (on Nautilus it has, BTW), DMA won't work. When you boot with
> DMA disabled, driver has to set right PIO mode, so you can safely
> enable DMA later.
>
> Can you (and Jason) try this patch with CONFIG_IDEDMA_PCI_AUTO=y?
Dave Miller asked me to try this patch. On sparc64, we've had a never
ending battle with ALi 5229 on Sun Blade 100's. After some time, files
would start to get corrupted (in memory, not on disk, unless the
corruption was saved somehow inadvertently). It exposed itself as two
null bytes at the start of a file.
I just tried this patch, and for the first time in a long time, I've
been able to boot with UDMA(66) enabled and not get the corruption.
Usually I can expose the corruption with kernel compiles within 10-60
minutes. I've been running your patch for almost 2 days now, and so far
have not been able get corruption. I even left a looping 2.5.69 compile
going (make clean; make) for over 10 hours.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2003-05-31 16:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 3:37 Linux 2.4.21-rc3 : IDE pb on Alpha Jason Papadopoulos
2003-05-27 4:53 ` Willy Tarreau
2003-05-27 9:40 ` Ivan Kokshaysky
2003-05-27 12:31 ` Willy Tarreau
2003-05-27 14:04 ` Ivan Kokshaysky
2003-05-27 14:37 ` Willy Tarreau
2003-05-28 0:38 ` Willy Tarreau
2003-05-28 1:41 ` Jason Papadopoulos
2003-05-28 3:12 ` Jeff Garzik
2003-05-29 0:35 ` Jason Papadopoulos
2003-05-29 1:10 ` Jeff Garzik
2003-05-28 14:45 ` Ivan Kokshaysky
2003-05-31 15:24 ` Ben Collins [this message]
2003-06-01 18:40 ` Ivan Kokshaysky
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 22:19 Linux 2.4.21-rc3 Marcelo Tosatti
2003-05-25 17:36 ` Linux 2.4.21-rc3 : IDE pb on Alpha Willy Tarreau
2003-05-25 17:00 ` Willy Tarreau
2003-05-25 20:37 ` Mike Fedyk
2003-05-25 20:45 ` Bartlomiej Zolnierkiewicz
2003-05-25 20:55 ` Mike Fedyk
2003-05-25 21:23 ` Bartlomiej Zolnierkiewicz
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=20030531152417.GY13766@phunnypharm.org \
--to=bcollins@debian.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jasonp@boo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=willy@w.ods.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