From: Linux Kernel Mailing List <kernel@iggy.triode.net.au>
To: linux-kernel@vger.kernel.org
Subject: ALI 15X3 DMA Freeze
Date: Sun, 10 Feb 2002 12:42:07 +1100 [thread overview]
Message-ID: <20020210124207.C5191@iggy.triode.net.au> (raw)
I'm using kernel 2.4.18-pre9, which has a problem when I switch DMA on
the IDE hard drive. With DMA enabled, I cannot complete a kernel
compile without the machine locking up. The motherboard is an
ASUS board, with 512MB of DDR RAM and an Athlon 1800 XP. If I
turn the ide DMA off, then I can compile as many linux kernels
as I like with no lockup. This DMA lockup also occurs on other
2.4.x kernels. Is anyone interested in getting me to test a
fix for this problem?
Feb 10 10:44:35 solaris kernel: PCI: Using IRQ router ALI [10b9/1533] at 00:07.0
Feb 10 10:44:35 solaris kernel: ALI15X3: IDE controller on PCI bus 00 dev 20
Feb 10 10:44:35 solaris kernel: ALI15X3: chipset revision 196
Feb 10 10:44:35 solaris kernel: ALI15X3: not 100%% native mode: will probe irqs later
Feb 10 10:44:35 solaris kernel: ALI15X3: ATA-66/100 forced bit set (WARNING)!!
with dma off hdparm -Tt /dev/hda gives:
/dev/hda:
Timing buffer-cache reads: 128 MB in 0.56 seconds =228.57 MB/sec
Timing buffered disk reads: 64 MB in 14.85 seconds = 4.31 MB/sec
with dma off hdparm -Tt /dev/hda gives:
/dev/hda:
Timing buffer-cache reads: 128 MB in 0.49 seconds =261.22 MB/sec
Timing buffered disk reads: 64 MB in 1.70 seconds = 37.65 MB/sec
Cheers. Paul
next reply other threads:[~2002-02-10 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 1:42 Linux Kernel Mailing List [this message]
2002-02-10 2:30 ` Alan Cox
2002-02-10 4:42 ` Linux Kernel Mailing List
2002-02-10 15:15 ` Alan Cox
2002-02-10 21:59 ` Linux Kernel Mailing List
[not found] ` <Pine.LNX.4.33.0202101817330.31698-100000@coffee.psychology.mcmaster.ca>
2002-02-10 23:28 ` Linux Kernel Mailing List
2002-02-11 0:30 ` Linux Kernel Mailing List
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=20020210124207.C5191@iggy.triode.net.au \
--to=kernel@iggy.triode.net.au \
--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
all inboxes | Powered by JetHome®