From: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
To: linux-kernel@vger.kernel.org
Cc: rgooch@ras.ucalgary.ca
Subject: Re: Lockup in IDE code
Date: Sat, 10 Nov 2001 15:36:51 +0200 [thread overview]
Message-ID: <200111101336.fAADapr02433@montezuma.mastecende.com> (raw)
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 21
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:pio, hdb:DMA
ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:pio, hdd:pio
hdb: CRD-8480B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
He only has the one device on IDE as you can see that the probe only shows
hdb, and i have a PIIX4 too and they do UDMA33 well enough, in fact i'm not
aware of any DMA problems with the PIIX4. Richard, have you tried disabling
CONFIG_IDEDMA_AUTO and CONFIG_PIIX_TUNING ?
But looking at the code in ide-features.c it doesn't look like we have
enabled DMA by the time we get to that code.
if (error) {
(void) ide_dump_status(drive, "set_drive_speed_status", stat);
return error;
}
<----- snip ----- >
#if defined(CONFIG_BLK_DEV_IDEDMA) && !defined(CONFIG_DMA_NONPCI)
if (speed > XFER_PIO_4) {
outb(inb(hwif->dma_base+2)|(1<<(5+unit)), hwif->dma_base+2);
} else {
outb(inb(hwif->dma_base+2) & ~(1<<(5+unit)),
hwif->dma_base+2);
}
#endif /* (CONFIG_BLK_DEV_IDEDMA) && !(CONFIG_DMA_NONPCI) */
But bear in mind i'm far from being remotely knowledgeable about this
specific code ;)
next reply other threads:[~2001-11-10 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 13:36 Zwane Mwaikambo [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-16 7:08 Ph. Marek
2001-11-10 13:22 Zwane Mwaikambo
2001-11-09 2:17 Richard Gooch
2001-11-09 9:45 ` Xavier Bestel
2001-11-09 16:56 ` Richard Gooch
2001-11-09 19:38 ` Dan Hollis
2001-11-09 19:49 ` Xavier Bestel
2001-11-09 19:41 ` Mark Zealey
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=200111101336.fAADapr02433@montezuma.mastecende.com \
--to=zwane@linux.realnet.co.sz \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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®