From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Ross Biro <rossb@google.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-pre3 kernel crash
Date: Mon, 27 Jan 2003 20:49:12 +0100 [thread overview]
Message-ID: <20030127194912.GI889@suse.de> (raw)
In-Reply-To: <200301271945.h0RJj7B26739@devserv.devel.redhat.com>
On Mon, Jan 27 2003, Alan Cox wrote:
> > On Mon, 2003-01-27 at 17:53, Ross Biro wrote:
> > > This looks like the same problem I ran into with IDE and highmem not
> > > getting along. Try compiling your kernel with out highmem enabled and
> > > see what happenes.
> >
> > Indeed, looking at the code, it seems ide_build_sglist() doesn't worry
> > much about highmem, just picks bh->b_data, assume it's a virtual
> > address, and gives that to pci_map_sg(). I beleive, at least for highmem
> > pages, it should rather pick bh->b_page and bh_offset(bh)
> >
> > I can hack something, maybe tonight, but I can't test HIGHMEM for a while
> > here. Interestingly, I had no problem report on PPC from users using IDE
> > with highmem though.
>
> I don't see how 2.4 IDE would be getting highmem pages. 2.5 IDE does handle
> this and does need to
?
The block-highmem patch is in the 2.4 kernels since 2.4.20-pre2/3 (I
forget which). __ide_dma_on() calls ide_toggle_bounce() which turns on
full 32-bit dma for that drive, if it's a disk. So IDE will be getting
highmem pages for io if you have them.
--
Jens Axboe
next prev parent reply other threads:[~2003-01-27 19:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 15:41 2.4.21-pre3 kernel crash Martin MOKREJŠ
2003-01-27 16:53 ` Ross Biro
2003-01-27 17:13 ` Martin MOKREJŠ
2003-01-27 19:23 ` Jens Axboe
2003-01-27 20:27 ` Edward Tandi
2003-01-27 20:36 ` Jeff Garzik
2003-01-27 20:47 ` Edward Tandi
2003-01-27 20:57 ` Jeff Garzik
2003-01-28 9:08 ` Alan Cox
2003-01-28 10:50 ` Martin MOKREJŠ
2003-01-27 23:18 ` J.A. Magallon
2003-01-27 23:24 ` Jens Axboe
2003-01-28 0:02 ` J.A. Magallon
2003-01-27 19:03 ` Benjamin Herrenschmidt
2003-01-27 19:21 ` Benjamin Herrenschmidt
2003-01-27 19:25 ` Jens Axboe
2003-01-27 19:45 ` Alan Cox
2003-01-27 19:49 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-28 16:41 Larry Sendlosky
2003-01-28 22:06 ` Jens Axboe
2003-01-29 8:23 ` Benjamin Herrenschmidt
2003-01-29 8:53 ` Jens Axboe
2003-01-29 9:44 ` Benjamin Herrenschmidt
2003-01-29 10:16 ` Jens Axboe
2003-01-29 8:23 Benjamin Herrenschmidt
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=20030127194912.GI889@suse.de \
--to=axboe@suse.de \
--cc=alan@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rossb@google.com \
/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