From: Jens Axboe <axboe@suse.de>
To: Carl Ritson <critson@perlfu.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS: 2.5.1-pre8 - cdrecord + ide_scsi
Date: Wed, 12 Dec 2001 10:38:52 +0100 [thread overview]
Message-ID: <20011212093852.GB13498@suse.de> (raw)
In-Reply-To: <20011211142831.GV13498@suse.de> <Pine.LNX.4.33.0112120754240.1679-100000@eden.lincnet>
In-Reply-To: <Pine.LNX.4.33.0112120754240.1679-100000@eden.lincnet>
On Wed, Dec 12 2001, Carl Ritson wrote:
> On Tue, 11 Dec 2001, Jens Axboe wrote:
>
> > On Sun, Dec 09 2001, Jens Axboe wrote:
> > > > Ok works with DMA off, so I expect that this new error is due to my resent
> > > > memory upgrade (36 Hours ago) and the switch to using HIGHMEM(4GB)..
> > > > So am I to believe that DMA is a problem with HIGHMEM(4GB) enabled ?
> > >
> > > No it's probably still an ide-scsi bug, I'm not suspecting your
> > > hardware. The reason I ask is because until -pre8 (since bio merge in
> > > -pre2), ide-scsi never used DMA even though it was set for the drive.
> >
> > Ok finally had a chance to look some more at this -- it was a bit more
> > hairy than I had hoped. Please try this ide-scsi one liner, it should
> > cure it. (the bug fix is the bio->bi_vcnt = 1 change only)
> >
> >
> This Patch appears to work fine. Tested with DMA on and DMA off, no
> Errors.. :)
Super, thanks for testing.
--
Jens Axboe
next prev parent reply other threads:[~2001-12-12 9:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 9:26 OOPS: 2.5.1-pre8 - cdrecord + ide_scsi Carl Ritson
2001-12-09 10:22 ` Jens Axboe
2001-12-09 10:31 ` Jens Axboe
2001-12-09 13:52 ` Carl Ritson
2001-12-09 13:58 ` Jens Axboe
2001-12-09 15:35 ` Carl Ritson
2001-12-09 15:38 ` Jens Axboe
2001-12-11 14:28 ` Jens Axboe
2001-12-12 8:02 ` Carl Ritson
2001-12-12 9:38 ` Jens Axboe [this message]
2001-12-15 0:06 ` Andre Hedrick
2001-12-15 10:13 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2001-12-15 15:03 Thomas Hood
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=20011212093852.GB13498@suse.de \
--to=axboe@suse.de \
--cc=critson@perlfu.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.