From: Jens Axboe <axboe@suse.de>
To: Paul <set@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [Oops] 2.5.45-mcp2 BUG at mm/highmem.c
Date: Mon, 4 Nov 2002 10:47:20 +0100 [thread overview]
Message-ID: <20021104094720.GG13587@suse.de> (raw)
In-Reply-To: <20021104045949.GG20069@squish.home.loc>
On Sun, Nov 03 2002, Paul wrote:
> Hi;
>
> Testing on a system that was LVM1 based. One oops from a
> gcc3.2 compiled kernel, the other from a gcc2.95.3 compiled
> kernel. (I wish it was vanilla, but it doesnt compile with device
> mapper, needed -mcp2) [compilation failure posted by others]
> [using latest device mapper and LVM2 tools from sistina]
> hda and hdc, who both work with DMA under 2.4.19,
It's a generic kernel bug exposed by the device mapper. Well actually
it's a trigger I put in long ago, blk_queue_bounce() needs a few fixes
before bouncing a cloned bio works. I'll see if I can't get that done
today.
--
Jens Axboe
prev parent reply other threads:[~2002-11-04 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 4:59 [Oops] 2.5.45-mcp2 BUG at mm/highmem.c Paul
2002-11-04 9:47 ` Jens Axboe [this message]
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=20021104094720.GG13587@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=set@pobox.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