From: "Bill Church" <bill@bsius.com>
To: <linux-kernel@vger.kernel.org>
Subject: PROBLEM: PIIXn DMA errors
Date: Wed, 10 Sep 2003 14:03:52 -0400 [thread overview]
Message-ID: <000601c377c5$e4c11e70$6900000a@bsi000> (raw)
I'm reposting this because I never saw it come through, if it's
duplicate I apologize in advance... Also, I saw *some* mention about a
similar issue in the archives which mentioned that 2.4.22 would fix this
problem, but doesn't seem to work for me. :(
I have a GigaByte GA-8IGX with an Intel 845G chipset.
Two new Hitachi 180GXP 80G DeskStar drives. Both set as master on two
ATA/100 channels (/dev/hda and /dev/hdc).
P4 2.53 Processor at 533FSB
2 Sticks of 512MB Corsair 333MHz DDR Ram
My issue:
Started out with Gentoo gs-sources Kernel (2.4.22_pre2-gss). When I
would boot with both drives connected, /dev/hdc would timeout and hang
when enumerating the partitions. If I disabled DMA, the system would
boot with out error. I disabled ACPI also, but that seemed to have no
effect.
I reverted to the vanilla-sources Kernel (2.4.22) with the same config
file and experienced the same results. However, /dev/hdc would time out
several times but no hang. Upon investigation I found that /dev/hda had
DMA enabled but /dev/hdc had DMA disabled. So with hdparm I enabled dma
on /dev/hdc and tried some operations on that drive. Just an fdisk
/dev/hdc produced timeouts. Checking hdparm again on /dev/hdc revealed
that it was again disabled.
I then tried setting both drives on the same channel, manually setting
master on one drive and slave on another. Same issues as before. I also
tried swapping cables and drive positions. Moving /dev/hdc drive to
/dev/hda and vice-versa.
So I decided to revert to 2.4.20, I experienced the same results as did
originally (time out on /dev/hdc to lockup).
I then decided to try 2.6.0-test4, same results...
I am using 80 conductor 40 pin ATA-100 cables. And I'm using the PIIXn
option under ATA/IDE/MFM/RLL support.
Thanks in advance...
-Bill
bill at bsius dot com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in the body of a message to majordomo@vger.kernel.org More majordomo
info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2003-09-10 18:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000601c377c5$e4c11e70$6900000a@bsi000' \
--to=bill@bsius.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
all inboxes | Powered by JetHome®